At 06:49  18/9/00 -0500, you wrote:
>At 07:00 PM 9/18/00 +1000, Peter Donald wrote:
>
>>I am usually also deadly opposed to people including their own names into
>>projects (ie rheise-os or whatever it was called) because it implies less a
>>group. It is a better idea to come up with code-names.
>
>Agreed.  This particular case came about because no-one could come up with 
>a name.  ;)  And now rheise.os has really split from jos so it further 
>complicates the issue.

okays :P

>> >So far each developer has worked on there own project with little help
>> >from other developers, and nobody wants to give up there project and
>> >work on someone else's.
>>
>>One thing I noticed here is that there is faaaaar to much re-invention of
>>the wheel. I saw a lot of projects mentioned that were started but never
>>finished but were almost 100% identical to external projects.
>
>Agreed again.  Much of JOS was started in the hurly-burly days when java 
>was really going crazy.  Most of the time, there were a dozen alternatives 
>with the same functionality and jos seemed to absorb one from each for each 
>major function point.  The lack of focus at jos I think made the more 
>focused, stand-alone competitors more appealing for both developers and
users.
>
>it's high time to do the rounds and try and collaborate again though.

Theres a certain amount of consolidating occuring at Jakarta apache
project. They are slowly aquiring projects that should fulfill all your
java orientated building needs.

Currently it has a build tool (Ant), they are moving JUnit to it (Unit
testing framework), as well as a logging framework (either log4j or one of
a few other potentials), they have general regular expression libs (both
ORO and regexp) etc. They are still missing a few tools (code
formatter/beautifier, installshield) but mostly they will aquire them
eventually. Combine that with the Bean Scripting Framework (OSS from IBM
that acts as interface engine for some of javascript, python interpreters)
and you have a complete build envionment. They also have all tools to build
documentaion from XML sources.

So they are good places to at least start looking also look at
www.jpython.org and www.mozilla.org for nice scipt engines.

>>Another thing to consider is making consistency across all the projects.
>>Currently copyright is assigned to various people and licensing is
>>different etc. It is much better to assign copyright to a non-profit
>>organisation as that means if the owner of code leaves the rest of team are
>>not screwed. You could look for a sponsor group if you don't want problems
>>of setting up jos.org - there are a few around.
>
>Yup.  Copyright has always been a problem with JOS.  I've always leaned 
>towards a BSD license but we could never agree on anything.  Once again, 
>this is probably mostly a matter of biting the bullet and doing 
>this.  There are core developers that will get pissed off and leave no 
>matter what decision is made though which is why the decision has never 
>been made.

I guess you will always loose people but you will also gain people by
consolidating. It may even be worth having a split license - GPL/LGPL for
jvm/os/classlibraries. BSD for execution environment and the rest - this
will allow you the most reuse as most JVMc/classlibraries are GPL and most
other stuff on top of that isn't. 

>>Personally I don't think a Wiki approach is the *right* approach - at least
>>not for this. It is too damn hard to maintain, manage, navigate and
>>standardize.
>
>+1  This is slated to change as soon as I can get the time.  See the mockup 
>at jos.sourceforge.net and send me a comment via email if you hate/like 
>it.  The content is really poor at the moment because I was just testing 
>out the look and feel.

I always like a navigation aid down the side that is large and hierarchial
so you know exactly where you are other than that I like :P

>>BTW if you are standardising projects structure you may want to wait until
>>end of november as I am trying to get a standard layout that all projects
>>conform to defined at Apache. If that is the case then it will slowly
>>trickle out - many of the other java projects rely on Apache tools and will
>>gradually conform.
>
>That's great.  Can you ping the list when that's ready so we can eval it?

yep :P

good luck with whatever you decide and if you decide something I am
comtable with maybe I will join up :P
Cheers,

Pete

*------------------------------------------------------*
| "Nearly all men can stand adversity, but if you want |
| to test a man's character, give him power."          |
|       -Abraham Lincoln                               |
*------------------------------------------------------*

_______________________________________________
General maillist  -  [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/general

Reply via email to