[TYPO3-doc] Encouraging people to contribute with Github

Jigal van Hemert jigal.van.hemert at typo3.org
Thu Feb 28 10:52:47 CET 2013


Hi,

On 27-2-2013 17:03, François Suter wrote:
>> we agreed that once the documentation team had everything sorted out
>> with branches and stuff (could that be the reason why the documentation
>> has been left alone a bit to give the team a chance to restructure
>> everything?) features which needed changes in documentation would have
>> an extra issue+patch for the documentation and once the code change is
>> merged the documentation could also be merged.
>> How is this done with GitHub, especially when looking at the
>> relationship between the patches in Gerrit, the relationship between
>> issues and patches in forge, the automatic status updates, etc.
>
> It's true that this is an issue and this process should be lost, now
> that we finally have a strict way of doing things.

You mean that you want to drop the rule for related documentation 
patches for features? Wow, that's step back. All this to use GitHub; 
that's a desperate move.
If that is the case there is no use complaining that new features do not 
get documentation.

-- 
Jigal van Hemert
TYPO3 Core Team member

TYPO3 .... inspiring people to share!
Get involved: typo3.org


More information about the TYPO3-project-documentation mailing list