search

coala / meta

A repository for non-code activities, such as engagement initiatives, and other meta issues
6 stars 5 forks source link

GSoC milestone tracking #107

Open jayvdb opened 6 years ago

jayvdb commented 6 years ago

As a yearly event, we need to build systems that streamline our GSoC processes and systems. We currently use GitLab repositories for tracking milestones.

We have https://gitlab.com/coala/GSoC-2017/ and https://gitlab.com/coala/GSoC2016, with slightly different repository names. We should use a consistent naming convention so that these gitlab tracking repos can be easily accessed by other systems. e.g. https://github.com/coala/community/issues/59

And next year, will we create another repo? Or do we rename the 2017 repo to a generic name , or create a generic "GSoC tracking" repo for all future gsoc? @nkprince007 found issue moving may be an option (however based on https://gitlab.com/gitlab-org/gitlab-ce/issues/20372#note_29025219 it would be wise to test moving issues first, to make sure the original author & date is retained)

I find one repo per year to be undesirable, as each repo wont grow beyond that short period of time, so there is little inertia and motivation to invest time into it beyond its limited purpose.

The 2017 repo was abandoned after gsoc until I cleaned it up before GCI.

See https://gitlab.com/coala/GSoC2016/issues/89 for more info about that one. It is likewise abandoned.

jayvdb commented 6 years ago

Worth exploring if there are other approaches we might use to track milestones; cloud project management type tools. But only if it is better than GitLab, and only if they provide better APIs than GitLab, which can be supported via IGitt (see https://gitlab.com/gitmate/open-source/IGitt/issues/62 )

jayvdb commented 6 years ago

Based on '10' https://github.com/coala/coala/wiki/GSoC-2017-Application#anything-else-we-should-know-optional , and there were 8 in 2016, I assume there were 2 in 2015. Is there any documentation about those two?