|
An overview of all initiatives, decisions, and progress on projects stemming from Meeting of the Minds in 2021.
Meetings[]
April[]
Topic | Presenter | Discussion | Plan | ||
---|---|---|---|---|---|
Next step | Lead(s) | Complete | |||
Announcements, updates, and awards | New staff members, anniversaries, Savior of the Damned, NotY 2020, Fandom awards, Vault Academy grads | Congratulate all awardees and welcome new staff | |||
Template creation and use | Need a designated group checking templates before they're implemented. Need more clear guidelines of what expectations are for documentation. Update template overview page and maintain it as templates are created, replaced, or retired. | Form quality assurance committee in project space | |||
Create subpages for work in progress, changelog, and template review/approval logs. | |||||
Plagiarism of game guides | Significant number of articles include direct copy paste and/or lack references concerning game guides. Need to paraphrase from and appropriately reference these source texts. | Start and setup project including article checklist table. | |||
Add unique parameter to cleanup tag for auto-adding articles to new project-specific category. | |||||
Identify and list plagiarized or poorly references articles in checklist. | |||||
Fallout 2 restoration project content | Discuss covering mod content, such as location images and/or character images with indication they are from restoration patch. Consensus is that the project content does not fall under our scope, as it is based on modders' interpretation of design documents and not developer statements or cut content, inability to independently verify. | Images renamed and labeled as restoration project, moved to blog or sandbox. | |||
Remove all remaining restoration mod content from mainspace. | |||||
Redirect category | Redirect category is unnecessary due to ListRedirects page. Consensus is that ListRedirects tool is sufficient for our needs and phasing out category is appropriate. | Run bot to remove redirect category from existing pages. | |||
Clarification of stub articles | Current policy outlines that a topic must have sufficient content to justify independent article. Stub articles are for topics that do have this content, but are yet to be written. Single mentions without sufficient content are not stubs. These mentions should be added to and referenced within a related, existing article. | Merge articles that do not have sufficient content into related, existing articles. | |||
Race infobox parameter | Discussed race in game file data and how it should be presented, as technical information as opposed to information used to determine a character's ethnicity. GECK base characters are prefabs and CK removes it entirely, replacing with skin tone. In cases that a character mentions details or it is outlined elsewhere, appropriate to add to background section. | Create specific parameter for GECK skin tone, move from bio to tech tab. | |||
Gender as parameter for robots/computers | Discussed assigning gender to computer and robot characters, currently using "male/female programming." Should not assign a gender to a robot based on presuming that of a voice actor. Exceptions are appropriate, favor only using gender parameter for those that explicitly refer to themselves as a specific gender, with verifiable reference to support. | Add voice type parameter to applicable templates. | |||
Remove gender/sex/programming from infoboxes of robots/computers | |||||
Reassess featured articles project | Current articles rotating as featured on main page are in need of an update. Purpose of featured articles rotating on main is to showcase our best content, and the current selections are in need of an update. Project would focus on reviewing existing features for quality, adding featured articles from FO4 and FO76, and shifting from calendar rotation to random selection. Users can nominate articles, project team assess if it's referenced correctly, eliminate speculation, ensure formatting is correct. Strong consensus and interest in project. Potentially use weighted inclusion for times of year i.e. Halloween articles during October. | Create project page, standards and action plan to be determined. | |||
Infobox alignment and capitalization | Discussed right alignment and capitalization of infoboxes across the site as well as the merits of options including remaining as-is and changing to other formatting. | Update template as described above. |
June[]
Topic | Presenter | Discussion | Plan | ||
---|---|---|---|---|---|
Next step | Lead(s) | Complete | |||
Announcements, updates, and awards | New staff members and Vault Academy grads | Congratulate all graduates and welcome new staff | |||
Infobox item template specificity | Item infobox too unwieldy, difficult to document, utilize, and teach. Call to split based on specific item, align with Fandom best practices. | Discussion will move to forum vote, posted and accessible here. | |||
Consistent headers for reference types | Both bold and colon are used, accessibility indicates colon should not be used. Wiki should be uniform in either direction. | Moving forward bold headers will be used instead of colon. Will add this clarification to reference guidelines. | |||
Appearance of FandomDesktop | New skins need work when considering design and colors for both light and dark modes. | Current design is temporary for rollout. Eckserah has sandbox page for reporting issues, see here. Will touch base with FDekker to get prototypes going for current oasis skin and dark mode version. |
July[]
Topic | Presenter | Discussion | Plan | ||
---|---|---|---|---|---|
Next step | Lead(s) | Complete | |||
Edit summary clarity | Frustration among users about their edits being reverted without good reason. | Discussion has been moved to a forum and pending results may proceed to a vote. | |||
Wikipedia link usage | Concerns of negative impacts resulting from wikipedia links in the background, to the detriment of our wiki specific content being linked or created. | Wikipedia links appropriate in behind the scenes only on gameplay/game articles and removed from other sections. Updated guidelines. | |||
BTS specifications and presentation | Concerns of what is and is not appropriate and how does speculation apply to cultural reference. Are there alternatives to current system or is it preferred? | ||||
Treatment of IRL information relating to articles | Concerns of what is and is not appropriate use of real world information as it applies to articles. Clarify intended scope of articles. |
August[]
Topic | Presenter | Discussion | Plan | ||
---|---|---|---|---|---|
Next step | Lead(s) | Complete | |||
Announcements | Any and all updates and news since the last meeting. | Announcements, updates, awards, upcoming events. | |||
Canonicity of Fallout Shelter | Not consistent with current canon qualifiers and policies. | Will move to forum discussion. | |||
SaintPain policy clarifications | Module for admin notifications, banning admin leave talk page open and message outlining appeal process | Policy update, process clarifications | |||
Module for admin notifications | |||||
Ban evasion addendum | Add addendum to user conduct forbidding editing on behalf of banned users | Policy update, SaintPain clock restarts for soliciting users to serve as proxy, regular warning/block duration for editing user. | |||
Review of admin policy | Concerning active bureaucrat clause line | Policy update, remove outdated bureaucrat elevate line | |||
General policy review | Overview of all policies | Topic to forum, see here | |||
Bureaucrat unilateral action/veto | Bureaucrat cannot give rights back to users who have resigned, resignation is permanent. For votes, purpose of crat sign off is only formality, not to change vote results. | Policy update on resignation component | |||
Forum, veto for vote results staff consensus |
September[]
Topic | Presenter | Discussion | Plan | ||
---|---|---|---|---|---|
Next step | Lead(s) | Complete | |||
Announcements | Any and all updates and news since the last meeting. | All, we were all Great McAdmin | |||
Games template | The usage of the games template in combination with infoboxes. | The games and addon images should turned off by wizards to unjanky the boxes. Css fix to omit. | |||
Update categories | Discuss the practice of adding new categories for each update, i.e. [Update name] weapons, locations etc. | ||||
IRL information | Incorporation of information for IRL locations & things which have only partial details provided. | All information to be placed in behind the scenes sections only, not background or elsewhere. | |||
Content warnings | Trigger/sensitivity warnings for articles containing specific content. | here). |
October[]
Topic | Presenter | Discussion | Plan | ||
---|---|---|---|---|---|
Next step | Lead(s) | Complete | |||
Announcements | Any and all updates and news since the last meeting. | Announcements, updates, awards, upcoming events. | |||
Real world people articles | Concerns of articles containing personal info without permission. | Policy and guidelines updated | |||
Remove personal information, focus on Fallout series involvement only. Wikipedia link ok, social media accounts not. Only information released by Bethesda, officially credited. Ongoing effort, potential project. | |||||
New plan ideas for exploits | Users currently find them difficult to organize and find. | Propose game-specific overview pages that include full list and transclude to specific object, location where exploit exists. Community interest, moving to forum. | |||
1RR replacing 3RR | Amend 3RR to 1RR in user conduct policy. | In effort to bring users to talk pages earlier and avoid conflict. Community interest, moving to forum. | |||
Moderation channels | Proposal to open up moderation channels on Discord. | To show more transparency with the community, keep them up to date, increase communication. Preliminary poll in #overseer-terminal was positive. Community interest, moving to forum. | |||
World object renames | World/workshop object renames to be consistent. | Policy and guidelines updated | |||
Need to name article by game and not add-on/update to be consistent across the board. Ongoing effort, potential project. |