harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ahmed Saad <myanywh...@gmail.com>
Subject Re: Organizing the Mailing List
Date Wed, 18 May 2005 01:35:08 GMT
that would be great so people can stop worring about the legal side... and 
if anyone wants to know about the current legal situation s/he could check 
that list.

On 5/17/05, Stuart Still <stustill@gmail.com> wrote:
> 
> I agree. Perhaps though it might be helpful to split into a legal
> and technical list shortly?
> 
> Cheer
> Stuart
> 
> On 17 May 2005, at 16:55, Geir Magnusson Jr. wrote:
> 
> > We tend to do this naturally - we put something in the subject line
> > to distinguish. Maybe we'll come up w/ some patterns.
> >
> > One thing to consider is when we get going with things, to split
> > off an architecture list if the volume gets too much. But for now,
> > it's light enough to keep it all here. Comments?
> >
> > geir
> >
> > On May 16, 2005, at 6:48 PM, Bryce Leo wrote:
> >
> >
> >> As harmony is just getting started, there is a great deal of good
> >> suggestions, questions and offers for help. Ever since the Slashdot
> >> announcement I personally think that the number of people whom have
> >> joined and offered their services has clearly gone up and to promote
> >> organization I'm proposing a naming scheme for subject of emails. The
> >> Bulletin board style tags are just to promote reading ease.
> >>
> >>
> >> First lets look at what seem to be the larger topics of discussion.
> >>
> >> [BigCategories]
> >> JVM: The Java Virtual Machine, where to start, different available
> >> codebases and strategies.
> >>
> >> Compiler: Creating a javac like tool.
> >>
> >> Documentation: It's always easier to document as you go along and
> >> well
> >> documented code can save tons of time in tracking down bugs.
> >>
> >> Libraries: Which ones to choose or develop individually
> >>
> >> Tools: The associated java tools, applet viewer, jar, etc.
> >>
> >> Introduction: This would be used for if your'e introducing yourself,
> >> listing prior experience, etc.
> >>
> >> DevPriority: The overall discussion of which parts of harmony should
> >> be developed first.
> >>
> >> Target OS: Seems small but it doesn't belong as a part of any
> >> other so
> >> it gets its own.
> >>
> >> Licensing: Should really be a minor concern for now, once we pick up
> >> steam this issue will be logically sorted out. It's and
> >> inter-dependancy (i apologize if i used the word wrong), choosing a
> >> licence effects our code base choices and visa-versa
> >>
> >> Organization: How things should be organized.
> >> [/BigCategories]
> >>
> >> Below these would be sub-categories that would provide more insight
> >> into the larger topic.
> >>
> >> [SmallCategories]
> >> Suggestion: General suggestion(s) for a particular topic.
> >>
> >> Questions: Questions about a particular topic.
> >>
> >> DevPriority: Probably shouldn't be used yet, would be used for
> >> sub-development. i.e. What order things should be developed for the
> >> compiler.
> >>
> >> Organization: How things should be organized.
> >> [/SmallCategories]
> >>
> >>
> >> So say for example you wanted to send a brand new suggestion for the
> >> JVM the topic of the post would be "JVM--Suggestion" and if you
> >> wanted
> >> to ask a questions about a compiler it would be "Compiler--question"
> >> and so on like that.
> >>
> >> This should be friendly for both threaded and un-threaded mail
> >> clients. And under this system this mail would be
> >> "Organization--Organization" but for now that's irrelevant.
> >>
> >>
> >> I think this system would really help focus the group and allow
> >> people
> >> to easily tune in to what interests them and keep a tab on the
> >> general
> >> flow of the project, while right now things seem a bit "willy-nilly".
> >>
> >> What do you think?
> >> --
> >> ~Bryce Leo
> >>
> >>
> >> --Veritas Vos Liberabis--
> >>
> >>
> >>
> >
> > --
> > Geir Magnusson Jr +1-203-665-6437
> > geirm@apache.org
> >
> >
> >
> 
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message