Mario,
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 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) 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!
- 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.
- 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.
- 05 Governance Model Proposal
- I would love gitter chat *and* the voice chat!
- 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
- 08 Consensus Seeking and Repo Structure
- I really like this structure, especially the plugins, docs, and
senatus split!
- 09 Request Access to Sub-Groups
- I think this is great - it allows the community to prioritize
people's contributions in the right way.
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!
- 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.
- 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?
On Monday, June 11, 2018 at 3:25:02 PM UTC-5, PMario wrote:
>
> Hi folks,
>
> you may be interested in a new Video series I did upload today. ... It'
> about improving Community Communication.
>
> The whole thing is an "experiement", so we can heavily test it, without
> damaging anything.
>
> It would be nice, if you guyes would request access to the different
> groups, that are interesting for you
>
> If you are interested in everything .... But just watch the videos and
>
>
> IMPORTANT.
>
>
> Starting from video 6 / 7 it t gets more and more developer centric, which
> is intended!
>
> We need to get the foundations wroking, then we can start to make it
> easier for end-users.
>
> have fun!
>
>
> https://www.youtube.com/playlist?list=PLuiC_HFhI4OyUiDGqvzB64mTQTURABjlW
>
>
>
>
--
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/e66ed104-4e53-4151-a705-1c28a8a2b11c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
