Recommended areas of focus for people who want to help out?

[Nyaa-rlathotep]

It might be useful to have a doc somewhere with general recommended areas of focus for people who are new to the engine and want to help out with coding and such.

The closest thing on the Godot site seemed to just be a link to a RocketChat instance, so there doesn't appear to be any publicly facing list of general priorities or areas that maybe need more manpower than expertise. Having something like that could help narrow down what sorts of things would be useful for people to take a crack at first.

[Captain-Wet-Beard]

That's part of what issues are for, to pitch a problem or look for a problem other people identify for you to put your talents towards fixing/ improving.

[baturinsky]

Documentation, guides, integration with external tools like VSCode.

[Nyaa-rlathotep]

That's part of what issues are for, to pitch a problem or look for a problem other people identify for you to put your talents towards fixing/ improving.

Somewhat, yeah. Though I expect there's probably many different things which could use some elbow grease, and requiring the experienced devs to create a whole issue for each of those before anyone outside the project knows they exist might be more taxing on the experienced devs than is needed.

Something super simple like a wiki page or text file could allow the experienced devs to just jot minor stuff down as they notice them, and then if someone feels like tackling the thing they can either do a PR or open an issue then, which would mean less overhead on the experienced devs while still allowing inexperienced ones to have some general ideas of what they could work on.

Of course, creating an individual issue isn't terribly difficult, but since godot is a large project, there's probably very many places where improvement is possible. And so it could still be useful to minimize how much effort the experienced devs need to put in to make others aware of things like that. Especially since good devs are probably more likely to want to make the issue be formatted nicely and maybe have some reasoning listed, and maybe add info about possible solutions, etc., etc., and it can quickly balloon into more work than is strictly needed at the time. Deliberately remembering to keep those kind of issue posts very short and sweet could remedy most of that, but that vigilance takes some effort, so something simpler could also avoid needing to be as constantly vigilant when the intent is primarily just to let people who don't know the codebase have some general ideas about what might be helpful for them to tackle.

Since the situation is also somewhat up in the air with the fork being recent (and there are decent odds of other forks cropping up in the near term before things eventually settle down), minimizing the amount of work that experienced devs need to do in order to herd newbies is probably a generally good idea. And allowing people who are interested in tackling an issue to be the ones who create the actual issue thread will help shift some of the grunt work away from the experienced devs.

It's a smidge of an unorthodox way to do things, but sometimes the nice ideal solutions end up being more work or psychological effort than they're maybe worth in some scenarios.

[Captain-Wet-Beard]

It would probably be a good idea to put together a document on the general goals the fork wants to achieve for sure. A lot of open source projects don't really have much direction, people just make changes they like and make a pull request, and because of poor communication a lot of times theres a bunch of discussion and changes back and forth which wastes a lot of time. Having things be more self directed is cool and all, but it isnt a bad idea to have a more formal feature request system where people discuss and idea 1st, and then popular ideas ending up on a list of desired changes for people to work based on. That sort of process probably needs a forum or a more dedicated discussion server on something like Telegram.

[DaelonSuzuka]

integration with external tools like VSCode.

I'm the developer of godot-tools, and I expect it'll take a LOT of divergence before the extension stops working with this fork. If there are any issues, please don't hesitate to ping me and I'll see what I can do to help.

[addmix]

Porting useful/wanted PRs from Godot is fairly easy, and in high demand. If the PR works properly in Godot, and solves the issue, you should port it over here.

[XORandom]

I may be biased, but it seems to me that first of all we need to focus on UX/UI and maintain compatibility with addons and godot code. If it becomes more convenient for users to use Redot, then there will be more people who are ready to contribute to its development.

Make several script tabs that can be opened simultaneously with the ability to customize them by groups. Make it so that the inspector panel can be minimized and it unfolds only when the mouse enters the area on the right, etc. Improve Regex support, add a func that allows you to blend multiple textures into one.

[SympleSynz]

I'm sorry if this is the wrong place to post this, but I have no idea how to open a new issue in this repo. I keep getting sent back to the godotengine repo.

[DaelonSuzuka]

I'm sorry if this is the wrong place to post this, but I have no idea how to open a new issue in this repo. I keep getting sent back to the godotengine repo.

Somebody needs to edit the Issue Templates here: https://github.com/Redot-Engine/redot-engine/tree/master/.github/ISSUE_TEMPLATE

@filipworksdev I don't know who's in charge around here but this sort of paperwork should be considered a high priority because of how much user interaction it's blocking. One chance to make a first impression and all that.

[SympleSynz]

I'm sorry if this is the wrong place to post this, but I have no idea how to open a new issue in this repo. I keep getting sent back to the godotengine repo.

Somebody needs to edit the Issue Templates here: https://github.com/Redot-Engine/redot-engine/tree/master/.github/ISSUE_TEMPLATE

I have a PR approved and ready to merge in for that, but the problem is the redot-proposal repo isn't set up to create the issues. That repo still points to godot as well

[Captain-Wet-Beard]

Redot-Engine/redot-engine#1 Redot-Engine/redot-engine#2 Redot-Engine/redot-engine#3 Redot-Engine/redot-engine#4 Redot-Engine/redot-engine#5 Redot-Engine/redot-engine#6 Redot-Engine/redot-engine#7 Redot-Engine/redot-engine#8 Redot-Engine/redot-engine#9 Redot-Engine/redot-engine#10 Redot-Engine/redot-engine#11 Redot-Engine/redot-engine#12 Redot-Engine/redot-engine#13 Redot-Engine/redot-engine#14 Redot-Engine/redot-engine#15 Redot-Engine/redot-engine#16 Redot-Engine/redot-engine#17 Redot-Engine/redot-engine#18 Redot-Engine/redot-engine#19 Redot-Engine/redot-engine#20 Redot-Engine/redot-engine#21 Redot-Engine/redot-engine#22 Redot-Engine/redot-engine#23 Redot-Engine/redot-engine#24 Redot-Engine/redot-engine#25 Redot-Engine/redot-engine#26 Redot-Engine/redot-engine#27 Redot-Engine/redot-engine#28 Redot-Engine/redot-engine#29 Redot-Engine/redot-engine#30 Redot-Engine/redot-engine#31 Redot-Engine/redot-engine#32 Redot-Engine/redot-engine#33 Redot-Engine/redot-engine#34 Redot-Engine/redot-proposals#13 Redot-Engine/redot-proposals#14 Redot-Engine/redot-proposals#15 Redot-Engine/redot-engine#38 Redot-Engine/redot-engine#39 Redot-Engine/redot-engine#40 Redot-Engine/redot-engine#41 Redot-Engine/redot-engine#42 Redot-Engine/redot-engine#43 Redot-Engine/redot-engine#44 Redot-Engine/redot-engine#45 Redot-Engine/redot-engine#46 Redot-Engine/redot-engine#47 Redot-Engine/redot-engine#48 Redot-Engine/redot-engine#49 Redot-Engine/redot-engine#50 Redot-Engine/redot-engine#51 Redot-Engine/redot-engine#52 Redot-Engine/redot-engine#53 Redot-Engine/redot-engine#54 Redot-Engine/redot-engine#55 Redot-Engine/redot-engine#56 Redot-Engine/redot-engine#57 Redot-Engine/redot-engine#58 Redot-Engine/redot-engine#59 Redot-Engine/redot-engine#60 Redot-Engine/redot-engine#61 Redot-Engine/redot-engine#62 Redot-Engine/redot-engine#63 Redot-Engine/redot-engine#64 Redot-Engine/redot-engine#65 Redot-Engine/redot-engine#66 Redot-Engine/redot-engine#67 Redot-Engine/redot-engine#68 Redot-Engine/redot-engine#69 Redot-Engine/redot-engine#70 Redot-Engine/redot-engine#71 Redot-Engine/redot-engine#72 Redot-Engine/redot-engine#73 Redot-Engine/redot-engine#74 Redot-Engine/redot-engine#75 Redot-Engine/redot-engine#76 Redot-Engine/redot-engine#77 Redot-Engine/redot-engine#78 Redot-Engine/redot-engine#79 Redot-Engine/redot-engine#80 Redot-Engine/redot-engine#81 Redot-Engine/redot-engine#82 Redot-Engine/redot-engine#83 Redot-Engine/redot-engine#84 Redot-Engine/redot-engine#85 Redot-Engine/redot-engine#86 Redot-Engine/redot-engine#87 Redot-Engine/redot-engine#88 Redot-Engine/redot-engine#89 Redot-Engine/redot-engine#90 Redot-Engine/redot-engine#91 Redot-Engine/redot-engine#92 Redot-Engine/redot-engine#93 Redot-Engine/redot-engine#94 Redot-Engine/redot-engine#95 Redot-Engine/redot-engine#96 Redot-Engine/redot-engine#97 Redot-Engine/redot-engine#98 Redot-Engine/redot-engine#99 Redot-Engine/redot-engine#100 Redot-Engine/redot-engine#101 Redot-Engine/redot-engine#102 Redot-Engine/redot-engine#103 Redot-Engine/redot-engine#104 Redot-Engine/redot-engine#105 Redot-Engine/redot-engine#106 Redot-Engine/redot-engine#107 Redot-Engine/redot-engine#108 Redot-Engine/redot-engine#109 Redot-Engine/redot-engine#110 Redot-Engine/redot-engine#111 Redot-Engine/redot-engine#112 Redot-Engine/redot-engine#113 Redot-Engine/redot-engine#114 Redot-Engine/redot-engine#115 Redot-Engine/redot-engine#116 Redot-Engine/redot-engine#117 Redot-Engine/redot-engine#118 Redot-Engine/redot-engine#119 Redot-Engine/redot-engine#120 Redot-Engine/redot-engine#121 Redot-Engine/redot-engine#122 Redot-Engine/redot-engine#123 Redot-Engine/redot-engine#124 Redot-Engine/redot-engine#125 Redot-Engine/redot-engine#126 Redot-Engine/redot-engine#127 Redot-Engine/redot-engine#128 Redot-Engine/redot-engine#129 Redot-Engine/redot-engine#130 Redot-Engine/redot-engine#131 Redot-Engine/redot-engine#132 Redot-Engine/redot-engine#133 Redot-Engine/redot-engine#134 Redot-Engine/redot-engine#135 Redot-Engine/redot-engine#136 Redot-Engine/redot-engine#137 Redot-Engine/redot-engine#138 Redot-Engine/redot-proposals#12 Redot-Engine/redot-engine#140 Redot-Engine/redot-engine#141 Redot-Engine/redot-engine#142 Redot-Engine/redot-engine#143 Redot-Engine/redot-engine#144 Redot-Engine/redot-engine#145 Redot-Engine/redot-proposals#17 Redot-Engine/redot-engine#147 Redot-Engine/redot-engine#148 Redot-Engine/redot-engine#149 Redot-Engine/redot-engine#150 Redot-Engine/redot-engine#151 Redot-Engine/redot-engine#152 Redot-Engine/redot-engine#153 Redot-Engine/redot-engine#154 Redot-Engine/redot-proposals#11 Redot-Engine/redot-engine#156 Redot-Engine/redot-engine#157 Redot-Engine/redot-engine#158 Redot-Engine/redot-engine#159 Redot-Engine/redot-engine#160 Redot-Engine/redot-engine#161 Redot-Engine/redot-engine#162 Redot-Engine/redot-engine#163 Redot-Engine/redot-engine#164 Redot-Engine/redot-engine#165 Redot-Engine/redot-engine#166 Redot-Engine/redot-engine#167 Redot-Engine/redot-engine#168 Redot-Engine/redot-engine#169 Redot-Engine/redot-engine#170 Redot-Engine/redot-engine#171 Redot-Engine/redot-engine#172 Redot-Engine/redot-proposals#18 Redot-Engine/redot-engine#174 Redot-Engine/redot-engine#175 Redot-Engine/redot-engine#176 Redot-Engine/redot-engine#177 Redot-Engine/redot-engine#178 Redot-Engine/redot-engine#179 Redot-Engine/redot-engine#180 Redot-Engine/redot-engine#181 Redot-Engine/redot-engine#182 Redot-Engine/redot-engine#183 Redot-Engine/redot-engine#184 Redot-Engine/redot-engine#185 Redot-Engine/redot-engine#186 Redot-Engine/redot-engine#187 Redot-Engine/redot-engine#188 Redot-Engine/redot-engine#189 Redot-Engine/redot-engine#190 Redot-Engine/redot-engine#191 Redot-Engine/redot-engine#192 Redot-Engine/redot-engine#193 Redot-Engine/redot-engine#194 Redot-Engine/redot-engine#195 Redot-Engine/redot-engine#196 Redot-Engine/redot-engine#197 Redot-Engine/redot-engine#198 Redot-Engine/redot-engine#199 Redot-Engine/redot-engine#200 Redot-Engine/redot-engine#201 Redot-Engine/redot-engine#202 Redot-Engine/redot-engine#203 Redot-Engine/redot-engine#204 Redot-Engine/redot-engine#205

And you wonder why some people start hating people like yourself, truly one of the world's greatest mysteries

[SkogiB]

I'm sorry if this is the wrong place to post this, but I have no idea how to open a new issue in this repo. I keep getting sent back to the godotengine repo.

Somebody needs to edit the Issue Templates here: https://github.com/Redot-Engine/redot-engine/tree/master/.github/ISSUE_TEMPLATE

@filipworksdev I don't know who's in charge around here but this sort of paperwork should be considered a high priority because of how much user interaction it's blocking. One chance to make a first impression and all that.

The template has been largely fixed, though I do see one non-link reference to Godot we need to change. There's a lot of web backend we don't have set up yet but we're getting there

[SkogiB]

I'm sorry if this is the wrong place to post this, but I have no idea how to open a new issue in this repo. I keep getting sent back to the godotengine repo.

Somebody needs to edit the Issue Templates here: https://github.com/Redot-Engine/redot-engine/tree/master/.github/ISSUE_TEMPLATE

I have a PR approved and ready to merge in for that, but the problem is the redot-proposal repo isn't set up to create the issues. That repo still points to godot as well

We also don't know how much we'll use that repo, it hasn't been priority yet as we're still working on a 4.3 stable build that we can then improve on. I'll look at some of this real quick and touch base with the core team

A link to that PR will help

On the original topic, I'll also chat with the internal team about how we want to handle that. It's definitely a good idea to have more than just "go to the github", though centralizing stuff on the github is nice too.

We're taking a loot at the proposals repo now, we'll see what we can do without pulling man power from the 4.3 work.

[tokengamedev]

redot-proposal (https://github.com/Redot-Engine/redot-proposals) is up and running, please look into issues there and see where you can help. In case you have ideas, don't hesitate to add an issue.