FOSS Events planner

[skade]

Project Lead: @skade @mattgathu @sebasmagri @celaus

Mentor: @schae234

Welcome to OL6, Cohort A! This issue will be used to track your project and progress during the program. Please use this checklist over the next few weeks as you start Open Leadership Training :tada:.

---

Before Week 1 (Sept 11): Your first mentorship call

• [x] Complete the OLF self-assessment (online, printable). If you're a group, each teammate should complete this assessment individually. This is here to help you set your own personal goals during the program. No need to share your results, but be ready to share your thoughts with your mentor.
  • [x] @skade
  • [x] @mattgathu
  • [x] @sebasmagri
  • [x] @celaus
• [x] Make sure you know when and how you'll be meeting with your mentor.

Before Week 2 (Sept 18): First Cohort Call (Open by Design)

• [x] Complete Assignment 'Write Your Vision or Mission Statement'. Leave a comment on this issue with your draft vision statement & be ready to share this on the call.
• [x] Watch 'Mozilla & Working Open'.
  • [x] @skade
  • [x] @mattgathu
  • [x] @sebasmagri
  • [x] @celaus
• [x] Check the Syllabus for notes and connection info for all the cohort calls.

Before Week 3 (Sept 25): Mentorship call

• [x] Look up two other projects and comment on their issues with feedback on their vision statement.
• [x] Complete your Open Canvas (instructions, canvas). Comment on this issue with a link to your canvas.
• [x] Start your Roadmap. Comment on this issue with your draft Roadmap.

Before Week 4 (Oct 2): Cohort Call (Build for Understanding)

• [x] Look up two other projects and comment on their issues with feedback on their open canvas.
• [x] Pick an open license for the work you're doing during the program.
• [x] Use your canvas to start writing a README, or landing page, for your project. Link to your README in a comment on this issue.

This issue is here to help you keep track of work during the first month of the program. Please refer to the OL6 Syllabus for more detailed weekly notes and assignments past week 4.

[skade]

I updated the issue a little and added individual checkmarks to the parts where individual action is needed.

[celaus]

Done the things, but can't edit your post @skade :+1:

[mattgathu]

I have done **Before Week 1 (Sept 11): Your first mentorship call***

[celaus]

Mission Statement draft

[celaus]

Mission Statement

We are working as the Rust community events team to create a set of open event planning guidelines so that tech community organisers can plan and organise tech events, on their own, successfully.

[skade]

Open Canvas here:

https://docs.google.com/presentation/d/1Tq5VufG2SB1QIcsvCJOY_p7WMNSwqTC73Je-MBy2rk0/edit?usp=sharing

[mattgathu]

Here is the draft roadmap:

FOSS Events Planner Roadmap

The FOSS events planner is meant to be a tool to help tech community leaders successfully build their own flexible events. It will highlight the many things that are possible and how to plan them.

We are working as the Rust community events team to create a set of open event planning guidelines so that tech community organisers can plan and organise tech events, on their own, successfully.

Milestones

software development goals, learning resources you’ll create, events or meetings you plan to hold, campaigns you’ll run.

Name

Come up with a catch name for the project.

Tasks:

• Suggest names
• Pick a name

Website

Have a teaser page for the project and register a domain.

Tasks:

• Register a domain
• Design Website Content
• Launch website

Learning Resources

Events and meetings

Campaigns

Other Goals / Milestones (to consider)

Build a progress/issue tracker.

Prepare a kanban-style boards for issue and progress tracking. This can be done using Github's Projects feature on the events planner repository.

Create and test prototypes.

A prototype is an early, unpolished version of your project or a feature of your project, created specifically for testing purposes.

User Testing

No matter what form your prototype takes, it should be something users can react to, and their feedback should help answer questions or define a direction for further work

There is a pull request to add it to the FOSS repo. We can improve on it - it needs more ❤️

[estherhersh]

Hey! I'm a big fan of your project and your canvas seems really well thought out. I'm curious how you would track the number of events organized based on your resources.

[celaus]

@estherhersh So far the plan is to rely on the organizers coming back and sharing their outcomes by contributing :smile:

[celaus]

README

[ghost]

HI @skade @mattgathu @celaus. Congrats on your project! :)

Feedback regarding your Open Canvas:

• Problem: The last sentence of the problem seems a bit generic to me. Maybe you can edit it with a specific problem that relates to your solutions.
• Resources: Do you mean people who're experienced with information design and running open events when you say "information design" and "experience with running open events"?
• Contributor Channels: I think you can also add LinkedIn where you can search with keywords and filters for people who're experienced with running Open Source conferences. You can also add websites such as: https://opensource.com/resources/conferences-and-events-monthly