[FLOW3-general] 2nd Neos code sprint doodle

Rens Admiraal renst3 at rensnel.nl
Thu Apr 11 10:53:17 CEST 2013


of course replace the CGL signing by CLA signing ;)

Op 4/11/13 09:59 , Rens Admiraal schreef:
> Good morning...
>
> We indeed have an open sprint, and we welcome new contributors a lot ;)
> To keep progress during the sprint it would be nice if such a
> contributor somehow matches the following:
>
> - Is a nice and positive person, passionate about his / her work and
> willing to work in one of the nicest teams I've ever seen ;-)
> - Is familiar with TYPO3 Neos and TYPO3 Flow
> - Has good skills in PHP, JavaScript and / or CSS (either one of those,
> or all :p )
> - Knows about composer, git, gerrit, CGL and stuff, or is eager to learn
> about it
> - Knows about the CGL and is willing to sign one (or has one signed
> already)
> - It will be a big pre if you're able to work on a certain task alone
> for a while
>
>
> When new contributors join we will give him a mentor from the team who
> will search for tasks with him and help him to start contributing.
>
>
>
> Greetz,
> Rens
>
>
>
> Op 4/9/13 20:44 , Pankaj Lele schreef:
>> Hello Team!
>>
>>> We plan to make this a community sprint, open to everyone - so feel free
>>> to participate if you feel qualified in any form (not only coding, but
>>> also design, UX, writing, …)
>>
>> 1. If I want to quality myself enough for participating in coding what
>> all I need to know in terms of technologies used?
>>
>> - Good understanding of Flow
>> - Good understanding of Neos internals (TYPO3CR, TypoScript, Routing,
>> Plugins)
>> - Prefered PhpStorm
>> - know CGLs
>> - know composer
>> - know Gerrit workflow
>> - Signed CLA
>> - know Unit and Functional testing
>> - EmberJS?
>> - RequireJS?
>> - RDFa?
>> - anything else?
>>
>> 2. While participating in coding from where to start contributing is
>> always a question. Start working on bugfixes would be a good start?
>>
>> Thanks!
>>


More information about the Flow mailing list