At 02:22 PM 9/18/00 +0300, you wrote:
>Robert Fitzsimons wrote:
>
> > 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.
>
>Sun has a nice system for managing parts of the Java platform: expert
>groups. My suggestion is that we use something like the JSR's and form
>expert groups, and have their proposals voted upon by members of JOS,
I think its a great approach but too much work for us. We're having
trouble keeping people involved without any more over head. If JOS
actually had a functional system, then I can see how this organization
would really help. And I think we really should be actively thinking about
how to set this up. But practically speaking I don't think we have the
number of developers needed to really need this.
In all honesty, I think we really just need a few really bull-headed people
to take this thing by the horns and set a direction for the group. The
number one problem seems to be lack of ownership. The project started out
as a committee idea and so no one person is "THE DESIGNER". And most of us
are a bit too polite and cautious to really just take the reigns. I'd
really like to see someone just say, I'm officially JOS Desktop and I say
JOS is linux + Xwindows + kaffe + JOS Desktop (a java window manager) and
then design it, recruit helpers, and build it. And someone else to say,
I'm officially JOS Kernel and I say JOS is decaf + jjos + classpath. In
addition, I think we have people that could and would do that already, but
most of them are just too busy with other things to be able to be that person.
> > For this to succeed we need to jump into the deep-end, new mailing
> > lists, web site, cvs server. We can keep the old stuff around but
> > only for reference.
>
>This is a good idea. The Wiki is useful, but there is no real
>organization strength behind it. The versioning must be made where and
>when it is useful. A hierarchy of information must be created. We need
>to separate news, discussion, reading material and implementation. The
>Wiki seems a bit too chaotic to serve such a huge project as an OS.
Yes. This is part of the web update suggestion already in the queue. I
think its already been "approved" in that we discussed in during the jos
meetings and everyone gave it a +1. The task should naturally fall on me
but I've been very busy at work and spending all my limited spare time
trying to stay away from the computer! :)
I promise to address it soon though.
>Regarding leaving all behind, I would just like to point out that all
>user-level applications should not be left out, but continue being
>listed. User-level applications do not hinder the development of the
>underlying OS, nor do they complicate the API's (they are not API's -
>you see).
Agreed. The current tactic I would propose is to tell every one to create
separate SourceForge projects, that link back to JOS. JOS's website will
create a link directory going back to the individual sourceforge
projects. Sound reasonable?
-iain
_______________________________________________
General maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/general
