<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hey Fabien<div><br></div><div>Good initiative.</div><div><br></div><div>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. <a href="https://github.com/flowpack">https://github.com/flowpack</a></div><div><br></div><div>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</div><div><br></div><div>Best regards</div><div>Aske</div><div><br></div><div>On 23/04/2014, at 14.55, Fabien Udriot <<a href="mailto:fabien.udriot@ecodev.ch">fabien.udriot@ecodev.ch</a>> wrote:</div><div><div><br class="Apple-interchange-newline"><blockquote type="cite">Hi Core list,<br><br>It would be good to agree with a community vendor name for third party extensions. As pointed out in<br>the Wiki [1], a namespace must not begin with TYPO3\* (except for sysext) but rather stick to<br>something related to a company name or anything else.<br><br>In my case, for my public extensions I would prefer to have something community driven as vendor<br>name instead of a company since they are developed in a community process. Below would be some<br>propositions:<br><br>1) T3Ext\MyExt<br><br>2) T3X\MyExt<br><br>3) TER\MyExt<br><br>4) CMSPack\MyExt<br><br>5) ...<br><br>Feel free to spontaneously vote (+1) or add your suggestion. I will collect them somehow. It could<br>be a Doodle is set up if it becomes too confusing.<br><br>FYI, in the Flow world, they have picked up "FlowPack" as community vendor name. I have only heard<br>that and if someone have more relevant details, feel free to tell more.<br><br>As little addition, the vendor name will also be reflected in the composer.json file eventually. the<br>Composer stuff is not yet fully ready for third party extensions but is work-in-progress for now. It<br>will be communicated when more stable.<br><br>Happy Easter time!<br><br>Fabien<br><br>[1] <a href="http://wiki.typo3.org/Namespaces">http://wiki.typo3.org/Namespaces</a><br>_______________________________________________<br>Before posting to this list, please have a look to the posting rules<br>on the following websites:<br><br><a href="http://typo3.org/teams/core/core-mailinglist-rules/">http://typo3.org/teams/core/core-mailinglist-rules/</a><br>http://typo3.org/development/bug-fixing/diff-and-patch/<br>_______________________________________________<br>TYPO3-team-core mailing list<br>TYPO3-team-core@lists.typo3.org<br>http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-team-core<br></blockquote></div><br></div></body></html>