Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

create draft roadmap #59

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
57 changes: 57 additions & 0 deletions roadmap.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,57 @@
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.

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
--

## 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

## Finding contributors

To make sure that we are not documenting our current conferences only, we should find additional contributors.

Tasks:
- Find additional writers
- Find website contributors of all kinds

## Finding users

To make sure that our content is helpful, we need to find first users.

Tasks:
- Find a first user to collect feedback