[Savannah-cvs] [149] SavannahHackingIdeas - minor fixes

[Assaf Gordon]

Revision: 149
          
http://svn.sv.gnu.org/viewvc/?view=rev&root=administration&revision=149
Author:   agn
Date:     2015-03-12 06:01:59 +0000 (Thu, 12 Mar 2015)
Log Message:
-----------
SavannahHackingIdeas - minor fixes

Modified Paths:
--------------
    trunk/sviki/SavannahHackingIdeas.mdwn

Modified: trunk/sviki/SavannahHackingIdeas.mdwn
===================================================================
--- trunk/sviki/SavannahHackingIdeas.mdwn       2015-03-12 05:52:49 UTC (rev 
148)
+++ trunk/sviki/SavannahHackingIdeas.mdwn       2015-03-12 06:01:59 UTC (rev 
149)
@@ -43,8 +43,9 @@
     projects - thus, a webinterface could simply be a wrapper around sending
     an email from the savannah user.
 3. Running savannah services locally. Not only the web-frontend (See
-    'Working on Savannah website' section above), but all the different
-    savannah hosts. Documentating how to configure then locally, and/or set
+    'Working on Savannah website' in [[HowToBecomeASavannahHacker]]),
+    but all the different savannah hosts.
+    Documentating how to configure then locally, and/or set
     them up from scratch will help future administrators and contributors.
     Especially: setting up a 'sandbox' environment for DebBugs.
 4. Migrating the web-pages of hosted projects from CVS to Git. See more
@@ -62,7 +63,7 @@
 7. Phase-out the PHP-based trackers (the bugs/support/tasks interface) -
     either in favor of the current bug-tracker (DebBugs), or evaluate other
     possible solutions (BugZilla/Mantis/RequestTracker/Fossil/Others).
-    This must include a way to perseve access to existing items (with the
+    This must include a way to preserve access to existing items (with the
     exact current URL). See
     
<http://lists.gnu.org/archive/html/savannah-hackers-public/2011-09/msg00000.html>
 8. Redesign/improve the web interface, make it prettier and more accessible,
@@ -74,8 +75,8 @@
     with continious-integration/testing on multiple POSIX platforms.
     perhaps using [pretest](http://pretest.gnu.org) (disclaimer: that's
     a project I develop). Integrate with Savannah or GNU projects.
-11. Per-project Wiki, perhaps using 'Jekyll' (need to verify savannah-policy
-    related issues with this).
+11. Per-project Wiki, perhaps using [Jekyll](http://jekyllrb.com)
+    (need to verify savannah-policy related issues with this).
 12. Provide a Free-as-in-freedom build environment (or instructions to
     create such build environment) for Windows and Mac OS X platforms.
     See <http://lilypond.org/gub/>.
@@ -84,3 +85,6 @@
 14. Explore allowing non-fast-forward commits on non-master branches,
     both from technical POV and from Savannah-policy POV.
     See: 
<http://lists.gnu.org/archive/html/savannah-hackers-public/2015-01/msg00011.html>
+15. Provide source-code browsing interface, integrate with GNU projects
+    (using [GNU Global](http://www.gnu.org/software/global/) or
+    [OpenGrok](http://opengrok.github.io/OpenGrok/) or other).