1153329 - Rename project to match browsercompat.org

Status: RESOLVED WONTFIX

(developer.mozilla.org Graveyard :: BrowserCompat, defect)

Description

[John Whitlock [:jwhitlock]]

What problems would this solve?
===============================
The project started as "webplatformcompat", but the production domain will be browsercompat.org.  The code and related websites have many references to the old name, which makes it difficult for contributors to discover the project

Who would use this?
===================
Code contributors

What would users see?
=====================
The will search for "browsercompat" on github and other sites, and find the project and related code.  They won't see an awkward discussion in the docs about the name of the project.

What would users do? What would happen as a result?
===================================================
Code contributors will submit code with confidence

Is there anything else we should know?
======================================
:hoosteeno has bought both browsercompat.org and browsercompat.com, as noted in bug 1059577.  He recently blogged with the name as browsercompat.org, so that's probably the one we'll go with: http://hoosteeno.com/2015/03/31/experiments-services/

A good first step is to move the main project from:

https://github.com/jwhitlock/web-platform-compat

to:

https://github.com/mozilla/browsercompat

Comment 1

[John Whitlock [:jwhitlock]]

Due to too many projects in the Mozilla organization, a better place is https://github.com/mdn/browsercompat

Comment 2

[John Whitlock [:jwhitlock]]

I've performed the first step, by moving the repo from https://github.com/jwhitlock/web-platform-compat to https://github.com/mdn/browsercompat.  To avoid annoying messages, you'll want to switch the remote URL in your local checkout, which is something like:

git remote set-url origin [e-mail]:mdn/browsercompat.git

Comment 3

[MDN Team (:mdn-dev)]

Commits pushed to master at https://github.com/mdn/browsercompat

https://github.com/mdn/browsercompat/commit/38326ffa8cbb24b9e45a61f1507914438ccb9758
bug 1153329 - Update browsercompat strings

Update docs, select docstrings, and web pages

https://github.com/mdn/browsercompat/commit/c24eefa39f6c58d1dfc40130407d1633a522973f
bug 1153329 - Add requirements for ReadTheDocs

ReadTheDocs is having difficulty building the project with the Heroku
requirements.txt.  This version has the requirements needed to build the
docs, which is currently none.  It requires setting this requirements
file in the admin.

Comment 4

[Renoir Boulanger [:renoirb]]

Is this solved? What is the definition of done here?

Comment 5

[John Whitlock [:jwhitlock]]

The code has several references to web-platform-compat, requiring string replacing and changing file names.  That should close the bug.

Comment 6

[John Whitlock [:jwhitlock]]

We're planning on shipping a contribution interface (CI) that makes it easy to view and modify API data.  These have different requirements and are currently being tracked a separate projects.  If they deploy as separate websites, it makes sense for the user-facing contribution interface to be at https://browsercompat.org, and the API to be at a sub-domain like https://api.browsercompat.org.  This may mean the github repo gets renamed again.  We'll know more when we start shipping CI to alpha users (after bug 1159406)

Comment 7

[MDN Team (:mdn-dev)]

Commit pushed to master at https://github.com/mdn/browsercompat

https://github.com/mdn/browsercompat/commit/11b441d0f37273e2e81091950458051879d9165b
bug 1153329 - browsersupports -> browsercompat

Fix an old, abandoned name for the service

Comment 8

[John Whitlock [:jwhitlock]]

The BrowserCompat project is canceled.  See https://github.com/mdn/browsercompat for current effort. Bulk status change includes the random word TEMPOTHRONE.