We need help composing ourselves

[Andrew Eddie]

:)

So, we've done up a bit of a list of to-do's for what we need to do to get the Framework to version 1.0. We might be missing a few things but there's quite a bit to do.

https://github.com/joomla/joomla-framework/issues?state=open

Some things are obviously for us on the admin side, but there are a few cathartic quick wins as well as some more challenging things.

Some tasks span all packages so if have a spare hour, you can just "claim" a package by commenting on the issue and hopefully nobody has picked the same one and collides (happens). Then, issue us a pull request and you can say you helped make version 1.0 of the new Joomla Framework :)

If you have any questions, ask in the issue or here and someone well get an answer to you one way or the other.

We are terribly excited about this - it's going to open us up to a new world of opportunities. I'd love you to be a part of it, even if it's an hour here or there.

Thanks in advance! Let's rock!

Regards,
Andrew Eddie
http://learn.theartofjoomla.com - free tutorials and videos on Joomla development

[Ronni KC]

My team will look on the todo list next friday (8th march) if some are more important than others etc. have a chat with Florian or Roberto - we will have around 10 developers taking part the entire day.

[Ronni KC]

Actually counting its 13 developers we are assigning to the contribution day from redTEAM Joomla!.

I reckon we can get some stuff done with 100+ manhours on that day.

[Andrew Eddie]

On 28 February 2013 20:39, Ronni KC <ron...@gmail.com> wrote:

Actually counting its 13 developers we are assigning to the contribution day from redTEAM Joomla!.

I reckon we can get some stuff done with 100+ manhours on that day.

Hi Ronni.

That's EXTREMELY generous of you. Let's touch base later next week so we can make sure we keep everyone busy.

Regards,

Andrew Eddie 

[Nils Rückmann]

@Ronni: The CMS needs manpower too ;)

[Roberto Segura]

This is a newly created group and most developers will require help to start contributing (setup git, coding standards...). So we need to be patient and take this as a great starting point.

I also want to thank Ronni for making this possible. His commitment with Joomla! is absolutely incredible.

About contributing to the CMS I'm the most interested. But if we want to build great things we first require great tools.

--
You received this message because you are subscribed to the Google Groups "Joomla! Platform Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-plat...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Andrew Eddie]

On 1 March 2013 18:15, Daniele Rosario - Skullbock <realsk...@gmail.com> wrote:

I'll try to help as best i can.
Is there something like this issues list for the CMS? (don't tell me it's the joomlacode tracker...)

No no no, we don't want to use Joomlacode. The todo list is here:

https://github.com/joomla/joomla-framework/issues?state=open

Thanks for chipping in.

Regards,

Andrew Eddie

[Daniele Rosario - Skullbock]

My question was related to the CMS issue list ;)

[Ian]

That should probably be raised on the CMS list.

Ian

[Daniele Rosario]

It was a bit off topic, i know. ;)

Daniele Rosario

[Donald Gilbert]

Not only do we not *want* to use joomlacose, we absolutely won't be using joomlacode. 

Issuing PR's and viewing diff's is 100% easier and more intuitive with Github than joomlacode will ever be. :P

[Andrew Eddie]

Thanks to all those who have been picking up tasks from the issues list for 1.0 - I really appreciate it.

I've added a few more quick wins to the 1.0 milestone, mostly just updating existing README examples to use namespacing.

https://github.com/joomla/joomla-framework/issues?milestone=1&page=1&state=open

There are also other documentation tasks I've added for later milestones in the year if you are interested.

The way I'm working the labels is anything marked "backlog" is work we need to catch up on (documentation not done, tests not written, etc). I'd love to see that all finished by end of Q3 this year so we can actually concentrate on new stuff :)

Regards,
Andrew Eddie