The problem, Seerah, is that those tickets on Jira are already open for months, with no fix in sight. Notice the "s" in "months". Ace3 won't even go into RC1 by October this year because nobody's working on it.
The whole forums seems to be moving kinda slow, but then again, I could just simply be checking it too often.
I would like to try and help out with Ace3Config, especially given the addon I'm working on is about to hit the config phase of production, so I guess I'll check out the tickets and see if there's anything I can help with.
What does it take to be allowed to contribute to ace3? I'd certainly be willing to help with some bits. For example I jira'd a bug in aceconfigcmd which literally requires a 2 line fix that I could easily do.
It's not clear to me at all that this is welcome or possible. The brief reaction I got on irc from nev was mildly negative (to the extend of "just don't use aceconfigcmd").
Hey guys, I know I'm swamped with trying to get curseforge launched. After that calms down I'm going to try to take a look at the remaining issues. Right now we only have 22 open issues, thats not bad honestly.
Time is short and there is a lot to be done. As far as contributing, one method would be to post patches on the tickets. We'd then review them and if found to be viable we'd include them into the main line.
As for Xinhuan's remark, I'll just ignore it, it's only there to spite and not constructive.
It was an attempt to get work started.
Known issues that are more or less simple fixes that doesn't need more than 10-20 minutes should be fixed quickly. Is the "Dead space at the bottom of the left-side options tree" issue really tricky to fix? It's probably just a miscalculated typo somewhere.
Ammo, you know quite well what I'm like, I'm not out to stir trouble, but really this is becoming more and more like abandonware. Ace3 bug responses are quick and acknowledged, but the speed of resolving them just isn't there. Seeing months of "we know about this bug, its already Jiraed" is not encouraging.
There's a lot of ideals and goals, opinions can differ (for example, about how Libstub should be embedded, WAU standards, etc), sparks can fly, but at the end of it, nothing is really being done. People are busy, everyone has things to do, raids to attend, real life to handle, work to complete. But people have offered to help, for example, Elsia mentioned 4 posts above that he'll like to help, but the response wasn't positive.
There is feedback, but feedback that isn't being used. In this light, it is difficult to get anything constructive done.
Ammo: Okay, you asked for it. I've created sub-tasks for each of the dropdown issues in ACE-161 because:
- Jira supports sub-tasks and this is an appropriate use for that feature
- reporting multiple issues in one Jira ticket is a good way to get only a couple of the issues fixed instead of all of them
I've also added screenshots to ACE-166, and have added ACE-184.
Kaelten: Thanks for checking in. I see that someone suggested a possible fix for ACE-166 in the comments for that ticket.