> -----Original Message----- > From: Christian Hammers [mailto:[email protected]] > Sent: Tuesday, 7 July 2009 2:32 AM > To: [email protected] > Subject: Re: Gathering Community Interest > > Hello > > As log4php was apperently in "coma" for a while I guess it's important > to update the web sites asap so that people see that they can again > use it for new projects. > > Improve the docs, things like "how to configure logging to an automatic > rotated logfile" are probably the first things people look for. > > Once the package is stable again it should be proposed to the various > Linux distributions (I could upload a Debian package) and to all the > Web Frameworks like Zend or Symfony who have started to build their own > logging framework and advertise this and to those who do not already > recommend one. > > Small press notes or one page tutorials for the various online and paper > PHP magazines would also be an idea. > > Maybe put all the suggestions into a TODO file under Development on the > web page > so that people who think that they can spend e.g. a weekend but do not > want to > contribute on a long term can pick an item and do it. > > bye, > > -christian- > >
Certainly a TODO list is a good idea. As an incubating project I'm not sure about the packaging ideas yet. The next goal I think is to set a target for doing an incubating release. A release is also one step further towards exiting the incubator and becoming a logging sub-project proper. (That release can then I guess be recommended to go into a Debian/Ubuntu package etc.) The project can also gain exposure by doing a release as we can work with the Apache Public Relations Committee (PRC) to help get the word out - and they will be more than happy to help do this. Also, blog early and blog often -- I know Christian already does this on his own blog. We also have blogs.apache.org - every project is entitled to have their own blog there and committers of those projects can have accounts. Christian (Grobmeier) let me know if you are interested and I'll set one up for log4php straight away. OpenEJB and others use it quite successfully. So, first job then is I would look at that batch of 15 open issues on Jira - 1. decide out of those which will form part of the initial release 2.0-incubating, 2. change the rest to become part of the 2.1 schedule. 3. Decide after that if there is anything else left hanging, i.e. not in the issue tracker but needs finishing off before a release. (Such as producing RAT reports to indicate if any files are missing license headers etc - this should actually be added to the Issue Tracker - I can do this part) For Step 1 above - decide if they are bugs or features/wishes, if features I guess they can immediately move to 2.1, if bugs decide if they important enough to do for 2.0 (our first release here) or if they too can move to 2.1 (Note most people use the default 'bug' but some can be changed) I believe once a release is out there then folks will use it more, will come back to the community and report any issues they find, out of that maybe one or two will even start providing patches etc. Growing a community is a slow process, a release and all that goes with it (promotion from PRC etc) will certainly help. Christian (Grobmeier), as the main active committer, you know your timeline better than anyone, so coming up with a guestimate of a release date should be down to you, I'll help as much as I can to go through the release process with you - everyone else of course is welcome to provide patches and also importantly to help test a release candidate - Christian Hammers and other users here - this will be your time to help in that process. If anyone has any documentation improvements they would like to see on the website - please provide patches or attach your ideas to the Jira Issue, we will apply them. Cheers Gav... > > > > > > On Mon, 6 Jul 2009 17:13:42 +0200 > Christian Grobmeier <[email protected]> wrote: > > > Folks, > > > > I know its summertime, but I feel quite alone at the moment. > > Would like to change this and would like to ask you how we could > > gather more community interest. > > My first idea was to update the website with what we did in the past, > > f.e. the PHP5 support. > > Would that help? Any other ideas of getting log4php in attention? > > > > Best, > > Christian > > > Checked by AVG - www.avg.com > Version: 8.5.375 / Virus Database: 270.13.3/2217 - Release Date: 07/05/09 > 17:54:00
