The reason the rfcs only had a number is historic (we had scripts to index them). They should be renamed to contain the title of the RFC.
Kind regards,
Peter Kriens
> On 4 jul. 2016, at 16:17, Raymond Auge <[email protected]> wrote:
>
> I have to agree with Cristiano.
>
> The issue may be fine on the RFP subdirectory, but on the RFC side it's
> really really hard unless you have a good memory for mapping numbers to RFC
> names. I can personally only keep one or two such mappings in my brain at a
> time. I often have to attempt an iterative search through the structure to
> find what I'm looking for and it's a royal pain in the backside. I
> occasionally get lucky if the person working on the document refers to the
> full name of the RFC in their git commits.
>
> I wish we could find a solution for this.
>
> Sincerely,
> - Ray
>
>
> On Mon, Jul 4, 2016 at 9:29 AM, Cristiano Gavião <[email protected]
> <mailto:[email protected]>> wrote:
> Aaah, that directory is much better:
> https://github.com/osgi/design/tree/master/rfps
> <https://github.com/osgi/design/tree/master/rfps>
>
> On 04/07/2016 05:33, David Bosschaert wrote:
>> Hi Christiano,
>>
>> You can simply see the list in github here:
>> https://github.com/osgi/design/tree/master/rfcs
>> <https://github.com/osgi/design/tree/master/rfcs> and
>> https://github.com/osgi/design/tree/master/rfps
>> <https://github.com/osgi/design/tree/master/rfps>
>>
>> Released OSGi specs can be downloaded from here:
>> <https://www.osgi.org/developer/downloads/>https://www.osgi.org/developer/downloads/
>> <https://www.osgi.org/developer/downloads/>
>>
>> Hope this helps,
>>
>> David
>>
>> On 2 July 2016 at 17:49, Cristiano Gavião <[email protected]
>> <mailto:[email protected]>> wrote:
>> Hello,
>>
>> In the github spec repository (https://github.com/osgi/design
>> <https://github.com/osgi/design>) readme page is specified that a list of
>> specs are maintained here: http://wiki.osgi.org/wiki/RFCs
>> <http://wiki.osgi.org/wiki/RFCs> and here: http://wiki.osgi.org/wiki/RFPs
>> <http://wiki.osgi.org/wiki/RFPs>
>>
>> But those link are not reachable anymore.
>>
>> could someone point me to the right place?
>>
>> thanks,
>>
>> Cristiano
>> _______________________________________________
>> OSGi Developer Mail List
>> [email protected] <mailto:[email protected]>
>> https://mail.osgi.org/mailman/listinfo/osgi-dev
>> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
>>
>>
>>
>> _______________________________________________
>> OSGi Developer Mail List
>> [email protected] <mailto:[email protected]>
>> https://mail.osgi.org/mailman/listinfo/osgi-dev
>> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
>
> _______________________________________________
> OSGi Developer Mail List
> [email protected] <mailto:[email protected]>
> https://mail.osgi.org/mailman/listinfo/osgi-dev
> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
>
>
>
> --
> Raymond Augé <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000)
> Senior Software Architect Liferay, Inc. <http://www.liferay.com/> (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org/> (@OSGiAlliance)
> _______________________________________________
> OSGi Developer Mail List
> [email protected]
> https://mail.osgi.org/mailman/listinfo/osgi-dev
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
