On Monday, June 11, 2018 at 11:54:30 PM UTC+2, Diego Mesa wrote: > > > As always - *thank you* for this. Side note - I requested access to > everything before getting to video 09, so I understand if that is not > granted. >
I think, I'll grant Guest or Reporter to basically anyone, that I know from github. .. :) ... For the more "destructive" levels, and new "unknown" names, we will need a short challenge, that lets us connect github user names with GitLab user names. ... I have an idea here. But for the start you are "Reporter" for the docs and "Guest" for the whole thing. .. This lets us play with the possibilities. ... > I can be more specific. My feedback on the videos: > > - 02 TiddlyWiki Landing Page Proposal > - I think this is a great idea, and I love your example. I was > recently blown away by just how similar the industry standard Scrivener > software is (https://www.literatureandlatte.com/scrivener/overview > > <https://www.google.com/url?q=https%3A%2F%2Fwww.literatureandlatte.com%2Fscrivener%2Foverview&sa=D&sntz=1&usg=AFQjCNHBuITaKA3nMu03MQyhYOOpXk0Unw>) > > to TW. But I had a person spend 2 min on their site and 10 min on TW > and be > confused about what TW IS, let alone what it can DO, to say nothing of > HOW. > Your landing page demo is a great step in the right direction! > > Thx. And since I do already have the "language" part as templates, it should be the first element of the experiment, which gets an automatic build system. > > - 03 Feature Request and Voting Mechanism > - I think this workflow is a great idea, allowing users to upvote > and developers to weight. This is not only great for developers, but > great > for the community - they can see what people are working on, and > interested > in. As a side effect, moving to gitlab (or even a new repo on github) > will > allow us to kind of "restart fresh", so there aren't over 600 open > issues/feature requests that are forgotten and ancient. > > I actually did a *full review* of the open issues and found out that are most of them ~450 are feature request. Many of them are still valid and make sense. ... But we as developers have no overview, if it is just 1 person or if there are many users, who would like to have it. IMO voting is a highly requested feature. ... And if we can link it nicely into a development workflow it is a plus. ... > > - 04 Using email to request a new feature > - a great idea - I didnt see it in 03 or this video, but I would > suggest having a *template* for feature requests, bug reports, etc. > > That's relatively straight forward. ... Just create an issue with some proposed text, and I'll directly add it to the settings. :) > > - 05 Governance Model Proposal > - I would love gitter chat *and* the voice chat! > > chat: https://gitter.im/TiddlyWiki/public voicechat: Will be discord server .... but I'm not very familiar with the admin stuff there. I like it, but I didnt do discord admin work yet. So help would be very welcome here :) > > - 06 and 07 - Issues and merging for governance model > - Great idea and explanations, but I saw this as more general way > for users/developers to contribute - not so much about the specific > governance model > > That's right. > > - 08 Consensus Seeking and Repo Structure > - I really like this structure, especially the plugins, docs, and > senatus split! > > Yea, we will see, how it turns out. We can adjust it further. .. I just found out, how to set repo specific roles. ... So we have a very fine grained control. > > - 09 Request Access to Sub-Groups > - I think this is great - it allows the community to prioritize > people's contributions in the right way. > > I think, it's a great way, to keep focus. Some users may only be interested in 1 or 2 aspects of the whole thing. > That's all the videos so far. More general comments: > > - This system will enable something I think is incredibly important > and currently missing: More experienced developers can now mark feature > requests or bugs as "beginner", "intermediate", etc. which does great > things for encouraging people to get involved! > > exactly! ... And the cool thing is, If we have users that push a lot of good stuff, we can promote them up to devs and they are able to create the content themselfs. ... Once the review is finished, the community can publish it. > > - There can now be a *gameplan* for the future! If we pretend > Jeremy/community was able to hire skilled programmers for 1 month - how do > we maximize their time? We can now point to the issue board across > different groups and say focus here. This is fantastic. > > yes. > > - My biggest question is this - how do we actually get to using this > system? If we could identify A) what Jeremy needs to see/do in order to > accept this plan and then B) having accepted, what does Jeremy need to > see/do to get us there? > > At the moment everything is a *big experiment*. ... Nothing is carved in stone! ... 1 "short term goal" is, to create a CI/CD workflow for the new landing page. So I can create the next video: TiddlyWik as a static site gnerator Where I can show the whole development cycle. - Forking - local development - pushing a new feature-branch - crate a Merge Request - CI/CD builds a preview page - After review is OK - CI/CD automatically publishes the page. Since this workflow is basically the same for every other repo ... we basically won :) -m -- 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/096bfc0e-60aa-49ad-997f-003ad38338aa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
