From: Peter Fitzgibbons Date: 2008-08-05T23:05:08+09:00 Subject: Re: perl and the culture of libraries ------=_Part_21316_18606088.1217945090725 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Isn't it true, though, that rubygems are the defacto distribution model for projects in RubyForge ? If so, then, like packaging a CPAN .tgz that includes the ./t, ./doc, ./lib and Makefile.pl, the "default" gem hierarchy created/expected by the gem tools should also have ./test, ./doc, and ./lib directories Also, I seem to recall that although many (most?) projects on CPAN include the usual-suspect titles in the documentation (Name, Synopsis, Description...), those titles really are purely cultural, there is nothing in POD spec that declares what the title should be... just "convention" A lot of this has to do with the 25yrs of history w/ Perl vs the 12yrs history w/ Ruby. 12 years is a long time... but seems to me a short time in social-cultural development. Your thoughts ? Peter Fitzgibbons (847) 687-7646 Email: peter.fitzgibbons@gmail.com IM GTalk: peter.fitzgibbons IM Yahoo: pjfitzgibbons IM MSN: pjfitzgibbons@hotmail.com IM AOL: peter.fitzgibbons@gmail.com On Tue, Aug 5, 2008 at 8:52 AM, Martin DeMello wrote: > On Tue, Aug 5, 2008 at 6:31 AM, Peter Fitzgibbons > wrote: > > Sounds like some changes to rubygems and it's toolset. > > Not really. For instance, if I had a small program, doc_init.rb, that > simply spat out a file project-doc.txt that had the following > ---------------------------------------------- > Project Name: > > Authors: > > Short Description: > > Long Description: > > Usage: > > Notes: > > ---------------------------------------------- > > it would (a) kickstart the documentation process and (b) give other > tools a standard set of headings to look for (c) give authors a > psychological incentive to include those sections in their > documentation (all of which are useful). Once this achieves a critical > mass, we can ask the rubyforge maintainers to consider looking for a > project-doc.txt in projects and make that the landing page. That in > turn will make sure people who submit to rubyforge include such a > file. It just requires a bit of initial buy-in. > > martin > > ------=_Part_21316_18606088.1217945090725--