pigmej at gmail
Jun 7, 2012, 3:46 PM
Post #2 of 2
I have some "pending" patches for Admin. I think one is in pull request in
github ( for CTK ).
I totally agree with your words. And I will try to manage some time for
admin things mostly... ( I have some fixes for market also, and updated
market packages ).. I just lack of time...
07-06-2012 22:31, "Stefan de Konink" <stefan [at] konink> napisał(a):
> Hi all,
> Long time I was totally against supporting really stable development. But
> over the time I have realised that some innovations in Cherokee that did
> fix some bugs, actually introduced more for other parts. Since I know many
> people on this list care for Cherokee and we all know what Alvaro is
> working on in his spare time, it would be a good thing to start fixing
> noticable, small things in Cherokee.
> We have a great webserver, a great admin. And it doesn't really matter if
> we are the fastest or not. It actually matters that people that try
> Cherokee end up with the same problems, and the bugtracker is getting
> overloaded. To make some points very clear:
> 1) The biggest issue in the "stable" branch is the fact that SSL and POST
> support is problematic due to recent Google 'inventions'. With some support
> of Google in the past (and some workarounds by myself) it is possible to
> get a working Cherokee "stable" anyhow.
> 2) There are so many low hanging fruit bugs around that virtually anyone
> could help fixing them or write tests for them. Tests help to reproduce
> things, and prevent them from happening again in the future.
> I know some people on IRC and on this list are actively fixing things in
> Cherokee, they are not getting "incorporated" in the stable. This should
> change, and can only change if the community starts to act.
> From now on I would like to ask people to get involved, and commit to fix
> one defect per week from the Google Bugtracker. It is not much, and can be
> done, any bug counts.
> Speak out and tell people you are working on things. That includes
> unreported bugs that you are taking care of, it doesn't really care about
> what you want to address, it matters it is one bug less to care about. If
> you are doing a good job in C, the server core is probably what you want to
> look at. Python might be more your thing if you would like to improve the
> Practice what you preach:
> The main reason I cannot switch back to stable on all my production
> machines is the SSL trouble. I would like to commit on the SSL POST on
> stable. Google has posted a oneliner for eJabberd, I would like to see the
> method its uses ported, opposed to my own workaround, which is also a one
> liner, but not really the right way.
> I hope some people join :-)
> P.S. If you can't code, but are extremely wealthy you could also help:
> place a bounty on your favorite bug to be fixed. If you don't want to cash
> your bounty, you could place it on another bug ;)
> Cherokee mailing list
> Cherokee [at] lists