Port maintainer newbie (was: [#22529] No response on ticket for netatalk Port update/fix)
Ryan Schmidt
ryandesign at macports.org
Thu Nov 19 10:25:31 PST 2009
On Nov 19, 2009, at 11:46, Ralph Böhme wrote:
>> Being the maintainer of a port means you are responsible for updating it in ways you see fit, and that tickets filed about the port will be assigned to you for resolution. In the absence of commit access, you supply your desired changes as patches in the issue tracker, which a committer will review and commit.
>>
>> Commit access is separate, and the prerequisites for granting it are a history of involvement in the project. So I recommend you contribute patches and updates to your port and other ports (by filing tickets), volunteer to maintain additional ports if possible, and contribute on these mailing lists, and after a time, if you wish, then apply for commit access.
>>
>> http://guide.macports.org/chunked/project.membership.html
>
> Ok, thanks! That way it's more time consuming for me but I see the necessity for some control on who can commit.
It is more time consuming, and I apologize for that inconvenience, but there are many nuances of Portfile writing that aren't always apparent at first glance. Submitting your proposals as diffs attached to tickets lets more experienced Portfile writers review your changes and suggest improvements or point out issues you may not have considered (or even known to consider). I have a few feedback items for you regarding the change from #22529 that I'll write up a little later. But once your patches are generally getting committed without changes, we'd be happy to have you as a committer.
More information about the macports-dev
mailing list