Please create Bug Reporting Best Practices blog post at the QTE blog.
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
In Progress | zeljkofilipin | T325276 Shallow work | |||
Open | None | T263660 Blog post writing club | |||
Resolved | • jbolorinos-ctr | T258076 Bug Reporting Best Practices office hours | |||
Declined | None | T258075 Bug Reporting Best Practices blog post |
Event Timeline
This might be already covered by https://www.mediawiki.org/wiki/How_to_report_a_bug , if I don't misunderstand?
Hey Andre, this is just a blog post that will be posted to the QTE blog, and like I said, originally I set this up because of my experience filing over 400 bugs at Apple, so I just wanted to share the lessons I learned there.
This certainly isn't meant to replace the already posted wikimedia guidelines, so my apologies if that's what it came off as. I actually think that page is already very helpful and I doubt my blog post will have anything to add that hasnt been covered already in the "How to report a bug" instructions. Of course if there's anything I could contribute I would be happy to, so just let me know if that's the case.
First draft can be viewed here: https://docs.google.com/document/d/1JrdxBmyIWOyj6VU6RmHA3wjMY1ZVWOv3NfXNkTqrhHo/edit#heading=h.khhxlhs176ed
Thanks, I've added some quick comments.
I think it would also be good if that document would not contradict with https://www.mediawiki.org/wiki/How_to_report_a_bug
I'm reading @jbolorinos-ctr's draft blog post and @Aklapper's comments and I have a few comments.
- @Aklapper is mostly thinking about anybody (developer, tester, volunteer) reporting a bug. @jbolorinos-ctr is mostly thinking about people paid to report bugs (like members of Quality-and-Test-Engineering-Team team). Please correct me if I'm wrong.
- It would probably be the best to link to How to report a bug at the very beginning of the post.
- The post should start with a disclaimer that it's a personal view on the topic and not an official document, to avoid any confusion.
- The title should probably be changed from Bug Reporting Best Practices to something like Bug Reporting Tips, to avoid any confusion.
Maybe we weren't clear on why @jbolorinos-ctr is writing this article. We are trying to create some content for Quality-and-Test-Engineering-Team blog. We are not trying to contradict the existing documentation. Blog posts are personal views on the topic. They should be clearly marked as such, to avoid any confusion.
@jbolorinos-ctr do you still want to do this? Do you want to pair on writing the first article?
Hey @zeljkofilipin, yes next week is my final push for fundraising banners, so after that I will definitely get this published. I would appreciate another pairing session yes, if early Jan sometime would work for you? Should I just go ahead and find a time on your calendar?