1. Create Proper Deadlines
It's time to ditch this "It's done when it's done" crap and move to a proper release schedule. Proper realistic deadlines need to be created, and the whole team should work reaching that deadline. No more "it should be done in 3 weeks" or anything like that, we need actual dates. The "It's done when it's done" mentality simply doesn't provide any motivation to complete releases on time.
Agreed. We should be working towards definite dates. To push ourselves harder! When a deadline is missed we also need more transparency on why it was missed.
2. Bi-Weekly Updates
Currently the only time we get real updates is when we constantly have to ask for them, or when shit hits the fan. That should not be the case, we shouldn't have to ask for updates as I've mentioned before, they should be provided in a timely manner. I suggest that GreXX provides the community with 2 weekly updates, covering everything that the team has done since the previous update. I suggest the updates take place on a Wednesday and Saturday each week.
Agreed. They should be provided in a more timely manner to stamp out any uncertainty.
3. External Communications Auditor
Frankly, at the moment we can't trust the word of any member of the team, therefore I suggest that we nominate a member of the community, one that is not currently on the Crypti Team, to view and participate in the internal communications channel between the Crypti Team members. The member of the community would then report back to community to verify the bi-weekly updates or to answer questions that need verification.
Agreed. You seem like a good candidate.
4. Open Testing Cycles
At the moment all testing of new Crypti releases, are being done internally, and at the moment terribly. I suggest that the Crypti Team make testing cycles open to anyone that would like to participate. The advantage of this, is that new releases are being tested across a wider variety of platforms and will be more conducive to bug finding than internal testing. The way this would be carried out, would be with BETA releases, which would be released normally, however only those who want to help with testing would download and use it. Errors could then be logged into a special BETA Repository on GitHub. None of the source code needs to lie there, the repository simply needs to exist so that issues can be logged. (The whole process should be carried out similar to the way OpenBazaar is going about their BETA releases.)
Agreed. Boris was doing this before during previous release cycles. There is always a small group of die-hards in the #CryptiTalk IRC channel ready to test new releases.