Create issue handler webtask for coaching repo

[jayvdb]

Each issue in https://github.com/gsocindonesia/coaching2018 has to be processed, such as adding to the coaching project, checking formatting, adding languages labels, etc.

This can be automated using GitHub issue hooks connected to a http://webtask.io , which can have a private GitHub token to use the GitHub API to read the issue and make changes to the issue. It could also read a Google Doc to use information provided there.

This ensures all issues are processed quickly and methodically/fairly, and the system can be improved upon and reused next year.

This sample acts on GitHub push events, but the same approach can be used for issue events.

Here is a more sophisticated webtask which I've been involved with that may help understanding how to do somethings like secrets.

[ceefour]

the system can be improved upon and reused next year

It's probably a good idea too to have a "meta" documentation about the coaching process, evaluating what Wikimedia and BesutKode (both GCI and GSoC) and TelU have been doing ... supported with data, and extract the core best practices with sound rationale for each. There will be hundreds of things learned for sure, but compiling that into a systematic and structured methodology will be a challenge. Probably not a task for students, but for me and you and interested lecturers will be a fun project (even if not too rewarding (yet) economically wkwkwk)

[ceefour]

At least I'm now a bit qualified to write a guide on How to Make 211 Informatics and Non-Informatics Students Even Those Without A GitHub Account Come Together to A Room to Learn About Google Summer of Code. For a start, that credential is not so bad. 😉