Hi!
On Sun, Apr 28, 2002 at 02:36:24PM +0800, Stas Bekman wrote:
- Move to "Tutorials": * 1.x::guide::HTTP_Headers * 1.x::guide::RDBMs * 1.x::guide::dbm_files * 1.x::guide::code_snippets (should maybe stay in mod_perl 1.x ?) * 1.x::guide::security (although it should be renamed to "Using Authentification to protect your site" or something ..) * 1.x::guide::performance_tuning
They are all version specific, cannot move.
After looking through them further, and after reading more about mod_perl 2.x, I think you're right (mostly).
ok
But HTTP_Headers is rather generic (there are only three or four mod_perl methods mentioned (header_out, content_type, content_length, ..). Although don't know it for sure, I assumed that those methods won't change a lot in 2.x)
let's try to go with your suggestion. certain APIs have changed in 2.0. 2.0 works as 1.x only with the compat layer (which is slower for certain things that used to be implemented in C).
- Split up guide::getting_help_further_reading to "mailing lists", "offsite resources" and "getting help"
this can go the general mod_perl docs. And have a small help.pod in the 1.x and 2.x point there.
As we now have a section of the site titled "getting help", I'd say we put it there, with links to it from 1.x and 2.x
ok
Win32 Platforms
(this was missed from the changes discussion). win32/ should be moved into 1.0/guide, we will have a similar platform specific notes in 2.x.
I missed it intentionally, but then put it in the wrong place. Should definitly stay in 1.x.
Maybe someone can add similar infos for OS X? I could collect the infos already availiable (someone posted something to the list, and there is a little information at http://david.wheeler.net/osx.html), but somebody who actually /uses/ OS X would be better suited as a maintainer ...
let' do piece by piece. first reorg what we have. release the site. next we will add new things. it's important not to move things after the site is released, but adding new files is always fine.
Another thing to think about is whether to do the same thing I've started with docs/2.0: drop the "guide" dirname and split docs into user and devel. But not sure if we really have any 1.x devel specific docs.
AFAIK there isn't much develpoment on 1.x done anymore, so nobody would
need that info.
agreed.
by 'devel' I call low-level things like hacking on mod_perl core, irrelevant to the user. so probably just s/guide/user/.
-1, I'd rather change the dir structur as little as possible. We can just rename the docs "User Guide", but leave the dirname untouched.
OK, I was just thinking to make things similar and more intuitive between 1.x and 2.x
BTW, Stas, how should we move around the files? If we just move them, than the CVS log info will be lost, so I think you'll have to do it by hand directly in the repository, don't you?
most likely. After you are done with the revamp, send me the whole src (or give me the URL I can grab things from) and I'll do the surgery manually on the cvs repository.
p.s. I didn't preserve the history when moving the guide from my cvs rep to apache.org, since I didn't think there will be any added value in it. So I've started from scratch: mod_perl guide: the next generation :)
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
