I just googled "MojoMojo" and was stunned by the paucity of third party sources.
Wikipedia aside, the lack of 3rd party commentary, is indicative of a "marketing problem" that needs to be addressed. (Yes Virginia, even open source projects need to market). The people involved seem to be pretty good about blogging and creating a web-presence but they appear to be over-relying on their own words. Buzz only happens when other people talk.
Some ideas for starters:
- invite users to add their websites to a list
- design a "powered by" button
- add a section to the wiki with MojoMojo "success stories" and implementation/roll-out adventures
- request/submit articles to moderated or juried e-zines or print magazines - even if developers write them, others outside of the project have to read them and comment on them.
- make requests like this - maybe one of the monks not on the project will take time to study mojomojo and write something up
- contact bloggers in the CMS, web design, etc community and ask them to review MojoMojo and write a short article
- start a facebook group for users of MojoMojo
- start a Linked-In group for developers and consultants interested in learning how to extend MojoMojo or considering MojoMojo for their clients.
- add technorati, etc buttons to your wiki webpages so that really helpful documentation/use cases have a chance of getting tagged.
It would be a shame to put all this work into a project like this without also getting a vibrant user community. Users generate users and third party reviews generate trust which generates users. Users creating their own extensions and helping each other use the software build community. Users - not developers.
In the long run open source projects survive and thrive because of their user base and the only way to create one is to get the word out.
Best, beth
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
