--
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 tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/a887606f-4c33-4e1d-89a7-19dbd1efc7fbn%40googlegroups.com.
GitHub’s mission is focussed on developers, a very different audience than TiddlyWiki.
GitHub Discussions might make sense for the Dev group but I worry that the whole mis-en-scene of GitHub is much too complicated and confusing for mainstream users, and so I struggle to see us adopting it for the main group.
Having said that, adoption by plugin authors such as yourself seems like a great way to investigate further. Many plugin authors are already on GitHub and so having a single stack of notifications to pay attention could be very useful.
--
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 tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/be80df8e-ffd3-4aff-9112-e369723e0430n%40googlegroups.com.
I think a reasonable proposal would be to move the Dev group to GitHub discussions:
* The developer community is already on GitHub because it's where the core development happens* Google Groups doesn't serve the developer community very well, lacking syntax highlighted code blocks, and the ability to reference existing issues and PRs* Switching the Dev Google Group to read-only and redirecting to GitHub discussions would give us useful experience for any subsequent move of the main discussion group
I don't see much point in just enabling discussions on the TW5 repository without purposely establishing the community there. People can experiment with discussions on other repositories.
Software communities don’t just write code together. They brainstorm feature ideas, help new users get their bearings, and collaborate on best ways to use the software. Until now, GitHub only offered issues and pull requests as places to have these conversations. But issues and pull requests both have a linear format—well suited for merging code, but not for creating a community knowledge base. Conversations need their own place—that’s what GitHub Discussions is for.
On 10 Dec 2020, at 08:41, Mohammad Rahmani <mohammad...@gmail.com> wrote:
Hi Jeremy,
I think a reasonable proposal would be to move the Dev group to GitHub discussions:Good idea!* The developer community is already on GitHub because it's where the core development happens* Google Groups doesn't serve the developer community very well, lacking syntax highlighted code blocks, and the ability to reference existing issues and PRs* Switching the Dev Google Group to read-only and redirecting to GitHub discussions would give us useful experience for any subsequent move of the main discussion group
I don't see much point in just enabling discussions on the TW5 repository without purposely establishing the community there. People can experiment with discussions on other repositories.
<image.png>There are some useful features: You can select the best answers, you can have categories, like ideas! you can have team discussion, pinned discussion, filter answered and unanswered questions, simply refer to issue and PR, and much more,...See GitHub announcement statementSoftware communities don’t just write code together. They brainstorm feature ideas, help new users get their bearings, and collaborate on best ways to use the software. Until now, GitHub only offered issues and pull requests as places to have these conversations. But issues and pull requests both have a linear format—well suited for merging code, but not for creating a community knowledge base. Conversations need their own place—that’s what GitHub Discussions is for.So this is a good move!Thank you Jeremy!--Mohammad
--
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 tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CAAV1gMCy%3DGHYo%2BJs1cBSZg-VrLbmAPWsMUZRKKe4%2BPHDRSfh6g%40mail.gmail.com.
One feature of GitHub discussions is that one can convert issues into discussions, either individually or in bulk. I can imagine that that could be very helpful for us.
I’ve set up https://github.com/Jermolene/TiddlyWiki5/discussions and will make a post about it shortly to the Dev group.
Best wishesJeremy.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/D18FBABC-FFC7-4506-A757-A9D5D3982879%40gmail.com.
Welcome to the TiddlyWiki5 developer discussion group. This is the place for talking about TiddlyWiki core internals and development, and plugin development issues. For general assistance with TiddlyWiki5 features, macros, formatting, documentation, etc., please see the TiddlyWiki group.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/D18FBABC-FFC7-4506-A757-A9D5D3982879%40gmail.com.
GitHub’s mission is focussed on developers, a very different audience than TiddlyWiki.
GitHub Discussions might make sense for the Dev group but I worry that the whole mis-en-scene of GitHub is much too complicated and confusing for mainstream users, and so I struggle to see us adopting it for the main group.
On 12 Dec 2020, at 09:23, TiddlyTweeter <tiddly...@assays.tv> wrote:
--
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 tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/80831c58-c720-4b12-bfa0-8d181b9d8860n%40googlegroups.com.