Hi Benedikt >I have created a twitter account: https://twitter.com/ApacheCommons >Please follow and retweet ;-)
Great initiative! I'm already following it, thanks! And while on a similar subject, few days ago I started a small python project to create a Twitter bot [1], that reads the [ANNOUNCE], [ANN] and [ANNOUNCEMENT] messages posted to the announce mailing list and tweets them. I've been doing that manually in another Twitter account, and thought it would be cool to automate it (like what was done in the Jenkins CI project [2]) I finished the code yesterday and after a few tweaks, and after today's release (Apache Camel) I believe it is working correctly, though I'll have to wait few more announcements to make sure it has no bugs. The code is hosted at GitHub [3], it's written in Python and uses a GPL MarkMail API (some simple python REST client). Thanks again and have a great week. [1] http://twitter.com/asf_releases [2] http://twitter.com/jenkins_release [3] http://github.com/tupilabs/asf_releases_aggregator Bruno P. Kinoshita http://kinoshita.eti.br http://tupilabs.com >________________________________ > From: Benedikt Ritter <brit...@apache.org> >To: Commons Developers List <dev@commons.apache.org> >Sent: Sunday, July 7, 2013 9:15 AM >Subject: Re: [ALL] Improving Commons public relations > > >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) >> - create a Twitter account where we can post news from commons. The Mesos >> project already has such an account. [2] >> > >I have created a twitter account: https://twitter.com/ApacheCommons >Please follow and retweet ;-) > >The account is linked to my @apache.org email address. Where do I put the >password? > >Benedikt > > >> >> 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 > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
