On Fri, 11 Feb 2011, Martin Budden wrote: [keeping people informed]
I'm one of the ones that argues that a ticket should be enough. From your comment I presume you don't. But to move on we need to understand why a ticket is not sufficient. Rather than a rather vague comment such as "exerience suggests this is not satisfactory", I'd rather have some concrete reasons as to why this is not satisfactory so that they can be addressed. For example, is the problem using trac milestones and the ticketing system, or is it that the tickets themselves do not contain enough information?
I'm summarizing what I've read from other people participating in this and other threads related to TiddlyWiki, as well as threads related to informing users of TiddlySpace. In both cases neither tickets nor commit messages were considered sufficient to do either of the following: * Keep people who wish to participate in active development aware of opportunities. * Keep people who wish to use new releases or new features aware of the changes and features. I'm one of the people who has said, to the people who are supposed to keep http://blog.tiddlyspace.com/ up to date, "Just read the commit messages". I was told that wasn't good enough, that it was my responsibility as one of the tiddlyspace core developers to provide accessible summaries with at least a bit of narrative. Eric has described a similar need in the TiddlyWiki context. FND as well. The problem isn't that commit messages and tickets "do not contain enough information" but rather that they contain the wrong information, or rather, information in the wrong form for consumption types in the list above.[1] In my perfect universe that wouldn't be the case, but "experience suggests this is not [the case]". We aren't in that world. Therefore we need to adapt.
Bear in mind also that TiddlyWiki is a relatively small project, both in the size of the codebase and in the number of people actively invovled. Something like RFCs, python PEPs or Java JSRs would, in my opinion, be overkill.
Goodness me, no. What we're talking about here is as simple as two things: * writing narrative user-oriented release notes * being forthcoming in this group where forthcoming means conversational about what people who are working on the core are up to and thinking about. Constant, ongoing dialog about what's happening. [1] It's important for me to state that I stand by my assertion made in a few different places that good, verbose commit messages are important. Code shows the result of a thinking process, it does not narrate the thinking process itself. -- Chris Dent http://burningchrome.com/ [...] -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
