i want to focus on the point of this thread much more closely:
http://forums.slimdevices.com/showthread.php?t=25472
i want to know the consensus view out there on what is both the most
effective and appropriate way to make suggestions about the hardware or
software that you'd like to see implemented in an upcoming future
release. how does one best bring something to fruition, outside of
writing the code themselves?
1) ask on the forum how something works, make sure that you understand fully what the intention was and are sure that you disagree with the existing implementation and have an improved idea. This doesn't have to be a code level idea, but you do need to think through what you want ("make it better" is not okay, "provide a button labeled 'foo' on the 'bar' page that does 'baz' when clicked" is okay).
2) enter that improvement into bugs.slimdevices.com. Include use cases and mock up pictures or sample files, if applicable. The idea here is to make it easy for a developer to understand what you want and to make that developer excited about doing it. You're trying to hook one of the people who periodically introduce themselves on the developer list and ask for something to do.
3) explain the request on the forum and link to the bug -- put the link in your signature, do a poll, start new threads, and continually ask for supporters. When other people ask about this thing, encourage them to vote for your bug too.
That will almost guarantee a considered and engaged response from the entire community, including SDI employees. If they say no, and you still disagree and think it ought to be done, your next step is to learn Perl and write it as a plugin, or beg/bribe someone else to do it.
This may all seem untenably awful, but it's how it was done for everything else.
--
"I spent all me tin with the ladies drinking gin,
So across the Western ocean I must wander" -- traditional
_______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
