From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andrei Borzenkov <arvidjaar@gmail.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
Vladimir Serbinenko <phcoder@gmail.com>,
Felix Zielcke <fzielcke@z-51.de>,
Paulo Flabiano Smorigo <pfsmorigo@linux.vnet.ibm.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Development practices?
Date: Tue, 22 Sep 2015 14:28:00 -0400 [thread overview]
Message-ID: <20150922182800.GA14331@l.oracle.com> (raw)
In-Reply-To: <20150911153453.GB21981@l.oracle.com>
On Fri, Sep 11, 2015 at 11:34:53AM -0400, Konrad Rzeszutek Wilk wrote:
> .. snip..
> > >>>>> From what I have gathered so far the not enough reviewers
> > >>>>>is tied in folks being overworked - so there simply was no
> > >>>>>point of posting on the mailing list as nobody had the time
> > >>>>>to review it or test it properly?
> > >>>>>
> > >>>
> > >>>Hi Konrad,
> > >>>
> > >>>back in 2008/2009 (when Marco Gerards gave over Maintainance to Robert
> > >>>Millan) there were indeed not much people actively reviewing code.
> > >>>
> > >>>Active people on the mailing list was just given commit access. It was
> > >>>expected that they only commit stuff without posting which doesn't need
> > >>>a review and complies with the rules back at that time.
> > >>>
> > >>>Due to me missing a few years on the mailing list, I can't tell you
> > >>>unfortunately how it compares to today.
> > >>>
> > >>
> > >>Not much changes as far as I can tell.
> > >
> > >OK.
> > >
> > >What qualifies as needing an review? Personal preference by
> > >the patch author?
> > >
> >
> > I suppose, common sense. When I was given commit access, it was for
> > "committing after review" so I still sent all patches to the list. Then it
> > happened that Vladimir dropped off list for a long time and I tried to pick
> > up obvious bug fixes from list or bug tracker to keep things going.
> >
> > I would say, any non-trivial bug fix or feature change needs to be posted
> > first.
> >
> > I would love to have every patch posted and reviewed bug given current level
> > of activity it is simply unrealistic.
>
> I see. From my perspective we are paid to work on the hobbies (Xen, Linux, etc)
> so the activity level is high since we have 8 hours a day to focus on it
> (minus bug activities, lunch, etc).
>
> While GRUB2 is all volunteer with whatever time can be spared?
>
> What if the companies that employ the committers allowed one day a week
> to focus on GRUB2 review/maintaince/etc? Would that help?
>
> Or is it unrealistic to expect that from committers employer's?
>
ping?
> >
> > >Thank you for answering my questions!
> > >
> >
next prev parent reply other threads:[~2015-09-22 18:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 19:34 Development practices? Konrad Rzeszutek Wilk
2015-09-03 20:27 ` Colin Watson
2015-09-08 17:57 ` Konrad Rzeszutek Wilk
2015-09-09 17:47 ` Felix Zielcke
2015-09-11 14:34 ` Andrei Borzenkov
2015-09-11 14:48 ` Konrad Rzeszutek Wilk
2015-09-11 15:16 ` Andrei Borzenkov
2015-09-11 15:34 ` Konrad Rzeszutek Wilk
2015-09-22 18:28 ` Konrad Rzeszutek Wilk [this message]
2015-09-24 18:42 ` Felix Zielcke
2015-09-24 19:09 ` Andrei Borzenkov
2015-09-24 19:27 ` Konrad Rzeszutek Wilk
2015-09-29 17:16 ` Sun, Ning
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=20150922182800.GA14331@l.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=arvidjaar@gmail.com \
--cc=fzielcke@z-51.de \
--cc=grub-devel@gnu.org \
--cc=leif.lindholm@linaro.org \
--cc=pfsmorigo@linux.vnet.ibm.com \
--cc=phcoder@gmail.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.