On 10/16/06, Peter Kriens <[EMAIL PROTECTED]> wrote:

The normal way of working is through RFPs. Non-members can provide
RFPs to our requirements committee.

Ok.

An RFP should only contain requirements, no solutions.

Ok.

I agree that there are many more areas that could be standardized but
we have the issue of man power ... Developing a specification is quite
a lot of work when you want to do it right and you need at least 3
companies willing to do work.

Is that so even if the RFP involves a fairly limited scope?

The most immediate one that comes to my mind, and has been bothering me for quite a while;

All OSGi platforms provides a Console interface, often with extensible ways to access it ( System.in, TCP, telnet, jabber) and often an extensible mechanism to add your own commands. It sounds a lot of waste to have several implementations of these, and the users will occassionally end up with several running at the same time, because some extensions are available on one and not the other.

The spec for this seems to me to be fairly small, and wouldn't require man years of effort. The main problem is probably to deviate enough from all existing ones, to avoid 'cronyism'.


Cheers
Niclas



Kind regards,

     Peter Kriens

----
Peter Kriens                              Tel +33467542167
9C, Avenue St. Drézéry                    AOL,Yahoo: pkriens
34160 Beaulieu, France                    ICQ 255570717
Skype pkriens                             Fax +1 8153772599


_______________________________________________
OSGi Developer Mail List
osgi-dev@bundles.osgi.org
http://bundles.osgi.org/mailman/listinfo/osgi-dev

_______________________________________________
OSGi Developer Mail List
osgi-dev@bundles.osgi.org
http://bundles.osgi.org/mailman/listinfo/osgi-dev

Reply via email to