Hi Rob, Every "decent" project website has a "development" section. While jal.orgsyndicate all jalv2 related projects (that's the goal), migrating some content from GC to jal.org would sound logical. JSG remains a nice recipe for jallib developers, but also jallib users and even jalv2 users. Moving PIC datasheet mapping wouldn't sound that ok...
BTW jal.org is meant for users, but also for developers... Cheers, Seb 2009/10/27 Rob Hamerling <[email protected]> > > > > Sebastien Lelong wrote: > > > I'm thinking about converting our JSG wiki page into DITA, and publish > > it to our website (in "Development" section). > > The first thing you read on 'justanotherlanguage.org' is what JAL is, > what you can do with it, etc. So apparently it is meant for Jal and > Jallib *users* (promotion, teaching, etc.). I do not understand why > having a development section on that site and even less why putting JSG > there. OK, I read a request for contributions, but contributors will > have to join GoogleCode where all the development tools, data and docs > are. So I would say: keep typical Jallib development stuff at > GoogleCode, which includes JSG. > > I have absolutely no problem with reading JSG, and I do not see the need > to convert it to Dita. > > Regards, Rob. > > > -- > Rob Hamerling, Vianen, NL (http://www.robh.nl/) > > > > -- Sébastien Lelong http://www.sirloon.net http://sirbot.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
