GSOC 2016: Difference between revisions

From Joomla! Documentation

Newer edit →
Created page with "300px|left == Welcome to GSoC 2016 == This page will aim to be a general informational page for students, mentors and others interested in Joomla's Goo..."
 
No edit summary
Line 1: Line 1:
[[Image:Gsoc2016.png|300px|left]]
[[Image:Gsoc2016.png|250px|left]]
 
<br>
== Welcome to GSoC 2016 ==
== Welcome to GSoC 2016 ==
This page will aim to be a general informational page for students, mentors and others interested in Joomla's Google Summer of Code Program.
This page will aim to be a general informational page for students, mentors and others interested in Joomla's Google Summer of Code Program.
Line 6: Line 6:
=== What is GSoC? ===
=== What is GSoC? ===
Google Summer of Code is a program run by Google for college students interested in contributing to FOSS projects. [http://www.google-melange.com Visit the Google Melange site to learn more.]
Google Summer of Code is a program run by Google for college students interested in contributing to FOSS projects. [http://www.google-melange.com Visit the Google Melange site to learn more.]
 
<br><br>
== Information For Students ==
== Information For Students ==
* [http://docs.joomla.org/GSOC_2016_Project_Ideas Joomla's Idea List]
* [http://docs.joomla.org/GSOC_2016_Project_Ideas Joomla's Idea List]
Line 12: Line 12:
* [https://groups.google.com/forum/#!forum/joomla-dev-cms General Joomla CMS Developer Mailing List]
* [https://groups.google.com/forum/#!forum/joomla-dev-cms General Joomla CMS Developer Mailing List]
* [https://groups.google.com/forum/#!forum/joomla-dev-framework Joomla Framework Mailing List]
* [https://groups.google.com/forum/#!forum/joomla-dev-framework Joomla Framework Mailing List]
 
<br>
===== CMS or Framework? =====
===== CMS or Framework? =====
Joomla is a community of developers that are currently working on three projects: the Joomla CMS, The Joomla Issue Tracker and the Joomla Framework. The CMS is the very popular and well known FOSS content management system. The Framework existed within the CMS as a tightly coupled set of utility packages and classes. Eventually developers decided they wanted to work with just those utilities and write new applications not coupled to the CMS. The Joomla Issue Tracker is the first Application built on top of the new Joomla Framework and is currently nearing it's first stable release.
Joomla is a community of developers that are currently working on three projects: the Joomla CMS, The Joomla Issue Tracker and the Joomla Framework. The CMS is the very popular and well known FOSS content management system. The Framework existed within the CMS as a tightly coupled set of utility packages and classes. Eventually developers decided they wanted to work with just those utilities and write new applications not coupled to the CMS. The Joomla Issue Tracker is the first Application built on top of the new Joomla Framework and is currently nearing it's first stable release.


The project now supports all three of these initiatives, as does Google Summer of Code. On our [http://docs.joomla.org/GSOC_2016_Project_Ideas ideas list] you will find projects related to the CMS, the Issue Tracker and the Framework.
The project now supports all three of these initiatives, as does Google Summer of Code. On our [http://docs.joomla.org/GSOC_2016_Project_Ideas ideas list] you will find projects related to the CMS, the Issue Tracker and the Framework.
 
<br><br>
===== Project Timeline =====
===== Project Timeline =====
For a Joomla GSoC student, there are two timelines that a student must be aware of as they are developing their project plan. The first is [http://www.google-melange.com/gsoc/events/google/gsoc2014 Google's own timeline] <!-- UPDATE WHEN AVAILABLE -->. But, because the Joomla CMS has its own specified release cycle, there is also a strong need to be aware of the Joomla release cycle.
For a Joomla GSoC student, there are two timelines that a student must be aware of as they are developing their project plan. The first is [http://www.google-melange.com/gsoc/events/google/gsoc2014 Google's own timeline] <!-- UPDATE WHEN AVAILABLE -->. But, because the Joomla CMS has its own specified release cycle, there is also a strong need to be aware of the Joomla release cycle.
Line 24: Line 24:


If you would prefer to subscribe to the Joomla GSoC 2016 Google Calendar, you may do so here:
If you would prefer to subscribe to the Joomla GSoC 2016 Google Calendar, you may do so here:
<br><br>
<!-- UPDATE WHEN AVAILABLE -->
<!-- UPDATE WHEN AVAILABLE -->
[https://www.google.com/calendar/embed?src=t2cvl5q9gm4nsgfckvtvnsopgc%40group.calendar.google.com&ctz=America/Chicago Joomla GSoC 2014 Google Calendar]
[https://www.google.com/calendar/embed?src=t2cvl5q9gm4nsgfckvtvnsopgc%40group.calendar.google.com&ctz=America/Chicago Joomla GSoC 2014 Google Calendar]
Line 35: Line 36:


NOTE: The above timeline will be updated as more information becomes available, so you may want to subscribe to the calendar using the above +Google Calendar button.
NOTE: The above timeline will be updated as more information becomes available, so you may want to subscribe to the calendar using the above +Google Calendar button.
 
<br><br>
===== Project Proposal =====
===== Project Proposal =====
It is essential for students wishing to be considered for Joomla's GSoC program that they complete and submit a full project proposal. There are some key essential elements we expect to see in the proposal:
It is essential for students wishing to be considered for Joomla's GSoC program that they complete and submit a full project proposal. There are some key essential elements we expect to see in the proposal:
* Full Project Description
* '''Full Project Description'''
** A proposal should detail the project in its entirety. This includes the general goals of the project, the problem the project tries to solve or feature that it adds.
** A proposal should detail the project in its entirety. This includes the general goals of the project, the problem the project tries to solve or feature that it adds.
* Highly Detailed
* '''Highly Detailed'''
** Proposals should be as detailed as possible. This includes being specific with aspects like potential file structures, php class designs with inheritances and even sample use cases.
** Proposals should be as detailed as possible. This includes being specific with aspects like potential file structures, php class designs with inheritances and even sample use cases.
* Sample Joomla Code
* '''Sample Joomla Code'''
** Students should know how to write code for Joomla. This requires some practice. Ideally a student will have written a sample module, component, or plugin on the Joomla CMS, maybe even helped squash some bugs for the Joomla CMS. The sample code will have proper code style and structure and demonstrate an understanding of Joomla's APIs and functions.  
** Students should know how to write code for Joomla. This requires some practice. Ideally a student will have written a sample module, component, or plugin on the Joomla CMS, maybe even helped squash some bugs for the Joomla CMS. The sample code will have proper code style and structure and demonstrate an understanding of Joomla's APIs and functions.  
* Detailed Timeline with Milestones
* '''Detailed Timeline with Milestones'''
** Students should take the time to plan their project in stages, this includes key milestones like discovery, planning, execution, and documentation. The nature of the project will detail sub-tasks or sub-milestones that consist of detailing each part of the project. In addition to this, if the student has information about their personal schedule such as university tests, vacations, or periods where they will be unavailable these dates and times should be noted as well.
** Students should take the time to plan their project in stages, this includes key milestones like discovery, planning, execution, and documentation. The nature of the project will detail sub-tasks or sub-milestones that consist of detailing each part of the project. In addition to this, if the student has information about their personal schedule such as university tests, vacations, or periods where they will be unavailable these dates and times should be noted as well.
* Blog Posts
* '''Blog Posts'''
** Each student is required to write and publish three (3) blog posts on the Joomla Community Magazine. The topics of each blog post can be decided by the student, but a general recommendation would be:
** Each student is required to write and publish three (3) blog posts on the Joomla Community Magazine. The topics of each blog post can be decided by the student, but a general recommendation would be:
*** Introduction to Student & Project
*** Introduction to Student & Project
Line 52: Line 53:
*** Final Project Update
*** Final Project Update


<br>
<!-- UPDATE -->
<!-- UPDATE -->
A full proposal in detail from Diana Neculai is available here. This proposal was submitted and accepted in GSoC 2012:
A full proposal in detail from Diana Neculai is available here. This proposal was submitted and accepted in GSoC 2012:

Revision as of 20:14, 20 January 2016


Welcome to GSoC 2016

This page will aim to be a general informational page for students, mentors and others interested in Joomla's Google Summer of Code Program.

What is GSoC?

Google Summer of Code is a program run by Google for college students interested in contributing to FOSS projects. Visit the Google Melange site to learn more.

Information For Students


CMS or Framework?

Joomla is a community of developers that are currently working on three projects: the Joomla CMS, The Joomla Issue Tracker and the Joomla Framework. The CMS is the very popular and well known FOSS content management system. The Framework existed within the CMS as a tightly coupled set of utility packages and classes. Eventually developers decided they wanted to work with just those utilities and write new applications not coupled to the CMS. The Joomla Issue Tracker is the first Application built on top of the new Joomla Framework and is currently nearing it's first stable release.

The project now supports all three of these initiatives, as does Google Summer of Code. On our ideas list you will find projects related to the CMS, the Issue Tracker and the Framework.

Project Timeline

For a Joomla GSoC student, there are two timelines that a student must be aware of as they are developing their project plan. The first is Google's own timeline . But, because the Joomla CMS has its own specified release cycle, there is also a strong need to be aware of the Joomla release cycle.

To assist in planning a project timeline we have compiled a suggested list of dates and deadlines for students. This includes requirements for all GSoC projects. Please submit a timeline that includes these key deadlines with your project proposal. It is not essential that you follow the same dates listed on the sample timeline, however you must include the milestones and an expected / planned deadline for each milestone.

If you would prefer to subscribe to the Joomla GSoC 2016 Google Calendar, you may do so here:

Joomla GSoC 2014 Google Calendar

NOTE: The above timeline will be updated as more information becomes available, so you may want to subscribe to the calendar using the above +Google Calendar button.

Project Proposal

It is essential for students wishing to be considered for Joomla's GSoC program that they complete and submit a full project proposal. There are some key essential elements we expect to see in the proposal:

  • Full Project Description
    • A proposal should detail the project in its entirety. This includes the general goals of the project, the problem the project tries to solve or feature that it adds.
  • Highly Detailed
    • Proposals should be as detailed as possible. This includes being specific with aspects like potential file structures, php class designs with inheritances and even sample use cases.
  • Sample Joomla Code
    • Students should know how to write code for Joomla. This requires some practice. Ideally a student will have written a sample module, component, or plugin on the Joomla CMS, maybe even helped squash some bugs for the Joomla CMS. The sample code will have proper code style and structure and demonstrate an understanding of Joomla's APIs and functions.
  • Detailed Timeline with Milestones
    • Students should take the time to plan their project in stages, this includes key milestones like discovery, planning, execution, and documentation. The nature of the project will detail sub-tasks or sub-milestones that consist of detailing each part of the project. In addition to this, if the student has information about their personal schedule such as university tests, vacations, or periods where they will be unavailable these dates and times should be noted as well.
  • Blog Posts
    • Each student is required to write and publish three (3) blog posts on the Joomla Community Magazine. The topics of each blog post can be decided by the student, but a general recommendation would be:
      • Introduction to Student & Project
      • Midterm Project Update
      • Final Project Update


A full proposal in detail from Diana Neculai is available here. This proposal was submitted and accepted in GSoC 2012:

http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/dianaprajescu/5629499534213120

Retrieved from "https://docs.sandbox.joomla.org/index.php?title=GSOC_2016&oldid=271744"