Continuing the discussion from Warning: new lan discovery feature in 2.3:
It has once again come to my attention that Beta Groups (and board meetings where ‘Market Research’ and Support History are discussed, and/or studied) are obviously NOT enough to ensure things go smoothly with corporate-lead technology changes here in SmartThings-land.
So, I suggest something more substantial, proactive, and intentional be officially established, and maintained to help in this area.
The group would be officially ‘Authorized’ by SmartThings, but not 'Authoritative’
i.e. their role would be as trusted and valuable advisers, but SmartThings would still make any and all critical decisions.
They would NOT be SmartThings employees; though they could be offered a ‘stipend’ through a Community-Supported donation fund.
They would be chosen (and membership would be maintained ) by a ‘board of directors’ of sorts that would be made up of both Community Members AND SmartThings employees; though the chair of this board (a SmartThings executive; i.e. thus, SmartThings) would have ‘the last word’.
There would need to be a number of different types of Members on the team; including…
Groovey Code-Slingers and Real-World Developers who understand what’s actually happening in the code and in the SmartThings infrastructure
Popular and helpful Members who have a finger on the pulse of the Community via their close and constant interactions with others here
Business-minded Members who understand Change Management ‘Best Practices’ and who can communicate and help guide the team in this regard
- Probably at least one official SmartThings employee (besides the exec in the Chair position) to help facilitate meetings and to serve as an Liaison/Interface between the Team and SmartThings. This position may also be required to participate in SmartThings’ official Communications, and Public Relations Teams (I would be happy to move to San Francisco, and take the position in order to serve in this capacity. ).
Any more ideas around this?