FamilySearch Wiki:Technical Meeting Agenda 24 August 2010

From FamilySearch Wiki
Jump to navigation Jump to search

Join the meeting, the ID is 5934

Green check.png
The usage of "Mormon" and "LDS" on this page is approved according to current policy.

Purpose of the meeting

  • To forge solutions with other community contributors.
  • To discuss content, technical issues, workarounds, community, site design, and strategy.

Agenda[edit | edit source]

Recognition[edit | edit source]

Add your recognition items below

  • Kudos goes to everyone who attended the FGS conference and introduced the society pages and adopt-a-wiki page initiatives to all in attendance at the conference. We hear that the conference was a great success! -Fran

Announcements[edit | edit source]

News items can now be found on the Research Wiki News page in the Wiki.

  • Questions?
  • Comments?

Discussion Items[edit | edit source]

From the Community[edit | edit source]

Community members who attended the FGS conference will share some of the experiences they had with their efforts to spread the word about the wiki:

  • Nathan
The Tennessee project was an official press release and heavily advertised at the FGS conference. Dick Eastman, the Genealogy Blog, Ancestry Insider, and the Deseret News and the FGS Conference Blog carried the press release. Over the past 45 days there has been an increase in traffic on the Tennessee page by 5,000 hits.
  • Michael
  • Nate
  • Others?

Layout of main locality pages - side-bars, navigation boxes, #ifexist function (related forum thread) --Steve 06:50, 23 August 2010 (UTC)

  • Introduction to the discussion (Steve)
  • What are we trying to accomplish?
  1. Ultimately, we would like to identify a documented Manual of Style guide for a consistent look and feel related to the navigational boxes that are created for places, topics, etc. Today there are several different types of navigational boxes, and we'd like to get to the point that we can have a consistent look and feel for navigation throughout the wiki content. -Fran
  • The "Topic" template. Purpose, usage, etc.
  1. {{Place|name of place}} - this one auto-generates the list of topics for a given place.
  2. {{Virginia}} - this was created to hold all the links to topics related to the state, the counties and other jurisdictions, etc. The vision is that major repositories and pioneer pathways will be added to the template.
  3. Note that
  • The "County" listing template. Purpose, usage, etc.
  • Issues related to combining the details from both templates into a single template.
  1. "Too many expensive parser calls" - what is this error? why does it happen? how can it be prevented? I have never seen an error message related to "too many parser calls" and would like to spend a few minutes in the meeting reproducing the error. Someone needs to document the steps to take in order to reproduce the error message. This will help us understand the issue. -Fran
  1. There is a limit of 500 functions the expensive parser function count, i.e., the number of calls of expensive parser functions. The parser is code that produces the actual visual page. --Don
  1. Other technical issues?
  • Perspectives from different areas of expertise.
  • So far this discussion has been related to the template's usage on US pages. What about the rest of the world?
  • The topic narrow column on all state and country pages.

From FamilySearch Staff[edit | edit source]

  • Nothing more than the nav box discussion posted to the agenda by Steve. We would like to spend the entire hour discussing the issues and possible solutions. Therefore, I propose that no other agenda items be added. Rather than having an open-ended discussion, we need to have this discussion based upon specific items. Therefore, I will be adding discussion points as I see issues are identified in the forum thread. -Fran 18:23, 23 August 2010 (UTC)

Be bold! Post your agenda items!

Feel free to post on the agenda any items you wish to cover during the meeting. If your item requires details or feedback, post some details on the discussion page and link to the discussion from the agenda.