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* 05 Governance Model Proposal ------------------------------ Hi Folks, Pietsch Mario again, with the next video about Community Communications The next topic is New Governace Model A proposal, how it could look like I did have a look at other open source projects Most of them are big. They have a lot of overhead I wanted to have something the is very sleek and similar to what we have already. Starting here again from the proposed main page there is a link which says: How to contribute It's called Community Info. In the end all of this information should land somewhere here. But now for the beginning, we needs something to discuss. There we have a repository, which I called "commitee" .. Which contains the basic information Most of the text I copied over from WebOS, the open source edition. Because they started a very new project. They start to build up their community. They have a very open and very sleek governance model. Here is "contributing". A lot of this text is copied over. That's not a problem, because it is Creative Commons I borrowed a lot this text and modified it, to work with TiddlyWiki. To get a little bit of a head-start The first element is the README. What's very important here is: Everything is WorkInProgress and it's made to be discussed. There is some description about: How can someone join the community If you are really a new user, you may want to have a new feature So we have the feature request, which we discussed already, with the feature request board. New users can get a fast overview New users can check out the different repositories and may open requirements. There is some information about requirements. There is a link to the different repositories, which I will discuss in detail. This is interesting for developers Then there is "Discuss your ideas". The idea discussion is part of the feature request section Which goes back to the "Feature Request" That's the way, how everything is linked together. Then there is the important stuff of this part. Which is called the: Governance Model which defines some basic rules. As I said, it should be as simple as possible. At the moment everything in the different repositories can not be merged, if there is a discussion "pending" So at the moment, it's a "100% consensus model" for the developers. Which is not very practical but for the beginning I set it as default. There is a little bit about the organisation. How tiddlywiki dot org. I used tiddlywiki dot org. I hope we can add it there. It uses the BSD 3 lizense, which is part of TiddlyWiki. This is the code and we use the Creative Commons 3 license for our documentation. Also "this" documentation should work with this license. Then there is the Communication Process with the different forums, which will be an other video. The Forums There is the Feature Request forum There is chat, which we proposed already. It's Gitter If I open it. It's a 3rd party "library", but we already have some communications going on here. With the "TiddlyWiki public" chat. This is also a request, that came very often I personally would like to have a voice chat. So having a "text chat" and a "voice chat" for me, it would be nice. So I did create a discord account and did set-up a discord server. We also have the TiddlyWik discussion group, that's already known. That's the different forums. Then there is a little bit of information about how we accept contributions. This is let's say the very basics. There is a "step by step" information. It also covers the Contributor License Agreement. It covers the review process Consensus seeking, and so on ... This is definitely part for improvement and discussion. Nothing here is carved in stone but we need a starting point, to start the discussions. How We Accept Contributions There is a little bit about the Community Guidelines, which I also wanted to have very very simple. There are big open source projects. They have pages and pages of information how you should NOT behave, which is not interesting for me I would like to have some information, how you SHOULD behave. Keep it as simple as possible. There is definitely some room for improvement but as a starting point I think it works. That's the basic information You should take your time and from the proposed landing page. There will be a link, which will lead you there. Then you can have a look at the different elements. As I said at the moment I'm using this repository which is called "commitee" There is a new structure, which is called tiddlywiki dot org Then I called it "senatus". Go to Wikipedia, to see, what it means, then there is the "commitee" This is the repository, where everything is stored at the moment. If you want to be a user, fork it and create "merge requests", so we can change the stuff. That's the basics for the Governance Model. The next video will be about the Consensus Seeking, because. ... There I need input about the possibilities we have 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/29028e4f-c421-4d0f-a598-17f5311a362eo%40googlegroups.com.
