[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-cvs] [637] review, drop obsolete bits
From: |
ineiev |
Subject: |
[Savannah-cvs] [637] review, drop obsolete bits |
Date: |
Thu, 27 Jul 2023 03:37:22 -0400 (EDT) |
Revision: 637
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=637
Author: ineiev
Date: 2023-07-27 03:37:21 -0400 (Thu, 27 Jul 2023)
Log Message:
-----------
review, drop obsolete bits
Modified Paths:
--------------
trunk/sviki/HowToBecomeASavannahHacker.mdwn
Modified: trunk/sviki/HowToBecomeASavannahHacker.mdwn
===================================================================
--- trunk/sviki/HowToBecomeASavannahHacker.mdwn 2023-06-23 08:24:39 UTC (rev
636)
+++ trunk/sviki/HowToBecomeASavannahHacker.mdwn 2023-07-27 07:37:21 UTC (rev
637)
@@ -1,38 +1,38 @@
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
-administrator) and help savannah.
+We need volunteers and look forward to your participation. This page
+is about becoming a Savannah hacker (e.g., a Savannah website
+administrator) and helping Savannah.
-Examples of tasks done by savannah volunteers:
+Examples of tasks done by Savannah volunteers:
-1. Evaluate and approve non-gnu projects submitted for hosting.
-2. Help savannah users, whether with questions or support issues.
-3. Administer the savannah servers and services.
-4. Improve the savannah web frontend code.
+1. Evaluate and approve non-gnu packages submitted for hosting.
+2. Help Savannah users, whether with questions or support issues.
+3. Administer the Savannah servers and services.
+4. Improve the Savannah web frontend code.
5. Improve this wiki.
-6. Develop new features for the savannah environment.
+6. Develop new features for the Savannah environment.
-A good starting point is helping with project evaluation (see below).
+A good starting point is helping with package 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
+servers (see [[ShellAccess]]). Others can be done by anyone willing to
help.
-Send your evaluation/contribution/patch to
-<savannah-hackers-public@gnu.org>. Please also include a bit about your
-background with free software, GNU, Savannah, or whatever else may
-be relevant. And your savannah account name.
+You can send your contributions to <savannah-hackers-public@gnu.org>.
+Please also include a bit about your background with free software,
+GNU, Savannah, or whatever else may be relevant. And your Savannah
+account name.
When accepted, you will be made an administrator of the administration
-project, which will enable the "Become Superuser" option in the
-left-hand menu. Then you can approve projects and do many other things
-through the web interface. Please explore.
+group, which will enable the "Become Superuser" option in the
+left-hand menu. Then you can approve new packages for hosting and
+do many other things through the web interface. Please explore.
Communication
-------------
-For communication with other savannah folks, see
+For communication with other Savannah folks, see
[[SavannahHackersCommunication]], which includes info on mailing lists
you should subscribe to and use.
@@ -39,73 +39,60 @@
Read the [[CodeOfConduct]] to understand how to communicate with our
users with politeness.
-Project evaluation and approval
+Package evaluation and approval
-------------------------------
-To be hosted on savannah, projects must comply with the hosting
-requirements: <http://savannah.gnu.org/register/requirements.php>.
+To be hosted on Savannah, software must comply with our [hosting
+requirements](http://savannah.gnu.org/register/requirements.php).
-Savannah volunteers evalute only non-gnu projects (gnu projects are
+Savannah volunteers evalute only non-gnu groups (gnu packages are
evaluated by the gnu evalution team).
-You can help with project evaluation before becoming a savannah
+You can help with package evaluation before becoming a Savannah
administrator; indeed, we recommend doing this as a first step for
-anyone who wants to help savannah.
+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
-projects](http://lists.gnu.org/archive/html/savannah-hackers-public/2010-08/msg00026.html).
+what a submitter should check, but also serves as a guide for Savannah
+hackers reviewing the package. See also Mario's [guide for reviewing
+software](https://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/)
+[Savannah-Register-Public](https://lists.gnu.org/archive/html/savannah-register-public/)
mailing list.
-Pick a pending (non-assigned) task in savannah's task list:
+Pick a pending unassigned task in administration task list:
<https://savannah.gnu.org/task/?group=administration>
-Read it, then write the answer that you would make as the savannah
+Read it, then write the answer that you would make as the Savannah
reviewer.
-If you wish, you can use the savannah hackers' macros file for emacs or
-vim (savannah.[el|vim]) to help in writing your answer. It is good
-information to know in any case. See:
-
- git clone git://git.savannah.gnu.org/administration.git
- ls administration/approvals/
-
When your answer is ready, send it (with a link to the task) at
<mailto:savannah-hackers-public@gnu.org>
-and one of the current savannah hackers will answer as quickly as
+and one of the current Savannah hackers will answer as quickly as
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/)).
-
-Helping savannah users
+Helping Savannah users
----------------------
See the
[Savannah Support
Tracker](http://savannah.gnu.org/support/?group=administration)
and the
-[Savannah-users mailing
list](http://lists.gnu.org/archive/html/savannah-users/)
-for examples of user questions and requests. Many of these items require
-administrator access to savannah servers, but some are general usage
+[Savannah-users mailing
list](https://lists.gnu.org/archive/html/savannah-users/)
+for examples of user questions and requests. Many of these items require
+administrator access to Savannah servers, but some are general usage
questions, and others deal with bugs in the website frontend code - those
-can be handled locally (see 'working on savannah website' below).
+can be handled locally (see 'working on Savannah website' below).
-
Working on Savannah internals
-----------------------------
The above is about helping as a Savannah administrator via the web
-interface. If you are willing and able to hack on the Savannah (Savane)
+interface. If you are willing and able to hack on the Savannah (Savane)
implementation itself, at the shell/sysadmin level, please essentially
do the same as the above with one of the open [support
requests](http://savannah.gnu.org/support/?group=administration).
-The active source code is in the "administration" project (using several
+The active source code is in the "administration" group (using several
of the VC systems). [[SavaneRewrite]] has a bit more history.
When accepted, some info about getting in at the shell level is at
@@ -114,11 +101,10 @@
For general information, read the [[SavannahServices]],
[[SavannahInternals]], [[UserAuthentication]], [[GnuArchitecture]] pages.
-
Working on the Savannah website
-------------------------------
-The savannah website <http://savannah.gnu.org> is written mostly in PHP
+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
@@ -135,20 +121,20 @@
Improving this Wiki
-------------------
-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
+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:savannah-hackers-public@gnu.org>.
The list of all pages is on the [[FrontPage]].
-Few suggestions for wiki improvements:
+Suggestions for wiki improvements:
-0. Running parts of savannah locally
+0. Running parts of Savannah locally
(e.g., [[RunningSavaneLocally]]) - testing, verifying and improving
the instructions.
0. FrontEnd documentation - (e.g., [[SavannahInternals]]) - improving and
- expanding this page, or creaeting a new page focused on the php code.
+ expanding this page, or creating a new page focused on the PHP code.
0. DebBugs documentation - The GNU DebBugs server <http://debbugs.gnu.org>
uses a customized version of [DebBugs](https://wiki.debian.org/BTS).
@@ -156,15 +142,14 @@
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 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>.
+ soliciting help and advice from other volunteers. Be sure to be polite
+ and patient with them. See
+ <https://lists.gnu.org/archive/html/help-debbugs/2015-01/msg00003.html>.
-
Developing new features
-----------------------
-New features are welcomed! Do send ideas (and patches) to
+New features are welcome! Do send ideas (and patches) to
<mailto:savannah-hackers-public@gnu.org>.
See [[SavannahHackingIdeas]] for possible starting points.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Savannah-cvs] [637] review, drop obsolete bits,
ineiev <=