a schedule/sequence of events to successfully reach the project objectives is required.

draft:

Event#1: first comment by non-owner.
Event#2: first commit by non-owner.
Event#3: first wiki-commit by non-owner
Event#4: first document by non-owner (doc=image, code, etc)
Event#5: first publicity outside GitHub
Event#6: first retweet/repost/share on social media
Event#7: welcome first hardware (part)
Event#8: hello world.
Event#9: welcome first software (function)
Event#10: first exchange between server and client
Event#11: welcome first robot (of non-owner)
Event#12: first demo towards friend
Event#13: first demo online (Video on Youtube?)
Event#14: first robot-robot behavior exchange (?)
Event#15: version 1.0 publicly available.

etc..

Conduct a tradeoff for a SW only development (assuming that HW integration is done seamlessly); or a complete system (Robot HW, Robot SW, Central SW elements)..

options:

1. working the requirements on a dedicated requirement management tool?
2. excel
3. finding a better way to navigate through "text+markup" on GitHub.

Tasks:

1. How are other guys doing it out there on GitHub?
2. How are people doing it on opensource - crowdsource online projects?

currently the user doesn't have a fast way of browsing the repository using in-line hyperlinks.

A good navigation is desirable.

start uploading files.

the update stream is not stable (0 issues, 0 pull requests, 0 second writers)... therefore the project seems to be a potential waste of time and resources.

a strategy for public-geek support is required.

First question mark:
how many developers does this project require to be effective.
Define "effective".