Hi, 

I am a big fan of more attention to the contributions. However, it seems to
me we should be more pragmatic about it and not aim too high. For me, the
basic questions are:

 1) How can we make it easier to people to add contributions? (Entry
barrier)
 2) How can we make it easier and more fun to maintain a contribution (i.e.,
in particular, keeping documentation/description and code in sync). This is
crucial for the quality of contributions, since nobody gets paid to work on
those, so it must be "painless". Without regular maintenance, contributions
soon become worthless.
 3) How can we make the process of maintaining high-quality contribs as
self-organizing as possible (without having to form committees etc.)
 4) How can we make contribs easy to find, understand, and install for
end-users as easy as possible.

I think 1) is the least problematic point. It is very easy to create a
contribution with the shipped scripts. Uplaoding to SVN also shouldn't be a
problem for anyone. 

2-4) present some more challenges, about which I have already given my
opinion earlier. I wonder if it was possible, as a community, to put
together a webapplication, written in qooxdoo, which allows for a one-stop
solution for everything that is related with a contrib: Documentation, API
viewer, Bug reports, Demo, Snippets to put into config.json, Version
information, FAQ, questions,  etc. etc. Some of the stuff is already there
and could be included via iframes. 

Such an application should be a tool for maintainers just as for users.
Maintainers could edit the contrib data (secured by the sourceforge / wiki
login, for example), Users could search for contribs, get installation and
usage help, and rate the contribs / write reviews. The latter would
contribute to the self-organizing aspect - let the users decide if something
is useful, not some committee. The Iphone App store and other such
mechanisms show the way. 

What we need help with is the server-side. If the devs could provide some
json web service that woud delive the Manifest.json data, and some
authentication scheme for contributors, it might be possible for the
community to write such an "Contrib store".

C. 
-- 
View this message in context: 
http://qooxdoo.678.n2.nabble.com/speed-of-development-tp5168583p5190282.html
Sent from the qooxdoo mailing list archive at Nabble.com.

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to