Whom should I send it? alex
>> I want to change that once and for all, I will ask that as >> you submit new code you also submit the JUnit tests if you >> have them as the documentation. The documentation can come mf> This doesn't make sense. I mean, "just like you have you junit test, mf> submit doco" Doco is not the junit obviously so the "junit as doco" mf> doesn't make sense, yes I am still talking about word files for the mf> documentation so that we can easily include them in our books. mf> And I don't want this to degenerate in 'What format should we use for mf> doco bla bla bla" just gives us WORD documents and we will deal with mf> them (text if you use linux) mf> marc f >> in 2 sets. The documentation should include a beginner >> "getting started" couple of paragraph, explaining the feature >> and how to use it for the "getting started" book. If your >> feature is complex enough, it should also come with FOR-PAY >> pages. These pages will be included in the for-pay >> documentation of JBoss and the author compensated based on >> the revenues. You don't need to produce a booklet (few stuff >> like the CMP stuff is big enough to warrant a booklet). >> >> Is it clear? Please follow these guidelines for the new >> submissions it is the only way your features will be used at >> all and it is also a simple way to make some easy money with us. >> >> regards >> >> marc f >> >> xxxxxxxxxxxxxxxxxx >> Marc Fleury, Ph.D. >> President, Founder >> JBoss Group, LLC >> xxxxxxxxxxxxxxxxxx ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
