#102 Redirect "Board public IRC meetings" wiki page to "Council ticket queue" docs page?
Closed: complete by jflory7. Opened by jflory7.

Summary

Redirect the Board public IRC meetings wiki page to the Council ticket queue docs page

Background

I searched DuckDuckGo for "fedora irc meeting protocol" and this was one of the top hits. Not only is it slightly misleading, it is also out of date. By a long time. Our Search Engine Optimization could benefit by creating a 301 redirect to the docs page and hopefully bury the wiki page from search engines.

As someone who is sensitive to preservation of historical data, this does not concern me because the wiki edit history is still preserved if we ever did want to go back and look at it.

Details

There is an (undocumented) way of redirecting wiki pages to Fedora Docs pages. We could use the macro and be done with it.

Outcome

People find up-to-date information about how decisions and processes work in Fedora's executive leadership body


+1 let's keep information fresh and accurate

There is also this: https://fedoraproject.org/wiki/Council_Meetings

The magic redirect, by the way, by design ONLY can target docs.fedoraproject.org, because the way it works is horrific and could be abused by spammers.

We have https://docs.fedoraproject.org/en-US/council/#_meetings, by the way, which redirects to that Council Meetings wiki page.

I think we should rewrite the Council Meetings wiki page to be up to date, stick it in Council Polices, update the Charter link to point to that redirect the wiki pages to it.

Maybe with some content combined in from the Board Meetings page.

@mattdm Think you could take this one on? I could pick up #103 then.

Yep #action mattdm.

Right after I do my mandatory end-of-2020 compliance trainings. :)

Metadata Update from @jflory7:
- Issue assigned to mattdm
- Issue priority set to: waiting on assignee
- Issue tagged with: type - dev tools

It appears this was completed, as the wiki page now redirects to the Fedora Council meetings page. I am closing this issue as complete.

Metadata Update from @jflory7:
- Issue close_status updated to: complete
- Issue status updated to: Closed (was: Open)

Metadata