Hi André,
Florent André schrieb:
On Thu, 19 Mar 2009 15:01:20 +0100, Andreas Hartmann <[email protected]>
wrote:
Florent André schrieb:
[…]
I also like Thorsten's idea having a page showing the status of the
components very much,
because people can see which contibutions are useable.
I also think to a think like that before...
Actually, module's folders have a module.xml file (in module/config). So
I
think :
* Add some tags like : <todo>,
<changes>,<improvement>,<howtouse>,<roadmap>, and other essential thinks
to
have a "dev status" of a module
IMO we should keep it simple – maybe the existing <readme> section is
sufficient?
IMO, this other sections have 3 benefit :
1 - they "force"/encourage dev and contributors to fill it
2 - they are more structured and "I know what I will read in this section"
than a "all going in" <readme>
3 - They allow to apply a nice xslt and render module description
attractive (and adaptive : "one source, multiple view")
Alright, would you mind preparing a patch? TIA!
* Dev can update this file and push it in the svn
* Official site have a modulestatus module :
** this module browse the svn branch repository and create/update
module's
pages on Lenya site.
That would indeed be a nice addition. We could even render these pages
dynamically – just make a request to the corresponding
svn.apache.org/viewvc/… document and apply an XSLT to the module.xml.
Yes, this is exactly my idea ! Thanks for the translation...
Do you think that is a difficult module to code ?
No, I think it would be quite straightforward. ATM the code to update
the SVN changes is in the forrest module, which is rather confusing. I
think we should create a new module ("projectsite" or whatever) for this
purpose.
Have a cool friday !
Thanks, you too :)
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
