FamilySearch Wiki:Suggestions for Engineering: Difference between revisions

FamilySearch Wiki:Suggestions for Engineering (view source)

Revision as of 18:53, 26 March 2011

1,853 bytes added , 26 March 2011

added process section

VisualWikitext

VasquezJL

2,785

edits

@@ Line 1: / Line 1: @@
-This page documents ideas/suggestions that require the involvement of FamilySearch Engineering:<br>
+This page documents ideas/suggestions that require the involvement of FamilySearch Engineering.<br>
+If you are interested in seeing something change in the wiki, and FamilySearch engineering resources will be needed to make the change, please add it here.
+See below for guidelines for [[#Process_for_Decision_Making|adding to this page and voting on suggestions]].
 <br>
@@ Line 16: / Line 20: @@
 | <br>
 |- valign="top"
 ! style="background: none repeat scroll 0% 0% rgb(204, 204, 255); text-align: right; padding-right: 0.4em;" | Priority Votes:<br>
-| <br>
+| [[User:VasquezJL|janellv]]-3;<br>
 |- valign="top"
 ! id="fileinfotpl_aut" style="background: none repeat scroll 0% 0% rgb(204, 204, 255); text-align: right; padding-right: 0.4em;" | Owner:<br>
@@ Line 45: / Line 49: @@
 | <br>
 |- valign="top"
 ! style="background: none repeat scroll 0% 0% rgb(204, 204, 255); text-align: right; padding-right: 0.4em;" | Priority Votes:<br>
 | <br>
 |- valign="top"
@@ Line 55: / Line 59: @@
 |- valign="top"
 ! style="background: none repeat scroll 0% 0% rgb(204, 204, 255); text-align: right; padding-right: 0.4em;" | Status:<br>
-| Posted on forum <br>
+| Posted on forum; discussed with owner of process<br>
 |- valign="top"
 ! style="background: none repeat scroll 0% 0% rgb(204, 204, 255); text-align: right; padding-right: 0.4em;" | Next steps:<br>
-| Propose at Tech meeting<br>
+| <br>
 |}
 </div>
@@ Line 74: / Line 78: @@
 | <br>
 |- valign="top"
 ! style="background: none repeat scroll 0% 0% rgb(204, 204, 255); text-align: right; padding-right: 0.4em;" | Priority Votes:<br>
 | <br>
 |- valign="top"
@@ Line 101: / Line 105: @@
 |- valign="top"
 ! style="background: none repeat scroll 0% 0% rgb(204, 204, 255); text-align: right; padding-right: 0.4em;" | Avg. Priority:
-| <br>
+| 1<br>
 |- valign="top"
 ! style="background: none repeat scroll 0% 0% rgb(204, 204, 255); text-align: right; padding-right: 0.4em;" | Priority Votes:<br>
-| <br>
+| [[User:VasquezJL|janellv]]-1;<br>
 |- valign="top"
 ! id="fileinfotpl_aut" style="background: none repeat scroll 0% 0% rgb(204, 204, 255); text-align: right; padding-right: 0.4em;" | Owner:<br>
@@ Line 113: / Line 117: @@
 |- valign="top"
 ! style="background: none repeat scroll 0% 0% rgb(204, 204, 255); text-align: right; padding-right: 0.4em;" | Status:<br>
-| Posted on Forum<br>
+| Posted on Forum; proposed at tech meeting<br>
 |- valign="top"
-! style="background: none repeat scroll 0% 0% rgb(204, 204, 255); text-align: right; padding-right: 0.4em;" | Next steps:<br>
+! style="background: none repeat scroll 0% 0% rgb(204, 204, 255); text-align: right; padding-right: 0.4em;" | Next steps:
-| Propose at tech meeting<br>
+|
 |}
 </div>
+=== Process for Decision Making:  ===
+In the Wiki, when something major needs to be changed, it's important for the community to be involved with discussing how those changes should be made. The following will help the engineering team know what is important to the community:
+''(The following is a proposed process - please add your thoughts to the discussion page.)''
+*'''Make a suggestion:''' Begin by making a suggestion on the Forums or a Discussion so that others can chime in on the proposal.
+*'''Add your suggestion: '''Then add your suggestion to the page above. Create a new table and add a link to where the issue is being discussed. (These items can also be discussed in the Weekly Contributor and Technical meetings, but it's important that the discussion is being discussed where there is documentation.)
+*'''Set a priority: '''Add your vote to the "Priority Votes:" row with your username and what you see as the priority of the item from 1-5:
+:*1-High: something that affects a large number of users a significant amount
+:*5-Low: something that's a change more for aesthetic reasons than for usability purposes<br>
+:As each person adds their priority, they should add their number into the average in the '''Avg. Priority''' row. If you are the owner, you should solicit at least x (how many?) votes for your item before you request that engineering review the priority.
+*'''Engineering Repsonse:''' When the engineers have reviewed it, they will add to the '''Next Steps''' section ....?