On Sun, Jan 12, 2014 at 04:10:05PM +0200, Mcgillion, Brian wrote:
Hi Jarkko,
The mailing list patch posting is a terrible idea, as we discussed
previously. Â As Ryan pointed out Intel is moving forward, github and
possible gerrit. Â Gerrit and git hub give proper traceability which is
lost in mailing lists, top posting and commenting on subsections and the
overall comments for a commit are lost because they are not inline. Â Many
old projects stick to their old ways because that is the established norm
for those projects, however many are moving forward.
I think you got it wrong here. Many projects stick to mailing list
because they work well and are easy to manage. You can even make
queries to past discussions and patch reviews while you are
offline. You cannot do that with Github and Gerrit. You don't have raw
access to your data. You have to use web interfaces to access it.
The approach of having four databases, two of which are partially
closed, does not sound feasible to me when I compare it to two fully
open databases (Git repository and mail archive). It sounds awfully
complicated.
Where have you came into conclusion that with mailing lists you lost
traceablity and how do comments get lost because they are not inline?
It's not hard to state line number in a reply. E-mail message have
these "References:" and "In-Reply-To:" fields defined in RFC 2822.
Github is still great for hosting Git repository, maintaining wiki and
reporting issues.
If you prefer cmd line integration that is your choice but the
rest of the
submitters should not have to suffer because of that choice. Â It is still
possible to do the cmd line integration ( 4 commands) using git hub as is
currently the established norm for this project.
I did not really get this part. Why using Git would be suffering for
contributors if they are already using Git?
/Jarkko