dataforgood-norway/season-1

🍂 Gathering infos and tasks on how we organise our first season of projects

season-1's Issues

Advertise workshop 1 (Brainstorm and define each project)

Book a space

cf StartUp Lab if we are many or Computas open space

Minutes Meeting 2018-08-21

This week, we finalized the text to use as advertising for the datathon.

We didn't get much time to share all the tasks to do before the kickoff among us, but we managed to share a few.

Action points:

• Check the board to see what's left (tasks unassigned yet).
• Help by taking one of these unassigned tasks or join forces with others.

Any questions? Join the team on slack and talk to us in the #organisation channel

Prepare "stickers" to help people categorize themselves before building teams

Those stickers will help visualize if a team is balanced in terms of skills:

• Colors may not be sufficient to distinguish between: "Idea provider", "developers", "designer", "marketer"
• Need some funny names to write on. I am sure creativity won't be a problem here 😜

Add a "team" section to the season webpage, and a Community page including it there too

Add more organizer's email to the contact mailing list

[email protected] sould be accessible by more organizers.
But as it is set now, everyone need an email ending with the dataforgood.no domain name, which costs a lot and is not necessary.

The group address has to change somehow...

Advertise the season & kick-off meeting

• collaborate on the text on a GDoc before next meeting
• design poster
• list channels to share it: universities, engineering schools, hack4no, social media, Tekna, ...
• contact meetup organizers

Learn from this season: By what date each project has Issues/Milestones/Projects followed on GitHub?

Make simple guidelines for projects and code-of-conduct obvious on the website

Can simply be re-used from DataFordemocracy or DataForgod-France or ...
But that is important like Geir mentioned, to have a clear statement about different subjects like licensing our work (MIT, gnu, ...), how we interact with for-profit companies, sponsorship or not and why, ...

Advertise Workshop 2 (project management methods & tools)

Prepare prizes :)

Minutes Meeting 2018-08-15

Based on this draft, we started planning the first season:

• a 3-months session starting with a Kick-off meeting on September 11th 2018 (Tuesday)
• finishing with a Final demo day on November 27th
• we agreed to stick to Tuesdays (the working space still need to be confirmed)
• Workshop 1: Defining project's details, as early as September 18th
• Workshop 2: mini-hands on on project management tools (Trello, Github, ...) on September 25
• we will have teams of mentors following the projects after every 2-weeks sprint. Possibly leading to additional technical workshops if needed.

The few tasks we talked about have been written as issues in this same repo.

We can now:

• share data on Google Drive in this folder
• share events on Google Calendar following these instructions: #5

The action points for the next meeting is just to write the text advertising the session, and we will start adding tasks and distribute them among us at the next meeting: Tuesday, august 22nd at 5:30pm, pub of Socentral, Oslo

Prepare a project template for workshop 1

• prepare a sheet with key infos to define about a project
• this workshop will probably be a "brainstorming phase" where each team will come up with:
  • a clear challenge to solve,
  • a vision of what would solve it,
  • the goal of the project which is one implementation of that vision,
  • and how we can measure the impact of the project.

There is maybe known methods to help derive such information for which we could find mentors. Otherwise common sense will apply :)

Prepare paper sheets with infos & our plan for the season to distribute during kick-off day

This means starting a Google Docs which will summarize important infos:

• write the schedule for season
• actions points: Join a team anytime by contacting the project leader, check the status of the project, help as you can (programing, ideas, deisgn, project management, coffee/cake... )
• FAQ: how to join on Slack? on github? link to the webpage of the Datathon
• ....

Detail the agenda of the kickoff meeting

• How long?
• who will be speaking on what?

possible agenda:

• Prepare paper sheets with our plan of the season to distribute
• short presentation of D4G (especially as probably hosted by Data Science meetup where people may join not purposefully for hearing us)
• Present how this first season will be held (when start/end, how to join a team, how we will work, ...)
• Ask how many people would be interested in pitching a project idea
• We let people pitch and adapt the duration to the number (same apply to the existing project we will present too). Keep 1min for 1 or 2 questions after each pitch. (one chairman needs to monitor the time and buzz as in hack4no!)
• Give some time to let people talk to the "pitchers" and let them join a project
• wrap up by collecting the "project cards"
• Remind about the coming workshop one week after!

Create "project cards" to distribute to the Pitchers at kick-off meeting

Collect the work done in workshop 1 & 2 on the season's page and on the home page

Create shared GDrive Folder with all coming documents

Here is the root folder:

https://drive.google.com/drive/folders/15E7e6DE3c7n9-4qQGXmO2OayYZQ0zzx_?usp=sharing

(The original folder was just share in view mode, I hope it is working now, otherwise let me know )

Advertise season closing

• FB event
• Data science meetup?
• flyers?

Webpage about season 1

From such website: https://www.datasciencesociety.net/datathon/, what I like is:

• The schedule: for finding easily the important dates of the event
• The button to show your interest by "Booking your spot" which can help us get an idea of many will come for the next seasons.
• the FAQ:
  • What is the difference between our season event and a hackathon?
  • How does the "season datathon" works?
  • I don’t have a team, yet. Can I take part in the Datathon?
  • How do I choose a case to work on?
  • How will my solution be evaluated?
  • Can I use the data & algorithms developed afterwards?
  • Can I join the Datathon virtually and how?
  • How do I present my solution if I participate virtually?
  • How do I form a team if I am participating virtually?
  • When does the registration end?
• also the "general terms of participation" section could make sure we clarify that ideas and code generated follows the MIT or gnu licence, ...

Contact DS Meetup organizers to ask for hosting the kick-off event

Normalize description of existing projects & project ideas proposed for this season

already 5 projects:

• OrcaTag
• Vertical Farming
• Ratifications of UN Treaties
• Teaching sessions by GirlsCanDoIT
• Teaching sessions by Ali

Create shared Google Calendar to help sync the team

Communicate about the goals & objectives of each project (social media)

Prepare cheatsheets and mini hands-on for Workshop 2 (project management methods & tools)

• which method to present (Agile: kanban/scrum, Interaction Design), who speaks about it?
• can we come up with a simple cheatsheet with videos and easy steps?
• do we ask participants to create accounts before-hand:
  • Github most probably to have at least a list of the team members,
  • Trello if not happy with the Github project boards?
  • UX tools e.g. Sketch or InVision?
  • Git for developers eager to learn and use it?

Prepare evaluation criteria

• select max 5 criteria
• prepare voting tool (cf Kahoot or survey monkey)
• prepare paper sheets to take notes on each project before voting at the end

Prepare an agenda for the Final Demo Day

How to use/involve Sci-code to help our teaching/mentoring sessions?

• ask Simen Fossnes for a demo to see the benefit and how to include it in our courses

Evaluation of projects

The criteria for evaluating each project and possibly define winner(s) needs to be defined in advance. These could include:

• relevance of the project (in terms of impact, challenge solved ,...)
• Project methodology (well defined, interaction with experts and beneficiary, possible existing solutions, ...)
• Final solution (easy to use, well designed)
• Presentation skills (lively speech)
• ...

We might or not give explicit weights on these various criteria as we might do it live during the event