[BLOG IDEA] Write about IATI Data Bugtracker

[andylolz]

What’s the blog about?

I think IATI Data Bugtracker is quite a cool MVP for publicly tracking issues with IATI data and metadata. It also has a couple of bots set up to help manage issues, which it would be good to write about and explain.

It would also be cool if more people knew about the service and used it, and it would be good to make existing bugs more visible to increase the likelihood of them being fixed. So it would be good to write about it.

What’s the goal of the blog?

Get more people using the service.

[andylolz]

It might be good to do codeforIATI/dashboard#28 before publishing this.

[andylolz]

Okay, codeforIATI/dashboard#28 is done now, so this is unblocked!

[andylolz]

How it works:

• Anyone can create an issue. We have templates in place for different types of issue
• The template includes a link to an email template in order to contact the publisher and let them know about the problem
• ~Newly created issues go into a triage queue, for an admin to confirm they are valid~
• Issues are labelled with the publisher name (this list of labels is auto-updated daily)
• After 30 days of inactivity, @CodeforIATIbot will check in, to ask if the issue is still valid.
• If someone replies to say the issue is still valid, it’s automatically moved to "long-standing issues"
• There’s a project board, for an overview of the status of all open issues
• Issues will appears on the C4I dashboard, e.g. on the ec-intpa publisher page. ~Issues awaiting triage and~ resolved issues are not shown

[andylolz]

I think it makes sense to publish this before the Analytics blog (and then refer back to it).

[andylolz]

WIP here: https://docs.google.com/document/d/1Vg5es-de3u5Ury0WdX0aFLw3_451qkjF-NefjGuwyPU/edit