Ecosystem Development
This proposal is about developing not just the code, but the ecosystem of SamePlace.
Is it easy for new developers to get their heads into the source? Do we manage to get SamePlace in front of all people who could find it useful? Does the bugreport process encourage participation or not? Are we making good use of all the communication channels, like chat rooms, mailing lists, and web forums, or is energy being dissipated?
Answering these (and asking more similar) questions is the first step. The next one is figuring out what to do about the answers we're not happy about: for example, if developers find it consistently hard to get into the code, write a small tutorial, some recipes, and document important patterns in the source; if similar support requests are placed in both mailing list and chatroom, find a way to redirect them so that they only need to be answered once.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Note to Summer of Code prospective students: this is the most open-ended, multi-disciplinary, cool and probably also hard project. Expect to write some computer code but also expect to "write" much
more "reality code" -- in other words, expect to be hacking the Matrix itself.
