On Friday, June 15, 2018 at 1:28:12 AM UTC+2, TonyM wrote: > > Sounding really good, but I hope the "limitations do not restrict our > futures" >
Which limitations? > To clarify, You said you did not understand my line > > I can still progress the matter but presenting a possible specification, > some detailed requirements or research that specifies relevant tiddlers > that make coding the solution much more straight forward. > > What I am saying is although I am not yet at the skill level to build push > able items, I am capable of the above input to a change request, making it > easier for the developer to action. We should encourage others to do this > support work as well. > Ah, OK. ... That's exactly the point with different "roles". ... eg: The "reporter role" is able to assign labels like: discussion, bug, feature-request ... Which makes it easier for developers to "scan" the lists. ... "developer role" is able to create new feature-branches and trigger the automated build process for "prereleases", so everyone can test new functions. ... but only the "master-role" and higher are able to push to master, after the final review process is finished and eg: 2 other developers reviewed and tested the code ... For documentation it should be much easier to get "developer" and even "master" status. Since it won't break the main core code. ... have fun! mario -- 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/e0cd2471-55cc-4de7-b2c8-14040c00dcbe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
