Prioritisation

looking at the prioritisation at

https://docs.google.com/spreadsheets/d/15IsDMPwSXx197Iqe4I9xh7K8anmJ5c0-OFEG7w0LHYM/edit?usp=sharing 


i found myself  wondering what the priorities mean, and how they were 
arrived at.

what they mean: could a low priority mean that work is under way to 
provide the functionality in question, and that therefore additional 
work is a low priority? Or does it mean that it is felt that this is a 
less important feature to have than others.  Presumably the latter would 
imply that, when bandwidth is limited, work should be directed elsewhere 
first; but once that high priority work is completed, does the priority 
change for the low priority features?  In other words, are all the 
features really important, but just less urgent than others?  Or are the 
low priority features really not terribly important?

how arrived at: who decided on the prioritisation, how was it done, and 
what communities do they represent? Some features are presumably likely 
to be of higher priority to certain subgroups – an easy example being 
vertical text, which got a high priority rating during the workshop in 
Japan, which was mostly attended by CJK folks, but is perhaps not so 
urgent in the West.  How is that factored into the prioritisation?

i suspect it would be useful to point to or include some text to 
describe these things for people looking at the spreadsheet.

cheers,
ri

Received on Tuesday, 4 August 2015 04:07:44 UTC