17 Feb
2012
17 Feb
'12
11:47 a.m.
Aaah ... I think i get it. Tim isn't some kind of advanced bot/cyborg
technology, and he has a life!
I think it is good on one hand that Trinity has '*the right person*'
controlling the patches. This ensures a type of quality control. On the
other hand, i have seen many one man shows come to a sudden halt. If Tim
were to face plant into his keyboard we would become one such project.
I agree a couple more people (read: not ronin) are needed to push patches
and this should be done on a majority vote (more than one in this case).
*which could has a purpose such as having a repo that always builds on
Slackware ;)*
I like this guy/gal !!
Jay
On Fri, Feb 17, 2012 at 5:59 AM, Timothy Pearson <
kb9vqf(a)pearsoncomputing.net> wrote:
should
Serghei also has commit access. I have been waiting
to
merge patches
until I can build test the packages, but with recent changes
I am waiting
on an archive rebuild for Ubuntu.
Ok, so you are waiting to start that big wooshing sound. Fair enough. :)
But that does not address the core concern: what happens to Trinity you become unavailable for a long period or
forever?
Additionally, Serghei is another sharp person but is fairly busy too. His
commit access does not change the picture of either of you being too busy
to keep patches merging, especially build related patches.
Of the non build related patches, many are small and don't need a rocket
scientist to decide that merging probably is safe. Should there be others
with commit access?
Darrell
Probably. I can't enforce it with technical means, but I suppose we could
use the Etherpad to review patches and if two or more non-core devs agree
that the patch looks sane (and doesn't remove functionality, etc.) the
patch could be pushed.
That leaves the question of who to grant access to. You and Calvin are
two that come to mind, but I would need poeple to agree that they won't
"go rogue" and just start pushing unreviewed patches. ;-)
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messages on the web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting