Should we cc: openmaintainer at macports.org in tickets?

[Blair Zajac]

On 09/05/2012 12:35 PM, Benoit T wrote:
> On Wed, Sep 05, 2012 at 08:39:37AM -0400, Jeremy Lavergne wrote:
>>> Section 7.1.3 of the MacPorts Guide says openmaintainer at macports.org must not be used in Assign to: but does not say anything for Cc: (which what non-committers have to use). What is the right thing to do?
>>
>> Don't use openmaintainer in any of the email-related forms. The person doesn't exist.
>
> Thanks, I have found the SpecialMaintainerAddresses page on the wiki so
> now I know what openmaintainer means.
>
> I submitted clarifications in the form of patches to sections 5 and 7 of
> the Guide.
>
> <troll>
> As a sidenote, and with all the admiration I have for the people of
> MacPorts for their invaluable contribution to the Mac OS community, in
> doing so I got a reality check on how much of a PITA subversion is for
> non-committers. I am not saying that everybody should be a committer,
> just that subversion is not the right tool when not everyone is.
>
> I don't see why I should spend more time chopping off the output of svn
> diff (that's not really a unified diff) and manually entering individual
> patches into Trac, than the time it took me to come up with the changes,
> when some other tools would have allowed me to just submit a single
> changeset that's also trivial to review and apply by the human being on
> the other side.
>
> Actually, even though I edited out the "Index:" lines of svn diff, Trac
> is smart enough to associate my diffs with the svn repo, so as to
> recreate those lines in the attachment viewer! So maybe I wasted my time
> turning those almost-unified-diffs into conforming unified diffs?
> Hopefully not, as patch -p0 would probably still have choked.
>
> And that's not even mentioning the fact that non-committers essentially
> get no version control benefits locally, and no incentive to split
> unrelated changes into separate changesets, save maybe for those brave
> enough to use yet another tool like quilt.
>
> So, in short, when is MacPorts switching to Mercurial or Git? :-)
> </troll>

That's a good idea.  We should look at moving svn into github and then 
we can have people push commits to their forks and submit pull requests. 
  If we do this, we should carve up the svn repo into separate git 
repos, such as one just for the ports themselves.

Blair