http://su.pr/6N0VlM

Thank you for the lovely post about how you are using cyn.in for your community. Its great to hear that you are enjoying using cyn.in v3.

Documentation, like you pointed out, is sparse. This has been a biting concern for sometime and we are actively working towards building and publishing video guides, tutorials and documents. Post the release of v3, we will also be looking at increasing the community involvement towards the documentation.

A whole lot of research reports reveal that the biggest barrier to adoption of open source software is lack of Support. We have taken it upon us to provide reliable support and drive adoption of our product throughly in the enterprises. I am really glad to know that it is really showing. “World-class support” is the best compliment that you can give us

Customer Feedback is the top driver to innovation at Cynapse. We connect and engage with our customers, understand what they think is important and focus on delivering it with the product. This also helps us create a competitive differentiation. Your ideas has been valuable and have helped us drive further enhancements into the product. Investing in the customer’s inputs have increased our success rates greatly. Certain very large customers are also driving us to innovate heavily and you can look forward to a lot more interesting capabilities to be added to cyn.in, in the near future.

Your usage of the cyn.in Events with Google Calendar sounds really interesting. We’d really like to hear more about it.

Look forward to reading your future posts and hearing more feedback about cyn.in

This is not open source development. As a matter of fact, quite the contrary. Take a look at Why the FSF gets copyright assignments from contributors.

FSF requires that each author of code incorporated in FSF projects provide a copyright assignment, and, where appropriate, a disclaimer of any work-for-hire ownership claims by the programmer’s employer.

In my case, I’m offering folks attribution for their work that contributes to the common goal. I’m offering a venue. For example: I may have the requirements for a user interface but lack specific user experience/ interface design and development skill-sets. There may be someone out there who currently has great ideas and talent but lacks the opportunity to implement them. If that someone believed in the cause/project then they could contribute & have their name among the credits.

As far as communicating new concepts is concerned, I agree – it’s difficult. Especially if you try cranking out volumes of Word documents, or, wiki pages which are completely unconsumable. In our case, we’ve been successful following the outside-in agile/scrum software development methodologies where we break things down into small time-boxed deliverables. This enables us to quickly validate / flesh-out our theories without being married to documents that quickly become obsolete. I understand not all environments can be Agile.

The true challenge of building a tribe, in my opinion, is to find people who are pre-disposed to share in value and passion for your mission. Formulating the messages for communication of a truly new concepts is very difficult as a dictionary, tags, keywords are still quite amorphous and people are overloaded by information (?).

You seem to approach this path “to become” from the place of introspection and service, and I hope you succeed in connecting your dots into it.