Ready to Adopt Issues
Sean McGregor
Welcome to the stage of the Privly effort I'll label "building an
airplane in flight" http://www.youtube.com/watch?v=L2zqTYgcpfg
It was great hearing from many of you, and I look forward to working
with you all. I have a lot of communicating to do to get us going, and
so expect a few more emails from me in the next few days.
This email focuses mainly on issues you can adopt right now. I'll
write again soon with more extension focused issues, as well as issues
for testing, legal, marketing, documentation, and more.
Ramp Up (https://github.com/smcgregor/privly-web/issues?milestone=2&state=open)
These issues are short term essentials for getting things going.
* A separate web application for the bug submission system
(https://github.com/smcgregor/privly-web/issues/45)
* Setup Privly community server
(https://github.com/smcgregor/privly-web/issues/49)
* Setup development server (https://github.com/smcgregor/privly-web/issues/48)
* Recruit people (https://github.com/smcgregor/privly-web/issues/29)
Alpha (https://github.com/smcgregor/privly-web/issues?milestone=5&state=open)
These issues are associated with getting us to the Alpha release
* Remove Marketing Materials from Web App
(https://github.com/smcgregor/privly-web/issues/40)
* Make resource identifiers random
(https://github.com/smcgregor/privly-web/issues/37)
* Eliminate recaptcha dependency
(https://github.com/smcgregor/privly-web/issues/13)
* Update database seeds (https://github.com/smcgregor/privly-web/issues/17)
* Make the public/private setting only accessible when the user has
share permissions (https://github.com/smcgregor/privly-web/issues/6)
* Make token authentication record failed attempts
(https://github.com/smcgregor/privly-web/issues/1)
Thanks and Let's Build That Airplane,
-Sean