Replies: 7 comments 7 replies
-
|
Nice move Jeremy, it's more intuitive to have the code and related discussion in the same place |
Beta Was this translation helpful? Give feedback.
-
|
@Jermolene - please pin your above post There is also categories, when someone posts he/she has to select a category, so you can add more categories if you think its better for directing discussions. |
Beta Was this translation helpful? Give feedback.
-
|
@Jermolene
You may add some specific categories if you think it is better to have different areas for discussions. I am not sure if who make a question can select the best answer or it is the admin can do this |
Beta Was this translation helpful? Give feedback.
-
|
@Jermolene this will be helpful. I've created issues/PRs in the last weeks just to have a discussion as this is where most developers are active. Hopefully we can also convert some current issues and PRs into discussions. At the moment it takes a lot of time to find issues that are actionable, i.e. where this consensus on what to do and only the implementation is lacking. |
Beta Was this translation helpful? Give feedback.
-
|
@saqimtiaz - I think it should be recommended in Jeremy welcome message, always start discussion, and when every aspects were clear, and the discussion is actionable, then author coverts his/her discussion to suitable ticket (PR or Issue). |
Beta Was this translation helpful? Give feedback.
-
|
Code and related discussion in the same place is an advantage. But is there a RSS feed? The big advantage for me of the Google Groups was easy reading with a RSS reader. |
Beta Was this translation helpful? Give feedback.
-
|
Sadly, GitHub doesn't support RSS or Atom. |
Beta Was this translation helpful? Give feedback.
-
|
I will miss the RSS/Atom feeds and the topic digests by email. I hope github will add these in the near future. For now I have enabled notifications for every new post |
Beta Was this translation helpful? Give feedback.
-
|
@Jermolene can we change the welcome message to make it clear these are developer discussions rather than end-user? We are starting to get posts here about end-user discussions that are better suited for the google group. |
Beta Was this translation helpful? Give feedback.
-
|
I am referring to this welcome message:
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks @saqimtiaz I've added the word "Developer". Annoyingly one doesn't seem to be able to change the banner image. |
Beta Was this translation helpful? Give feedback.
-
|
Is there any way to pin this Welcome message to the top? |
Beta Was this translation helpful? Give feedback.
-
|
This conversation is actually already pinned to the top, GitHub just has a slightly strange way of implementing it: it appears as the banner at the top of the discussion page (see the illustration above). |
Beta Was this translation helpful? Give feedback.
-
|
yeah, I had NO idea that was a link! Very odd UI/UX decision there. Oh well, I tried LOL Thanks for the info! |
Beta Was this translation helpful? Give feedback.
-
Welcome!
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.
When posting a question, please use a short "[keyword]" in the subject line to indicate the general area of concern. Include your OS, Browser, Tiddlywiki version and other relevant details in your message so that the community can help you better.
Visit tiddlywiki.com to use, learn, read about & download TiddlyWiki.
Discussions about TiddlyWiki Classic have moved to the TiddlyWikiClassic group
An enhanced group search facility is available via mail-archive.com
Please use this thread for discussion about our adoption of GitHub Discussions.
Beta Was this translation helpful? Give feedback.
All reactions