Ian Monroe wrote: >I could actually see individual projects picking up the "have the >maintainer pull from branches" method. But yea, we should support the >current development method, projects can switch to the pull method >when and if they want to. It doesn't even need to be enforced by >technical constraints: people already routinely submit patches to >projects they have svn commit access to.
I too see it happening for a few projects, especially Amarok and Plasma.
Those projects have a very core developer group and people wouldn't dare
pushing there without asking first. Even I ask first, before committing
today. And Plasma today is using the review board very nicely.
However, the use of ReviewBoard is orthogonal to the push access. Many
people submit patches and then someone says "Ship it". That means "please
commit this, it's fine", not "thanks, I'll commit it". Whether that may
change, I don't know.
However, for the large majority of projects, and especially kdelibs, this
will not work. We need multiple committers in kdelibs. And besides, we
need people like Dirk, David, some Trolls and me who routinely build
everything and go fixing issues. (This is also why need need a central
"make world" solution)
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
