On Jun 11, 2008, at 12:13 PM, Doug Cutting wrote:
Luke Lu wrote:
Subversion users can still use the old way, attaching patches to
jira and let one of the subversion "committers" apply and commit
the changes.
Git users would just publish their urls and ask the mailing list to
review the patch with better UI and then "maintainers" to pull
their changes.
The problem is that "maintainers" isn't a defined role at Apache.
We need to map this to "committers". The well-defined terms at
Apache are "contributor" and "committer".
Sure, I have no problem with these terms. "committer" would imply
write access to "official" repository.
I worry that folks will post changes to their private repos and that
other Git users might pull these changes without any on-list
traffic. Is that unfounded?
What's the problem with that? It enables high-bandwidth exchange
between Git collaborators. The code only needs be reviewed when they
are ready to be reviewed and pulled/merged into official repository.
Is it possible to configure Git so that whenever someone posts a
version of a change to their public repo that email is automatically
sent to the -dev list? (Forgive me if I'm massacring Git
terminology...) Something like that might go a long ways towards
addressing this concern.
I don't think it's necessary as they're non-official repositories, any
changes that need to go into official repository will have to go
through the list and the "commiters" anyway.
__Luke
