Re: CVS, www.xemacs.org, and not solving the problem ( was Re: Yeah! Using instructions missing from the README, xemacs installed! (was Re: How can xemacs have been made so hard to install? Do the developers have any clue it is needlessly
john s jacobs anderson <jacobs(a)azstarnet.com> writes:
[ *META* could we please cc: xemacs-webmaint or webmaster(a)xemacs.org
when we start jawing about the web site? ]
Consider it done! (I didn't know there was a xemacs-webmaint list).
[ META2 hey i'm the new guy blah blah blah ]
Welcome. [BTW1 I like /newlook]
people who make critical decisions. That person or small group of
people is going to be the 'core' group that keeps the site going, and
CVS makes their lives *harder*.
I can guess why having multiple people hack on it randomly will cause
problems. But how does CVS do so?
First of all CVS will make your access problem easier: You just edit
the stuff locally and CVS will take care of what needs go to the site.
More importantly, CVS is designed for group collaboration, that means
that you can see _what_ is changed and by who.
Not to stomp on toes, or anything, but in the long run, *CONTENT*
*IS* *EASY*. And CVS only simplies content addition.
Yes, but our current problem is (or better was) one of content, I can
write all the READMEs , installation notes, little items telling
people there is know problem with version so-and-so of the mule-base
package but I have no way of getting it to the site.
as we're working!) Give us a bit of time (like a couple weeks or
so)
to make some changes.
SUMMARY MESSAGE FROM A WEB SITE VOLUNTEER: Implementing a whole bunch
of cruft (like CVS, IMHO) is only going to make the whole thing
messier in the long run.
Well, I respect your opinion and I promise to leave you alone while
you do your work. However when your work has stabilized I would like
you to consider a solution that allows multiple people to work on the
website, if need be[1]. A solution that no longer makes the maintenance[2] of the
website dependent on one (or a few) persons time. For me such a
solution is CVS, it isn't perfect but we already have the infra
structure in place.
Footnotes:
[1] I am not claiming this should be the normal mode of operation.
[2] Note: That is maintenance, _not_ design. I think we are
disciplined enough to keep a make minor (but possibly crucial
information wise) changes in accordance with your style guides if you
are on that round the world trip.
Jan
P.S. Are you now also de facto FAQ maintainer or do we need a new
volunteer for that too.