[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-cvs] administration/docs/hacking_savannah AUTHORS TO...
|
From: |
Sylvain Beucler |
|
Subject: |
[Savannah-cvs] administration/docs/hacking_savannah AUTHORS TO... |
|
Date: |
Fri, 15 Apr 2005 17:12:08 -0400 |
CVSROOT: /cvsroot/administration
Module name: administration
Branch:
Changes by: Sylvain Beucler <address@hidden> 05/04/15 21:12:08
Modified files:
docs/hacking_savannah: AUTHORS TODO hacking_savannah.texi
Log message:
Emptied the TODO and added some other fixes & additions.
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/administration/administration/docs/hacking_savannah/AUTHORS.diff?tr1=1.6&tr2=1.7&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/administration/administration/docs/hacking_savannah/TODO.diff?tr1=1.5&tr2=1.6&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/administration/administration/docs/hacking_savannah/hacking_savannah.texi.diff?tr1=1.104&tr2=1.105&r1=text&r2=text
Patches:
Index: administration/docs/hacking_savannah/AUTHORS
diff -u administration/docs/hacking_savannah/AUTHORS:1.6
administration/docs/hacking_savannah/AUTHORS:1.7
--- administration/docs/hacking_savannah/AUTHORS:1.6 Wed Apr 13 20:53:46 2005
+++ administration/docs/hacking_savannah/AUTHORS Fri Apr 15 21:12:08 2005
@@ -13,3 +13,6 @@
Node "Importing Repositories" is derived from the savannah.texi file
in the Savane distribution, written by Vincent Caron, Loïc Dachary and
Mathieu Roy.
+
+Node "Trademark logo" contains text originally written by Richard
+M. Stallman.
Index: administration/docs/hacking_savannah/TODO
diff -u administration/docs/hacking_savannah/TODO:1.5
administration/docs/hacking_savannah/TODO:1.6
--- administration/docs/hacking_savannah/TODO:1.5 Sun Feb 13 12:37:51 2005
+++ administration/docs/hacking_savannah/TODO Fri Apr 15 21:12:08 2005
@@ -1,93 +0,0 @@
-Various notes to add in hacking_savannah.texi:
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-If it doesn't have source code, you can't check the licensing issue (although
the automatic approval message will remind them about the GPL howto), but you
have to check the other criteria as much as possible. For example, I asked a
game project to resubmit their project with a description about planned
platforms and programming languages
-
-Beuc: it is totally necessary use a resubmit ?
-<Beuc> The goal is to keep a trace of why the project was approved. So whether
it is in the description, or in the archive, it doesn't matter. It is a problem
when the project wants to be GNU, because we usually forward the description
verbatim to GNU-Eval; it is also a problem when the description changed during
the approval process (in that case, it is better to resubmit to avoid confusion)
-
-If they guy just provides additional information, without
-contradicting the submitted description, I don't think it is worth
-resubmitting, but that's up to you :)
-
-<asubedi> hi
-<asubedi> Beuc: can you tell me steps to expire projects :)
-<Beuc> asubedi: hi
-<Beuc> since recently, we send a 'ping' after 1 week
-<Beuc> 1 week during which there was no reply
-<Beuc> after 2 weeks we usually consider the project can be cancelled, and we
send a 'timeout'
-<Beuc> the way to kill the project is currently done in a root shell, so
mjflick or I have to do it
-<Beuc> There are sv-ping and sv-timeout in the latest savannah.el
-[...]
-<asubedi> so the 'ping' is just a reminder to the submitter?
-<Beuc> yes, just in case he forgot, or in case we did'nt get a mail, before to
definitely close the submission
-
-Approving projects:
-1) It is quite easy actually, you go to the pending page, you click on
-"Manage/Edit Project Registration", then you witch the status from
-"pending" to "active", clikc update, and then you click on the "Send
-New Project Instruction Email" link
-
-
- When mjflick is coming over, I'll ask him about giving you a read-only access
to Savannah.
-<Beuc> You will be able to study how Savannah works inside, and troubleshot
some requests
-<zeus> ok
-
-<Beuc> What would be good is also giving you access to create mailing-lists.
-<zeus> Beuc: Where I can found the ruls to create a mailing-list ?
-<Beuc> the 'rules' are in the Savane code..
-<Beuc> nongnu-> address@hidden or address@hidden
-<zeus> Beuc: we just create the #nongnu.org mailing-list right ?
-<Beuc> gnu -> address@hidden or address@hidden or address@hidden or
address@hidden or... let me check, there's one left
-<Beuc> oh yeah, address@hidden
-<Beuc> so, we also create @gnu.org
-
-
-
-
- What is our (Savannah's) policy regarding the inclusion of trademark
- logo images in the source code distribution of a project licensed
- under GNU GPL? Specifically, I have a project at hand which allows the
- distribution of trademark logos in the following terms:
-
-It is no problem if the program contains trademarked images and names,
-provided the trademark usage and requirements don't make it difficult
-in practice to change the program and publish a modified
-version. In other words, it has to be easy to find and remove the
-trademarks, if and when the trademark conditions require this.
-
- Please note, all images showing "aroundme" or "barnraiser" logos are
- a trademark of Barnraiser. You can distribute them under the terms
- of the copy license, however you are forbidden to alter them.
-
-This poses no problem at all, since they don't say you have to remove
-the trademarks under any condition.
-
-
-
-<Beuc> zeus: btw, I think it is not of our competence to look at non-obvious
patent issues like the "Dijkstra algorithm"
-<Beuc> incidentally I think it is a simple algorithm that I learnt at school
-<zeus> yes, it isn't of our competence, but IMHO it is of our competence know
if that algorithm it's licensed or not
-<zeus> Beuc: hehe, I know nothing about that algorithm, that's why I ask him
-<Beuc> zeus: for consistency, we should then study if all patented algorithm
are licensed to be used in free software...
-<zeus> Beuc: I'll be more carefully about that point
-
----
-
-Mention this article (part of the Savannah philosophy)
-http://fsfeurope.org/news/article2001-10-20-01.en.html
-
----
-
-Hi Beuc,
-
-There's a submitted project called 'tim' that works with MSN and ICQ
-AFAIK MSN it's a non-free protocol (don't know if ICQ is), there's any
-problem in host projects that will use non-free protocols? Can we
-consider this protocol is a proprietary software? IMHO, we should
-promote the use of free IM protocols.
-
-I don't think there is any problem with reverse-engineering non-free
-protocols, as done in Gaim/aMSN/etc.
-
-You still can mention Jabber to the developers.
Index: administration/docs/hacking_savannah/hacking_savannah.texi
diff -u administration/docs/hacking_savannah/hacking_savannah.texi:1.104
administration/docs/hacking_savannah/hacking_savannah.texi:1.105
--- administration/docs/hacking_savannah/hacking_savannah.texi:1.104 Wed Apr
13 20:53:46 2005
+++ administration/docs/hacking_savannah/hacking_savannah.texi Fri Apr 15
21:12:08 2005
@@ -1,5 +1,5 @@
\input texinfo @c -*-texinfo-*-
address@hidden $Id: hacking_savannah.texi,v 1.104 2005/04/13 20:53:46 Beuc Exp $
address@hidden $Id: hacking_savannah.texi,v 1.105 2005/04/15 21:12:08 Beuc Exp $
@comment %**start of header
@setfilename hacking_savannah.info
@include version.texi
@@ -10,11 +10,12 @@
This manual (version @value{VERSION}, edition @value{EDITION},
@value{UPDATED}) is about Savannah.gnu.org, a place where GNU lives.
address@hidden Copyright @copyright{} 2004 Sylvain address@hidden
address@hidden Copyright @copyright{} 2004, 2005 Sylvain address@hidden
@indent Copyright @copyright{} 2004 Michael address@hidden
@indent Copyright @copyright{} 2004 Rudy address@hidden
@indent Copyright @copyright{} 2004 Elfyn address@hidden
@indent Copyright @copyright{} 2004 Mathieu Roy
address@hidden Copyright @copyright{} 2005 Richard Stallman
@quotation
Permission is granted to copy, distribute and/or modify this document
@@ -95,6 +96,10 @@
It is a SF.net-like development platform aimed at promoting free
software and educating developers about freedom.
+Loïc Dachary wrote an interesting article at the beginning of
+Savannah:
address@hidden://fsfeurope.org/@/news/@/article2001-10-20-01.en.html}.
+
[TODO: complete this section]
@node This manual, , Savannah.gnu.org, Introduction
@@ -125,6 +130,7 @@
* Mailing lists::
* IRC::
* Real life contact::
+* First steps::
@end menu
@@ -200,15 +206,19 @@
@node Mailing lists, IRC, WWW, Team work
@section Mailing lists
+[TODO] revamp this section and include sv-hackers-public/private, and
sv-register-public.
+
@menu
-* savannah-hackers::
+* savannah-hackers-public savannah-hackers-private::
+* savannah-hackers savannah-help-public savannah-help-private::
* savannah-root::
* sysadmin::
* savannah-cvs::
@end menu
address@hidden savannah-hackers, savannah-root, Mailing lists, Mailing lists
address@hidden savannah-hackers@@gnu.org
+
address@hidden savannah-hackers-public savannah-hackers-private,
savannah-hackers savannah-help-public savannah-help-private, Mailing lists,
Mailing lists
address@hidden savannah-hackers-public@@gnu.org and
savannah-hackers-private@@gnu.org
Savannah hackers is a group of volunteers.
@@ -217,6 +227,9 @@
This list is public.
address@hidden savannah-hackers savannah-help-public savannah-help-private,
savannah-root, savannah-hackers-public savannah-hackers-private, Mailing lists
address@hidden savannah-hackers@@gnu.org, savannah-help-public@@gnu.org and
savannah-help-private@@gnu.org
+
The @email{savannah-hackers@@gnu.org} address is placed at various
places at Savannah and receives user requests. It also receives
notifications from group administration's trackers, project approvals,
@@ -236,8 +249,15 @@
reply whthing 24 hours. Our responsiveness is part of what makes
Savannah a good development platform.
+We now recommand to use the more descriptive
+savannah-help-public@@gnu.org, which is a fencepost alias. We keep
+savannah-hackers managed by Mailman because it is still an important
+mailing list references from a few official places (including our TLS
+(https) certificates). If savannah-hackers were the alias, anybody
+with a fencepost account could hijack it.
address@hidden savannah-root, sysadmin, savannah-hackers, Mailing lists
+
address@hidden savannah-root, sysadmin, savannah-hackers savannah-help-public
savannah-help-private, Mailing lists
@subsection savannah-root@@gnu.org
@uref{http://lists.gnu.org/mailman/listinfo/savannah-root}
@@ -307,7 +327,7 @@
all important, policy-related and administrative decisions are made.
address@hidden Real life contact, , IRC, Team work
address@hidden Real life contact, First steps, IRC, Team work
@section Real life contact
Direct contact information like phone numbers and location information
@@ -316,6 +336,21 @@
It is not reproduced here for privacy reasons.
address@hidden First steps, , Real life contact, Team work
address@hidden First steps
+
+When a new volunteer wants to work on Savannah, we grant him a
+read-only access to Savannah, via the @samp{svadmin} accounts. Care
+must be taken to make this account truly a read-only one.
+
+At a point, this account had access to the Apache certificates that
+were not @command{chmod}-ed appropriately :/
+
+This account also has read-access to the database.
+
+The hopefully future Savannah hackers is then be able to study how
+Savannah works inside, and troubleshot some support requests.
+
@node Savannah configuration, Using MySQL, Team work, Top
@chapter Savannah configuration
@@ -2251,6 +2286,7 @@
* Adding a Frequently Asked Question::
* Manually setting up commit e-mail notification::
* Updating the menu::
+* Adding a banner::
@end menu
@node Adding a Frequently Asked Question, Manually setting up commit e-mail
notification, Some Savannah tasks, Some Savannah tasks
@@ -2298,7 +2334,7 @@
you'll have to do that by hand.
address@hidden Updating the menu, , Manually setting up commit e-mail
notification, Some Savannah tasks
address@hidden Updating the menu, Adding a banner, Manually setting up commit
e-mail notification, Some Savannah tasks
@section Updating the menu
Check @file{/savannah/etc/gnu-content/menu.txt} and
@@ -2313,6 +2349,29 @@
try to find a way to do so that will not break future Savane update,
ie provide a generic way to do so in Savane.
address@hidden Adding a banner, , Updating the menu, Some Savannah tasks
address@hidden Adding a banner
+
+Adding a banner on the Savannah homepage can be done by editing
address@hidden/gnu-content/homepage.txt} and
address@hidden/nongnu-content/homepage.txt} (and translations) in the
+Savannah administration repository.
+
+This requires the approval of RMS (political decision). However, we
+can do it without asking for @url{ffii.org}-originated requests for
+action
+(@url{http://lists.gnu.org/@/mailman/@/private/@/savannah-hackers-private/@/2005-February/@/000020.html}):
+
address@hidden
+ Would it be ok to add a banner in the front page of Savannah as can be
+ found at demo.ffii.org for the 02/17 event against software patents?
+
+ If yes, can it be done for subsequent banners related to ffii.org
+ events against software patents?
+
+Yes, please support the ffii.org in this way whenever they ask for it.
+No need to ask me each time.
address@hidden verbatim
@node Frequent support requests, Some quirks, Some Savannah tasks, Top
@@ -3171,6 +3230,72 @@
can say somethink like ``We will reconsider your project for inclusion
at Savannah''. Up to you :)
+TODO: we use the @samp{administration} project task tracker now; most
+of mail-related intructions are out-of-date.
+
+Approving projects: You go to the tracker item, you click on the
+``Original Submission: Site Admin. Approval/Edition URL:'' link, then
+you witch the status from "Pending" to "Active", click Update, and
+then you click on the "Send New Project Instruction Email" link.
+
+If the project asked to be GNU and is not, then change the project
+type to ``non-GNU'', and also click on ``Ask gnueval-input@@gnu.org to
+evaluate for inclusion in the GNU project''.
+
+
address@hidden
+* Project description::
+* Project submissions expiration::
+* Project without source code::
address@hidden menu
+
address@hidden Project description, Project submissions expiration, Approving
projects, Approving projects
address@hidden Project description
+
+The submission should come with a technical description of at least
+half a page.
+
+If not, it is better to ask a resubmission. One of our goal is to keep
+a trace of why the project was approved. So whether it is in the
+description, or in the archive, it doesn't matter.
+
+It is a problem when the project wants to be GNU, because we usually
+forward the description verbatim to GNU-Eval; it is also a problem
+when the description changed during the approval process (in that
+case, it is better to resubmit to avoid confusion)
+
+
address@hidden Project submissions expiration, Project without source code,
Project description, Approving projects
address@hidden Project submissions expiration
+
+We send a 'ping' (@code{sv-ping}) after 1 week during which there was no reply.
+
+After onother week of silence we usually consider the project can be
+cancelled, and we send a 'timeout' (@code{sv-timeout}).
+
+The project is actually deleted by editing the project via the site
+administration area. A link to that administration page is
+automatically prepended to the project submission description.
+
+There, you can set the project status as ``Deleted''. A cron job will
+take care of cleaning the database.
+
+We do all these steps is just in case he forgot, or in case we didn't
+get a mail, before to definitely close the submission.
+
address@hidden Project without source code, , Project submissions expiration,
Approving projects
address@hidden Project without source code
+
+If a project doesn't have source code yet, you can't check the
+licensing issue, but you have to check the other criteria as much as
+possible. For example, I asked a game project to resubmit their
+project with a description about planned platforms and programming
+languages
+
+Once you feel the project can be approved, you do so the usual way,
+except that you place the tracker item in the ``Approved Projects to
+be Reviewed'' category, and let it open.
+
@node Approval Criteria, GNU projects, Approving projects, Projects approval
@section Approval Criteria
@@ -3188,7 +3313,6 @@
* Legal Notices::
* Kind of software::
* Words to avoid::
-* GIFs::
* Mirroring::
@end menu
@@ -3289,10 +3413,34 @@
laws of a particular country or state. See for example
@url{http://www.gnu.org/@/licenses/@/license-list.html#PythonOld}.
+RMS:
address@hidden
+ - do we accept projects that are compatible with the GNU GPL (for
+ example, released under the mBSD), but that rely on GPL-incompatible
+ free software?
+
+ The code hosted at Savannah is compatible with the GNU GPL,
+ it does not rely on proprietary software, but the project as a whole
+ is not compatible with the GNU GPL. I think we have several projects
+ hosted at Savannah that are in this situation.
+
+This is ok, as long as use of the software does not actually require
+violation of the licenses. For instance, TeX is GPL-incompatible free
+software. If a GPL-covered Savannah package forks and execs TeX, that
+is fine. Thus, if Makeinfo is on Savannah, that is ok.
+
+If it had to link with TeX, that would still be ok, as long as the
+Savannah package has a license exception permitting linking with TeX,
+and provided linking them together does not violate the TeX license
+either.
address@hidden verbatim
+
@menu
* Perl and the Dual GPL&Artistic License::
* Java::
* .Net::
+* Optional non-free dependencies::
+* Non-free protocols::
@end menu
@node Perl and the Dual GPL&Artistic License, Java, Dependencies, Dependencies
@@ -3354,7 +3502,7 @@
cannot approve his project.
address@hidden .Net, , Java, Dependencies
address@hidden .Net, Optional non-free dependencies, Java, Dependencies
@subsubsection .Net
.Net as a dependency is a similar issue to Java (@pxref{Java}). You
@@ -3363,6 +3511,41 @@
[TODO: add links]
address@hidden Optional non-free dependencies, Non-free protocols, .Net,
Dependencies
address@hidden Optional non-free dependencies
+
+RMS:
address@hidden
+ - do we accept projects that _optionnaly_ rely on proprietary
+ software. For example, a program licensed under mBSD that can be built
+ to enable a proprietary module (distributed somewhere else)
+
+This is acceptable provided that (1) none of the important
+functionality of the Savannah package depends on using that
+proprietary module, and (2) including support for that proprietary
+module here won't greatly boost use of the proprietary module.
+
+For instance, it is ok for programs on Savannah to be able to run on
+MS Windows. Few users will learn of the existence of MS Windows
+because they saw a package on Savannah that supports it. However, if
+important parts of the functionality are only available on Windows,
+then the package becomes a Windows enhancement, and that is not
+acceptable.
+
+Mentioning non-free add-ons to free software is very bad.
address@hidden verbatim
+
+
address@hidden Non-free protocols, , Optional non-free dependencies,
Dependencies
address@hidden Non-free protocols
+
+There is no problem with reverse-engineering non-free protocols, as
+done in Gaim or aMSN, this is not a proprietary dependency.
+
+You still can mention free alternative protocols to the developers to
+encourage free standards.
+
+
@node Legal Notices, Kind of software, Dependencies, Approval Criteria
@subsection Legal Notices
@@ -3401,6 +3584,19 @@
though - they have to find themselves how to write them, else we would
have taught nothing to them.
address@hidden Trademark logo
+
+Some projects include non-free trademark logo images in the source
+code distribution of a project. These logo can be ``non-free'' because
+of trademark laws, or because of a non-free license that applies to
+the logo (and the logo only).
+
+It is no problem if the program contains trademarked images and names,
+provided the trademark usage and requirements don't make it difficult
+in practice to change the program and publish a modified version. In
+other words, it has to be easy to find and remove the trademarks, if
+and when the trademark conditions require this.
+
@node Kind of software, Words to avoid, Legal Notices, Approval Criteria
@subsection Kind of software
@@ -3418,6 +3614,7 @@
purposes, but it primarily aimed at better goals (such as network
analysis tools), we can accept it.
+
Approving GNU User Groups (GUG) or GNU/Linux User Groups (GLUG - which
can inappropriately be called Linux User Groups or LUG) is not made by
the Savannah hackers, but by people maintaining the GUG page at
@@ -3425,7 +3622,7 @@
reached at @email{user-groups@@gnu.org}. Once the GUG is listed on that
page, the project can be accepted.
address@hidden Words to avoid, GIFs, Kind of software, Approval Criteria
address@hidden Words to avoid, Mirroring, Kind of software, Approval Criteria
@subsection Words to avoid
The approval process is adequate to teach our users about our
@@ -3445,8 +3642,25 @@
it, but be sure to tell the user we would like to see these things to
change.
address@hidden GIFs, Mirroring, Words to avoid, Approval Criteria
address@hidden GIFs
address@hidden Patents
+
+We check for a few well-known patent violations in projects. These are
+the ones the FSF focuses on. However, it is not of our competence to
+look at non-obvious patent issues; for consistency, we otherwise would
+have to study if all patented algorithm are licensed to be used in
+free software, which is a lifetime job. The author of zlib says that
+it took him more time to study and avoid patents, than actually
+working on the algorithm and writing the software...
+
+Here is two patents we want to avoid:
+
address@hidden
+* GIFs::
+* MP3::
address@hidden menu
+
address@hidden GIFs, MP3, Words to avoid, Words to avoid
address@hidden GIFs
GIF is a symbol in the fight against software patents. For that
reason, and because it is illegal to use this format without patent
@@ -3454,13 +3668,26 @@
format to other ones, such as PNG or JPEG. Check
@uref{http://www.gnu.org/@/philosophy/@/gif.html}.
- Philosophy of the GNU Project
+Philosophy of the GNU Project
(@uref{http://www.gnu.org/@/philosophy/}) and Richard Stallman's book
(@uref{http://www.gnupress.org/@/book13.html}) also present
interesting materials about software patents and the damages they
cause.
address@hidden Mirroring, , GIFs, Approval Criteria
address@hidden MP3, , GIFs, Words to avoid
address@hidden MP3
+
+There are patents on @emph{both} the encoding and the decoding
+(playing) of MP3 audio files. We recommand instead Ogg Vorbis and Free
+Lossless Audio Codec (FLAC).
+
+If a program parses MP3 files to find information (such as ID3 tags),
+then this is not (as far as I know) covered by a patent and is
+acceptable at Savannah. However, we are concerned that not only MP3
+files are supported by such a project.
+
+
address@hidden Mirroring, , Words to avoid, Approval Criteria
@subsection Mirroring
We only accept projects if they are going to use Savannah as their
@@ -3470,6 +3697,16 @@
For example, check:
@uref{https://mail.gna.org/@/public/@/project/@/2004-05/@/msg00001.html}
+We do accept, however, that project at Savannah get mirrored somewhere else.
+
+In the case of a migration from a SourceForge account, we usually ask
+the project submitter to use a SourceForge interface special feature
+that says the project relocated, not to delete the account.
+
+We generally accept that project use only part of our services, as
+long as it is not only the download area - in which case, there are
+other free ways to get storage space.
+
@node GNU projects, GNU web-only projects, Approval Criteria, Projects approval
@section GNU projects
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Savannah-cvs] administration/docs/hacking_savannah AUTHORS TO...,
Sylvain Beucler <=