GSOC 2016 Project Ideas: Difference between revisions
From Joomla! Documentation
Puneet.0191 (talk | contribs) |
Puneet.0191 (talk | contribs) |
||
| Line 175: | Line 175: | ||
---- | ---- | ||
====Project IV: | ====Project IV: Embedded Content Done Right! ==== | ||
<table border="0" style="width:100%"> | <table border="0" style="width:100%"> | ||
| Line 182: | Line 182: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Develop a unified framework for adding any form of embedded content. A standardised syntax for embedded content tags would be used to call a content plugin that would parse the tag and call plugins in a new embed group to return the appropriate embed code. | ||
This builds on the idea of oembed(http://oembed.com/) but with the capability of overcoming the problems of invalid content associated with some oembed providers. It is not restricted to oembed providers and can be used to embed any kind of content for which an embed plugin can be written. Support for new data sources can be added by writing an embed plugin, making it easy for site builders to integrate new embed sources to their sites. We would gain a powerful, extendable method of embedding content anywhere that supports content plugins.</td> | |||
</tr> | </tr> | ||
</table> | </table> | ||
| Line 190: | Line 192: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>An appropriately coded set of plugins that could be merged into Joomla 3.x, including a selection of embed extensions for popular services such as YouTube, Vimeo, Slideshare, Twitter, Facebook, MediaWiki, etc. | ||
Bonus points for writing a JavaScript extension for TinyMCE to make it even easier to embed content. | |||
Code must be accompanied by documentation in the form of wiki pages and full help screens. | |||
Code must be accompanied by appropriate tests.</td> | |||
</tr> | </tr> | ||
</table> | </table> | ||
| Line 198: | Line 206: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>PHP, Joomla CMS</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
| Line 206: | Line 214: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Medium</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
| Line 214: | Line 222: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Ashwin Date, Ashan Fernando</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
| Line 220: | Line 228: | ||
[[Image:Gsoc2016.png|50px|center]] | [[Image:Gsoc2016.png|50px|center]] | ||
---- | ---- | ||
====Project V: Name ==== | ====Project V: Name ==== | ||
Revision as of 05:37, 20 February 2016

Welcome to GSoC 2016 Ideas Page
Welcome to the Joomla! Google Summer of Code (GSoC) 2016 project ideas page. As we move forward with the 2016 version of the Joomla! GSoC, we will post ideas that have been submitted to the GSoC Team below.
Please keep in mind that projects need to be realistically something that is able to be functionally completed by a student working full time for about eight weeks. Thanks!
If you are interested in participating as a student please review the materials on applying that are available at Google. We strongly encourage you to ask questions about process and ideas on our joomla-gsoc mailing list.
Guidelines for sending proposal are present on our GSoC Home Page
Find examples of other years at https://docs.joomla.org/GSOC_2014_Project_Ideas
Idea Pool
Joomla CMS Ideas
Project I: Improved multi-lingual content management
| Project Description: |
|---|
| The idea is that when users want to translate content items on a multi-language site, they can have the articles side-by-side (dual-pane). This way you don't have to switch back and forth between articles. Respect also the ACL settings. So someone assigned for Dutch cannot translate any French documents for example. |
| Expected Results: |
|---|
| A dual-pane translation screen An ACL setting for allowing access to language based articles |
| Knowledge Prerequisite: |
|---|
| PHP, Joomla CMS multi-lingual system, JavaScript, Joomla ACL |
| Difficulty: |
|---|
| Medium to Hard |
| Possible mentors: |
|---|
| Jean-Marie Simonet, Achal Aggarwal |

| Brief explanation: |
|---|
| There is currently no easy way to share a draft version of an unpublished article with people who do not have Administrator access. This project would add elements to the Articles: Edit user interface that would support the generation of a shareable link that would allow those with the link to view a draft version of an article. This project would be a complete new feature that could be merged into Joomla 3. |
| Expected Results: |
|---|
| The details of the user interface would be subject to change/discussion, but could look something like the following:
A new "Save as Draft" toolbar button on the Articles: Edit page. When clicked the article will be saved as a draft in the content version history. The version history page will need to be modified to show this special version of the article. A new "Share" toolbar button on the same page. When clicked, the draft version of the article opens in a new tab with a special URL which can be copy-pasted so that the draft may be shared prior to publication. Bonus points for adding a "Preview" toolbar button that will open a new browser tab with a preview of the article currently being edited, without needing to save the article first. Code must be accompanied by documentation in the form of wiki pages and full help screens. Code must be accompanied by appropriate tests. |
| Knowledge Prerequisite: |
|---|
| PHP, Joomla CMS |
| Difficulty: |
|---|
| Medium |
| Possible mentors: |
|---|
| NA |

Project III: Administrator Menu Editor
| Brief explanation: |
|---|
| This has been discussed at some length here: https://issues.joomla.org/tracker/joomla-cms/5492 |
| Expected Results: |
|---|
| An appropriately coded extension that could be merged into Joomla 3.x.
Code must be accompanied by documentation in the form of wiki pages and full help screens. Code must be accompanied by appropriate tests. |
| Knowledge Prerequisite: |
|---|
| PHP, Joomla CMS |
| Difficulty: |
|---|
| Medium |
| Possible mentors: |
|---|
| Tharuna Balaji |

Project IV: Embedded Content Done Right!
| Brief explanation: |
|---|
| Develop a unified framework for adding any form of embedded content. A standardised syntax for embedded content tags would be used to call a content plugin that would parse the tag and call plugins in a new embed group to return the appropriate embed code. This builds on the idea of oembed(http://oembed.com/) but with the capability of overcoming the problems of invalid content associated with some oembed providers. It is not restricted to oembed providers and can be used to embed any kind of content for which an embed plugin can be written. Support for new data sources can be added by writing an embed plugin, making it easy for site builders to integrate new embed sources to their sites. We would gain a powerful, extendable method of embedding content anywhere that supports content plugins. |
| Expected Results: |
|---|
| An appropriately coded set of plugins that could be merged into Joomla 3.x, including a selection of embed extensions for popular services such as YouTube, Vimeo, Slideshare, Twitter, Facebook, MediaWiki, etc.
Bonus points for writing a JavaScript extension for TinyMCE to make it even easier to embed content. Code must be accompanied by documentation in the form of wiki pages and full help screens. Code must be accompanied by appropriate tests. |
| Knowledge Prerequisite: |
|---|
| PHP, Joomla CMS |
| Difficulty: |
|---|
| Medium |
| Possible mentors: |
|---|
| Ashwin Date, Ashan Fernando |

Project V: Name
| Brief explanation: |
|---|
| Texto |
| Expected Results: |
|---|
| Texto |
| Knowledge Prerequisite: |
|---|
| Texto |
| Difficulty: |
|---|
| Texto |
| Possible mentors: |
|---|
| Texto |

Project VI: Name
| Brief explanation: |
|---|
| Texto |
| Expected Results: |
|---|
| Texto |
| Knowledge Prerequisite: |
|---|
| Texto |
| Difficulty: |
|---|
| Texto |
| Possible mentors: |
|---|
| Texto |

Project VII: Name
| Brief explanation: |
|---|
| Texto |
| Expected Results: |
|---|
| Texto |
| Knowledge Prerequisite: |
|---|
| Texto |
| Difficulty: |
|---|
| Texto |
| Possible mentors: |
|---|
| Texto |
| Idea Submitted By: |
|---|
| Texto |

Project VIII: Name
| Brief explanation: |
|---|
| Texto |
| Expected Results: |
|---|
| Texto |
| Knowledge Prerequisite: |
|---|
| Texto |
| Difficulty: |
|---|
| Texto |
| Possible mentors: |
|---|
| Texto |

Project IX: Name
| Brief explanation: |
|---|
| Texto |
| Expected Results: |
|---|
| Texto |
| Knowledge Prerequisite: |
|---|
| Texto |
| Difficulty: |
|---|
| Texto |
| Possible mentors: |
|---|
| Texto |

Project X: Name
| Brief explanation: |
|---|
| Texto |
| Expected Results: |
|---|
| Texto |
| Knowledge Prerequisite: |
|---|
| Texto |
| Difficulty: |
|---|
| Texto |
| Possible mentors: |
|---|
| Texto |

Project XI: Name
| Brief explanation: |
|---|
| Texto |
| Expected Results: |
|---|
| Texto |
| Knowledge Prerequisite: |
|---|
| Texto |
| Difficulty: |
|---|
| Texto |
| Possible mentors: |
|---|
| Texto |

Project XII: Name
| Brief explanation: |
|---|
| Texto |
| Expected Results: |
|---|
| Texto |
| Knowledge Prerequisite: |
|---|
| Texto |
| Difficulty: |
|---|
| Texto |
| Possible mentors: |
|---|
| Texto |
| Idea Submitted By: |
|---|
| Texto |

Issue Tracker Ideas
In addition to the Joomla CMS, the Joomla Project also maintains a piece of software called "JIssue tracker". This is Joomla's issue tracker which handles how bugs in the CMS are identified and fixed. The Issue Tracker relies heavily on Joomla's own framework packages.
Visit the Joomla Issue Tracker
There are two major enhancement projects for the issue tracker. NOTE: Because each of these projects are 'smaller' in scale, students should plan to implement both features as a single project during the GSoC period.
For more information please see this mailing list discussion