discuss: Some ideas for TLDP
Subject:
Re: Some ideas for TLDP
From:
Serge Victor ####@####.####
Date:
9 Jan 2016 14:07:03 +0000
Message-Id: <CAPRDrAGqCEZBGu8+zUrg-tQzEJvAJ-362rC8hAKCc+76tkY=tQ@mail.gmail.com>
On Sat, Jan 9, 2016 at 8:54 PM, Daniel Pocock ####@####.#### wrote:
> On 09/01/16 14:51, Serge Victor wrote:
>> Hi, I need more time to answer the initial mail authored by J.S.
>> Evans, but I am able to quickly reply to Daniel's.
>>
>> On Sat, Jan 9, 2016 at 7:59 PM, Daniel Pocock ####@####.#### wrote:
>>
>>> I contacted the mailing list some time ago about the RTC Quick Start
>>> Guide. The discussion was very brief and I still have no idea whether
>>> the guide would become part of TLDP.
>> I'm really sorry, it seems I missed that discuss. I moved some time
>> ago all documents to github to allow easier collaboration. Please feel
>> free to remove the outdated HOWTO and replace it with your brilliant
>> RTC Guide (which I've read before, making myself familiar with RTC).
>> And of course please send a pull request after that, Daniel.
>>
>> https://github.com/tLDP/LDP
>
> How would you feel if some guides were maintained as Git submodules
> rather than directly in your repository?
>
> Maybe I will just submit it as a pull request, but there may be reasons
> for me to keep it in the current repository and find some way to give
> TLDP maintainers joint access through Github ACLs
To be honest, I don't want to make a precedence, Daniel. Generally
it's of course a good solution, until for example someone's repository
disappears, and it will disappear from LDP as well. LDP is a long time
repository, and we are famous for keeping docs forever.
But of course if you are able to suggest some data flow which allows
us to keep a copy, please share. I am not 100% fluent in git
submodules.
S.
