Changes between Version 24 and Version 25 of NewCommittersGuide

Timestamp:

Sep 11, 2012, 6:01:51 PM (12 years ago)

Author:

ryandesign (Ryan Carsten Schmidt)

Comment:

repository URL changed

NewCommittersGuide

@@ -33 +33 @@
 Notification of change logging is either via the [http://lists.macosforge.org/mailman/listinfo/macports-changes macports-changes] list or by subscribing to the RSS feeds provided by trac (see the RSS feeds of the [/projects/macports/timeline Timeline view] and the [/projects/macports/log/trunk Source Repository]). Note that you may customize the Timeline prior to subscribing to it, in order to control which types of information you are fed. In addition to getting an RSS feed of [wiki:TracTimeline general project events], you may also subscribe to changes to some [wiki:TracBrowser portion of the source tree] or to [wiki:TracQuery bug reports/tickets].
 
-If you use a newsreader such as [http://www.newsgator.com/NGOLProduct.aspx?ProdID=NetNewsWire NetNewsWire], and if you subscribe to the https version of the feed, you must ensure that you trust the certificate svn.macosforge.org from the certificate authority opensource.apple.com. You can tell Safari to "trust" this certificate when it sees it; you may need to set the trust settings for the certificate and/or authority from within Keychain access. Without these trust settings, NetNewsWire will not receive the feed. A better solution is to make sure that you subscribe to the http version of the feed (change the scheme on the URL to http from https).
+If you use a newsreader such as [http://www.newsgator.com/NGOLProduct.aspx?ProdID=NetNewsWire NetNewsWire], and if you subscribe to the https version of the feed, you must ensure that you trust the certificate svn.macports.org from the certificate authority opensource.apple.com. You can tell Safari to "trust" this certificate when it sees it; you may need to set the trust settings for the certificate and/or authority from within Keychain access. Without these trust settings, NetNewsWire will not receive the feed. A better solution is to make sure that you subscribe to the http version of the feed (change the scheme on the URL to http from https).
 
 == Checking out from subversion for committing ==