In this case a README.MD file in the rfcs and rfps directories would be very helpful. The README.MD file could countain "RFP-number: Title" lines or just a link to website where this information is already available.
If I do such a file, will you put it in? Shall I sent it by mail to someone or should I create pull request? Balazs Zsoldos Software Architect Mobile: +36-70/594-92-34 Everit Kft. https://www.everit.biz Everit OpenSource http://everit.org On Tue, Jan 14, 2014 at 4:24 PM, BJ Hargrave <[email protected]> wrote: > > BTW.: Would it be possible to take the title of the RFC into the > > name of the folder at https://github.com/osgi/design/tree/master/rfcs > > ? It is really hard to keep in mind what-is-what based on number > > codes. > > The github repo is a read-only mirror of an OSGi internal git repo. OSGi > already has many internal links to RFC documents in the internal repo so > renaming folders will mess up many internal OSGi web pages. So I don't > expect this will happen. Sorry. > > > Also, if there was a commit on a folder, the commit message > > does not say what the RFC is about. > > > > It is up to the OSGi members making commits to use helpful commit > messages. Unfortunately, not every commit has a useful commit message. > -- > > *BJ Hargrave* > Senior Technical Staff Member, IBM > OSGi Fellow and CTO of the *OSGi Alliance* <http://www.osgi.org/> > *[email protected]* <[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 >
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
