The PDF rendering project is named everywhere Proton, but the gerrit project is chromium-render. To be consistent (and make everyone's life easier) we should rename the project to proton.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | ovasileva | T181079 [GOAL] Provide an expanded reading experience by improving the ways that users can download articles of interest for later consumption | |||
| Resolved | None | T181084 [EPIC] Deploy the mediawiki-services-chromium-render service (Proton) | |||
| Resolved | phuedx | T210652 Handoff Proton service to Reading Infrastructure | |||
| Declined | pmiazga | T211375 Rename chromium-render gerrit project to Proton |
Event Timeline
Comment Actions
Gerrit renames are quite painful in my experience. We'd also lose git history right? Is this worth it @pmiazga it's not clear to me from the description that this trade off has been considered. Can you also update the description with the expected steps that will be required to do this?
For instance Popups extension never got renamed (although I imagine renaming extensions is more complicated than services).
Comment Actions
You won't loose git history if you create the new repo and then git mirror the old repo to the new repo :).
Comment Actions
I would advise against this. Apart from gerrit pains with renames, this would also involve changing all of our puppet code surrounding proton. I really think we should keep it as-is, especially now that the service is already in production.
Comment Actions
Should the task just be declined based on @mobrovac comment? Not sure whether it is worth all the overhead.