> ... there IS an "insider-vs-outsider" schism with > regard to TWCore development should be of some concern, and is a good > topic for discussion for the entire TiddlyWiki community.
Ok.. > * How should new TWCore features proposed and refined? e.g., online > discussions, tickets, conference calls, emails, personal > conversations, formal RFPs/RFCs (YUCK!), etc. As en enduser I would like to be able to follow development anticipating a release on the devgroup. I would "pay my 2 cents" there, whenever I thought I could add something usefull myself. I would expect to get more than just an announcement of a new release.. > * What criteria are used to evaluate new features? e.g., public > demand, code complexity/risk, adaptability (plugin potential), > backward-compatibility, cross-platform compatibility, etc. I'd like to be able to vote for "public demand", however I would be *very* responsive, whenever a develloper/programmer explained the adaptability of a possible new feature, and my vote would reflect just how responsive I am as a potential user of TiddlyWiki for many years to come (I hope..).. I'm not very concerned about backwards compability, unless we are talking about wikitext, evaluated parameters and forEachTiddlerPlugin... Then I *am* pretty concerned... If I get WysiWyg as a full replacement for wikitext - no evaluable parameters via the tiddlermacro and no help from fET, then it's comparable to taking a kids Lego bricks and replace it with readymade toys - no more fun or creativity left for someone like me :-( I still have a bunch of "old" TWs which won't work if they are upgraded, however they work as they are now - so why upgrade? One example is the jTab plugin http://jtab.tardate.com/jtabtwiki-help.htm, I haven't been able to make it work since TW ver. 2.5.3... However I use it still, I just don't upgrade the core... If I'm told that I can get more and better "legobricks", but I have to forget about some plugins, that the plugindevelopper doesn't want to maintain or adjust to meet the new demands, then I can choose to upgrade "with my eyes open" - and I would happily write a section about "known issues" to inform/warn other users about the consequences... TiddlyWiki isn't just *one* program, it becomes a new application everytime you have tailored it for a new usercase. If it works for that particular usercase, that's fine, and it doesn't need to be upgraded unless the conditions for the usercase changes. If they do and need some refactoring a new plugin which depends on something still unsupported by the core, what are my chances to make things work with TiddlyWiki? I don't know? - Mayby some other software maintained by someone who gets paid to deliver superficial solutions/results as fast as possible... - Problem is that you can only afford to pay a few - TiddlyWiki on the other hand has *many* eager contributors (both amateurs, semiprofessionals and pros) of plugins and code - Most of them give their work away for free, however there's a certain expectation of high quality and sensation - and I believe that it must be worth it somehow - maybe its enough to experience that other users respect and use their work - don't know. To mee it seems that quality is a keyword here?! - and I think this goes for everybody involved in the TiddlyWiki project.. My 2 cents... Cheers Måns Mårtensson -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" 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/tiddlywiki?hl=en.
