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".
Anyone with commit access to the git.thrift-rpc.org repository
("contributor") can post a patch to Git. Anyone (Git user or otherwise)
can evaluate these changes via Git or web interfaces. Any committer
(preferably one who uses Git) can commit these changes to the SVN
repository (git svn dcommit).
> 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.
If anyone ever does this, I will personally punch them in the face.
Okay, that is not true. Chad and I have been doing this a little bit
with the templates branch, BUT (1) it is in the public repository, (2)
we announced our intentions and our branch names so that anyone could
follow the development, and (3) we will absolutely submit this branch
for a thorough public review before we try to commit to trunk.
> Is that unfounded? 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.
Terminology is fine. It is absolutely possible to set this up.
Upayavira told us that he didn't think these should go to the -dev list
because it is an unnofficial repo. I've been working on setting up my
own listserve on thrift-rpc.org, but all the emails get marked as spam
by Gmail and I haven't been able to figure out why.
Another option would be for users to subscribe to the Thrift repo on
GitHub. However (and I forgot to mention this in my response to Luke),
I would prefer if our development process was not dependent on
proprietary technology. (For the record, I agreed to use JIRA before I
knew it was closed-source.)
--David
