Tarantool development patches archive
 help / color / mirror / Atom feed
From: Konstantin Osipov <kostja@tarantool.org>
To: tarantool-patches@freelists.org
Cc: georgy@tarantool.org
Subject: [tarantool-patches] Re: [PATCH] Output of fiber.info will contain only non-idle fibers
Date: Wed, 24 Jul 2019 18:11:48 +0300	[thread overview]
Message-ID: <20190724151148.GB31283@atlas> (raw)
In-Reply-To: <20190724080009.l37vvopimxjdqs5h@tarantool.org>

* Kirill Yukhin <kyukhin@tarantool.org> [19/07/24 11:03]:

> > * Maria K <marianneliash@gmail.com> [19/07/23 21:01]:
> > > The output used to be too cluttered due to idle ones.
> > > 
> > > Closes #4235
> > 
> > @kyukhin, first, please I don't get how does this get scheduled to a
> > milestone? How does this follow triage guidelines? 
> 
> I won't ever discuss any internal documents publicly, sorry.
> I believe this contradicts ethitcs. That is second time you doing
> this, please stop.

Well, I guess then it is time to make  SOP public.

How do you expect me to participate in it as a community member if
I don't share how the project is run and direction it takes? 

I've been mentioning this before -- things will have to become more
open, including defining the product roadmap and what features get
in, if we're to switch to a community driven model.

You can't expect one contributor party to drive the roadmap and
another merely do the review work.

> 
> > Please don't schedule anything that is not a priority, even if
> > it's a noob issue, since it takes time of everyone involved.
> 
> That was a customer request. If you'd like not to review the patch -
> feel free to just skip it, we'll find another reviewer.

Well, then it has to be well defined- I pointed out obvious
issues with this change. 

PS And no, TTLing reviews is also a wrong idea. One or two bad
patches getting in like that and it will be easier for me to fork
and cherry-pick changes than provide any reviews and work on a
common trunk.

-- 
Konstantin Osipov, Moscow, Russia

  reply	other threads:[~2019-07-24 15:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-23 18:00 [tarantool-patches] " Maria K
2019-07-23 19:56 ` [tarantool-patches] " Konstantin Osipov
2019-07-24  8:00   ` Kirill Yukhin
2019-07-24 15:11     ` Konstantin Osipov [this message]
2019-07-25  6:14   ` Георгий Кириченко
2019-07-25  9:26     ` Konstantin Osipov
2019-07-25 13:02       ` Георгий Кириченко

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190724151148.GB31283@atlas \
    --to=kostja@tarantool.org \
    --cc=georgy@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='[tarantool-patches] Re: [PATCH] Output of fiber.info will contain only non-idle fibers' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox