The change to the documentation system itself was only documented with a single line. Or maybe not even that. I don't know what it means to work on the documentation branch. Do I make a branch below the documentation branch, or call my own branch by that name?
As far as I can tell, the tiddler, Improving TiddlyWiki Documentation was not updated to reflect the changes. Thanks! On Friday, December 6, 2019 at 2:16:47 AM UTC-8, Jeremy Ruston wrote: > > A couple of thoughts: > > * Pinning should never have been globally available. I appreciate the > argument that no great harm was done, but it evidently created confusion as > to who could see that a thread had been pinned > * We should agree on general rules for what threads might qualify for > being pinned. To me, pinning would start with urgent announcements (e.g. if > discovered a serious bug in a release and wanted to warn people to > upgrade), important on-going informational threads like “Newbies start here” > * Generally I think it might be interesting to experiment with more use of > pinned threads that are updated by an admin (e.g. we could have a thread > “Announcements December 2019” that a volunteer like (say) Mohammad might > undertake to update on a regular basis) > * As to plugin announcements, maybe the route to the widest audience is to > put them on tiddlywiki.com. For a year now we’ve had the ability to do > near instantaneous updates to tiddlywiki.com just by merging a pull > request. It’s a shame we haven’t seen more use made of this; for the first > time, tiddlywiki.com is editable by anyone who can create a PR > * We can appoint as more group managers if we need to > > Best wishes > > Jeremy > > On 6 Dec 2019, at 09:45, TonyM <[email protected] <javascript:>> wrote: > > Bit of a storm in a tea cup > > I had never pinned anything before. Found I could and assumed it was > private. Two other pins occurred then I found out it was public and started > a pin exit plan. > > As far as I can see this has being the extent of pins in the last year or > more so, with respect, I suggest education before restricting or dictating. > > This is only my opinion but I have seen dozens of forums fail by the > overzelouse slippery slope arguements that gradually disable features, > create moderator roles where none were necessary, all due to perceived only > possibilities. > > As soon as you remove member responsibility you stop them taking > responsibility. > > By the way my two pins received substantial contributions as a result, to > a community wide need. > > Please solve problems by education first, not reducing things to an > imaginary lowest common denominator. > > Sincerly > Tony > > -- > 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] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/c508d140-c1c8-4d3c-9e04-60f08190be15%40googlegroups.com > . > > > -- 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/52466f0d-3ff4-4b17-b0c6-c9975d5d3d1c%40googlegroups.com.
