Tim Ellison wrote:
Probably best to put the 'concerted work in progress' description on the
wiki, so anyone can join in; the website status page was intended to be
more of a current state of the code overview. We should also start to
set ourselves some goals, in terms of applications to run, etc.
Why not have "started" on the webpage, and then a like to the wiki page
if there is one?
Or just encourage people to ask here on the dev list...
If you want to make a start on the wiki page that would be good, or if
anyone else has an idea for tracking intent...
It's also worth mentioning that I don't believe we should be exclusive
about areas of work within, and contribution to, Harmony.
Absolutely.
While I
understand that the goal is to minimize redundant work, we may find
ourselves in the situation of having more than one implementation of the
same APIs (we already saw this happen with 'security' and 'security2'
contributions). This is no bad thing as it allows us to evaluate the
best technical option (quickly) and proceed with the combined group of
experts collaborating on a single code base. I hope we can continue to
do so 'harmoniously'.
Choice and competition is good. This isn't "live or die" competition,
but "we can choose best of breed" competition, and we all benefit.
There are no losers.
geir
Regards,
Tim
karan malhi wrote:
Hi,
I am writing the interfaces for the javax.accessibility package. Some of
the interfaces are dependent on classes from the awt package. Are we
expecting any donations for awt, swing packages?
If donations are not expected then what approach should I take? Should I
start writing stuff for awt and swing (on which accessibility depends
on) so that accessibility classes compile during a build in harmony?
Please guide me here.
Secondly, once a volunteer starts working on a "Missing" module as
stated on
http://incubator.apache.org/harmony/subcomponents/classlibrary/status.html
, should the status be changed to something else like "Work in progress"
or something?
