On 4/16/15 1:12 AM, Joakim wrote: [edited] Cherry-picking one easy-to-address question:
If they're not scratching their own itch, how do they know whether the random issue they've chosen is actually a priority?
That's simple - does it fit with the vision or not? Walter and I also find it useful to use that way.
Sure, and lists of priority issues can even emphasize to the current contributors which high-impact work you feel should be done first. You have pointed out which direction you want the community to go in the vision document, but some of those are too broad, ie "improve quality." Stick some meat on those bones, by providing a list of issues you feel would move those agendas forward, and you might get the language moving further in your direction.
This is worth trying. I'll put a list together perhaps during the hackathon. The more difficult part will be maintaining it, which becomes a job - one extra thing on the plate of the same people. I guess the first item on the list will be "maintain the list". Deliciously self-referential :o).
Andrei
