Hi michael, we actually don't want to change the name. Hopefully we can use the official name at github.
Regards also from berlin, Jan On Wed, Feb 27, 2013 at 8:43 PM, Michael Heid <[email protected]> wrote: > Hi, > as far as i know; David is still hard working on the migration from trac to > github. > So agavi isnt "death".. > Forking will create a new framework with new name which less people know, > less support etc.. > Wouldnt like to see that people goes that way just because we have no update > since some time... :/ > > > cheers from berlin > michael > > > > 2013/2/27 Jan Schütze <[email protected]> >> >> Hi Yossi, >> >> Like you stated: the last release has been a while and trac is closed >> since dec 2011 [1]. Some guys from the #agavi channel and my >> co-workers have several small patches, which should be reviewed and >> discussed. >> >> Currently we create and maintain agavi pages since agavi 0.10 and it >> plays nicely for heavy load pages with a setup of varnish/nginx and >> some php-fpm workers ;). >> >> We are currently thinking about forking agavi on 2013/03/01 and we >> want to maintain it on github: to push agavi development forward! >> >> Would be awesome to have you and your developers contributing! >> >> Regards, >> Jan >> >> >> >> >> [1]: https://twitter.com/Agavi/status/152838667738693632 >> >> On Wed, Feb 27, 2013 at 6:53 PM, Yossi Ben Haim <[email protected]> wrote: >> > Is Agavi dead? >> > >> > The Company I work for will start a new project shortly and we need to >> > select a framework to use. The project is expected to have a big code >> > base >> > and high load (Millions of requests per day). >> > >> > Our project have multi-tier caching/storage systems which include >> > memcache >> > and Couchbase servers, and the new project will be at least as >> > demanding. >> > >> > We are 8 PHP developers, and we need to make a selection of framework to >> > use. Up until now the team here used Symfony (1) and I am the only one >> > with >> > experience with Agavi. As much as I love almost every aspect of Agavi >> > (over >> > the crappiness of symfony), I don't feel very comfortable making the >> > push to >> > use Agavi for the following reasons: >> > * It's been more then a year since the last version released. And a year >> > since the lase update on the move to github. >> > * I have no experience with Agavi under such high load, will it manage >> > (routing, etc)? >> > >> > I would appreciate your thoughts. >> > Yossi. >> > >> > >> > _______________________________________________ >> > users mailing list >> > [email protected] >> > http://lists.agavi.org/mailman/listinfo/users >> > >> >> >> >> -- >> >> http://dracoblue.net >> >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.agavi.org/mailman/listinfo/users > > > > _______________________________________________ > users mailing list > [email protected] > http://lists.agavi.org/mailman/listinfo/users > -- http://dracoblue.net _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
