I’ve started a new thread to follow on from the initial conversation we had about getting into Google Code-In.
So, we’re in! But this is just the beginning! We have 4 weeks to prepare everything needed before the kick-off on 28th November!
Next steps as I see it are as follows. I’ve put names next to those.who have already offered, but
- Invite mentors to the Code-In site (popey)
- Find more mentors to help (everyone)
- We need to spread the load among mentors, and ensure we have backups for when mentors are on vacation ( / etc) or unavailable ( / ️ )
- Create tasks (everyone/mentors)
- We need a minimum of 75, but in all likely-hood need way more than this.
For those creating tasks, below is the data needed, bear this in mind. I have mad a template spreadsheet you can copy and link to if desired. There’s a sample task in there to give you an idea of how it may look. If you’d rather not use Google Sheets (for whatever reason) then feel free to use that as inspiration, and submit yours in csv or some other sane format.
- Title - a short title for your task - 200 characters
- Description - Describe your task in as much detail as possible. May include [limited Markdown]
(https://developers.google.com/open-source/gci/help/markdown) - 1500 characters
- Instance count - Increase this value instead of making duplicate tasks. This task can be claimed by this many students simultaneously. Each student has an independent instance. If an instance is completed, that reduces the number available to claim.
- Time to complete (in days)
- External URL - Optional link to external bugtracker or wiki
- Beginner task - toggle
- Categories - Code / User Interface / Documentation & Training / Quality Assurance / Outreach & Research
- Tags - A few keywords that describe this task. It is OK to include programming languages and technologies here. Example: C++, Video, Optimization. Press Tab or Enter after each item. - up to 5
- List of mentors for the task
Let’s get started!
Any questions, just ask!