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* 01 Improve Community Communication - Intro02 TiddlyWiki Landingpage - proposal03 Feature Request and Voting Mechanism04 Using e-mail to request a new feature05 Governance Model Proposal06 Use Issues, to contribute to governance model07 Use merge request, to contribute to governance08 Consensus Seeking and Repo Structure09 Request Access to Sub-Groups ======= LONG POST WARNING for those who don't want to watch videos. =========== The following posts are based on the transcription of a video series I did some time ago. I didn't promote it, since I thought, the time wasn't right. Is it right now?! ====================================== This is the *initial post *about: How can we improve the Community Contribution, in the way, that the community contribution is independent from the TiddlyWiki release cycle. In February 2018 there has been a hangout where Jeremy created a new issue: Introducing Continuous Integration (CI) CI is a process where developers can push something to the main repository. Then robots take over, "compile" the stuff and "release" the stuff If we can do this automatically, we can remove a lot of manual work for Jeremy. If we have a described procedure, how something should work or should be distributed, different users can say: "Create the release" or something like this. Everything should, always, be done in the same way. --------------- A new developer joined the community: Luca He did create an issue, which says: "Things that scare off potential contributors" In this case the original post is about developers. See: https://github.com/Jermolene/TiddlyWiki5/issues/3313 and video https://youtu.be/497hRzpRHuI?list=PLuiC_HFhI4OyUiDGqvzB64mTQTURABjlW&t=79 As you can see, it's a quite long discussion It immediately became a discussion about: "documentation or user feedback" That's why Luca splited it into 3 issues One which says: "How can we improve user feedback" see: https://github.com/Jermolene/TiddlyWiki5/issues/3319 It should not involve: compilation stuff and all these things In my personal opinion It should be as easy as sending an e-mail There is a 3rd post, which says: "..contribute to the TiddlyWiki documentation" see: https://github.com/Jermolene/TiddlyWiki5/issues/3318 Where a mechanism is involved how to push something to the main repository. Since February I was constantly searching for a workflow that I want to have. There was also a little discussion about: the community governance see: https://github.com/Jermolene/TiddlyWiki5/tree/master/licenses At the moment everything is "governed" or let's say: contributions are protected by Jeremy's review cycle But if the community has the possibility to independently push something We need some rules. They should be as simple as possible. So that everyone can easily follow them But there should also be a possibility that we really can USE THEM in a way that is good for TiddlyWiki This is the main reason for this video series At the moment I'm planning to release 5 videos. With this one 6 (9 at the end ;) see: https://tiddlywiki.org.gitlab.io/videos/gitlab-talk.html The first thing I want to discuss is: A Landing Page: See video #2 All of this is a proof of concept. So it's not carved in stone Everything is meant to be discussed and can be changed There are some ideas I would like to have a new landing page and show how it should look like Then some information about Feature Requests: see: Video #3 How feature requests should look like. Let's say the easiest way to give feedback for new users And the possibility, for example: to create an e-mail workflow for new feature request. see: video #4 There is a suggestion about a - New Governance Model. See: video #5 - How Consensus Seeking should be executed: video #8 - There should be some rules, how someone can become a member with merging rights: video #6 In this case, how can we create a workflow That the community can really publish independently from the TiddlyWik workflow Then there is some information about - TiddlyWiki as a Static Site Generator: video #2 We have a very very powerful tool which allows us to create sing pages, static pages There is some information about - GitLab ToDo Lists: video #3 - or the Web IDE = (Integrated Development Environment) As I said: Everything is a proof of concept: at the moment I'm using GitLab Because it gives us the best possibilities, for the proposed workflow. Then as you can see it goes deeper and deeper into development area So there is a Developers Workflow - How we can create: Merge Request - How Continuous Integration and Continuous Deployment can be done There is a lot of work involved. I want to show you how the workflow looks like There should be a proof of concept at the end of the videos There are some external tools, which we have proposed already - There is a chat. For example: Gitter - https://gitter.im/TiddlyWiki/public I personally would like to have the possibility for a voice chat That's why I did setup a Discord server: TW5 https://discord.gg/uQZrVB May be there are some other topics which should be discussed That's basically it, what the video series will be about This was the first video and the next one starts with the proposal for a new Landing Page have fun! mario -- 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/b63dae41-3512-45af-bb7c-41678698b71bo%40googlegroups.com.
