URL:
<http://gna.org/support/?func=detailitem&item_id=718>
Summary: savannah.conf.pl documentation lack of clarity
(savane vs. savannah; GNU `leftovers`)
Project: Savane
Submitted by: mech
Submitted on: Tue 09/13/2005 at 23:21
Category: Installation/Configuration
Priority: 5 - Normal
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Release:
_______________________________________________________
Details:
A meta-comment about savannah.conf.pl
This is probably already the subject of a savane Bugs Tracker ticket #
somewhere, but I couldn`t find it: Don\'t we think it`s about time for
savane to stop making references to `savannah`? (e.g.
/etc/savannah/savannah.conf.pl)
There are other problems of this sort, like the documentation included in the
source. I went to the trouble of compiling and converting the .texi
documentation into HTML and studying it, and it doesn`t really have any
bearing on what savane is and does any more. I know this is a known problem
- this was mentioned in a support req. I filed the other day about this
documentation having compile issues on my system - but I would say that
fixing the issue should be made a high priority. It`s hard to think of
anything worse than including documentation that is wrong! >;-)
On a side note, I would also like to suggest that the `GNUification` of
savane be removed soon. There is no reason at all that GNU-specific
information such as everything on the first page of registering a new
project, and I think everything on the second page (the license-related
stuff, especially the VERY GNU-specific message at the bottom of that page)
should be present on a `vanilla` savane installation. My own site`s policies
about GIFs and about licensing and so on may be very different from GNU`s. I
suspect that this is just stuff that needs to be moved out into the
site-specific files area, and re-written into sane default text that people
like the GNU project can customize for their site while everyone else can
just ignore it. A related issue is that as an admin I should be able to
completely disable the licensing page for people registering a project. That
should only appear if I want it to and have a list of acceptable options to
provide with regard to licensing. This is not a huge issue, but it could be
very confusing to users trying to register new projects to be told that a GNU
admin will have to approve their license choice, when they are working on an
internal project at a non-GNU site! Heh.
PS: I think it`s very hazardous to have both savannah_conf.pl and
savannah_conf.php, and only have one of them editable; it would be very easy
for someone to mistakenly edit the wrong file. I would strongly recommend
changing these to savane_conf.pl, and savane_DO_NOT_EDIT.php.
_______________________________________________________
Reply to this item at:
<http://gna.org/support/?func=detailitem&item_id=718>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
