Godot-proposals: Add a godot-ideas referral to the issue template

[willnationsdev]

Describe the project you are working on:
Managing community expectations for the Godot-Proposals repository.

Describe how this feature / enhancement will help your project:
I think we should add a blurb in the godot-proposals issue template that redirects people to the new godot-extended-libraries/godot-ideas repository if they do not feel as though they can adequately answer the questions, or if they already know that their proposal is not applicable to the engine development itself.

The reason this would help, aside from things already brought up in #47, is that it drives users awareness of this space up.

Show a mock up screenshots/video or a flow diagram explaining how your proposal will work:

See below.

Describe implementation detail for your proposal (in code), if possible:

Just add a comment to the top of the message, exactly like the one in godotengine/godot that tells people they can go to godot-extended-libraries/godot-ideas instead.

\

Something like that.

If this enhancement will not be used often, can it be worked around with a few lines of script?:

Relates to the GitHub repository, not Godot itself.

Is there a reason why this should be core and not an add-on in the asset library?:

See above.

[willnationsdev]

cc @Xrayez @clayjohn

[Xrayez]

There are stuff which doesn't fit godot-proposals, like extended discussions, trackers, controversial topics etc. Also, this can channel proposals like #58 to community place.

[golddotasksquestions]

Unfortunately as it is right now, I feel like the reddit post alone just adds more confusion than anything.

For this to work and be of actual value, instructions and purpose have to be crystal clear and super easy grasp to a user who never participated or cared about this discussion.
Crossed out text in someones private wall-of-text reddit post does the opposite.
Channeling needs to happen at the Point Of Interest. Which is the place where people go to submit an issue.
As someone has mentioned in the reddit post, it also needs official blessing. So if core devs want this to work, there will have to be a blogpost about this as well to make clear this is now a legitimate way to voice ideas concerns, brainstorm or have a discussion about plugins and modules however it will be maintained by non core members.

Otherwise it will always just be someone private Github rant page and will probably die more quickly than my 12 yo cousins Youtube "gaming channel".

I still wish it would be integrated into the official Github and just be a seperate Repo like "Proposals".

[willnationsdev]

@golddotasksquestions

Hard to argue with the reality of things. No official support means it's more likely to just die. I'll maintain it either way, since I think it has a valid use-case, but we'll just have to wait and see what akien/reduz decide to do.

[Xrayez]

Any updates? Almost a year passed. 😕

@akien-mga we'd like to know your opinion regarding this proposal. Look at the sheer number of current proposals which won't be ever implemented in Godot directly (as previously stated by clayjohn), some are just discussions. But if that's acceptable for GIP, than that's totally fine as-is, but then we'd like to expect an appropriate conduct from the core developers, currently they outright express disapproval for something which does not belong to Godot itself, also see #779 (at least the way I see it, lately I've noticed that some are just getting tired to repeat the same song of "this should be a plugin" 🙂, and I myself started to follow the same trend unfortunately, but trying to bring myself up to consciousness every time).

And probably rightly so, because the scope of proposed features should also be defined, currently people assume that Godot is still a small engine which keeps growing (Waiting for Godot, as regurgitated by some community members), but according to the development direction I've experienced myself, it seems like it's not the case, the current direction is exactly to keep the engine as small as possible at its core, so we just ask for clarifications and coming up with correct expectations, I see nothing wrong with that personally.

Here's a good example for a Godot Idea which doesn't belong to GIP: godot-extended-libraries/godot-ideas#5. These kind of discussions and further implementations can bring useful insights as to what core functionality may be required to help implement this idea to reality, without getting into useless demagogy of "no, this should not be core, this should be plugin" etc, which only make it worse to the desired outcome. Ideas would be exactly the answer to "Describe the project you're working on", because you'll instantly see that something is already needed rather than speculated.

[Calinou]

If you want to go that route, I think adding a mention of godot-ideas in the README is a better idea than in the issue template. Many people may not realize that they can copy a link from the issue template to their browser's address bar (believe me on this :stuck_out_tongue:).

I would recommend amending rule 2 for submitting proposals in the current README:

1. All proposals must be linked to a substantive use-case. In justifying your proposal, it is not enough to say it would be "nice" or "helpful". Use the template to show how Godot is not currently meeting your needs and then explain how your proposal will meet a particular need.

to:

1. All proposals must be linked to a substantive use-case. In justifying your proposal, it is not enough to say it would be "nice" or "helpful". Use the template to show how Godot is not currently meeting your needs and then explain how your proposal will meet a particular need. If you feel that you cannot provide highly detailed instructions with the proposal, consider creating a more simple, open-ended issue in the unofficial, community-maintained Godot Ideas repository.