Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: pass (hermes.apache.org: domain of myanywhere@gmail.com
 designates 64.233.184.198 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references;
        b=M2rjYFC5xrYEichglN+L+dcZDVwrzSBWW8T2L0J8OmfOHsBR3kGx2vdsy99Z7mZQZ14oVNl9a8ywC0YsuFUyD+iPsFVihZkUAGQU3EGHDPa5BYC0azG5gXQXuGJIIbZPyz63SrI6CA2Ah7zGR6n2xyxsWoyr/GEw+gfWwuLvIpM=
Message-ID: <1cfd215805051717093c78432e@mail.gmail.com>
Date: Wed, 18 May 2005 03:09:25 +0300
From: Ahmed Saad <myanywhere@gmail.com>
Reply-To: Ahmed Saad <myanywhere@gmail.com>
To: harmony-dev@incubator.apache.org
Subject: Re: Organizing the Mailing List
In-Reply-To: <40376185-5BC9-4430-91F0-08CA0EB6E220@apache.org>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_6673_5214834.1116374965490"
References: <bc89fc2505051615482cffb06c@mail.gmail.com>
	 <40376185-5BC9-4430-91F0-08CA0EB6E220@apache.org>

------=_Part_6673_5214834.1116374965490
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

can we push some priorities rather than running everywhere.. like

1. decide on a language to use: c, c++, java (did i hear pascal)
2 . an architecture=20
3. ....

According to this architecture we will divide our efforts. So we can focus=
=20
on more specific subjects
and may be we can do more organized studies about how other open similiar=
=20
projects did X or Y and whether we gonna for for them or build it from the=
=20
scratch. We need a priority list and we, i hope all will, can resolve each=
=20
items in order. i think we can get to work faster that way.

comments?

on 5/17/05, Geir Magnusson Jr. <geirm@apache.org> wrote:
>=20
> We tend to do this naturally - we put something in the subject line
> to distinguish. Maybe we'll come up w/ some patterns.
>=20
> 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?
>=20
> geir
>=20
> On May 16, 2005, at 6:48 PM, Bryce Leo wrote:
>=20
> > 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--
> >
> >
>=20
> --
> Geir Magnusson Jr +1-203-665-6437
> geirm@apache.org
>=20
>

------=_Part_6673_5214834.1116374965490--