How about letting people from outside volunteer by cloning the repo,
fixing the readme and doing a push request?
I think many people who search for a spec might lend a hand here. I
volunteer for creating an initial version if you are interested.
Christian
On 14.01.2014 17:05, BJ Hargrave wrote:
> Maybe one could add a simple README.md file with all RFC codes and
> their title in the OSGi internal repo which is then showed in github
> mirror? Would be very helpful.
> How about a readme in the directory master/rfcs that describes all
> rfcs in a table and links to each doc?
Yes. But then this file would soon get out of date. Many OSGi members
are working on different documents. People will forget to update the
central readme when new documents are added or existing documents are
renamed. This would require some OSGi member to volunteer to maintain
the central readme. So far, no volunteers...
We have the same problem internally in OSGi. :-) We have an internal
wiki which we use to hold the list of documents, but it is frequently
out of date for these reasons. We just learned to accept it given the
many OSGi members contributing documents.
--
*BJ Hargrave*
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the _OSGi Alliance_ <http://www.osgi.org/>_
[email protected]_ <mailto:[email protected]>
office: +1 386 848 1781
mobile: +1 386 848 3788
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
