2013/7/4 Benedikt Ritter <brit...@apache.org> > Hi, > > we had this discussion lately where we talked about attracting new > contributors for commons [1]. Over the past few days I've been thinking > about this topic again and I've come to the conclusion that there are > several things we could do to improve our "public relations". > > Here is a list of things that I would like to change (and by this I mean, > that I volunteer to do the work ;-) > > 1. Make commons more visible in coding social media > - request git mirrors for every proper component, so that everything is > also at github > - add all proper components to Ohloh (and clean up the existing ones) >
I've worked my way through Ohloh this weekend. I cleaned up all components that where already present. They all follow the structure of [MATH] now: Project Name: Apache Commons <component-name> URL: http://www.ohloh.net/p/apache-commons-<component-name> I've updated all URLs and added links to the mailing list. I also added some tags were it seemed reasonable. I ran into problems with some components: * IO could not be renamed because "Apache Commons IO" is already in use. I've searched Ohloh for this name and didn't find anything. So I've created a request in their support forum. Some for Commons Transaction. * There are two entries for OGNL: The components and Commons and the original source at github. * Betwixt, FileUpload and Jelly haven't synchronized for a long while. I've created a separate thread for this in the support forum. * I wasn't able to edit JEXL, because it is managed by henrib. Most components don't have a manager and changes can be made by anybody. I don't know if it makes sense to restrict this. Now I have enough of Ohloh for a week :-) I'll start adding missing components, when I got the time. Regards, Benedikt > - create a Twitter account where we can post news from commons. The Mesos > project already has such an account. [2] > > 2. Make the website more attractive > - Use a modern design - I don't know who said it, but I loved it when > someone said "our website looks like we're java 1.3 users". Well, this is > true. Simone made several attempts to make commons switch to the maven > fluido skin [3,4,5]. I think the time has come to finally do something > about the website. > - include a news section on the main page - Having all the components > listed on the home page is a good thing for navigation, but what I'm really > interested in, are news about the development. A new git mirror has been > created? Cool, thanks for telling me. Collections 4 alpha1 has been > released? Good to know, I'll download it right away. No need for a big fat > list that contains all components when most people probably only use a few. > > WDYT? > Benedikt > > [1] http://markmail.org/message/o7ef6o4ahe23k5iu > [2] https://twitter.com/ApacheMesos > [3] http://markmail.org/message/tkh4yqfcqg5i444g > [4] http://markmail.org/message/jnlyhbh5yq3zp54t > [5] http://markmail.org/message/jk4addjqw67476bk > > > -- > http://people.apache.org/~britter/ > http://www.systemoutprintln.de/ > http://twitter.com/BenediktRitter > http://github.com/britter > -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
