This repository has been archived by the owner on Nov 1, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 58
GSoC 2016
Olivier Paroz edited this page Mar 7, 2016
·
25 revisions
Gallery has a number of projects up on the "ideas list" for this year's GSoC, but any feature request already mentioned on Github can be used as a base for a project and candidates are welcome to add their own so that they can be discussed among community members to see if it would fit with Gallery's goals.
- Read the GSoC manual for students. That way, everybody will be on the same page in terms of expectations
- Use the issue defined for each project to ask your questions. That makes it easier to share answers and changes with everybody
- Bear in mind that not all projects are well defined. Some are rough ideas and a good opportunity for you to put on your strategic cap
- Try to fix issues labelled "Junior job" on your own. Read comments in the code, learn about the structure, etc.
- Don't hesitate to ask questions if you're stuck, even if it's while fixing a "Junior job"
- The maintainer prefers long term solutions over quick hacks, because it makes it easier to maintain the project. Take the time to learn the app's architecture and don't hesitate to suggest improvements
- Set up a development environment with
core
and Gallery. You have to be able to load the app to be able to debug it - Be familiar with an IDE letting you work with both PHP and Javascript files. We recommend PHPStorm which is free for students
- Be familiar with git. Pulling, rebasing, squashing, etc.
- Set up configuration files both in the top album as well as in sub-albums in order to be able to test the configuration features
- You will be expected to write and run tests both in PHP and Javascript
- PHP Composer
- ownCloud AppFramework
- Codeception and/or PHPUnit
- Bower
- jQuery
- Backbone
- Handlebars
- General
- Installation
- Configuration
- OCC commands
- Developers