FamilySearch Wiki:Wiki Support/Administration
From FamilySearch Wiki
(Difference between revisions)
|Line 87:||Line 87:|
== Wiki Maintenance ==
== Wiki Maintenance ==
*See [http://meta.wikimedia.org/wiki/Help:Recent changes Help:Recent changes] to begin understanding how you can monitor recent changes to help with maintenance issues.
== Wiki Content ==
== Wiki Content ==
Revision as of 23:19, 28 December 2010
Transparency in Development
- FamilySearch Wiki:Known Issues - be familiar with the issues listed on this page. Archive the items when needed. Support the issues by moving them through the process in JIRA and product engineering. Based upon the issue additional help content may be needed. When this happens, work with tier 2 to have existing Help articles updated or to get additional Help articles written. This includes assisting with bug reporting, testing fixes, giving feedback to engineers, etc.
- Taxonomy Implementation: The integration of the wiki in betaFamilySearch is another item that needs to be communicated to the wiki community members. The community meeting attendees benefit from know what the current status is for the integration. One item that is still being worked on is the implementation of the FamilySearch topic taxonomy into the wiki. David Dilts is heading up the project to implement this taxonomy, and has given reports in the past to this group.
- Status reports from David Dilts and Dallan Quass
- Identify technical issues, roadblocks, and questions as they rise
- Plan and implement resolutions
- DevNet: DevNet is the wiki development backlog that the community had access to for reporting bugs and requesting enhancements. They could use this site to communicate with the engineers and help troubleshoot bugs and add the documentation. This site has not been used by engineering for a long time, so when items are added by the community, they basically go into a black hole. The community was told that something better would come, but in the mean time use DevNet. The wiki still does not have something better to replace DevNet.
- Finalize issue related to the use of DevNet for the public facing backlog
- What is the status of betaFamilySearch’s usage of GetSatisfaction feedback, especially for the wiki?
- FamilySearch Wiki:Project backlog - this page was originally created by the product manager for purposes of communicating with the wiki community all the development we had on the backlog for the wiki project. Some of the backlog were tasks that could only be done by an engineer. Others were items that any community member could help with. All community members who attended the technical Community Meeting were encouraged to help with the development by signing up for one of these projects. The list was hard to maintain and keep current by product management. There is still a need to be transparent with the development of the wiki, particularly with development projects that can be done by community members.
- New Features - this page was originally maintained by our Admin on Penny's team. Right now the wiki does not have an Admin on Penny's team. Consequently, this page is not being updated.
- Forums: Respond to Forum posts, particularly those in the Technical Support forum. You will find bugs reported here and also technical questions by the community members.
Wikipedia and MediaWiki Documentation
Some Wikipedia and MediaWiki pages that have helped with self-training understanding wikicode include:
- Wiki text markup articles: Wikipedia: How to edit a page and specifically the Wiki Markup section of the article.
- Help Template
- Template Messages
- ToDo template and list
- Community portal
- Management and development
- Build an easy way for users to know which templates are available for use in writing and editing content.
- The FamilySearch Wiki:Maintenance Templates page was a beginning step to make templates more visible to the community. The page only lists some of the maintenance templates. The templates were created with the old wiki when we had more horizontal room for content. (We have discovered that the problem with horizontal room is browser related it does not happen when using Internet Explorer 7 and above.) Now the templates are too big on a page. Some redesign is needed. You could work with User:Cottrells because he has helped create a lot of our templates.
- Templates need to be easy to use. We receive many comments about not wanting to know the techie stuff, but still wanting to use the features and functions of a template.
- The community meeting held on November 23rd was about templates. Steve Cottrell presented some "training" on the usage of templates and where to find a list of all the templates that are currently available in the wiki. Please see the meeting agenda page for links to the pages he used in the training. If you did not attend the meeting, I'd suggest that you listen to the recording.
- What are extensions?
- Where are they documented?
- Access the list of extension through Special pages
- The report that lists the current extensions is "Version"
- See the Help:Magic words page in the wiki for details about using Magic Words.
Policies and Guidelines
- Governance in the wiki was developed as 80% preventative and 20% repair and based upon the policies and guidelines. We see Tier 2 supporting all the preventative measures and Tier 3 supporting the repair measures. The "Delete" templates are an example of a repair measure for content.
- Delete requests
- Delete ASAP requests
- Delete Portal requests
- FamilySearch Wiki:Policies/Proposed enhancements
- The Delete Log - find the delete log; use the log to watch for vandalism; take action when possible vandalism is detected.
- Also we can understand what the community is trying to accomplish by watching what pages they are requesting for deletion and why they are requesting the deletes. Is their method the right way to accomplish their goals? Can we provide alternative ways to accomplish the work they are doing?
- See changes Help:Recent changes to begin understanding how you can monitor recent changes to help with maintenance issues.
Share Your Opinion!
Give feedback on our new look! Tell us what you like, and what you would do differently.Give Feedback