Join the core team for 2 days of concentrated effort on the next generation of the Elgg framework.
When: Friday, September 23rd - Saturday, September 24th
Where: Online (http://gitter.im/Elgg/Elgg)
What: Resolve issues on the interim and 3.0 milestones
Who: Developers interested in contributing to Elgg core
We will have much of the core team available on these days so that pull requests (PRs) can be reviewed quickly and merged. We hope to make significant progress paying down technical debt and making Elgg a more modern, testable, lower-maintenance PHP framework.
If you’re new to open source development this is a great time to jump in and get assistance through the process of making your first PR. We have a list of easy tickets that we think would be good fits for newcomers.
Claim your issue now if you already know what you want to work on. You can self-assign or just request to be assigned on the issue itself and someone will assign it to you. This way we can avoid duplication of effort on the days of the hackathon and gauge interest in participation. Some of the tickets might even require preparation/design beforehand, so it may help to post your plans for how to address the issue before the hackathon to get some early feedback and make sure the core team agrees with your direction.
We would also like to give some love to our community site. We have some pending PRs, and we are open to other contributions. Feedback and ideas from the community members are more than welcome.
I’m not a developer. Can I still participate?
Yes, please! We’d really appreciate your help in:
Testing open issues to see if they’re still reproducible/valid, or adding more information that would help us get them resolved quicker
Reviewing our documentation to make sure it is up-to-date, thorough, and helpful. Report any bugs that you find or suggestions for improvement, missing docs. Maybe even write some of your own!
Bumping open pull requests and issues that you’d like to see get more attention
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by Raül Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
Is there more information about this available?
How do we join?
What kind of additional information would you like to receive?
It's a virtual hackathon. You can join by hacking remotely and chatting with everyone on gitter channel.
Thanks! Let me know if this is right.
We can fix issues in the 2.x branch. Some issues are marked as "easy" or "hackathon"
What about other issues: https://github.com/Elgg/Elgg/issues?
For the 3.0 Milestone, we can fix issues in the master branch.
https://github.com/Elgg/Elgg/milestone/78
Finally there are also open Issues for the Elgg.org site but lot of them the are more than a year old. Are they still good?
https://github.com/Elgg/www.elgg.org/issues
I will try to participate by installing branches, looking at issues and testing. Maybe make fixes. I'm also trying to convince other developers.
Any contributions are welcome. Generally speaking we don't have a specific roadmap, the core team tends to work on issues that are closer to their heart. Feel free to pick anything that you think would be fun to work on and would benefit Elgg at large. Feel free to ask questions on Github if anything is unclear - we do our best to keep the discussion references intact so you can trace things back to their origins. We do however have a number of issues that need triaging - they were fixed within another pull request but were not marked as resolved, sometimes there are duplicate issues. And of course you don't have to wait for the hackathon to get started - for Steve and I it's a perpetual hackathon.
The hackathon is in full swing. Join us at https://gitter.im/Elgg/Elgg
May be helpful if you want to submit changes: https://elgg.org/pages/view/1123473/preparing-to-develop-elgg-patches, and of course the Contributor Guide.
Also note we can't accept GPL or other "copyleft" code except in plugins (/mod folder) as the engine is available as MIT.