Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adoption by non-Mozilla projects? #71

Open
schumaml opened this issue Sep 30, 2016 · 5 comments
Open

Adoption by non-Mozilla projects? #71

schumaml opened this issue Sep 30, 2016 · 5 comments

Comments

@schumaml
Copy link

@schumaml schumaml commented Sep 30, 2016

Hi,

came across contribute.json when I was testing https://www.gimp.org with the Mozilla Observatory (i.e. via https://wiki.mozilla.org/Security/Guidelines/Web_Security#contribute.json ).

Do you expect adoption of this standard by non-Mozilla projects?

And if a project did (or a critical mass of them), how would the data they provide be accessible to users - do you plan to offer a directory for arbitrary projects where users can search/browse/find projects?

@pmac
Copy link
Member

@pmac pmac commented Oct 1, 2016

Expect is strong, but I think we hope for adoption across the broader FLOSS world. A directory is something we've toyed with, and we do have a thing that uses contribute.json files for Mozilla webdev projects. There's also a Firefox addon that will notify you if a site has info at /contribute.json. We'd love to hear how it might be useful to others though.

@april
Copy link

@april april commented Oct 5, 2016

@schumaml: Note that the Observatory doesn't penalize (non-Mozilla) sites for not having contribute.json. It is great if you do, though, and we hope to use it for all sorts of things in the future!

@schumaml
Copy link
Author

@schumaml schumaml commented Oct 5, 2016

Yeah, I'm aware of the non-penalizing aspect.

Got intrigued by the concept because figuring out a way to present all this information on a website always leads to the n+1th differently designed "How to participate!" page (or worse, page_s_). Collecting it in one file ensures maintenance at a single place.

Approaching larger umbrella organizations might be a good way to spread the idea, especially if they are currently implementing similar ideas. For example, Freedesktop has Appstream: https://www.freedesktop.org/software/appstream/docs/ - less focus on getting participation info across, more focus on having things that you can find in software package management.

One issue I see there is that larger umbrellas might have a site structure of https://umbrellaorg/projectfoo|projectbar|projectbaz; handling this by one /contribute.json won't work.

@pmac
Copy link
Member

@pmac pmac commented Oct 6, 2016

One issue I see there is that larger umbrellas might have a site structure of https://umbrellaorg/projectfoo|projectbar|projectbaz; handling this by one /contribute.json won't work.

that is a good point. perhaps a primary contribute.json file at /contribute.json or /.well-known/contribute.json should be able to list URLs to sub-project contribute.json files?

@april
Copy link

@april april commented Oct 6, 2016

I think that's a great idea. Maybe a projects object, like:

{
  "projects": {
    "Firefox": "https://getfirefox.com/contribute.json",
    "Thunderbird": "https://www.mozilla.org/en-US/thunderbird/contribute.json"
  }
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants