Community Meeting Agenda 9 February 2010: Difference between revisions

Community Meeting Agenda 9 February 2010 (view source)

Revision as of 18:08, 11 February 2010

4,471 bytes added , 11 February 2010

→‎Feedback Requested: Current engineering priorities and future backlog prioritization process

VisualWikitext

Benrbennett

467

edits

@@ Line 15: / Line 15: @@
 == Discussion Items  ==
-=== Feedback Requested: Current engineering priorities and future backlog prioritization process  ===
+=== Update!: Current engineering priorities and future backlog prioritization process  ===
+'''Update:''' As discussed in our last meeting, while we work on a long term solution to share our engineering backlog within the wiki itself, we've created an interim solution to share the backlog, allow you to vote/promote issues so that they are prioritized higher and add new issues. For those who are intrested, the process is as follows:
+. Log on to the [https://issues.devnet.familysearch.org/ FS Developer's Network] and create an account (yes, you'll have to create another account... my&nbsp;apologies, but, it's an interim solution)
+. Send email to [mailto:bennettbr@familysearch.org] notifying me that you've created a Developer's Network account.
+. I'll add you to the private Wiki Development Backlog project where you'll be able to see the backlog (once I've added you as a member of the group, you can use the following link to access the backlog in the future:[https://issues.devnet.familysearch.org/projects/wikioperations/issues Research Wiki Dev Backlog]
+Once inside the backlog, note that you can view issues (in list form), vote on issues (by clicking on the subject line link and then using the up or down arrows on the subsequent page) and add issues&nbsp;(by clicking on the 'new issue' tab).&nbsp;
+Also, answers to your questions posted after the meeting are as follows:
+. 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. [Ben Bennett]&nbsp;Unfortnutally you're right (at least for the time being).&nbsp; That said, one of the items that we've added to the engineering backlog is a task to add an extension to the wiki that will allow us to track issues/bugs within the wiki itself.&nbsp;
+. Is DevNet there for everyone to add information, or is Ben the only one who keeps the discussions updated in DevNet?&nbsp;[Ben Bennett] As long as you sign up for a DevNet account, you can view, add, modify and vote on items on the issues list.&nbsp; &nbsp;<br>3. If the conversation is going on in the Forums, who would take it and move it onto the backlog. [Ben Bennett] Anyone can move the issue to the backlog (ideally whoever sees it first) and then add a reply in the forums that the issue has been added to the backlog with a link to it should the original submitter wish to see the full list.&nbsp; <br>4. 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? [Ben Bennett] Voting isn't over, but, the forums aren't exactly the easiest way to manage&nbsp;the&nbsp;engineering backlog.&nbsp; For now, items will be moved from the&nbsp;forum into the backlog on&nbsp;DevNet where you can vote/promote those items that are of greatest interest to you.&nbsp; Note that the&nbsp;voting functionality is already&nbsp;enabled, however, I've had some problems seeing the voting buttons using IE7/8.&nbsp; You can see them just fine using Firefox.&nbsp; <br>5. I am concerned that the majority of the backlog will be content backlog and the DevNet tool is only geared toward tracking engineering backlog. [Ben Bennett] Correct... for starters, we'll use DevNet for the engineering backlog.&nbsp; We're looking for other solutions for the content backlog.&nbsp; <br>6. Wikicode backlog is also another aspect of our tracking needs. [Ben Bennett] For now, I'd propose that we add this to the backlog on Dev net as it's engineering related.&nbsp; To the extent that members of the community can/want to complete wikicoding tasks, they can assign themselves those tasks in the DevNet backlog.&nbsp; If a wikicode task goes un-assigned (for whatever reason) and is voted as a high priority, we can look at having the FamilySearch staff work on this.&nbsp; Open to feedback if you disagree with this approach.&nbsp; <br>7. We need three backlogs: Content, Wikicode, Engineering <br>8. 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. Thomas_Lerman 22:20, 9 February 2010 (UTC) [Ben Bennett] I like your definitions and I think that those are fair for starters.&nbsp; <br>
 '''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).
@@ Line 34: / Line 52: @@
 :*Wikicode backlog is also another aspect of our tracking needs.
 :*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)
+::*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  ===