From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: grub-devel@gnu.org, 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>
Subject: Re: Development practices?
Date: Tue, 8 Sep 2015 13:57:02 -0400 [thread overview]
Message-ID: <20150908175702.GA20019@l.oracle.com> (raw)
In-Reply-To: <20150903193429.GA19514@l.oracle.com>
On Thu, Sep 03, 2015 at 03:34:29PM -0400, Konrad Rzeszutek Wilk wrote:
> Hey,
Expanding the circle, including folks on the To list.
Colin had answered some so snipping thouse out.
>
> I've noticed a couple of things that the community seems
> to be doing different than other open source projects and
> was wondering why? And also how to conform to this (or perhaps
> it is time to change?) so that ideas/releases/patches can move forward.
>
.. snip..
>
> - Some patches have been posted and hadn't much any architecture
> feedback or review. I am referring to Daniel's multboot2
> extensions and the ARM multiboot implementation for example.
>
> Is that due to the tradition (not sure if that is the right
> word) that there aren't enough reviewers so folks shouldn't
> expect reviews?
>
.. snip..
>
>
> I don't know enough about the community (or the history) to
> understand it but would very much appreciate input.
> And if I have offended somebody with my questions + feeble
> analysis: my deepest apologies - and please straighten me out!
>
>
> 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?
>
> [*1]: My background is in Linux kernel and Xen Project.
next prev parent reply other threads:[~2015-09-08 17:57 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 [this message]
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
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=20150908175702.GA20019@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.