02-02-2025, 03:44 PM
(02-02-2025, 12:10 PM)ZeWaka Wrote:(02-02-2025, 07:14 AM)FlameArrow57 Wrote: Add a "Code help requested" or "Sprite help requested" GitHub label, so that people can easily add it to a PR they have in draft or in work
Are people really trolling GitHub to find projects to help with? I'm not aware, but if they are and this would help, we can look into adding this.
I'm not sure, and maybe a less ideal suggestion, but I think it wouldn't hurt (though maybe better suited if there were a lot more PRs). I think it would be more helpful for smaller PRs that aren't Player Project sized but still need additional help at the least. Unless something that requires 2 people should always be considered a Player Project. If Player Project usage of "Help Wanted" tag doesn't get additional help often then maybe it'd be an indicator for how this would go.
(02-02-2025, 12:10 PM)ZeWaka Wrote:(02-02-2025, 07:14 AM)FlameArrow57 Wrote: Additionally, I think there should be a Dev Disapproved tag, ...
I think if you seek an approval and don't get one, this is the same as a disapproval. I don't see a need for a tag.
I think I worded this in a wrong way. The suggestion was more at receiving an explicit "not interested" or "don't think this would work" feedback, rather than looking for or being ready for a response but not receiving anything. Not saying this hasn't ever happened.
(02-02-2025, 12:10 PM)ZeWaka Wrote:(02-02-2025, 07:14 AM)FlameArrow57 Wrote: I feel this is the exact place where devs should be providing direct feedback, not just when pinged directly but in general.
I agree. Personally, a reason why I have not given feedback on multiple player projects is purely just because I'm not super interested/engaged by them.
This makes sense and I'm not saying there's a problem with it. I think that it's not always clear when working on a project if it's that there's a lack of dev interest, or if that devs haven't had time to look at the project
(02-02-2025, 12:10 PM)ZeWaka Wrote:(02-02-2025, 07:14 AM)FlameArrow57 Wrote: I have no knowledge whatsoever of any testing that was done for this by devs/admins, which there has been at least some ...
We technically have a 'testmerged' github label that gets applied/removed when testmerging a PR. I wish there was better tracking, and perhaps that could come to the Goonhub round page in the future - with linking to the PR somehow.
Clarifying on this, I'm aware the code was testmerged and when. It just was not visible to me at how many times it was tested in game, no feedback from the tests given, and I was never notified of when any of it was happening. The other day I was given a comment on the PR itself of an experience in game from a dev, but I'm not sure from when it was, and it was a comment where I wanted to clarify the purpose of what was commented on