Join the core team for 2 days of concentrated effort on the next generation of the Elgg framework.
Where: Online (http://gitter.im/Elgg/Elgg)
What: Resolve issues on the 2.0 milestone
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 2.0 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.
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.
Yes, install the latest stable version of Elgg, choose an open issue and try to reproduce it.
What do you mean?
Ah, good question. For that you'll need access to command line. First you need to get the code from Github using git and then install the core dependencies using composer.
I can give more detailed instructions in a separate thread in case you have command line access and you're willing to learn how to use git and composer. :)
I think this would not be such a bad idea for devs not using git and devs to be :)
Michele, does that mean you don't have command line access or that you're not willing to learn awesome git magic? ;)
Dries is interested, so I'm going to make a very short tutorial in any case. :)
We at ColdTrick will open our office for everyone who needs a workspace on Friday from 09:00 +1 GMT until 23:00. Free drinks included!
So if you live in the neighborhood of Enschede, The Netherlands, you are more then welcome!
https://www.google.nl/maps/place/ColdTrick+IT+Solutions/@52.222909,6.871894,17z/data=!3m1!4b1!4m2!3m1!1s0x47b81392f6f541e5:0x8fc220d255f9731e
Your excitement over that made me smile! So you're going to be around for the Hackathon then?
@Juho Jaakkola:
Where can this separate thread (or your help to Michele) be found?
@basti.wiesn I've added some basic commands and instructions here: https://community.elgg.org/pages/view/2104008/command-line-cheat-sheet
I'll add more subpages later.
to confirm, I don't see a 2.X branch so we should PR against master ?
Yup, master currently stands for 2.x as there's no point in having 3.x in development at this point. We only create branches for less recent lines of development.
@all: Sadly, I can't participate myself in the hackathon as I'm away over the weekend. But I wish you all a lot of fun! I'm curious to see the open issue counter next week. ;-)