Lets go survey!

But, hey, please stop.
What's the goal? To know how to motivate community members? Is this really the most helpful think we could do? I don't think so.
I personally feel that there are pretty heavier problems in the air. We should concentrate on those and motivation comes by the way. If I understand the Alfresco survey well, the key goal was to know where are the holes in our boat, captains

First fix the holes, then paint the boat

Do we really know our problems? Problems of newbies, users (these who use it) and contributors? Every group has specific ones and all are important. Maybe that community is really bunch of newbies and the rest - to be clear - it's not us and them - everyone is a part of the community and they should know about it (community without newbies is just a boat full of old rats

) But our task (regardless of our size) is to help them and their task is to listen. Everyone who wants to listen is welcome.
Well,
I think the goal of this survey should uncover problems of the domain groups - newbies (group A), and group B - users and old rats

. Maybe some survey could go also to Liferay employees, what do they think? ;)
My friend has one gold rule -
don't come with problem, come with a solution (doesn't mind if bad / primitive solution). So first part should be something like - "How can we help you?" and the second part "Tell us simplest solution how would you solve it?" - keep in mind that everyone has responsibilities (together with influence) in the community - even survey takers

(and I want smart community members who think, not those who only choose from A,B,C).
Survey can be segmented by vertical view (groups (newbies, users + rats) specific view) and horizontal view (problem domains questions). We first need to aim the user - from which continent, developer/manager, how long live with Liferay, already community member? - to correctly setup the vertical view. The horizontal could have categories:
I, what are we not aware of1, your problems - how can we help you
2, tell us the simplest solution you see
II, what are we aware of (in case the category I, won't bring any results
):3, knowledge (how they get to solutions, is documentation complete/useful, is forum well organized, etc., are forum answers helpful, response in-time?, what about wiki, blogs, do you want to go deeper inside the portal?),
4, contributions (how many

, how would they imagine to contribute, what are we missing),
5, social aspects (community mood, expectations, do you want to be part of community+why (not), symposiums/local events, what do you (dis)like),
6, another (quality, security, ...?) ... please help ...
Together with stats we should have good knowledge which group want's what, some ideas how to solve it and how is the survey complete - how many peoples we have in each category and how are the problems hot (we still need to somehow deliver the survey to more than 30 users ;) ).
And after this we can start to work on it. 100 PCs, Leadership team, Bug Squad and Community Verifiers teams are gaining big success (thanks to big James' effort!). Why not to continue and create workgroup(s) to solve discovered problems (e.g. documentation sqad

)? I know it takes James' time to organize it but it has visible and
useful results.
This could be a way how to rise motivation. We can give them better knowledge of Liferay, learn new technologies, help them to scratch their own itches (they still have to to listen what to do) and they give something back to community - help us (and themselves), will be part of something bigger and they will gain respect - which are the motivators we have and expressed.
I hope it makes sense - I've never conducted any survey so I can be totally out

-- tom
Please sign in to flag this as inappropriate.