Sounds good -- I don't know if people have already seen the classlib
status page [1] which gives a very broad view of what's happening; and
(as you point out) the JAPI tool output [2] that gives a very detailed view.
The tools we need are not reflected in those lists yet, though there has
been som
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 28, 2006 12:07 PM
To: harmony-dev@incubator.apache.org
Subject: Re: assigned modules
We actually don't assign things because we don't want to create feelings
of territory.
That said, if someone is working in an area, it's court
PROTECTED]
Sent: Tuesday, February 28, 2006 12:07 PM
To: harmony-dev@incubator.apache.org
Subject: Re: assigned modules
We actually don't assign things because we don't want to create feelings
of territory.
That said, if someone is working in an area, it's courteous to show
Hi
I have been thinking about this for a while. The reason is that I would
like to contribute but as others have noted before, it's a little
difficult to see where to start.The work of Stuart Ballard [1] made
this a little bit easer. The problem that remains is that sometimes
there is a big work b
Yes I am interested in documenting this thing. I dont know the best way
to do it, but I was thinking if everybody could send in the following
information:
1. Name
2. Module and classes working on
Then I can create a simple wiki page with the above information.
However, it would be very difficul
We actually don't assign things because we don't want to create feelings
of territory.
That said, if someone is working in an area, it's courteous to show some
deference in order to avoid commit clashes :)
However, I think your question is different - we don't have a full
classlibrary map, a
