Mark Brouwer wrote: > I move to a different subject because I think it is better if we have > each roadmap item in a separate thread. > > Dan Creswell wrote: >> Couple of comments inline but I'd like to suggest something of a >> strategic option. For me, at this stage, moving the specs around or >> whatever is a detail (an important one) but I think we need a plan for >> what we're trying to achieve overall - something like: >> >> (1) Figure out what documentation we think we need overall >> >> (2) Figure out what we have >> >> (3) Figure out how (2) intersects with (1) >> >> (4) Fill in the gaps >> >> (5) Move it around 'til we like where it all lives >> >> Now it might be y'all have answers to the above already in which case, >> great - let's get 'em all out here. > > It is important to talk about what kind of documentation we need and > something we should get rolling, but to me it is not a priority and as > such also not something I expect to spend much time on. >
And that's all fine but: (1) Realize that all your good work elsewhere mightn't get recognized/used if we don't look seriously at the issue. After all, no user community, no interest in all the good stuff Mark has done. (2) The stuff that you do elsewhere can make it more difficult to get users through the door if it's the wrong choice for them whilst being the right choice for you. > The only thing I find important at this stage is whether we are going to > follow a common rule about how we are going to spec and keep that > uniform. E.g. if there is maintenance on the lookup and discovery > specification are we going to move that over in a fashion comparable > with the newer specs or are we going to defrost the current HTML specs > to the minimum that we can alter a few paragraphs. > And I'd say let's get ourselves up and running and worry about this issue when we hit it. There's lots of other stuff that needs doing as well. I must admit, I'm a little concerned about all these rules we seem to want to put in place up front in the absence of experience in this new environment. It feels somewhat like trying to write specs before we've had experience with solving an issue which is an oft-cited failing of such things as WS-* Dan.
