[MacPorts] NewCommittersGuide modified

[MacPorts]

Changed page "NewCommittersGuide" by raimue at macports.org from 91.11.238.40*
Page URL: <http://trac.macports.org/wiki/NewCommittersGuide>
Diff URL: <http://trac.macports.org/wiki/NewCommittersGuide?action=diff&version=16>
Revision 16

-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: NewCommittersGuide
=========================================================================
--- NewCommittersGuide (version: 15)
+++ NewCommittersGuide (version: 16)
@@ -4,7 +4,7 @@
 
 == Port Committer Responsibilities ==
 
- 1. PortIndex is now updated automatically (every 12 hours) so it must not be touched
+ 1. PortIndex is now updated automatically (every hour) so it must not be touched
  1. A commit affects one port (including however many files are required for that one port)
  1. The exception to the one port/one commit rule is where several Portfiles make use of some feature which is in need of updating
    1. Due to a new feature which has been added to the current release to fix hacks used by various Portfiles
@@ -12,14 +12,16 @@
    1. You need to change your email address for your ports
    1. Other, similar reasons
  1. All committers must subscribe to the [http://lists.macosforge.org/mailman/listinfo/macports-changes macports-changes] list under their MacPorts credentials to keep track of current changes and because the list is subscriber-post-only, so commit messages will otherwise be rejected
- 1. New top-level categories (those which are represented by subdirectories directly beneath dports/) need to be approved prior to adding; secondary categories (the second and later ones listed on the '''categories''' Portfile key) can be added when it makes sense (since these really only show under the web interface, and have no filesystem representation)
+ 1. New top-level categories (those which are represented by subdirectories directly beneath dports/) need to be approved prior to adding; secondary categories (the second and later ones listed on the '''categories''' Portfile key) can be added when it makes sense (since these really only show under the web interface, and do not necessarily have a filesystem representation)
  1. Make sure the port name matches between the MacPorts svn directory name and the '''name''' Portfile key (while the system works fine when they don't, keeping them synchronized avoids confusing situations)
+ 1. Run `port lint` before committing to be sure not to violate one of the guidelines
  1. Should commit logs finally be standardized?  The output is shown in various places and forms: trac, RSS, email, [http://cia.vc/ CIA] stuff; some of these may just use the first line
  1. Under most circumstances, do not modify a port belonging to another maintainer; this is to be done either via a Trac ticket or by direct communication with the maintainer.  Exceptions are:
    1. When a port is broken (and the update should be just to fix the port, no other updates "while you're there")
    1. When ''nomaintainer at macports.org'' is the maintainer; this really means the port is unowned (feel free to take it over)
    1. When ''openmaintainer at macports.org'' is co-maintainer; this signifies that the primary maintainer has no prior objections to others changing it
    1. When the maintainer says the update is okay and asks you to commit your update; in this case, be sure to note in the commit message that it was '''Approved by:''' the maintainer (see the bit about commit log entries above)
+   1. When a ticket was already filed and you making use of the [http://guide.macports.org/#project.update-policies.nonmaintainer maintainer timeout], note this fact in your commit message and add the ticket id for reference.
  1. Set up automatic properties for Subversion, as described on the [wiki:CommittersTipsAndTricks#SetsvnpropertiesautomaticallyonnewPortfiles Committers Tips and Tricks] wiki page.
 
 == Mailing Lists and Change Logs ==

-------8<------8<------8<------8<------8<------8<------8<------8<--------

* The IP shown here might not mean anything if the user or the server is
behind a proxy.

--
MacPorts <http://www.macports.org/>
Ports system for Mac OS

This is an automated message. Someone at http://www.macports.org/ added your email
address to be notified of changes on NewCommittersGuide. If it was not you, please
report to .