Is this the official place to report bugs?
This forum topic looks like where you would go to report a bug. We are accumulating bug reports here. Sorry for having been out of touch with the project over the last few months, but I'm only now noticing the bugs reports that have accumulated here.
@lafayette Generally this gives regular users that won't go to github a place to submit bugs. If they are actually bugs then I usually look to create a github issue for them and link back to any discussion here.
@lafayette I personally use this one for map only bugs (example, my two Civil War topics) and, instead, post engine bugs in your GitHub repository.
I'm concerned that:
A. we are inviting many of the same historical problems we have already seen:
- confusion on where to report, how to report, what to report
- divided effort of devs to track and keep up with reports
- duplicated and out of date documentation which lead to additional confusion
B. Silo'd responsibility. @redrum if you take a break then we'll have a problem with bug reports getting stale and languishing here. While it's great you're taking care of it, not having a team process get built up in a trial by fire to handle this I think in the long term does us more harm than good.
C. inviting confusion, new players asking the 'regulars' what to do, will be referred to here despite all other official documentation, links and buttons.
D. Doing things for the wrong reason. Github got a bad rap and is 5% understood. Even seeing terms like "your github repository" is evidence of this and is off-base.
I think part of what makes this hard is a lack of understanding of why dev's use bug tracking software, and why forum does not satisfy those needs (said another way, forum is not bug tracking software). To make it even harder, source control management is yet another piece of software. So the github repo has nothing to do with this, we could turn off the issue queue if we wanted. I think though we find that there are problems when we try to do project management, task tracking, bug tracking, research reporting, project proposals, general discussion all from forum software. You can do some of that in forums, but trying to do it all for something as complex as TripleA I think will lead again to many of the problems we have already seen.
I'm also suggesting a slippery slope here, and I think we are seeing it. As more and more users and infrastructure is dedicated to reporting bugs here, we'll expand on that and want more of the bug tracking and reporting to be done in the one place. Again, we've seen what happens going down that road, and we know it won't work fundamentally as project task tracking is too complex to effectively handle in forums.
@lafayette Maybe you want to edit this:
@cernel Or delete it np here
@lafayette Well the way I see it is github issues are the actual bug tracker. Almost all games have a forum section that regular users can report bugs/issues/problems which are then reviewed and added to the actual bug tracker if deemed actual bugs. I personally don't really see a problem with that and that is how it generally worked with the old forum and SourceForge issues list. If you think you can get all users to just create an issue directly on github then you could try that as well but I think you still need something on the forum pointing to that.
Besides... the entire thing is not just one guy... all of the Devs pop in here to scan the forums... and as a last chance desperate measure there are people like myself and @prastle that scan here daily and have at least a working knowledge of GIT to transfer issues there that are critical.
If you think you can get all users to just create an issue directly on github then you could try that as well but I think you still need something on the forum pointing to that.
@prastle that scan here daily and have at least a working knowledge of GIT to transfer issues there that are critical
- It would be more efficient to have that be in one place. You're describing what is already done for the official bug queue, it's a duplicated effort to do that here too.
- Scanning forums does not work well:
A. not clear what needs work, need to read a full forum post to know status and even then the issue might be closed.
B. older issues potentially lost. Are they actually followed up on and fixed? (these are all problems that are solved by proper task tracking software)
C. there is more that could have been done on some reports. It would be hard to know without some additional technical background. Sometimes you need a dev to jump in and say "oh, that is actually this other thing, and it is easy to fix, you totally should not ignore that problem and I'll have it fixed in 5 minutes, OMG if i had only known sooner it would have been fixed."
And again, the original list of concerns I raised I don't see necessarily addressed or resolved.
Having a forum section titled "Bug Reports" I think is intrinsically the problem. Keeping that I think is difficult without repeating previous project mistakes/problems.
all of the Devs pop in here to scan the forums
Respectfully I'm not sure about that, and it's an important difference.
A. It's a problem to scan and track multiple places. Efficiency loss. We don't have so many devs we can afford inefficiency.
B. I don't think all devs do that scanning. There is not the time, we have a place to scan for bugs, and I did not scan here so clearly not all devs do that. I don't see devs keeping up consistently, and I suspect we'll see cases again where various reports get lost in the winds of forum paging.
@lafayette All good. I know when I'm out of my league. I leave this to better minds than my own.
(the above topic is secreted in the moderators only section, so you need to be logged in and belonging to a group having the privilege to access Bunker)
Thank you everyone for chiming in, the feedback is welcome. In short, I'd like for us to consider options on this:
- status quo - keep things as is
- rename 'bug' category to something else
- merge 'bug' category to another category like 'help & ideas'
- formalize user bug reports to land in forums first, forums mod team will create bug reports in official github issues task queue as needed
- devs bite the bullet and consolidate to forums, mitigate/solve any tracking problems we have in forums and just use forums for all bug reports and tracking
- other direction, migrate all bug forum threads to bug tracking in github issues and focus on making it easy for bug reports to godirectly to github issues
All in all, it does seem there is a team here that is willing to take a first crack at helping users, and I can't see that as anything but as a good thing and I'm really happy that is available. I'd like the outcome of this thread and discussion to be a retrospective of how things have been working so far relative to bugs, and for us to identify what next steps we can take to be more organized and more effective. I'm curious how the group feels about our options, and if there is something else we could/should consider doing.
I will speak my mind freely, and I hope that I am not misunderstood. I don't want to create a split, but I will point out a split that I all ready see.... not necessarily a negative one, but one I think we have to recognize and live with.
I have always felt that the TripleA community is made up of very different people, ranging from people who hang out and do work at Github, who have programming skills, interests and expertise enough to work on the engine, some of them rarely visiting the forum and engaging with that part of the community ... and ranging to the other end of the spectrum; TripleA pure gamers who have little or very limited technical knowledge and no interest either in regards to Github, game engine and even XMLs and game files. Still this group can be enthusiastic fans, playing for fun, contributing to the donation drive, giving great user based feedback, and produce ideas that fuel game development etc. (Of course some people are a mix of the two caricatures and some might not fit at all.)
It was envisioned at the old forum to have the new forum bring people more together, but as I see it, after looking back, people are different and have different interests regarding TripleA. We cannot force people together or expect them to be of equal mind. We cannot look at community members and say, that a new member is the one who has just started to play the game, when he gets more experienced he will engage himself in the technical side of the game, after that he will go and engage himself in Github, and finally when his motivated enough, he will help out in regards to development. That's is only a description of like 1% of TripleA fans. The community as a whole is and will remain a bunch of very different people with different interests .... many of them will NEVER go register at Github just to report a bug, and if they do, not all developers will be satisfied with their maybe "amateurish", un-detailed, lacking bug report anyway, and be irritated about the reporter not conforming to the standard report-form or understanding what people are saying at Github. Finally, if a developer can be absent from the forum for months and if many players (most I would guess) never think about Github or would rather stay away, I see it as the final proof of community members being very different people with very different interests.
My main point is, if TripleA development was to force community members to register at Github because it would be "convenient" for development, I must say that I see a lack of understanding or recognition about how different community members are and what kind of involvement members might want to engage in. A proposal that would demand the casual player to register at Github just to place a bug report (one that he might not even be sure is a bug, or he is "certain", but in reality it isn't) would be a step that excluded voices... a step in the wrong direction if you ask me.
If I should be more constructive, and say something else than "Bug reporting at forum seems to be great", I would propose a new in-game/launcher based bug report system. Maybe it could even auto upload crashes. But then again, the forum's bug report category brings folk into the forum and lets them see the whole thing, maybe motivating them to socialise, engage in discussions, try out map development, maybe even offer to help out with engine development.
RogerCooper last edited by
@frostion I would say report your bugs here first, as in many cases what looks like a bug is a misunderstood feature. Then if it can't be resolved, make a formal bug report on GitHub.
@lafayette My suggestion is tracking map bugs in forum and engine bugs in the official TripleA issues tracker. This would need to be made clear to the users by updating the @prastle post I linked and changing the name of the subforum to "Map Bug Reports". We can, then, lock all threads that aren't pending map-only issues. Of course, this would require the developers to keep an eye on the forum (probably good anyways), to avoid that engine bugs remain forgotten in here (locking them and telling the users they need to go in GitHub); so, it's your call if you like this idea and want to roll with it. You'll have, then, to decide what to do with the map bug reports in your tracker. Also turning off the issue queue in all map repositories.
Also, minor note, it's not really true that currently we have duplicate places for bug reports.
We rather have triplicate places, since there is also the bug reporting in the issue queque of each map.
For example, you can find bug reports about WWII Global in Forum, in the main GitHub tracker and in the issue queque for the map.
Like here you have a few bug reports too:
Also we have bug reporters that either don't know about this forum or if they knew, would not create another account here, but would report their issues on their platform.
So we have axisandallies.org as another place for bug reports. Most of those can be resolved easily and quickly as many of them are issues on the user's side. However we had issues in the past that were valid , could not be resolved instantly and thus needed to be transferred to a (whatever) appropriate place (at GitHub in the past).
Personally I would not think of transferring an issue from one forum to another one, if Github appeared to be the appropriate place to note it.
@panther Yep. Generally, if there is a true engine/map bug not just user error we should look to get it into a github issue as that is the actual queue of bugs to fix.