2,175
edits
(Comment) |
|||
Line 15: | Line 15: | ||
== Discussion Items == | == Discussion Items == | ||
=== Feedback Requested: Current engineering priorities and future backlog prioritization process === | === 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. | '''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 [https://issues.devnet.familysearch.org/projects/wikioperations/issues] to share and manage the backlog. | '''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 [https://issues.devnet.familysearch.org/projects/wikioperations/issues] 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 [https://issues.devnet.familysearch.org/projects/wikioperations/issues] is the proposed solution. | 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 [https://issues.devnet.familysearch.org/projects/wikioperations/issues] 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. | 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? | Thoughts on this proposed approach? | ||
:*No major objections. One concern was that it will be just another site check for information. Currently we have the Wiki, talk pages, and Forums, and this new site will add yet another site that needs to be checked. | :*No major objections. One concern was that it will be just another site check for information. Currently we have the Wiki, talk pages, and Forums, and this new site will add yet another site that needs to be checked. | ||
:*Is DevNet there for everyone to add information, or is Ben the only one who keeps the discussions updated in DevNet? | :*Is DevNet there for everyone to add information, or is Ben the only one who keeps the discussions updated in DevNet? | ||
:*If the conversation is going on in the Forums, who would take it and move it onto the backlog. | :*If the conversation is going on in the Forums, who would take it and move it onto the backlog. | ||
:*For example, the current Poll in the Forum related to the red links in search results now has 14 votes. Is the voting over? Is this feature/enhancement automatically moved to the backlog? Has it been moved already? Where is it in the priority? | :*For example, the current Poll in the Forum related to the red links in search results now has 14 votes. Is the voting over? Is this feature/enhancement automatically moved to the backlog? Has it been moved already? Where is it in the priority? | ||
:*I am concerned that the majority of the backlog will be content backlog and the DevNet tool is only geared toward tracking engineering backlog. | :*I am concerned that the majority of the backlog will be content backlog and the DevNet tool is only geared toward tracking engineering backlog. | ||
:*Wikicode backlog is also another aspect of our tracking needs. | :*Wikicode backlog is also another aspect of our tracking needs. | ||
:*We need three backlogs: Content, Wikicode, Engineering | :*We need three backlogs: Content, Wikicode, Engineering | ||
::*From my discussions with Fran, I believe the definitions are as follows: Content = anything that most any contributor can handle; Wikicode = anyone at least a little more technical that can work in Wikitext, create templates, etc.; Engineering = only FamilySearch.org employees can work on. [[User:Thomas_Lerman|Thomas_Lerman]] 22:20, 9 February 2010 (UTC) | |||
=== Feedback Requested: proposed changes to our FamilySearch wiki license === | === Feedback Requested: proposed changes to our FamilySearch wiki license === |
edits