The NEW Official Unofficial Discourse bug tracker!
-
Yeah, we've mentioned how WTF using a forum as a bug tracker is.
OK, can you show me another open source project similar to Discourse in scale (5 man team) that fixed 4 bugs in the last 24 hours using their bug tracker
-
Fixing bugs isn't the problem.
The bugs fixed by Adhocracy is just silly in comparison to the issues out there. I'll be home in about 2 hours to give you more concrete examples as I start adding things to the bug tracker.
I would argue that a bugtracker is more vital because you have limited resources (IE: 5 man team)
-
That is nothing, you are not including the number of bugs that Jeff deleted because his definition of bug is different than...the rest of humanity.
-
You can't call it nothing, but I would attribute a suspected 25% (minimum) to both open & closed sides for 'vanished' items.
-
OK, can you show me another open source project similar to Discourse in scale (5 man team) that fixed 4 bugs in the last 24 hours using their bug tracker
Nope. I tend to not track open source projects as much as possible.
-
I would attribute a suspected 25% (minimum) to both open & closed sides for 'vanished' items.
Because somehow magically you can hard disable the delete button in bug trackers and make it impossible to delete bugs.
Nope. I tend to not track open source projects as much as possible.
Filed under: I have zero experience with open source, but here is how you should run your open source project, your'e welcome
-
Aww, I was going to post a couple bugs from that thread but they removed the "" quotes so they can no longer be reproduced.
ℵ still works! Good.
-
Because somehow magically you can hard disable the delete button in bug trackers and make it impossible to delete bugs.
You should never delete bugs, even after closed and especially if you think they are not bugs. If you do not have historical data on what you have fixed, you can never go back and see how many are regressions. If you delete bugs that you think are not, then you also delete your explanation as to why you disagree with them being filed as bugs and no one can ever do a search to see if a bug has already been filed and then you end up getting the same shit filed over and over again.
-
Perhaps you have too big a scale for your resources and your technical debt works to your disadvantage as a consequence.
Also, I've worked in open source with a project of non-trivial complexity and fixed more bugs than that in a single day before now, including doing functional testing and regression testing. 4 bugs in 24 hours is an arbitrary stat that is meaningless.
Not being funny but your attitude here stinks like Jeff's. You cannot impress us with your sorcerer's ways when we're all sorcerers here.
-
Because somehow magically you can hard disable the delete button in bug trackers and make it impossible to delete bugs.
You are correct, I can't . . . On your board.
But this isn't going to be your board. This is going to be a list of discourse bugs that I control, and you're welcome to review. And I am implementing a policy that no bug will ever be deleted. They can be closed;wontfix - but they will never be deleted.
-
But this isn't going to be your board. This is going to be a list of discourse bugs that I control, and you're welcome to review. And I am implementing a policy that no bug will ever be deleted. They can be closed;wontfix - but they will never be deleted.
Whomever supports him, give this post a like or a quote to show your support.
-
Because somehow magically you can hard disable the delete button in bug trackers and make it impossible to delete bugs.
I can't recall ever using a bug tracker that had a delete button. "Closed - not a bug" yes, but not delete.
-
My issue here is you are all complaining, "you need a new tool" when the issue you have is "you need different process"
Tools do not dictate process.
-
Ah, but see @sam, the reason I haven't posted it on meta.d yet is because the data isn't in the tool yet. My plan was to populate the tool, then propose the process, and create an automated tool to populate the tracking tool.
You see, I'm efficient like that.
-
Filed under: I have zero experience with open source, but here is how you should run your open source project, your'e welcome
It doesn't take much to figure out that a forum used as a bug tracker has many WTFs, no matter what kind of project you are talking about.
-
Tools do not dictate process.
Good tools do not dictate process, but bad tools can dictate bad processes when they are shoehorned to do shit they were never meant to do. Using a forum as a bug tracker is not "dog fooding" (I fucking hate that term), it is trying to drive screws with a hammer.
-
Arguing right now doesn't really matter. Let me populate the information tonight, and just show how useful it is rather than argue about it being useful. It's just one of those things you have to see to believe, and then you are awed and amazed when six months down the road you can actually search and find that regression bug, and how you originally fixed the issue.
-
@Matches Is Doing It Wrong™<t3103p18>
-
You know what I am 100% supportive of this, if it kills off the bugs category here and Discourse team just need to go to your bug tracker to see the bugs TDWTF have. It is about 10k times better than what we have now, with you reporting bugs we don't look at on your forum.
Makes it much easier for me to open up bugs on meta
-
@sam If you are willing to actually use it, I can give you and @eviltrout status update permissions on the bugs if you report them to meta.d so you don't have to wonder where you left off on reporting them.
This isn't some jab at Discourse that is completely without constructive thought. I actually did pay money for the domain, and it's tied to my personal business bitbucket which means I don't want bullshit on there. I just want you guys to stop pretending we're making shit up when it comes to the number of bugs we find and experience literally every single day.
The bug tracker will also let you know how serious we think it is (most fall under trivial/minor category)
-
if it kills off the bugs category here
That will probably never happen. We still like talking about the bugs.
Discourse team just need to go to your bug tracker to see the bugs TDWTF have.
That would be nice. Then we would have one more argument to give Alex for kicking you all back down to non-staff levels.
-
I just wanted to chime in and say thank you, @Matches for doing something constructive in this whole TDWTF - Discourse debacle.
@Sam I am currently not really sure why you are so riled up about this. The users here - for once - aren't just criticising Discourse. They aren't even criticising the work you guys put in there. They are trying to make the project better by adding a bugtracker they can agree with. Isn't this the best for you guys, too. You don't HAVE to use it. You don't even have to look at it. But you can. You get more options because TDWTF users think, using a real bug-tracker is better than using a forum. In a way you could say this is @Matches way of contributing to Discourse.
I understand that it feels like some control is taken away from you and that sucks. But really, people create worse sites about projects. Hell, just look at all the websites just listing the bad things from PHP and they aren't even contributing much in that regard.
So here is my proposal (pretty sure proposal is the wrong term here): Just try it out. Give it an honest shot, like we try (sometimes :D) giving Discourse an honest shot. And if you still don't like the whole thing at the end of the day, tell us why you don't like it and maybe @Matches will change his approach, too.Filed Under: Happy Internet Family and stuff
PS.
I'd still be happy to see you guys around for some WTF-stuff!Addendum: And then I re-read your reply @Sam and realize I might have interpreted it wrongly as "I don't want to look at TDWTF-forums anyway"... If that was the case, I apologize (once more) but I don't want to delete the wall of text I wrote and I believe there is still some truth in what I said!
-
@sam, please for the love of god change the new smiley emotes. They are terrifying.
-
+X {X ∈ ℝ | X > ∞ }
Filed Under: New Admin-Setting for Emotes? | Because > ∞ is clearly a real number!
-
What does Xerox have to do with anything?
-
Looks more like Xerix to me
Filed Under: There are some google-entries for xerix but none made enough sense to append *sigh*
-
Yeah, we've mentioned how WTF using a forum as a bug tracker is. Let's not get into that again.
Considering they don't seem to know what the word "heatmap" means (and I had severe doubts that Jeff understood "copy" until I saw him use it correctly himself), maybe they just also don't know what a "bug tracker" is.
-
Filed under: I have zero experience with open source, but here is how you should run your open source project, your'e welcome
I can't speak for abarker, but my personal experience is all open source projects, with very few exceptions, produce really, really shitty end-products. So I'd say the correct way to do open source is to not do open source in the first place.
Definitely don't charge people cash money for your broken open source crap, then also don't pay people who volunteer fixes. That's just shitty on a moral level.
-
I see @LikeBot is still working. That's wonderful.
-
Filling in for SignatureGuy, I agree with whatever @Matches posted just above.
-
I love that we have bots filling in for bots. Who fills in for @likebot if he needs a vacation?
-
-
As long as all the bases are covered. Where is my reply @LikeBot??
-
Filling in for SignatureGuy, I agree with whatever @Intercourse posted just above.
-
That's better. Gracias amigo.
-
Left @sam and @eviltrout a present at
https://bitbucket.org/masamunewos/discoursebugs/issues?status=new&status=open
-
You have been a busy little beaver.
Even if they do not appreciate it, we here on the forum do. Thank you.
-
We still like talking about the bugs.
yea, everyone seems to have a bug up their asses right now!
-
i think @pjh can just delete the new smilies from the plugins/emoji directory and they go away?
-
And we have a winner for the first bug.
<a href="DiscourseBugs.com">DiscourseBugs.com</a>
That link would go to http://what.thedailywtf.com//t/the-new-official-unofficial-discourse-bug-tracker/DiscourseBugs.com, which isn't a thing.
-
Yeah whatever. I didn't file it.
-
i think @pjh can just delete the new smilies from the plugins/emoji directory and they go away?
The only access I have to this installation is through the web interface. I neither have, nor - as I've said to Alex in the past - particularly desire, shell access to the server.
I get enough of that sort of thing at work TYVM...
-
This is our bug tracker
Two things about that:- No categorization possibility whatsover. You can't sort that list by severity.
- You don't see how many bugs there are in total. Let alone how many "severe" ones.
This has been said repeatedly: a forum is not a bug tracker. The time and energy you spend on the administrative overhead of using a forum as a bug tracker would be better spent on fixing bugs.
Or on making Discourse a bug tracker. You've got the basic infrastructure, expanding it into a bug tracker shouldn't be too difficult.
Edit: minor grammar edits.
-
OK, can you show me another open source project similar to Discourse in scale (5 man team) that fixed 4 bugs in the last 24 hours using their bug tracker
What for? That is not a metric for quality or achievement. 4 bugs in 5 man days? Nothing to be proud of. I remember the "email leaking bug" was fixed in less than one hour.Like " No JSON request when clicking latest" actually:
" I'm gonna dive in and change some stuff" - 5:36 p.m.
"Fixe submitted" - 6:59 p.m.And this has nothing to do with Open Source. You are all more or less on what may be called the "payroll" of CDCK, Inc. Either as founders or as intern.
-
Tools do not dictate process.
But they do.Using Discourse as a bug tracker dictates the process because you have to manually filter the bug category by severity and keep that list somewhere else, because you can't do it in Discourse.
Using, say, Bugzilla as a bug tracker also dictates the process in that you have to look at the bugs assigned to you first thing in the morning and then to decide what bug you fix first.
Different tools require different processes. You usually choose the tool that requires the least additional overhead in day-to-day operation.
The administrative overhead of using a forum software as a bug tracker is, on a day-to-day basis, larger than that using a dedicated bug tracker.
-
@Intercourse said:
You have been a busy little beaver.
Even if they do not appreciate it, we here on the forum do. Thank you.
+W
-
Just wanted to post the "[X] Button on Edit Window not visible" bug in the new bug tracker, but it is no longer necessary - they've shrunk the white popup with the edit history.
-
One of my earlier bugs doesn't seem to be in there. Is this an oversight?
-
So here is my proposal (pretty sure proposal is the wrong term here): Just try it out. Give it an honest shot, like we try (sometimes :D) giving Discourse an honest shot.
We find that most people get used to it within 60 days or so, even though they bitch about it a lot to start with…
-
Mobile so I don't know who this is at, if it's at me probably not. I only got through about 30 last night. We have like 250 reports. I should get there.