Improving involvement

[Kalvir Sandhu]

Hey again,

I mentioned early that this mailing list could be an issue. For things like getting the right feedback on talk proposals, encouraging talk proposals themselves or just getting people that attend fully involved in engineering the content. Perhaps some people just ignore the mailing list, don't know, is anyone that attended the last ruby manor actually reading this message?

So before I outline my proposed idea, a quick overview of the pain that this aims to improve:

- Not getting all people that attend the conference involved

- To stop getting simple +1, "yeah would love to hear about that" type of feedback

- Not getting enough talk proposals (not related to mailing list but something that needs to be improved)

The answer, yep a webapp, I know Richard mentioned one in a reply to the 'what happens next?' thread. Would love to hear if people think this might help?

Attendees would register, as part of the registration you are encouraged to propose a talk idea, something you are or have worked on? Maybe something you want to know more about?

Others will then be able to view that idea (views are recorded in backend so we can determine things like who viewed to commented ratio).

Others can then vote for or against the idea, with specific sections asking for added context on their response. Attempt to get the right type of feedback.

In order to increase visibility on involvement have the ability to indicate which attendees are contributing and those that aren't. It's hard to present this neatly and automated with the mailing list.

Maybe have the ability to discuss with attendees against that idea so that people can keep talking and getting the talk ready.

Email notifications on activity, feeds, etc to keep people informed.

This could be something used before a ruby manor is held, to register interest, generate content and attendees. Then if there is enough content to hold a ruby manor then throw together a cheap venue and do it. This then could be repeated, so the size of the ruby manor would depend on how many talks there are and the number of attendees. Moving from the conventional buy ticket, create schedule to create schedule then be awarded the possibility of buying a ticket.

That's the main gist of it, am I crazy?

Kalv.

[Murray Steele]

I think there's some definite merit in trying out an app with more structure than a mailing list for the talk suggestions.  I've got some time this weekend and will take a crack at it.

Does anyone have any comments on Kalv's suggestions below about how it should work?  Or ideas of your own?

Muz

--
http://rubymanor.org
Group home: http://groups.google.com/group/ruby-manor?hl=en
Unsubscribe at ruby-manor+...@googlegroups.com