766906 - Improve discoverability of a project bugtracker and contacts

Status: RESOLVED FIXED

(Websites :: other.mozilla.org, defect)

Description

[Anthony Ricaud (:rik)]

When you have a problem with a website, it's not easy to find out how to report it.

- It's not easy to find the right product/component in Bugzilla
- Sometimes the bugtracker is not Bugzilla
- If it's urgent, which human being should I reach?
- etc.

Chris and I recently discussed how we could improve this. We think each website should have metadata to improve this situation

Clochix found the DOAP vocabulary that seems like a very good fit. http://en.wikipedia.org/wiki/Description_of_a_Project

Actions:
- Figure out how to embed this format in our websites. Embedded metadata in every page? Standalone XML file at a default location? Make it part of Playdoh and our Wordpress installations.
- Build some tools to use those metadata. Browser Extension for one-click bug filing? Wikimedia extension to replace our project pages?

Comment 1

[:glob ✱]

if you used a standalone xml at a default location, it could be expanded to include more than just websites (eg. pdf.js issues are tracked on github).

Comment 2

[Clochix]

Here's some samples of embedding bug-tracker's url in RDFa, RDFa Lite and microdatas https://gist.github.com/2949158

Comment 3

[Clochix]

Using a single XML file for the whole website may be cleaner, but harder to discover for the user. Some inspiration may be found in RFC 6415 ( http://tools.ietf.org/html/rfc6415 ) which define a standard way to provide host and resources metadatas.

Comment 4

[Anthony Ricaud (:rik)]

(In reply to Byron Jones ‹:glob› from comment #1)
> if you used a standalone xml at a default location, it could be expanded to
> include more than just websites (eg. pdf.js issues are tracked on github).
When I'm talking about a default location, I'm thinking something like http://website.tld/.well-known/metadata. Something really easy for websites.

What would be a default location for pdf.js?

Comment 5

[:glob ✱]

(In reply to Anthony Ricaud (:rik) from comment #4)
> When I'm talking about a default location, I'm thinking something like
> http://website.tld/.well-known/metadata. Something really easy for websites.

oh, i was thinking there would be a central site somewhere which housed all the doap files for our projects.  nevermind; websites only > nothing :)

Comment 6

[Anthony Ricaud (:rik)]

Such a project should replace a page like this:
https://wiki.mozilla.org/Webdev:WhoWorksOnWhat

Comment 7

[Chris More [:cmore]]

This list below was started a long time ago too, but it is difficult to get everyone to keep a central wiki page updated. I like the idea of manifesto-like file on the website provides some of the key info about the website. If it was a standard for Mozilla websites, it would also be scriptable and reportable across all sites.

https://wiki.mozilla.org/Websites/Active_List

Comment 8

[Anthony Ricaud (:rik)]

Peter: I think you worked on contribute.json, do you have a bug we can dupe this to?

Comment 9

[Peter Bengtsson [:peterbe]]

(In reply to Anthony Ricaud (:rik) from comment #8)
> Peter: I think you worked on contribute.json, do you have a bug we can dupe
> this to?

Dupe? Not really. Because contribute.json started as a general discussion and quickly grew into a github project which was just a README and later became the validator. It'll soon be available at https://www.contributejson.org but for now it's on https://contribute.paas.allizom.org

There's also http://mozilla.github.io/webdev/ which is 1.5 times all of this. It's a curated list of Mozilla Webdev project all on one page and the /contribute.json initiative is strong within this because projects that have one get a nice clear big green button.