On Friday, June 8, 2018 at 11:12:56 AM UTC+2, @TiddlyTweeter wrote: ... > I am, frankly, feeling some of this effort could be wasted because IMO the > single biggest danger with TW is *yet more fragmentation*. The GitHub > side is the most integrated and consistent at the moment. >
You are right. At the moment, we face a lot of fragmentation, because there is no "easy" ways to create something, that is tightly coupled to tiddlywiki.com, but are *outside of the release cycle* of tiddlywiki.com So users use what they know best, or they introduce a 3rd party platform, they think could be useful. ... That's great but causes fragementation! We have many different resources, that are great. So over time as things get bigger, because they are useful. .. It starts to get a full-time job for 1 user, because the different elements don't play well together. As Jeremy points out there should be an eg:* tiddlywiki.org umbrella! *which keeps all elements loosely coupled. eg: GifMex'es tw-dynalist is a great resource: https://dynalist.io/d/zUP-nIWu2FFoXH-oM7L7d9DM ... But he had to tell the community, that he's on holyday, so the list won't be extended for several days! ... That's a problem. ... Not the holydays, but the "helpnessless" of the community. ... I personally think, that this is an "access control problem" ... At the moment we can't create a "workplace" for new projects that are outside of tiddlywiki.com but still belong to the tiddlywiki-community. We simply can't allow everyone to write to a repository that contains the core software, without reviewing the content. But not everyone can be, or will want to be involved in every aspect of the community. ... That's why we need "groups" with different possibilities. So there should be a possibility to have: "TiddlyWiki Toolmap" group, that is "self-governed" and has the possibility to publish to tiddlywik.org/community/editions/toolmap.html ... The path is an example only! - The release cycle is maintained by *group members* - The layout is maintained by *group members* - *Devs *should provide a template to get started - *Devs *should provide some basic rules, that *group members *can adopt and / or change ... - *Group members *should vote on content, that is ready to be published. - ... BUT .... Publishing is done by a *robot*. So group members don't need to know, what exactly needs to be done. It should *just work!* > Out in the world of end-users some of us are struggling to > join-the-informational-dots of the scattered resources so everyone knows > what is where. just finding things, plugins, tutorials, example TW etc is > almost a full-time job. > As I wrote. I want to have it under the tiddlywiki-community umbrella. Preferably tiddlywiki.org > On the dev end my concern is: could the desire to improve actually have > unintended consequences that actually increase fragmentation? > I'm trying to solve this. I'll publish more info on sunday and hopefully have some 3-minute videos too have fun! mario -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/51cb3e06-b357-4b14-9d63-84ec37c56d31%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
