Closed Bug 1445071 Opened 6 years ago Closed 4 years ago

Delete SeaMonkey localization wiki page

Categories

(Websites :: wiki.mozilla.org, enhancement)

Production
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rpmdisguise-nave, Assigned: spike)

References

()

Details

There is a page in the SeaMonkey and L10n categories:

https://wiki.mozilla.org/SeaMonkey:Localization_Teams

that intended to list the L10n volunteers working in SeaMonkey L10n. However, keeping pages like this one updated is difficult, even more when there are general L10n team pages that include the same information.

So, we have replaced all references to that page to the main L10n teams page:

https://wiki.mozilla.org/Category:L10n_Teams

or to the main SeaMonkey L10n page:

https://wiki.mozilla.org/SeaMonkey:Localization

depending on the source.

We're now ready to request the deletion of the SM L10n teams page:

https://wiki.mozilla.org/SeaMonkey:Localization_Teams

Adding Ian Neal and Frank Wein, from SeaMonkey Council, to validate the request.
Any pressing reason to actually delete this article? I see a lot of history going back pretty much to the 'Dawn of the Wiki' (c). Would it be acceptable instead to flag it as being outdated (https://wiki.mozilla.org/Category:Outdated_articles) and a link  to the current article?
Flags: needinfo?(rpmdisguise-nave)
It was actually a sense of keeping things tidy. :-) The issue with keeping the page alive is having to watch that nobody modifies it. The link to the current article, as you see, is already in place.

All in all, I think we're willing to follow the established procedure for these cases. If removing pages is not part of Mozilla Wiki policies, we can instead flag it as outdated and link to the L10n:Teams page. Can a page be blocked for modifications?
Flags: needinfo?(rpmdisguise-nave)
Assignee: nobody → spike

https://wiki.mozilla.org/SeaMonkey:Localization_Teams has been marked with the "THIS PAGE MAY BE OUTDATED" warning banner as suggested above so this bug can now be closed.
Thank you to @RickieES for making the change.
Spike

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.