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

Aske Ertmann aske at moc.net
Wed Apr 23 15:17:38 CEST 2014

Hey Fabien

Good initiative.

Just a little information regarding Flowpack. It was chosen because we wanted something similar to Symfony’s “FriendsOfSymfony”, we discussed it for a long time and decided on “Flowpack” in the end. https://github.com/flowpack

Personally, I’m not really particularly fond of those suggestions though. If I had to choose I’d go with T3Ext, but I’d like to see more suggestions. Don’t have any good ones myself though :S

Best regards

On 23/04/2014, at 14.55, Fabien Udriot <fabien.udriot at ecodev.ch> wrote:

> Hi Core list,
> It would be good to agree with a community vendor name for third party extensions. As pointed out in
> the Wiki [1], a namespace must not begin with TYPO3\* (except for sysext) but rather stick to
> something related to a company name or anything else.
> In my case, for my public extensions I would prefer to have something community driven as vendor
> name instead of a company since they are developed in a community process. Below would be some
> propositions:
> 1) T3Ext\MyExt
> 2) T3X\MyExt
> 3) TER\MyExt
> 4) CMSPack\MyExt
> 5) ...
> Feel free to spontaneously vote (+1) or add your suggestion. I will collect them somehow. It could
> be a Doodle is set up if it becomes too confusing.
> FYI, in the Flow world, they have picked up "FlowPack" as community vendor name. I have only heard
> that and if someone have more relevant details, feel free to tell more.
> As little addition, the vendor name will also be reflected in the composer.json file eventually. the
> Composer stuff is not yet fully ready for third party extensions but is work-in-progress for now. It
> will be communicated when more stable.
> Happy Easter time!
> Fabien
> [1] http://wiki.typo3.org/Namespaces
> _______________________________________________
> Before posting to this list, please have a look to the posting rules
> on the following websites:
> http://typo3.org/teams/core/core-mailinglist-rules/
> http://typo3.org/development/bug-fixing/diff-and-patch/
> _______________________________________________
> TYPO3-team-core mailing list
> TYPO3-team-core at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-team-core

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20140423/e0a54be1/attachment.htm>

More information about the TYPO3-team-core mailing list