[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [equinox-dev] ProSyst contribution
|
This is really great.
I propose we take the code into the incubator area (once proper paperwork
is in place) to enable code reviews, etc. before we consider promoting to
the main equinox project.
Also, I think the dependencies on non-open source code (e.g. ProSyst util
classes) must, of course, be remove before we put the code in the
incubator. Otherwise we will have no way to build and run it.
We already have a Config Admin impl (which Simon pointed out I still need
to code review... :-) and a DS impl. But the current DS impl is a bit
wonky and I am very much intrested to see if the ProSyst version is
suitable to replace it.
BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the OSGi Alliance
hargrave@xxxxxxxxxx
office: +1 386 848 1781
mobile: +1 386 848 3788
Dimitar Valtchev <d.valtchev@xxxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx
03/12/2007 11:01 AM
Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
To
Jeff_McAffer@xxxxxxxxxx
cc
equinox-dev@xxxxxxxxxxx
Subject
[equinox-dev] ProSyst contribution
Hi Jeff,
Following our conversation at EclipseCon we finalized the ideas for a
possible initial ProSyst contribution to Equinox. We could donate the
following OSGi services, which do not have a full Equinox
implementation yet:
1. Initial Provisioning
2. IO Connector Service Specification
3. Wire Admin Service Specification
4. Configuration Admin Service Specification
5. Declarative Services Specification
We can provide working implementations with packages in the Equinox
namespace comparatively fast but removing the dependencies on some
ProSyst util classes will take more time.
The developers who will be responsible for this work are Pavlin Dobrev
and Teodor Todorov. Both of them are involved with ProSyst OSGi
implementation and participate in the OSGi EG. I think it makes sense
to add them as Equinox committers.
Please let me know if you support the suggested approach.
Best regards,
Dimitar
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev