Hi Folks, For those who don't want to read - there is a List of videos <https://www.youtube.com/watch?v=497hRzpRHuI&list=PLuiC_HFhI4OyUiDGqvzB64mTQTURABjlW> about
*Improve Community Communication proposal* 08 Consensus Seeking and Repo Structure -------------- Hi Folks, This is Pietsch Mario With the next video about the Community Communications and The Consensus Seeking Process As you have seen in the other videos: New Governance Model we have the possibility, to write down, how the workflow should look like So that users know, what they can expect. At the moment I did set everything to 100% consensus so as long there is a discussion going on, a merge request can not be merged Which is a little bit strict. Still it "may" work, if all the developers reach consensus, something can be merged But it should be a little bit easier and a little bit more structured We will have a closer look at gitlab - tiddlywiki.org project which is a group and a namespace. I changed the user. I'm here "pmario" now, which has full access to everything The overall structure is like this: There is a tiddlywiki.org group Where different members can join. Basically everyone, which wants to be part of tiddlywiki.org can join, let's say, this level. There are different roles. We have a guest role, a reporter, developers, master and owner If you are there, then you can see the whole structure and create issues or feature requests or what ever ... depending on the level of rights that you have. Then we have different "sub-groups". For example: 1 of them is "documentation" This is "TiddlyWiki Home and Documentation" It should contain German documentation NOT the translation That's something different. I did translate content from tiddlywiki.com and made a German version There is a French version This should be the source for the static homepage. The source home directory contains this info, with the templates and everything. And there is the English documentation, which is, let's say, tiddlywiki.com The extended documentation, because Jeremy wants the "core" documentation the "reference" documentation, inside the core. The goal here is, that we find users, that want to contribute to the documentation. Some of those users may have write access, to the different repositories. Because this "german" (link) is a repository. This then contains the real code. The "docs" is the group Everyone, which is part of the documentation group, may be is interested in different languages, because I would contribute to German and English I can not contribute to French There may be some Switzerland guys. They may be able to contribute to German, to the French version, to the Italian version and to the English version. That's why it's called "group documentation" There is an other group, which is called "editions" Which contains the different templates. At the moment this is the different editions from tiddlywiki I definitely think, that those "editions" need a different "live cycle" then the core That's why there is a different group, which can update the edtions in a much faster pace, than the core. Then there are the plugins. The standard plugins, which the community can maintain. There should be also the possibility for example: I want to have a new project, where I can say OK, I want to have a public project I want to have my "wikilabs". wikilabs plugins, that they are part of the community Tobi Beer may have his own plugins ... and someone else may also want to have his plugins. The cool thing here is: With this structure - it's possible. Because we can say: If you are part of the plugins group and we trust you enough, that you can merge something to master AND you have 2 or 3 up-votes from "key-developers" otherwise you can NOT merge to master, then this structure is possible. Plugins Then we have all the translations ... sorry ... THE translators editions. There is an edition with tiddlywiki, which you can download and it should be possible, to transfer the information, per mail, or something like this I wanted to have 1 group, which improves this "translators edition" There are the different "themes" "themes" is the same thing, as with plugins There should be the possibility that the "themes - group", adds new projects to tiddlywiki.org. To the organisation The different repositories are still completely independent. All the copyrights and so on. They all belong to the different authors, if they want. There is the "base" element, which is "the core". TiddlyWiki core which contains almost everything The whole code, plus the languages It needs a little bit longer ... ahh ... I didn't push it yet. Tiddlywiki core There is the "organisational structure", which I called "senatus" You can have a look at wikipedia, what it means It contains the "committee". Since everything should be open, all the projects, everything, is public. All the discussions, all the issues can be seen by the whole community. There is a repository, which is called "dist" for distribution It's not used at the moment. Just for playing There is the "feature-request" section, which you know already "feature-requests" handles the feature request issues and the board Different possibilities ... Now I have the possibility to switch it over to "under consideration" or to "plugin territory" or I say: OK it's part of the "backlog" If you have seen the other videos, I couldn't switch it. Now I have all the rights. I can switch it. OK - Feature Request Then there are some test elements. This is the repository, which hosts the main page! As you can see there is no https connection, because I made a mistake tiddlywiki.org.gitlab.io doesn't work at the moment. There is a problem with the certificates. That's why we may need to switch to tiddlywiki dash org or slash org .. German landing page. - Only for testing The videos is this one. The gitlab-talk tiddlywiki is hosted here. At the moment this is also used for testing the CI/CD process If we have this file. If it is active the CI/CD does all the publishing Everything is done automatically. If I push changes - the homepage is updated automatically This is for testing mainly What we need to establish now. This is the basic structure. What we need to establish now, "How can someone become a member" Which will be part of the next video. See you soon! -- 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/463721cc-a796-4d1c-ad8e-7ebf95bb8d19o%40googlegroups.com.
