Commit 983dea1a authored by Fabien Udriot's avatar Fabien Udriot
Browse files

Remove paragraph regarding synchronisation of git.typo3.org with Packagist

@see https://github.com/TYPO3/CmsComposerPackageGenerator/issues/4

Change-Id: I7a5a6145e357234e8adb264fb43194c4c2323af0
parent eee4b634
......@@ -99,15 +99,7 @@ dependencies. The file must be placed at the root of your extension and must loo
The ``vendor-name`` must be one of yours. It must not be "typo3" which is reserved for Core extensions.
There are some [conventions notes](http://wiki.typo3.org/Namespaces#Does_and_don.27ts_for_developers) to be read in the TYPO3 Wiki related to namespaces.
Also, you have the chance to synchronise your package on Packagist, if you are hosting your code on git.typo3.org.
The benefit would be to be able to use the "master" branch as long as the "tags" - which is not possible with the TER. To have this possible, make sure to:
* Have a Composer file at the root of the extension, as shown above.
* Register the package at [Packagist](https://packagist.org/packages/submit)
* Add "typo3" as additional maintainer of your package on Packagist. This is required to have Gerrit's hook correctly triggering the update on Packagist.
There are some [conventions notes](http://wiki.typo3.org/Namespaces#Does_and_don.27ts_for_developers) available in the TYPO3 Wiki related to namespaces.
How it works?
-------------
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment