Community Meeting Agenda 9 February 2010

To Attend the Meeting:
 * 1) Click here to join meeting ID number is 9218 and click the "Attend Meeting" button.
 * 2) Select the desired "Connect Me" options and enter the phone number that you want MeetingPlace to call you at
 * 3) Click the Connect button

To Attend the Meeting Without Using your Computer:
 * 1) Dial into 801-240-2663 (Local/International) or 877-453-7266 (US Toll-free)
 * 2) Follow the prompts to enter the Meeting ID 9218 and join the meeting

= Agenda and Notes =

Feedback Requested: Current engineering priorities and future backlog prioritization process
Summary: Ben Bennett is the product manager for the Wiki and requested this item be added to the agenda. Ben will be joining our meeting and will lead this discussion. For some time now, our wiki user community has been posting bugs, suggestions and feedback to the FamilySearch wiki Forums. FamilySearch Product Managers (who ultimately prioritize engineering work on the wiki), pull data from the forums as well as other sources (e.g. requirements from other FamilySearch.org products and affiliates who want to integrate with the wiki) to create a prioritized list of engineering/development priorities. Engineering work happens in cycles that are approximately 5 weeks during which fixes and features are rolled out as they are completed. Going forward, it's our desire to create a) more transparency in terms of what the current and planned engineering priorities are, b) solicit community input on prioritization of future fixes/features and c) solicit assistance from community members with PHP, Wikicode and other programming experience who desire to assist in completing some of the engineering priorities (thus delivering more fixes/features to the community faster).

Detail: While the long term solution will be to build a series of bots and maintenance pages within the wiki to manage engineering priorities, for now, it's proposed that we use the FamilySearch Developers Network to share and manage the backlog. Here, users can see current issues that have been logged, current priority/status, and users can vote to increase the priority of an existing issue. Users can also add a new issue to the list.

While we will continue to direct the community at large to the FamilySearch Wiki forums to log their issues, for those who are interested in seeing additional detail and assisting in prioritizing and developing future fixes/features, the FS Developers Network is the proposed solution.

By creating an account (sorry, you can't just use your wiki account to log in here - at least not yet), you can see priorities for this current sprint. In addition, I'm working to update the list with all past issues which have been raised/logged. I expect to have this done this week (and you're welcome to add or update with your votes any other issues in the meantime).

Thoughts on this proposed approach?

Feedback Requested: proposed changes to our FamilySearch wiki license
Summary: Ben Bennett is the product manager for the Wiki and requested this item be added to the agenda. Ben will be joining our meeting and will lead this discussion. For background on this discussion, the FamilySearch wiki uses a creative commons non-commercial license vs. the Creative Commons Attribution-Share Alike license which Wikipedia.org and many other well known wikis use. As the hosts of the wiki, we are proposing a change in the licensing of our content in order to allow our community members (and others) greater flexibility in the way that the wiki content is used. Prior to doing so, we want to solicit community input on this planned change. We plan to solicit input from the wiki community at large starting on Wednesday, February 10th - Friday, February 19th via a notice on the wiki home page. After the feedback period is complete, we will communicate the planned decision and appeal process should any contributors disagree with the outcome. Additional details (and links to the exact language for the different licenses) can be found below.

References:
 * 1) Current FS Wiki License: Creative Commons non-commercial
 * 2) Proposed FS Wiki License (pending community input): Creative Commons Attribution Share-Alike
 * 3) General Description of all Creative Commons licenses: Creative Commons Summary - All Licenses

Note that the full legal language of each license is available by clicking on the "Legal Code" link at the bottom of each page.

Detail: FamilySearch originally selected a non-commercial license for the wiki because we did not want a commercial company to be able to put a different face on the content and wanted to keep our content ad-free. That said, as we've looked at ways that other wikis are run, organized and licensed (namely Wikipedia.org ) and considered how our community and FS may want to use content in the future, we think that a license change may be in order. In support of this intention, some research with our legal advisors at FamilySearch has helped us understand why a non-profit, community site such as Wikipedia.org might choose a license that permitted “commercial” use of the content. The legal advisors informed us that “commercial” is associated with anything where money is being charged. The ambiguity of the non-commercial license could place restrictions on the FamilySearch wiki, limiting future use of the content, even for legitimate non-commercial purposes. Some examples of activities that are not allowed under the current FamilySearch wiki license are included below:
 * 1) 	I contribute a large portion of information to begin a new article. Others edit the information, but the bulk of the content is still my original work. Later, I want to utilize the information with edits in a class syllabus for a conference. Under the current license, I would not be able to do this as a paid conference presenter. I could use my original contribution, but not any of the updated, current information contributed by others.
 * 2) 	I am teaching a free family history class, but no Internet access is available at the venue. I want to print copies of a few articles from the wiki for the participants in my class. I need to recoup my copying costs, and so I want to charge a small fee for the copies. It is questionable whether or not this would be allowed under the current license.
 * 3) 	I am a commercial company and I want to contribute content to the existing wiki, rather than create my own online research tool. I determine that the FamilySearch Research Wiki is the best place to send my customers to get the most current research information. I want to provide links to the wiki on my website to show my customers how the wiki may work with my own products and still provide a unified, good experience for my customers. By linking to the wiki, I will drive more traffic to the wiki and help my customers get the research help they need. Some of my customers may even become potential contributors to the wiki. I cannot do this under the current license.
 * 4) 	A non-profit entity realizes that some parts of the world do not have access to the Internet. They decide to print relevant articles of interest for those parts of the world, and package them in a small booklet to be sold at cost to peoples in these regions. This would not be allow under the current license.

While the commercial license has been implemented with Wikipedia (see ), it is interesting to note that we have been unable to find any company who has chosen to risk using this license in a commercial way. The general ambiguity of the Creative Commons licenses appears to have limited commercial companies from using the content, possibly due to the potential risk of unclear interpretations of the terms of these licenses.

Stay Informed
Stay informed by visiting the FamilySearch Wiki Forum and by viewing the following pages:


 * Wiki Product Backlog
 * Wiki Known Issues