Hi Hans,<br><br>I wont be a fanboy here and express the benefits of git over svn, but the coolaid tasted great! <br><br>I figured from the gist of Edi's original post that there just isn't enough time (understandably) to move hunchentoot forward and I believe that garnering a little community support on this worthwhile, at least to me, project would be helped by converting it into a "community project", and a distributed decentralized development model should help in that regard. <br>
<br>Will<br><br><div class="gmail_quote">On Thu, Jan 29, 2009 at 2:27 PM, Hans Hübner <span dir="ltr"><<a href="mailto:hans.huebner@gmail.com">hans.huebner@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>
<br>
<a href="http://bknr.net" target="_blank">bknr.net</a> was temporarily down due to a power failure at the data<br>
center. The machine is back up now.<br>
<br>
What is the plan for the git repository? Why is it needed, what makes<br>
it useful? I'm aware of the "centralized maintenance" "problem" of<br>
Subversion, but as Hunchentoot is not going to convert into a<br>
community project (i.e. we'll review all patches that we accept into<br>
the repository that eventually becomes the release), I'm not sure how<br>
another level of indirection helps. It may be possible to convince us<br>
to switch to git if there is a good reason to do so, but that'd need<br>
some explanation.<br>
<font color="#888888"><br>
-Hans<br>
</font><div><div></div><div class="Wj3C7c"><br>
On Thu, Jan 29, 2009 at 18:28, William Halliburton<br>
<<a href="mailto:whalliburton@gmail.com">whalliburton@gmail.com</a>> wrote:<br>
> Hello everyone...<br>
><br>
> I would like to volunteer any amount of time needed to get Hans's changes<br>
> folded into the main repository and/or get the development version moving<br>
> forward and more accessible. I am working on a startup that is currently<br>
> using hunchentoot and, as chance may have it, I am right about now going to<br>
> be digging into hunchentoot and friends as part of a performance and<br>
> understanding push.<br>
><br>
> Currently the BKNR repository is down, but once it gets back up I would like<br>
> to set up a git repository of flexi-streams, hunchentoot, chunga, and drakma<br>
> and I invite anyone that wishes to help contribute to this effort.<br>
><br>
> I am most interested in figuring out and testing the performance<br>
> characteristics of the libraries with respects to threading/non-threading,<br>
> select/epoll, and proxy/no-proxy on SBCL and am most willing to put in the<br>
> time and effort to develop and test these different scenarios.<br>
><br>
> Thanks to everyone.<br>
><br>
> Peace,<br>
> Will<br>
><br>
> On Thu, Jan 29, 2009 at 7:52 AM, Edi Weitz <<a href="mailto:edi@agharta.de">edi@agharta.de</a>> wrote:<br>
>><br>
>> On Wed, Jan 21, 2009 at 11:22 AM, Volkan YAZICI <<a href="mailto:yazicivo@ttmail.com">yazicivo@ttmail.com</a>><br>
>> wrote:<br>
>><br>
>> > Thanks Hans Huebner for his kindly helps and Edi Weitz for his<br>
>> > uninterest in any effort.<br>
>><br>
>> Volkan,<br>
>><br>
>> If you think you're somehow entitled to an immediate reply or any<br>
>> action from me just because you sent a patch that is "not well tested"<br>
>> and "doesn't include any documentation", you're obviously living on a<br>
>> different planet or at least you don't know what it means to have a<br>
>> job and a family in addition to taking care of more than a dozen open<br>
>> source libraries in your spare time. I might look at these patches if<br>
>> and when I find the time to work on Hunchentoot again or I might not.<br>
>> If that's not acceptable to you, the license on all of my libs always<br>
>> allows you to fork them and basically do with them whatever you want.<br>
>><br>
>> For those of you who wonder why Hunchentoot and some other libraries<br>
>> have been in limbo for quite some time now, here's a quick<br>
>> explanation: A company paid Hans to make a couple of additions to<br>
>> Hunchentoot which are now in the <a href="http://bknr.net" target="_blank">bknr.net</a> repository. I also worked<br>
>> on this a bit in my spare time and added some code, mainly for<br>
>> performance improvements. The good thing is that due to Hans' work<br>
>> the development version is much improved in several aspects over the<br>
>> current release. The bad thing is that due to Hans' and my changes<br>
>> the dev versions of Hunchentoot, Chunga, and Drakma have to be<br>
>> released together, because they are mutually incompatible with the<br>
>> released versions. And, for them to become acceptable (for me)<br>
>> release versions, there's a certain amount of clean-up and<br>
>> documentation needed that still has to be done.<br>
>><br>
>> Now, the deal with the afore-mentioned company was that they would pay<br>
>> Hans and me to do this clean-up and integration work so that we once<br>
>> again have "official" release versions that are feature-wise in sync<br>
>> with the current dev versions. This hasn't happened so far, and right<br>
>> now I fail to see why I should spend a significant amount of my spare<br>
>> time to do this clean-up work when I have more interesting things to<br>
>> do. /Maybe/, this will happen in the future (paid or unpaid), or<br>
>> maybe there'll at some point just be another Hunchentoot release based<br>
>> on 0.15.7 and the dev changes will be lost. Until then, I think the<br>
>> current release isn't perfect, but certainly something that can be<br>
>> used (and is used) without significant problems.<br>
>><br>
>> Cheers,<br>
>> Edi.<br>
>><br>
>> _______________________________________________<br>
>> tbnl-devel site list<br>
>> <a href="mailto:tbnl-devel@common-lisp.net">tbnl-devel@common-lisp.net</a><br>
>> <a href="http://common-lisp.net/mailman/listinfo/tbnl-devel" target="_blank">http://common-lisp.net/mailman/listinfo/tbnl-devel</a><br>
><br>
><br>
> _______________________________________________<br>
> tbnl-devel site list<br>
> <a href="mailto:tbnl-devel@common-lisp.net">tbnl-devel@common-lisp.net</a><br>
> <a href="http://common-lisp.net/mailman/listinfo/tbnl-devel" target="_blank">http://common-lisp.net/mailman/listinfo/tbnl-devel</a><br>
><br>
<br>
_______________________________________________<br>
tbnl-devel site list<br>
<a href="mailto:tbnl-devel@common-lisp.net">tbnl-devel@common-lisp.net</a><br>
<a href="http://common-lisp.net/mailman/listinfo/tbnl-devel" target="_blank">http://common-lisp.net/mailman/listinfo/tbnl-devel</a><br>
</div></div></blockquote></div><br>