From c79dd8ff0201dcfb39471ec7c026207a3694fdd1 Mon Sep 17 00:00:00 2001 From: Matt Gathu Date: Thu, 27 Sep 2018 19:04:58 +0200 Subject: [PATCH 1/2] create draft roadmap --- roadmap.md | 60 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 60 insertions(+) create mode 100644 roadmap.md diff --git a/roadmap.md b/roadmap.md new file mode 100644 index 0000000..3b8130d --- /dev/null +++ b/roadmap.md @@ -0,0 +1,60 @@ +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 From 3281fe95c84a1f82faf0c9c4af93c883283f43be Mon Sep 17 00:00:00 2001 From: Florian Gilcher Date: Tue, 9 Oct 2018 19:33:00 +0200 Subject: [PATCH 2/2] Flesh out roadmap --- README.md | 2 ++ roadmap.md | 51 ++++++++++++++++++++++++--------------------------- 2 files changed, 26 insertions(+), 27 deletions(-) diff --git a/README.md b/README.md index 3c4f928..07485f5 100644 --- a/README.md +++ b/README.md @@ -8,6 +8,8 @@ Additionally, the planner gives additional documentation for general subjects (b This project is intended to be collaborative, see [Contribution](#Contribution) for details. +Also, see the [Roadmap](roadmap.md) for a high level overview of our current goals. + ## Cards Features take the form of **cards**. Each card holds some basic information: diff --git a/roadmap.md b/roadmap.md index 3b8130d..dce59fb 100644 --- a/roadmap.md +++ b/roadmap.md @@ -6,18 +6,27 @@ 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. +There is currently no central place to go for _first-time organisers_ +to learn how to run a conference and get _actionable_ tasks out of it, +without building a copy of an already existing event. +The FOSS events planner tries to address this point. + +Using the FOSS events planner, people can pick _features_ for their +conference and then get presented with a set of _tasks_. For example, +if you want to run a conference with speaker selection, the tasks will +include "running a call for proposals", "selecting the speakers", etc. +Some tasks might have dependencies, for example, "determining a ticket price" +requires that all tasks of the kind "find out what feature X costs" are done. + +With this technique, we're trying to get people to both be aware what's possible, +but also be able to quickly filter by what's relevant for them. 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. +Come up with a catch name for the project. Tasks: - Suggest names @@ -32,29 +41,17 @@ Tasks: - Design Website Content - Launch website +## Finding contributors -## Learning Resources - -## Events and meetings +To make sure that we are not documenting our current conferences only, we should find additional contributors. -## 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. +Tasks: +- Find additional writers +- Find website contributors of all kinds +## Finding users -## User Testing +To make sure that our content is helpful, we need to find first users. -> 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 +Tasks: +- Find a first user to collect feedback \ No newline at end of file