Re: Moving documentation to git
| From: | Andreas Heigl | Date: | Wed, 14 Jun 2017 16:12:50 +0000 |
| Subject: | Re: Moving documentation to git | ||
| References: | 1 2 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969386627@lists.php.net to get a copy of this message | ||
Hey Patrick
> Am 14.06.2017 um 17:54 schrieb Patrick Schwisow <patrick.schwisow@gmail.com>:
>
> I can't answer any of your questions, but I'm intrigued by the idea and would be
> willing to help. (To clarify, I am not a very active contributor to docs at this point and know
> little about how the tooling works.)
Thanks for your offer :)
I'll keep you posted and will contact you separately for further infos.
Cheers
Andreas
>
>> On Wed, Jun 14, 2017 at 10:34 AM, Andreas Heigl <andreas@heigl.org> wrote:
>> Hi everybody.
>>
>> Some time ago I requested karma for the documentation
>> (http://news.php.net/php.doc/969386047 and
>> http://news.php.net/php.doc/969386046) and at that time I
>> also mentioned
>> I'd like to help move the docs to git/Github.
>>
>> Time flew by but finally I'd love to give that a go.
>>
>> My idea was as follows:
>>
>> * Move the current trunks of the subfolders of
>> https://svn.php.net/repository/phpdoc/ each to a new
>> git-repository
>> using "git svn"
>> * Move those new git-repositories to GitHub (or somewhere else?)
>> * Make sure that the current manual build-process still works
>>
>> What I don't know yet:
>>
>> * How does that affect edit.php.net - Any insight there is highly
>> appreciated!
>> * How does that affect the automated builds - Also insight here would be
>> highly appreciated.
>>
>> My aim would be to leave as much of the current infrastructure and
>> workflows as they are in the first step and only move the VCS from SVN
>> to git.
>>
>> The improvement would be that it is much easier and more transparent for
>> people without karma to get a documentation change in as it is possible
>> to create a PR on github which is for the most people more intuitive
>> than using edit.php.net
>>
>> A second step could then be to move the automated build-process to a
>> CI-System that would build on merging to master.
>>
>> Or is that a completely futile idea or way to go? Or did I miss some
>> vital parts that need to be considered? (I'm pretty sure I did)
>>
>> Thank you all for your feedback!
>>
>> Cheers
>>
>> Andreas
>>
>> --
>> ,,,
>> (o o)
>> +---------------------------------------------------------ooO-(_)-Ooo-+
>> | Andreas Heigl |
>> | mailto:andreas@heigl.org N
>> 50°22'59.5" E 08°23'58" |
>> | http://andreas.heigl.org
>> http://hei.gl/wiFKy7 |
>> +---------------------------------------------------------------------+
>> | http://hei.gl/root-ca
>> |
>> +---------------------------------------------------------------------+
>