Issues that we as a software project need to address: Consolidation and identification of all digital assets(s) - identify all services provided to the network by both community members and by the core team. It seems to me we have a lot of community members providing base services that people depend on. It would be nice to know that we have a disaster recovery plan for all those services to return online. (dashninja, block explorers, faucets, websites, dnsseeds, etc). Define and commit to using software development roadmap/best practices - this roadmap should include a defined release schedule. The schedule should be followed to the best of the ability of the dev's so that masternode owners can expect when they will need to do updates and prepare accordingly. We should document from the last commit all the way to the push of the download. Best practices mean defining where our source code is, how we expect people to contribute, what we need help with. We have done a real poor job of maintaining the fluidity of our github repo's. I've had lots of people confused as to where all our utilities are and which ones are the valid ones. This leads us into the next issue. Defining how we expect dev's to help and where will help get more people involved. Define and commit to using an official announcement space/page/blog - I want to see a clearly defined spot that the community can expect to get the actual facts regarding an issue, a discussion, a potential vote. Nobody in their right mind is going to read pages of drivel to find the nuggest's of actual info. I don't mind that the majority of hte dicussion goes on in dct forums but after the issue has been discussed we need to be going behind sifting through the thread and actually posting the relevant links to an official space. Not to BCT not to DCT to a well defined and known spot (cause having this inside the wallet seems illogical?). Stop making the same mistakes. When we do document them so that our side is officially represented - Pretty simple. When we make them learn from them. Talk about them (on our official channel) and correct them. This apply's to how we handle dev's, how we disseminate new info, the project continues to become more powerful as we continue to make less mistakes. Mistakes have been powerful and also very well looked at. I think it would be beneficial to have an official place where we also talk about each of these mistakes we have made and how we have learned from them. I'd like to see info about the "insta mine", info about early stages of darksend, god people still jump into irc and ask if we have open sourced our code because all white papers and such referring to the opensource code all refer to the old github that no longer exists. I think it would be powerful if the community could hear both sides of all of these mistakes. Show them we are transparent and that we are a growing and learning community.