On Sunday, August 16, 2020 at 3:53:08 PM UTC+2, Mark S. wrote: > > > > >> Hi, ... Not really. >> >> > We would ask first, of course. > > So your plugins aren't open source? >
Sure they are. ... But being in control and defining an organisational hierarchy in Git*H*ub is a PITA. As far as I can see, the access rights can only be defined per repo and not per "subdirectory". .. And there is no convenient and easy to explore "sub-repo" structure. I did play around with a tiddlywiki-org organisation <https://github.com/tiddlywiki-org> at github 3 month ago. ... As you can see "plugins" is 1 element of it. ... It also contains some basic configuration for 15 teams, that will allow users to create a basic "access" structure. .. But the system at GitHub was designed for Enterprise organisations, where you have 10 admins that have a full time job, doing the maintenance (Just my experience, but I may be missing the simple stuff.). I did want to mimic something which I had experimented with at Git*L*ab 2 years ago: https://GitLab.com/tiddlywiki.org ... where it is easy and convenient to configure. There is even a youtube playlist <https://www.youtube.com/watch?v=497hRzpRHuI&list=PLuiC_HFhI4OyUiDGqvzB64mTQTURABjlW>, that describes most of the ideas in much more detail. ... Down to a prototype of *1 possible* Governance Model <https://gitlab.com/tiddlywiki.org/senatus/committee>, that starts as simple as possible and is just a starting point. >From my point of view, before we put a lot of energy into an "un"official plugin library, We should put it into an "*Official Community Dot Org*" project. (I actually don't know, who owns tiddlywiki.org ... but it also could be tiddly.wiki which imo belongs to TT) BUT from my point of view, we need a Governance Model first, that defines the basic "rule set" for contributions to the different elements. We need to describe the "decision making" process, so users know about them, so they can be sure what to expect. see: Governance Model <https://gitlab.com/tiddlywiki.org/senatus/committee> -------------------------------- List of videos <https://www.youtube.com/watch?v=497hRzpRHuI&list=PLuiC_HFhI4OyUiDGqvzB64mTQTURABjlW>, so you know, what I was thinking about: 01 Improve Community Communication - Intro 02 TiddlyWiki Landingpage - proposal 03 Feature Request and Voting Mechanism 04 Using e-mail to request a new feature 05 Governance Model Proposal 06 Use Issues, to contribute to governance model 07 Use merge request, to contribute to governance 08 Consensus Seeking and Repo Structure 09 Request Access to Sub-Groups Have fun! mario PS: I didn't promote the Git*L*ab idea, since I didn't see a convenient way to migrate contributors from GitHub to GitLab. PPS: tiddlywiki.org.gitlab.io isn't possible anymore. ... But the second video shows, how it was meant ;) PPPS: I personally think, that GitHub is not mature enough to make the management easy, but if *someone can tell me the simple stuff *it may be a possibility too. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/e08a9754-8d57-4d13-af00-0167edfe0bd4o%40googlegroups.com.
