todo: Are there better ways to manage comments and changes to draft level documents?

[kidayasuo]

With draft stage changes can be large and complete write. How we can track history of discussions and results?

[himorin]

Does this issue targets ones in wiki of jlreq-d repository, or something else like ones written in respec format or something?

[kidayasuo]

This is about jlreq-d draft that is currently uses wiki within jlreq-d repository.

[r12a]

Can one not raise issues against the wiki in the GH issue list?

[tgraham-antenna]

As you may already know, GitHub also offers discussions. See https://docs.github.com/ja/discussions and https://docs.github.com/en/discussions

Discussions work like issues but with a gentler name and with the possibility to close a discussion as being outdated or a duplicate. Issues can be converted into discussions, and discussions into issues.

[kidayasuo]

Thank you @r12a and @tgraham-antenna for suggestions! When the process of GH issue is felt a bit too heavy the discussions seem to serve as a good alternative method. I will investigate.

[kidayasuo]

It seems I can't enable the "discussions" in jlreq-d repository. Is it something I need to ask you @r12a ? or actually, it would be great if you could assign me necessary permissions. (thanks!)

[r12a]

@kidayasuo i created a team of moderators for jlreq-d repo. You should receive an invitation. I'm hoping that this will give you the necessary permissions.

[kidayasuo]

I now see the discussions tab as well as the settings menu. Thank you @r12a!

[kidayasuo]

We've moved documents under "~/Code/drafts/", and will use issue to track change requests. also we'll use discussions for more broad discussions. Now I believe we can close this issue.