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

Remove contribute.json #13878

Closed
1 task
Tracked by #14229
stevejalim opened this issue Nov 9, 2023 · 4 comments · Fixed by #14423
Closed
1 task
Tracked by #14229

Remove contribute.json #13878

stevejalim opened this issue Nov 9, 2023 · 4 comments · Fixed by #14423
Assignees

Comments

@stevejalim
Copy link
Collaborator

Description

Just noticed that https://www.mozilla.org/contribute.json could do with a bit of updating:

{
    "name": "Bedrock",
    "description": "The app powering www.mozilla.org.",
    "repository": {
        "url": "https://github.com/mozilla/bedrock",
        "license": "MPL2",
        "tests": "https://ci.vpn1.moz.works/blue/organizations/jenkins/bedrock_multibranch_pipeline/activity/?branch=master" <-- STALE
    },
    "participate": {
        "home": "https://wiki.mozilla.org/Webdev/GetInvolved/mozilla.org", <-- a little stale
        "docs": "http://bedrock.readthedocs.org/",
        "mailing-list": "https://www.mozilla.org/about/forums/#dev-mozilla-org", <-- STALE?
        "irc": "irc://irc.mozilla.org/#www", <-- STALE
        "irc-contacts": [  <-- STALE
            "agibson",
            "craigcook",
            "jpetto",
            "pmac",
            "kohei",
            "jgmize"
        ]
    },
    "bugs": {   <-- STALE? / should be GH now?
        "list": "https://bugzilla.mozilla.org/describecomponents.cgi?product=www.mozilla.org", 
        "report": "https://bugzilla.mozilla.org/enter_bug.cgi?product=www.mozilla.org", 
        "mentored": "https://bugzilla.mozilla.org/buglist.cgi?f1=bug_mentor&o1=isnotempty&query_format=advanced&bug_status=NEW&product=www.mozilla.org&list_id=10866041"
    },
    "urls": {
        "prod": "https://www.mozilla.org",
        "stage": "https://www.allizom.org",
        "dev": "https://www-dev.allizom.org",
        "demo1": "https://www-demo1.allizom.org",
        "demo2": "https://www-demo2.allizom.org",
        "demo3": "https://www-demo3.allizom.org",
        "demo4": "https://www-demo4.allizom.org",
        "demo5": "https://www-demo5.allizom.org"   <-- We should add demos6-9 as well, if we're showing them at all
    },
    "keywords": [
        "django",
        "html",
        "jinja2",
        "protocol",
        "python",
        "sass-css"
    ]
}


Success Criteria

  • Contribute.json contains no stale info
@alexgibson
Copy link
Member

@stevejalim We might actually want to consider removing this, since (afaik?) the system that used this is no longer really maintained https://github.com/mozilla/contribute.json

@stevejalim
Copy link
Collaborator Author

stevejalim commented Nov 9, 2023

I was thinking that but while putting futuremo through observatory.mozilla.org I discovered that a site on mozilla.org without a contribute.json is marked down. That doesn't mean we have to keep it of course, but we should zap or update, for sure

@alexgibson
Copy link
Member

That's a bit of an odd thing to be marked down for in a security audit if you ask me :/

@janbrasna
Copy link
Contributor

janbrasna commented Mar 28, 2024

This month www.contributejson.org was taken down and the repo archived, and the scoring was also removed from Observatory:

So while it'd be "nice" to have all the updated content like Matrix instead of IRC, current CI info, all the envs etc., it's probably just time to remove it:/ I guess there is a placeholder for removal in #14229 epic anyways.

(Hint: there's a symlink from root_files to root, for anyone getting rid of it.)

@alexgibson alexgibson changed the title Update our contribute.json Remove contribute.json Apr 4, 2024
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

Successfully merging a pull request may close this issue.

3 participants