> I've seen this phrase "short-term priorities at Osmosoft" bounced > around this thread a few times. The implication is that Osmosoft is > making all the core decisions and core commits. > Since that is considered a problem let me restate one of the reasons > for a move to github: > Make it possible for the at large community surrounding TiddlyWiki > to make patches and other contributions to the core.
+1 If I care about something and feel strongly that it should be in the core, why expect the core developers (let alone Osmosoft) to implement this instead of myself? This perception and lack of diverse _code_ contributions has been a _major_ flaw of this community in the last few years. (Obviously, we all - myself included - contributed to this. No pun intended.) Anyway, I'm hopeful that the GitHub move will improve this situation as it lowers the barrier to contributing and reduces gatekeepers' significance. > As I previously posted, I feel *very* strongly that the existing > tickets should be migrated into the new system I have equally strong beliefs that this would do (much) more harm than good, for all the reasons discussed so far. Simply dumping that data in the ticket system will do nothing to improve triage and resolution. Once an issue is being tackled, reviewing relevant notes is just part of the due diligence, no matter the URI. -- F. -- 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.
