Name: wmcs-superset
Type of project: Component
Description: Superset instance to explore wiki replicas.
https://wikitech.wikimedia.org/wiki/Superset
Canonical code repository URL of the project (if this project has a code base):
https://github.com/toolforge/superset-deploy/
View policy of the project itself:
Public (default)
@rook: Sure. Please see https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects and use the template link under "Request a single project" to provide all required information.
Thanks. https://phabricator.wikimedia.org/project/profile/5683/ currently talks about "Wikimedia's Superset instance(s)." What should that be changed to, so users can find the right project tag?
@Aklapper https://wikitech.wikimedia.org/wiki/Superset has a disambiguation on it, if that helps. Simply put Data Engineering runs a restricted superset instance; superset.wikimedia.org, while WMCS has launched a public instance at superset.wmcloud.org. The existing tags and documentation only spoke about Data Engineering's restricted instance. With the addition of the public instance, we need to keep them separate and clear. I might update the existing project to say something like
Design, implementation and maintenance of the NDA restricted Wikimedia Superset instance(s), administrated by Data Engineering....
It's possible you may wish to force both tags to have prefixes or suffices on them. And updating the tags to have public and NDA/restricted prefixes/suffices might make more sense in the longterm rather than attaching to a specific team name or prefix.
So something like
superset-nda (convert existing tag to this)
superset-public
Thanks. I have updated Data Engineering's https://phabricator.wikimedia.org/project/profile/5683/ accordingly and decided to differentiate by URL name (as that does not require knowledge of some organization's internal teams).
Requested public project superset.wmcloud.org has been created: https://phabricator.wikimedia.org/project/profile/6584/
(In case you need to edit the project or project workboard itself at some point and lack permissions, please see Trusted-Contributors.)
Interested people are welcome to join the project as members, and to watch the project in order to receive notifications on task updates.
If tasks are created under this new project which are about a specific codebase, please make sure to also add these codebase project tags to the tasks in addition.
Recommended practices for project and workboard management in Phabricator are available.
Feel free to bring up any questions you might have about Phabricator or about best ways to manage projects in Phabricator.
Enjoy!