[TYPO3-core] Decide on community vendor name for CMS

Ernesto Baschny [cron] ernst at cron-it.de
Thu Apr 24 23:38:13 CEST 2014

Am 2014-04-24 10:19, schrieb Steffen Müller:
> Hi.
> I agree with Thomas.
> On 23.04.2014 15:46 Thomas Maroschik wrote:
>> Vendor names also tell you who is the main maintainer of the code. If
>> it's the community then everybody is allowed to directly push to that
>> repository? I don't think so. There are always a bunch of people that
>> are gatekeepers and have a vision of the roadmap. If these people form a
>> team then the team name should be the vendor.
> For Extension Builder, we use the namespace:
> EBT/ExtensionBuilder
> EBT stands for ExtensionBuilderTeam.

+1 on that.

I also agree with Tom also that we don't need (or even don't want) to
have a standard "typo3 extensions vendor name". A vendor name is not the
place to define the "type" of a package. In the composer world, you
define the type of your package in the composer.json, "type". TYPO3 CMS
extensions have a "typo3-cms-extension" type, and that's enough.

If an extension is an individual development, he uses his own vendor name.

If it is work of a "team", give this particular team a name (like "EBT").

If the extension is later moved over to a different new maintainer, they
simply use a new vendor name.

The extension key can stay the same.

AFAIK "FlowPack" is not a vendor for "community packages", but a vendor
name for a group of core developers developing kind of "a-class"
packages. See also http://flowpack.org/. This doesn't look like a vendor
name people should start using at will!


More information about the TYPO3-team-core mailing list