Ben Rockwood wrote:
> The almighty powers, for the near future anyway, are term and cK, who
> basically get final say in what gets cut, if
> things do. (Trust me, I've tested their power. \(^_^)/)
HAHAHA :) I'm really not picky, I'd just like to request three things:
- don't brag. It doesn't help. Being modest will pay off much more.
- write using good english. No "tellya", "gotta" etc.
- use a spellchecker before stuff gets committed :)
> This brings us to the revisitation of DR16. We need to revisit all the
> work done on DR16's docs and FAQs
> and "bring them up to date". Essentially, this means blowing the dust
> off 'em, filling in any loose areas,
> creating any content that might have been missing, etc. Chief among
> these would be a "New Users Guide",
> kind of a Enlightenment for Dummies, if you will, and secondly (and most
> neededly) a theming guide.
> There are still alot of people using DR16, and we can draw in even more
And will be for some time to come :) If somebody could dedicate some
time to a themeing tutorial, that'd be great. I started a postscript on
the topic ages ago, but couldn't finish it. If you want to continue
these efforts, you can look at it here:
I can send you the tex sources if you want.
> In the future (a couple months from now) we'll need to start ramping
> documentation toward the DR17 release.
> Of course we need to be way ahead of the actual release date, which is
> why I say months. But most of that can
> wait, and should be worried about now too much. Just look at the docs
Yes. Don't spend too much time on the current CVS now, it'll outdate
soon. More e16 info would be very nice.
> that have already been written, just in the
> last month... most of them are useless now because of all the changes.
> One flick of Tillsan, Smugg or Rasters
> wrist and hours of our work goes to shit. That why I don't want to see
> people wasting too much effort.
> Something I really don't want anyone to worry about now is the topics of
> DocBook, SGML, etc transitioning.
You don't need to use docbook for additional doco, the packages'
documentation works that way, and that's enough. Like it was said a few
days ago, if somebody could investigate the possibilities of running a
cron job that automatically uploads generated html to the website,
that'd be absolutely awesome.
> ____CVS Issues and Closing_______
> Please look over CVS closely and think before you commit. When you make
> a change it can often effect the whole site,
> so be careful. There are 2 main directories in CVS, "data" and "pages".
> All your modifications should happen to the pages
> in "data". Once you've made the changes, you can then back down a
> directory and run the makefile "s/make". This will
> create (or recreate) all the pages in the "pages" directory by putting
> the headers, footers, navbar and the like on the pages.
If you go up to the "e" directory (which contains data/, pages/ etc) and
type 'make' there, only those pages that were touched will be rebuilt,
so a small change doesn't cause all pages to be checked out again when
somebody does an update after these changes were committed.
Try to check the pages with a validator, if possible.
Cheers, keep it up,