--- tags: TO-DO --- # CodeRefinery TO-DO list :::info - This TO-DO list is open for CodeRefinery members and the community. - Editing is possible for signed-in users - Link to this document: https://hackmd.io/@coderefinery/CR_TO-DO - You can add headlines to this document and arrange it in topics - A topic should have some info/goal - Members or CodeRefinery HackMD organisation can add more HackMD documents with `tags: TO-DO` (see the top) and link from here to keep this document cleaner - When you choose to work on a task, please add your initials or tag yourself. - If two people are working on same task please find a way to coordinate - After a task is ready, check the tickbox ::: [toc] ## Good first issue :::success Check these out if you are just starting or need something to get brains working again :relaxed: ::: - [ ] List TO-DO items from [the Kick off discussion](https://hackmd.io/@coderefinery/kickoff2022) to here - [ ] Browse coderefinery.org and open issues about problems or unclarities you find ## Website Issues are at https://github.com/coderefinery/coderefinery.org Most important: - [ ] Describe better where we want to arrive at - [ ] Describe better how somebody or some org can help - [ ] Add page for "staff"; with link to manual (task from kickoff) - [ ] Add ICS aggregator for calendars (task from kickoff) ## Manuals - [ ] New page in manuals under “Workshop roles” that explains evaluation process (certificates) (task from kickoff) ## Onboarding: make it easier to join for people and organizations - [ ] List the steps that need to be done by a new person - [ ] organizational chart, define what is staff (?) (task from kickoff) ## Workshop Sep 2022 - [ ] Convert https://hackmd.io/@coderefinery/2022-sep-ws-planning to a manual page (playbook) for future workshops and then delete https://hackmd.io/@coderefinery/2022-sep-ws-planning (SW working on it, collaborators welcome) -> https://github.com/coderefinery/manuals/pull/220 - [ ] Port changes done to workshop page back to template: https://github.com/coderefinery/template-workshop-webpage/issues/59 - [ ] Report how many people registered and how many viewed. It may require adapting @MatiasJJ - https://coderefinery.org/about/statistics/ - https://coderefinery.org/workshops/past/ - @MatiasJJ has started analysis in a repo: https://github.com/coderefinery/workshop-stats - [ ] collect relevant data or comment what is still needed - [ ] Make sure past events do not show up under future events ## Blog posts and outreach - [ ] Blog post on what help we need - [ ] Link this HackMD - [ ] Blog post summarising [the Kick off discussion](https://hackmd.io/@coderefinery/kickoff2022) - [ ] Write and send a newsletter - [ ] Decide what to do with tinyletter (many subscribers but we don't use it) and coderefinery-announce mailing list (extremely few subscribers) - [ ] Schedule one of our future team meetings to focus on improving twitter outreach (collect posts, learn about best practices) - one-liner per week a la "terminal-Tuesday" or shell-one-liners - at next development day ("social media day"): come up with 20-30 and prepare and automate every Tuesday ## A great endeavour: Collaborative Training Portfolio Please describe here the goal and context of this work to make it more manageable - [ ] Help to get an overview of courses by filling some in https://hackmd.io/@coderefinery/collaborative_course_portfolio `@anyone` ## Done - [x] Link this HackMD ("how can i help out") visible on website (SW)-> https://github.com/coderefinery/coderefinery.org/pull/702 - [x] CarpentryCon session needs to be made visible (notes and video link) notes (SW)-> https://github.com/coderefinery/coderefinery.org/pull/703; where is video? - [x] Add [Calendar](https://coderefinery.org/calendars/) to "joining coderefinery" page somewhere (task from kickoff) (SW)-> https://github.com/coderefinery/coderefinery.org/pull/704