[TYPO3-team-core-v5] [TYPO3-core] [Summary] Using Github for TYPO3.PackageBuilder

Tobias Liebig tobias.liebig at typo3.org
Wed Feb 13 16:19:52 CET 2013


Hej Robert, hej Rens,

a few days ago Philipp Gampe proposed an possible GSoC idea about a "next generation TER" and a "composer based package repository" for both Flow packages and CMS extensions [1].
I'm not sure if this overlaps, but maybe you could get in touch with each other and check, if both ideas are going into the same direction, and if it could make sense to let someone (a student) work on a side-project during the GSoC. I could imagine, if we can find a appropriate student, he might help us with his "outside point of view".

kind regards
   tobias

[1] http://forum.typo3.org/index.php/mv/tree/194267/#page_top



Am 13.02.2013 um 10:34 schrieb Robert Lemke <robert at typo3.org>:

> Hi folks, 
> 
> a short summary of an IRC chat with Rens Admiraal, replies go to the Neos list.
> 
> Rens is working on the new package builder which eventually can kickstart Flow packages, but also TYPO3 extensions or any other code base (Fluid templates, Symfony2 bundles). This project is partly funded by the TYPO3 Association.
> 
> The team working on that package has already been using Github for development during the last few months and is happy with the working mode. Two questions arose: which PHP namespace should be used eventually and which Github organization should host the repository?
> 
> For the time being, we decided to go for this solution:
> 
> 1) the PHP namespace is "TYPO3.PackageBuilder" because
> 
> 	- it will become an important part of both, TYPO3 and Flow
> 	- it is maintained by the core team(s) and funded by the TYPO3 Association, thus belongs to the "official" TYPO3 namespace
> 
> 2) we use "TYPO3" as the Github organization and create a team "PackageBuilder"
> 
> Regarding 2), it's clear that we don't really use Github yet for the TYPO3 project, but we would like some packages as a pilot to see if Github can be potentially useful.
> 
> I have some ideas regarding which organizations and namespaces to use for which purpose and would like to discuss this in a broader group (but am mostly lacking time for it right now). Anyway – if you plan something Github related or have ideas regarding the namespaces, I'd be grateful if you kept me in the loop.
> 
> Cheers,
> Robert
> 
> -- 
> Robert Lemke
> Lead Developer TYPO3 Neos and TYPO3 Flow
> Co-Founder TYPO3 Association
> 
> Blog: robertlemke.com/blog
> Get involved: typo3.org – flow.typo3.org – neos.typo3.org
> 
> 
> 
> 
> 
> _______________________________________________
> 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

-- 
Tobias Liebig
TYPO3 Core Team member

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

http://bit.ly/supportTYPO3



More information about the TYPO3-team-core-v5 mailing list