Roadmap
From socialswarm
First draft:
- Collect our requirements
Some brief bullet points for this can be found in this pad.- Functional level: What do we expect, as users, from such a system?
- Other levels: Hardware requirements (dedicated? shared computers?), implementation (do we aim for a general framework or is the primary target one implementation which others can link to if they want?)
- Nail down the basic security / software architecture
- Basic frontend features we have to consider / agree on before going any further:
- How to access the network? (web / multiple interfaces?)
- Access a friend's profile / status messages / files by visiting his own host / website or access it from one's own instance?
- Actual daemon running on a machine or HTTP stuff?
- Federated / fully distributed?
- Consider hardware / software requirements for the end user!
- What sets us apart from Facebook (besides security and reliability)? Ideas (please add):
- Share any files you want with whom you want (p2p?), including yourself (= your own personal cloud)
- Full synchronization between devices
- How to access the network? (web / multiple interfaces?)
- Security features
- See Secure Share's comparison page to get an idea what else is relevant (security-wise).
- Basic frontend features we have to consider / agree on before going any further:
- Look for software projects that meet our requirements
- Backend development
- Depending on the outcome of 2.:
- Modify the software to fit our demands or
- Develop it on our own (agree on a protocol first)
- Security audit
- Depending on the outcome of 2.:
- Frontend development
- Collect feature ideas, don't forget usability.
- Look for UI designers who make it pretty and useful. :)
- Programming…
- Extensive beta testing, security audit (again), polishing
- (Far future) Develop a campaign to advertise our software