Remove/Thread GitHub discussions or the suggestions forum.

[Shadeykins]

 

GitHub is great for bug tracking, and tracking changes, for coders.

 

1) It makes things easy and convenient (bugtracking).

 

2) It makes the creation of changelogs easier.

 

3) It avoids organizational hell.

 

With that said...

 

GitHub is not great for suggestions and discussion, whilst having a discussion forum because...

 

1) Most of the community if asked probably don't know what it is, and is therefore removed from discussion.

 

2) Most of the people who do know what it is, do not participate on it and are therefore removed from discussion.

 

4) It adds barriers between the community and the coding team, who will typically look at the GitHub and give more attention to PR's than forum suggestions.

 

5) It requires a separate account, and demands attention be divided between what's essentially now two forums.

 

6) I can't count to five.

 

We have three places to "discuss/suggest" changes at present, which leads to an inability to appropriately ascertain community wants/needs.

 

It should be bundled into one spot by...

 

1) Removing the Code Discussion subforum.

 

2) Not using GitHub for discussions, or creating linked threads in the present suggestion forums leading to the GitHub regarding suggestions.

 

Or...

 

1) Removing the Code Discussion subforum, and it's parent, the suggestion forum - replacing them with a link to the GitHub.

 

Discuss.

 

[tigercat2000]

 

No fucking way. A thread for every single PR? That would be, at best, chaos, at worst, downright fucking hell.

All three places have very clear intentions. Suggestions is for new ideas, things people would like to see. Code discussion is for discussing current code which people would like to see changed. Github is where discussion takes place before PR's are merged into the code.

 

[Tauka Usanake]

 

Shadey makes a bunch of good points and I agree with them. However you can't remove one or the other. Tigercat stated that all three have their usage and I see it too. What the problem is with having all three is that more often than not Suggestion topics are not linked with a GitHub counterpart and that's IF a suggestion gets turned into any sort of project or PR. The issue is not having multiple places to talk about additions to the server. The issue is that there are lots of ideas but no one who wants or is capable of implementing them and have no place on the repository for discussion.

Running on that, the GitHub issues and PR sections are used for discussions on only those topics. Issues are useful for finding out what sort of problem exists in the code and PRs are for talking about and addition to the server that is already in the works. If that PR joints off from a Suggestion then it should be linked appropriately. If not then maybe it should have been before getting a PR to see what the community's thought on it would be.

 

TL;DR - Suggestions are for things that don't exist but might, and should be accordingly linked to a PR if made. GitHub is for things that are getting implemented and are being activity worked on.

 

[Shadeykins]

 

No fucking way. A thread for every single PR? That would be, at best, chaos, at worst, downright fucking hell.

All three places have very clear intentions. Suggestions is for new ideas, things people would like to see. Code discussion is for discussing current code which people would like to see changed. Github is where discussion takes place before PR's are merged into the code.

 

Not for every single PR, no.

 

But important ones? Absolutely.

 

More often than not we skip the first two steps (Suggestions, Code Discussion) and go straight to the PR which is barely visible to the community.

 

Suggestions is basically a graveyard for broken dreams at this point.

 

I can't even begin to think of the last suggestion that was actually implemented.

 

[Tauka Usanake]

 

I can't even begin to think of the last suggestion that was actually implemented.

You mean besides R&D getting lockboxed a bunch? Then again that was more of a balancing issue than a feature request.