If there will be effort put into actually building something, we might want to look into what other purposes it could serve, such as virtual (persistent?) meetups, remote CFAR sessions, etc. with features such as a “talking totem” that can be passed to enable audio from that person.
(Split from a previous comment for concept independence)
Later. Keep the project requirements small until it’s working well. Get it to serve one desired purpose very well. Only then look at extending its use.
This is true for any coding project, but an order-of-magnitude more true for a volunteer project. If you want to get a programmer to actually volunteer for a project, convince them that the project will see great rewards while it’s still small. In fact, you basically want to maximize intuitive value, while minimizing expected work. It feels so much better when your actual, original goal is achieved with a small amount of work than it feels when your tiny, first step is only the start of achieving your goal.
If there will be effort put into actually building something.
Yes, effort is going into actually building something. :-) Shannon got the ball rolling, and we’ll be contacting some of the other volunteers in this thread over the next few days. We’re currently exploring our design options. I’ll make a post on the subject once we figure out the proper approach.
Later. Keep the project requirements small until it’s working well.
Absolutely. Version 1 will be as minimal as possible. (probably equivalent to tinychat plus one or two features)
If there will be effort put into actually building something, we might want to look into what other purposes it could serve, such as virtual (persistent?) meetups, remote CFAR sessions, etc. with features such as a “talking totem” that can be passed to enable audio from that person.
(Split from a previous comment for concept independence)
Later. Keep the project requirements small until it’s working well. Get it to serve one desired purpose very well. Only then look at extending its use.
This is true for any coding project, but an order-of-magnitude more true for a volunteer project. If you want to get a programmer to actually volunteer for a project, convince them that the project will see great rewards while it’s still small. In fact, you basically want to maximize intuitive value, while minimizing expected work. It feels so much better when your actual, original goal is achieved with a small amount of work than it feels when your tiny, first step is only the start of achieving your goal.
Yes, effort is going into actually building something. :-) Shannon got the ball rolling, and we’ll be contacting some of the other volunteers in this thread over the next few days. We’re currently exploring our design options. I’ll make a post on the subject once we figure out the proper approach.
Absolutely. Version 1 will be as minimal as possible. (probably equivalent to tinychat plus one or two features)
Agreed in retrospect. Scope creep creeped up on me.