savannah-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-cvs] [152] english


From: karl
Subject: [Savannah-cvs] [152] english
Date: Fri, 13 Mar 2015 00:22:22 +0000

Revision: 152
          
http://svn.sv.gnu.org/viewvc/?view=rev&root=administration&revision=152
Author:   karl
Date:     2015-03-13 00:22:16 +0000 (Fri, 13 Mar 2015)
Log Message:
-----------
english

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

Modified: trunk/sviki/DownloadArea.mdwn
===================================================================
--- trunk/sviki/DownloadArea.mdwn       2015-03-12 21:53:31 UTC (rev 151)
+++ trunk/sviki/DownloadArea.mdwn       2015-03-13 00:22:16 UTC (rev 152)
@@ -123,5 +123,5 @@
 add contact information to `/root/administration/mirrors-contacts.txt`;
 2) on dl.sv.gnu.org, add the mirror url(s) to 2a)
 `/srv/download/00_MIRRORS.html` (alphabetical, check
-<http://download.savannah.gnu.org/releases-noredirect/00_MIRRORS.html>)
-and 2b) `
+<http:///download.savannah.gnu.org/releases-noredirect/00_MIRRORS.html>)
+and 2b) `/srv/download/00_MIRRORS.txt` (no order).

Modified: trunk/sviki/HowToBecomeASavannahHacker.mdwn
===================================================================
--- trunk/sviki/HowToBecomeASavannahHacker.mdwn 2015-03-12 21:53:31 UTC (rev 
151)
+++ trunk/sviki/HowToBecomeASavannahHacker.mdwn 2015-03-13 00:22:16 UTC (rev 
152)
@@ -1,5 +1,5 @@
 Contributing to Savannah
-------------------------
+========================
 
 We need volunteers and look forward to your participation. This page is
 about becoming a savannah hacker (e.g., a savannah website
@@ -14,9 +14,10 @@
 5. Improve this wiki.
 6. Develop new features for the savannah environment.
 
-Some of these tasks require administrator-level access to the website and
-the servers (see [[ShellAccess]]). Others can be done by anyone willing to
-help. A good starting point is helping with project evaluation (see below).
+A good starting point is helping with project evaluation (see below).
+Some tasks require administrator-level access to the website and the
+servers (see [[ShellAccess]]). Others can be done by anyone willing to
+help.
 
 Send your evaluation/contribution/patch to
 <address@hidden>. Please also include a bit about your
@@ -28,34 +29,36 @@
 left-hand menu.  Then you can approve projects and do many other things
 through the web interface.  Please explore.
 
-communication
+Communication
 -------------
 
 For communication with other savannah folks, see
 [[SavannahHackersCommunication]], which includes info on mailing lists
-you should use/subscribe to.
+you should subscribe to and use.
 
 Read the [[CodeOfConduct]] to understand how to communicate with our
 users with politeness.
 
-project evaluation and approval
+Project evaluation and approval
 -------------------------------
 
 To be hosted on savannah, projects must comply with the hosting
 requirements: <http://savannah.gnu.org/register/requirements.php>.
 
 Savannah volunteers evalute only non-gnu projects (gnu projects are
-evalutated by the gnu evalution team).
+evaluated by the gnu evalution team).
 
-You can help with project evaluation even before becoming savannah
-administrator.
+You can help with project evaluation before becoming a savannah
+administrator; indeed, we recommend doing this as a first step for
+anyone who wants to help savannah.
 
 Read [[HowToGetYourProjectApprovedQuickly]], which explains in detail
 what a submitter should check, but also serves as a guide for savannah
-hackers reviewing the project. See also Mario's [guide for reviewing
+hackers reviewing the project.  See also Mario's [guide for reviewing
 
projects](http://lists.gnu.org/archive/html/savannah-hackers-public/2010-08/msg00026.html).
 You can also read past submissions (and responses) on the
-[Savannah-Register-Public](http://lists.gnu.org/archive/html/savannah-register-public/)
 mailing list.
+[Savannah-Register-Public](http://lists.gnu.org/archive/html/savannah-register-public/)
+mailing list.
 
 Pick a pending (non-assigned) task in savannah's task list:
 <https://savannah.gnu.org/task/?group=administration>
@@ -76,9 +79,9 @@
 possible.
 
 An attempt to automate some of the evaluation process is in beta at
-<http://gnueval.housegordon.org>. Contributions and improvements to this
-project are very welcomed (see
-[source code](http://git.housegordon.org/cgit/gsv-eval.git/)).
+<http://gnueval.housegordon.org>.  Contributions and improvements to
+this project are very welcomed (see [source
+code](http://git.housegordon.org/cgit/gsv-eval.git/)).
 
 Helping savannah users
 ----------------------
@@ -112,14 +115,14 @@
 [[SavannahInternals]], [[UserAuthentication]], [[GnuArchitecture]] pages.
 
 
-Working on Savannah website
----------------------------
+Working on the Savannah website
+-------------------------------
 
-The savannah website <http://savannah.gnu.org> is written mostly in PHP with
-MySQL database and some Perl scripts. An overview is available at
-[[SavannahInternals]]. The PHP code (with a stub database) can be run and
-developed locally, without administrator access.
-see [[RunningSavaneLocally]] and [[SavaneInABox]].
+The savannah website <http://savannah.gnu.org> is written mostly in PHP
+with a MySQL database backend and some Perl scripts.  An overview is
+available at [[SavannahInternals]].  The PHP code (with a stub database)
+can be run and developed locally, without administrator access.  see
+[[RunningSavaneLocally]] and [[SavaneInABox]].
 
 You are encouraged to hack on the frontend code! Either adding new features,
 improving the code, or fixing bugs. See open [support
@@ -133,31 +136,31 @@
 to work on a new feature, be sure to discuss it at
 <mailto:address@hidden>.
 
-
 Improving this Wiki
 -------------------
 
-The savannah wiki pages could always be improved. You can help without
+The savannah wiki pages can always be improved. You can help without
 being a savannah administrator. See 'Running this wiki locally' section
 at [[HowToAdminThisWiki]]. Add your improvements, and send a patch to
 <mailto:address@hidden>.
 
-The list of all pages is at the [[FrontPage]].
+The list of all pages is on the [[FrontPage]].
 
 Few suggestions for wiki improvements:
 
-1. Running parts of savannah locally (e.g. [[RunningSavaneLocally]],
+0. Running parts of savannah locally (e.g., [[RunningSavaneLocally]],
     [[SavaneInABox]]) - testing, verifying and improving the
     instructions.
-2. FrontEnd documentation - (e.g.[[SavannahInternals]]) - improving and
+0. FrontEnd documentation - (e.g., [[SavannahInternals]]) - improving and
     expanding this page, or creaeting a new page focused on the php code.
-3. DebBugs documentation - The GNU DebBugs server <http://debbugs.gnu.org>
+
+0. DebBugs documentation - The GNU DebBugs server <http://debbugs.gnu.org>
     uses a customized version of [DebBugs](https://wiki.debian.org/BTS).
-    It will be *very* beneficial to document the installation, configuration,
+    It would be very beneficial to document the installation, configuration,
     and perhaps even instructions on how to setup such a server locally.
     Gathering this information will require not only tinkering with the
     [debbugs source code](https://wiki.debian.org/Teams/Debbugs) but also
-    soliciting help and advise from other volunteers. Be sure to be polite
+    soliciting help and advice from other volunteers. Be sure to be polite
     and patient with them. See
     <http://lists.gnu.org/archive/html/help-debbugs/2015-01/msg00003.html>.
 
@@ -165,8 +168,7 @@
 Developing new features
 -----------------------
 
-New features are welcomed! Do send ideas and patches.
+New features are welcomed! Do send ideas (and patches) to
+<mailto:address@hidden>.
 
-Send suggestions and patches to <mailto:address@hidden>.
-
 See [[SavannahHackingIdeas]] for possible starting points.

Modified: trunk/sviki/SavannahHackingIdeas.mdwn
===================================================================
--- trunk/sviki/SavannahHackingIdeas.mdwn       2015-03-12 21:53:31 UTC (rev 
151)
+++ trunk/sviki/SavannahHackingIdeas.mdwn       2015-03-13 00:22:16 UTC (rev 
152)
@@ -1,10 +1,10 @@
 Developing new features
------------------------
+=======================
 
-(the following section lists my opinions
+(the following lists my opinions
 ([assaf's](https://savannah.gnu.org/u/agn)), based on personal experience,
 and is not official savannah views, wish-lists or future plans. There is no
-guarentee any of the listed ideas will ever be accepted or implemented,
+guarantee any of the listed ideas will ever be accepted or implemented,
 or even considered worth-while.)
 
 New features are welcomed! Do send ideas and patches.
@@ -67,12 +67,12 @@
     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,
-    while keeping it in line current priorities and values (no JS, no tricky
+    while keeping it inline with GNU's priorities and values (no JS, no tricky
     CSS, viewable on non-graphic browsers, etc.).
-9. Develping 'sandbox' environments for web-pages updates, and for DebBug
+9. Developing 'sandbox' environments for web-pages updates, and for DebBug
     learning.
 10. Complement [GNU Hydra](https://savannah.gnu.org/projects/hydra-recipes/),
-    with continious-integration/testing on multiple POSIX platforms.
+    with continuous-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](http://jekyllrb.com)
@@ -92,7 +92,7 @@
     orchestrated by cronjobs periodically querying for database updates
     (see [[SavannahInternals]]). Explore other methods (e.g. queues?).
 17. Create development/testing envrionments replicating the production one,
-    enabling faster developments (perhaps access to non-administrators).
+    enabling faster development (perhaps access to non-administrators).
 18. Importing and Exporting trackers items (bugs/support/tasks).
     Perhaps a conversion tool from 'trackers' to MBOX format compatible
     with DebBugs (i.e. work towards migrating all trackers to DebBugs?).




reply via email to

[Prev in Thread] Current Thread [Next in Thread]