If you try to tell people how they should do things you don't know how to do yourself, you're just setting up failure further down the line.
To be clear, the idea
here is that all the people who already have plans report and explain them to a general audience within a unified, living document. As for what you said, I
agree.
If I understand you correctly CLains you're not exactly proposing a masterplan in the traditional sense and not trying to tell people what to do
Yes. Not sure what a better name would be. What about
Bitshares Schedules?
There is one big risk though. I do not think this plan should be editable by large numbers of random people, because even your average troll would love to mess with such a plan, especially if it allows them to mess with the minds of a large number of people.
Yes. That is a problem we need to solve.
How can decentralized planning and management work effectively?
In the spirit of
better is good enough for now the idea is that people will be able to manage themselves and take on suitable roles IF they know what everyone else is doing and what their plans are. At least without this condition it is impossible to decentralize organization.
It would be great to have this all in one place. Given how finicky people are about 'missed deadlines', though, I might suggest avoiding hard dates....
--Master Plan (Having worked on Master Plans before, I believe that the best such plans are living documents. These contain important goals and goalposts, but the content and metrics leave some room for flexibility. In other words, if DAC A is anticipated in 2 months, but encounters an unexpected programming hurdle, or if a decision is made to introduce DAC B before DAC A for certain reasons, then those changes can be written in as the document is updated to suit changing times.)
Agree. 100%
--Chart w/rough timelines ...
--Recurring feature in the newsletter which notes each DAC's development team, progress, and prognosis
Yes, we should do this as well. Especially, once we have it all in once place, we can make abstracts for specific purposes like the newsletter and visualizations for marketing purposes etc.
--Wiki, blog, or some organic document that DAC developers themselves could edit to update the info for their sections
Wiki are better for documentation and specifics, blogs for unique written content. I vote for organic, living document of some sort; it would be a living set of schemas that lets anyone understand the gist and motivation behind every action and anticipated action; documentation, specifics, and unique written content can be referenced by neat links to wiki, blogs, github, threads, etc.