On Tue, 8 Feb 2011, Eric Shulman wrote:
However, the same may not be true for other, non-TiddlyTools plugins that are still constructing their own tiddler element IDs. I suggest that, before releasing any fix for #472, we should perform a simple text search through as many known, published plugins as possible, to
I think this is a) unreasonable, b) maintains a damaging precedent that has limited TiddlyWiki's growth and maturation. TiddlyWiki suffers from something that might be called the tyranny of the legacy[1]. It's captured in the idea that it is up to the maintainers of the core to go out and search for plugins that might be harmed by changes to the core. NO! Plugin maintainers should be responsible for tracking the core and keeping up to date as needed, or stating that their plugins require an older version. Core maintainers should be responsible for announcing changes in good time and providing suitable beta periods (in the order of weeks not months). Plugin maintainers who don't track those changes aren't _maintainers_ they are absent[2]. The nature of TiddlyWiki makes it so that people who don't want to upgrade don't have to: Their stuff is all there and already working. If they want new stuff, it is _new_ stuff, which they have gotten for themselves. This isn't like upgrading iTunes and suddenly you can't play your oog files. [1] This tyranny is made extra strong by many of the techniques used in some plugins. [2] To get back to what I took as FND's original point, the issue here is not this one bug about jQuery, but rather how long it is taking it, as an example of many bugs, to get resolved. A healthy open source project "should move more rapidly and be more responsive". The fact that this bug, and many other bugs, languish gives the impression that the project is neither healthy nor maintained, which we _know_ is not true, so how do we change things so that that impression is not given? The move to github is an effort to shake things up, blow out the dust a bit, but it will not make enough of a difference if there is not a fundamental change in the attentiveness, accessibility and responsiveness of the people responsible for the core. -- 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.
