Hey, i am no committer so i am not allowed to enter a vote, but i've been using open source projects for a long time now (since the JServ days as a matter of fact) so i just wanted to add a consideration.
I just wanted to make sure that in the discussion you guys are now having on "Visibility" and "Publicity" you should consider how you are going to measure that visibility.(it is common practice in applied science to state that "measuring is knowing" :-)) I remember Marc Fleury telling that in the days before they put JBoss on SF they had download numbers that were low, but once they got on SF the numbers really started rising. And this concerns the way it is being measured and not the "Visibility" or "Publicity", so have you asked yourself how you will measure the success xdoclet would have when being part of jakarta ? I like xdoclet a lot and want to make sure it gets the right exposure it deserves. ;-) thanks for listening Werner Vincent Harcq wrote: > Good points Ara. > I only begin to understand these days that still a lot of java programmers > even didn't even know Ant 6 months ago. Who knows javamake for example ? > This product is just as beautiful as Ant imho, but it's not on Jakarta. > JDOM and JUnit are the _only_ two exceptions of successful tools out of > Jakarta. > Very good points Ara. > Vincent > > >>>On Jakarta you will get "Visibility" but not "Publicity". The >>> >>difference >> >>>is >>>that visibility >>>means you are seen by many developers, publicity is when are made >>> >>public >> >>>in >>>an >>>article, presentation, book etc. which aren't always developers. >>> >>You're absolutely right Andreas. We're already successful, because of >>quality and of course a good level of publicity and reputation in >>TSS/etc. >> >>So what's the point in gaining this visibility? It's really the >>visibility and jakarta's hallmark. >> >>Let me tell you in what kind of company I'm working. We're a >>conservative IBM shop. We use everything IBM-ish. Open source is >>non-sense here, except those which are more like de-facto/Jakarta-ish, >>like Apache web server or Ant. Funny I even had problems at first to >>make my management accept to use xdoclet in our project! You get the >>idea. XDoclet in SF is viewed by many as "yet another SF project"; in >>Jakarta it would be "a high quality de-facto project". >> >>Btw, it's even funnier when you consider the root of this problem. >>Again Ant for example, it's bundled in WSAD but it's v1.3, but if you >>upgrade it to a higher version you can't ask IBM for any support, >>you've changed WSAD. My goal is to make xdoclet visible to >>app-server/tools vendors to. IBM will not support xdoclet in WSAD, but >>may support it if it's a Jakarta project, like Ant. That's the moral of >>the story. >> >>And don't view it from a JBossic point of view. JBoss is itself an >>industry, it's a big platform other things converge to it. It competes >>with the whole world! It's non-sense to move JBoss to Jakarta, for >>example. Why move a big platform to jakarta and make it yet another >>little project in Jakarta? It's different for a tool like xdoclet. >> >> >>>group of projects like Jakarta. A good idea is to have your own >>> >>web-site, >> >>>try to get feedback from users, publish it, provide more and more >>> >>advanced >> >>>examples etc. >>>This is more effective and will help to brand the name. Then you get >>>publicity >>>nearly for free. >>> >>Articles/samples/presentation/... all help. I myself have been thinking >>about a code-snippets section in our cvs. As an example I've written a >>generic/cool Finder which is kick as for listing behavior, and it of >>course uses xdoclet in a very interesting way. Probably not popular >>enough to be a module of its own but at least a very interesting usage >>of xdoclet for writing generic finder code. Erik's Ant book (will be >>out soon!) also covers xdoclet extensively. And we also need articles >>here and there, and so on. But most importantly we need good samples in >>xdoclet itself and a clean doc, and that's what we're going to have >>pretty soon based on the new structure we've laid on ground in >>MODULE_REFACTORING_BRANCH. >> >>Yes there's a lot to improve.... >> >>Ara. >> >> >>_______________________________________________________________ >> >>Don't miss the 2002 Sprint PCS Application Developer's Conference >>August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm >> >>_______________________________________________ >>Xdoclet-devel mailing list >>[EMAIL PROTECTED] >>https://lists.sourceforge.net/lists/listinfo/xdoclet-devel >> > > > > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > _______________________________________________ > Xdoclet-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-devel > > -- ---------------------------------------------------------------------- ir. Werner Ramaekers Enterprise Java Solutions Architect - Shift@ Sun Certified Java Programmer "May the source be with you." <mailto:[EMAIL PROTECTED]> <http://www.shiftat.com> ---------------------------------------------------------------------- _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
