We need your ideas for Google Summer of Code 2013

[Javier Gómez]

As you may know we are working yet in Google Summer of Code 2013. Google Summer of Code is a global program that offers post-secondary student developers ages 18 and older stipends to write code for various open source software projects.

Last year we had very successful incomes to the joomla project thanks to it ( see Chad's Joomla World Conference session about it: http://conference.joomla.org/speakers/session/session/83-joomla-and-google-summer-of-code-2012.html ).

WE NEED YOU! we want you to write ideas in the 2013 wiki page.  We are not asking you that you become a mentor (that you also can) but we are only asking that you just take 10 minutes to write an idea that can improve Joomla!.

Please, add now your ideas here: http://docs.joomla.org/GSOC_2013_Project_Ideas (see last year ideas here http://docs.joomla.org/GSOC_2012_Project_Ideas ).

Thanks very much ^_^

[hoochicken]

Hi,
I got some ideas, but I don't know whether they're good or not.
Will the ideas be reviewed by somebody with J! knowledge and will that somebody take out stuff that is not needed?
So can I just post it or do I have to ask someone for a permission?
And question: Is there something special about this wiki's behaviour and its generation of a new entry that one should know before using?

Greetings
Mareike

[Javier Gómez]

Yes indeed!

We will review them, and also students will have to choose between the ones that they like more.

^_^

[TobsBobs]

Hello,

would be nice to see

Project: Refactor Media Manager

This is one of the most important things the Joomla CMS is different from others. Since we have definitely a disadvantage.

greeting

[Nils Rückmann]

+1 for Refactoring Media Manager

Another Idea: New or better WYSIWYG-Editor for the core

I think most of the users will use JCE, but Joomla should ship an extandable editor.

[Herman Peeren]

Added " ORM in Joomla" as a proposal in the 2013 wiki-page.

[elin]

So a proposed idea should follow the format of providing at least minimal description of the task and goals for the 8 week project and the kinds of skills a student should possess. 

You don't need to have all the technical details worked out but you do need to have something more than "implement multisite" or similar ... this is not ideas.joomla.org.    Remember that software projects often take double the estimated time even for experienced professionals and be realistic about what can be achieved.  It is better to have a smaller well defined objective with code that is well documented and has full test coverage than it is to have huge, messy and untested.

Also my feeling is that student projects are best if they are in the "nice to have" category, not in the category of something essential that will hold up other work.  Also ... students are being paid so work that is needed but not always fun or easy to convince people to spend time on is great, helping with system tests is a good example of this.

Elin

[Beat]

Great! and thanks for the call-for-action.

I added "Project: html contenteditable front-end editor for content, categories and modules as proposal to the wiki page. Feel free to edit/enhance/change.

Think that should really go into core joomla 3.2, so feel free to edit or remove if someone is already working on this.

Best Regards,

Beat

http://www.joomlapolis.com/

[hoochicken]

Hi,
I know, I'm not really in the CMS team, I added some ideas concerning things, that I would have needed while setting up a bunch of websites,
and each time I wondered why it was not in the core and why had to implement it myself.
I write, because I want you to know why I came up with these ideas that I hope you like.
Mostly that are small things, easily to programm. (And maybe someone would like to have a very easy summer of code.)
That is:

• Field 'created' in frontend article edit view
  Some clients wanted to show article that have a future date in a list; the only date file left for use was 'created' (couldn't use publish_up/-_down)
  Not having the possibility to modify the created date was the only reason, why the client could not use the frontend administration, that is so fine.
  
  
• Plugin 'mvc override'
  Sometimes I wished I could have overidden just one single line of a component's model. I had to install the plugin mvcoverride (J!2.5) and make it work on J!3.0.
  That should be easiser
  (When I desperately neede the 'created' field above, I would have loved to have this thing in the core; though I don't like the idea of overwriting a core file :-)
  
  
• Plugin 'modal'
  If a dev wants to use the modal behaviour, he's got to add the code in a template. That should be easier.
  And: For a normal user (no dev) working with Joomla! it would be great if he didn't have to go to the html source code to add the class="modal"
  

• Hathor is beautiful
  Isis sometimes produces mistakes in 'ordering' and module position field when inserting a custom position. That is why I love Hathor as an additional admin template, but her functional design/ugliness strikes me every rare occassion I see her. I want her to be beautiful - at least a little bit, please.
  

• Fieldtype 'oclock' in fields
  Sometimes a date field as well as a time field is needed. It would be great if J! provided that one, too.
  

Greetings
Mareike

[Nick Savov]

Hi Mareike,

The good news is that there's not really a CMS team. It's open open
development for the CMS, so whoever would like to work on it is welcome.
There isn't a set of people that are considered a core team. It's open to
everyone that wants to write the code for it :)

The JBS Team, which is open to everyone, does a lot of the day-to-day
issue handling, but it's not reserved just for JBS. Everyone can pitch in
and help out by writing code and testing. Mark and I are currently the
JBS co-coordinators so we do a lot of the managing (I just started so
Mark's doing most of it), but not necessarily the code writing (in fact, I
can barely code:).

Here's a good one for you to get started in, if you're interested:
http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=29031

It's an override plugin for the Joomla core :) It needs some polishing up
to get into the core and some testing.

Hope this helps! Let me know if you have any questions and I'll be glad
to answer (or someone will beat me to it).

Kind regards,
Nick

> Hi,
> I know, I'm not really in the CMS team, I added some ideas concerning
> things, that I would have needed while setting up a bunch of websites,
> and each time I wondered why it was not in the core and why had to
> implement it myself.
> I write, because I want you to know why I came up with these ideas that I
> hope you like.
> Mostly that are small things, easily to programm. (And maybe someone would
> like to have a very easy summer of code.)
> That is:
>

> - Field 'created' in frontend article edit view

> Some clients wanted to show article that have a future date in a list;
> the only date file left for use was 'created' (couldn't use
> publish_up/-_down)
> Not having the possibility to modify the created date was the only
> reason, why the client could not use the frontend administration, that
> is
> so fine.
>

> - Plugin 'mvc override'

> Sometimes I wished I could have overidden just one single line of a
> component's model. I had to install the plugin mvcoverride (J!2.5) and
> make
> it work on J!3.0.
> That should be easiser
> (When I desperately neede the 'created' field above, I would have loved
> to have this thing in the core; though I don't like the idea of
> overwriting
> a core file :-)
>

> - Plugin 'modal'

> If a dev wants to use the modal behaviour, he's got to add the code in
> a
> template. That should be easier.
> And: For a normal user (no dev) working with Joomla! it would be great
> if he didn't have to go to the html source code to add the
> class="modal"
>
>

> - Hathor is beautiful

> Isis sometimes produces mistakes in 'ordering' and module position
> field
> when inserting a custom position. That is why I love Hathor as an
> additional admin template, but her functional design/ugliness strikes
> me
> every rare occassion I see her. I want her to be beautiful - at least a
> little bit, please.
>
>

> - Fieldtype 'oclock' in fields

> Sometimes a date field as well as a time field is needed. It would be
> great if J! provided that one, too.
>
> Greetings
> Mareike
>

> --
> You received this message because you are subscribed to the Google Groups
> "Joomla! CMS Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to joomla-dev-cm...@googlegroups.com.
> To post to this group, send an email to joomla-...@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

[Javier Gómez]

Hi,

For the ones that would like to be mentors, please remember to fill the mentors form: https://docs.google.com/spreadsheet/viewform?formkey=dHA2V1lJbThYQXpwMERiRG1FOTZlV3c6MA

Also remind you that we have a specific group for Students and Mentors GSoC 2013 at: https://groups.google.com/forum/?fromgroups=#!forum/joomla-gsoc-2013

And finally, for Herman and others that have proposed a project idea and want to offer themselves to become mentor of it, feel free to add your name just like Mark Dexter have done here: http://docs.joomla.org/GSOC_2013_Project_Ideas#Project:_Webdriver_system_tests_for_CMS

Thanks ^_^