GSOC proposal deadline passed today, quite the learning process for us. Proposal process seems nice for larger projects, and having the mentor-student relationship could be a way to better hang on to contributors in general. A lot fail to connect with the game, the issues, or the community, for a variety of reason, and fade away again. We got thirty five proposals while as a 1st year org we are likely to only get 1-2 slots, maybe 3 if we get lucky. Some proposals are duplicates (3+ MOO, 3+ Anatomy, 4+ particle system) but there are still going to be good proposals on topics we won't have slots for Also @Rostyslav Zatserkovnyi came across up-for-grabs.net (#2244) recently, one of the nice sites where you can get your easy / friendly / welcoming open source tasks listed to help attract new contributors So maybe rather then "Contributor Friendly" and "GSOC" with the two able to overlap instead we do: Bite-size - small issue fitting up-for-grabs.net's definition (few hours, fairly easy to do). Doable with general assistance on IRC/forum/GitHub Mentor-size - medium issue likely to take one to a few weeks of effort with advice and assistance from a casual mentor. Or doable solo by a somewhat skilled contributor. GSOC - large issue suitable for a summer and inclusion on the GSOC ideas list, with assistance of a veteran mentor. Alternatively could be broken into a series of mentor-sized tasks. Unsure of naming. "up-for-grabs" doesn't work well with several sizes of "contributor friendly" items in different labels. Edit: There is a new thread on overall organizing with forum, GitHub issues, labels, ZenHub, Trello, etc To better organize these labels we'd give push access to the engine repo to a few more people like @Rostyslav Zatserkovnyi specifically for label and issue editing rather than code pushing (the two roles are in the same permission at present. May also fit well with the Hunter team badge here on the forum, while SpecOps could be veteran mentors) If a new contributor desires to try a mentor-sized issue, having done a bite-sized issue or two, they register their interest on the issue and get assigned to it. Hopefully we'll have a casual mentor willing to help out both plan the change in more detail and assist with any issues (along with IRC etc as usual). If not may have to wait or try to solo it. Probably organize in a forum Suggestion thread? Or on GitHub? Too notification-spammy? Those issues would likely be prime candidates for code bounties, and could probably also be considered mini-projects for the student as well as mentor with some sort of formal acknowledgement that work was done on success. That could fit well on a resume, LinkedIn "project", and so on, which the mentors could help formulate. And after completing one the student could then become a casual mentor themselves. For our many current GSOC students maybe breaking apart some of the unpicked GSOC items into these new mentor-sized issues could help still provide an interesting learning experience for those eager to still pursue the work even without the GSOC stipend (any code bounties may also help a little there). It just might take a little longer to get casual mentor attention, depending on how many more mentors we could recruit. On a related note actually assigning more issues to people may help stay organized and motivated as well. It could also help prevent overlap/rework. We had a couple GSOC items approached by non-students for work and don't really have a plan for handling that. We aren't supposed to reveal details on student projects till April 22nd. Maybe new interested contributors can just spend the time learning the base code and if the item gets picked chip off a piece the student proposal doesn't include. Thoughts, interest, volunteers?