logilogi-list Mailing List for LogiLogi - Software Libre for the Web (Page 3)
Status: Beta
Brought to you by:
wybow
Menu
▾
▴
logilogi-list — Main mailinglist for LogiLogi.
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(6) |
Oct
(1) |
Nov
(72) |
Dec
(28) |
| 2007 |
Jan
(30) |
Feb
(34) |
Mar
(21) |
Apr
(30) |
May
(32) |
Jun
(34) |
Jul
(23) |
Aug
(10) |
Sep
(22) |
Oct
(57) |
Nov
(28) |
Dec
(62) |
| 2008 |
Jan
(5) |
Feb
(57) |
Mar
(59) |
Apr
(105) |
May
(89) |
Jun
(63) |
Jul
(55) |
Aug
(38) |
Sep
(68) |
Oct
(13) |
Nov
(11) |
Dec
(5) |
| 2009 |
Jan
(3) |
Feb
(7) |
Mar
(3) |
Apr
(4) |
May
(10) |
Jun
(8) |
Jul
(6) |
Aug
(2) |
Sep
(5) |
Oct
(1) |
Nov
(2) |
Dec
(20) |
| 2010 |
Jan
(1) |
Feb
(6) |
Mar
(7) |
Apr
(9) |
May
(4) |
Jun
(1) |
Jul
(10) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(2) |
| 2011 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Hornby M. <mar...@li...> - 2009-12-22 10:05:04
|
Le 19/12/2009 19:54, Wybo Wiersma a écrit : > I'm almost finished with my PhD applications, and am now going home > for Christmas (by ferry)... Time in the UK so far has been great, but > quite busy. > > Will be working on making LogiLogi translateable over the coming > week(s), especially in the evenings... > > greetings, > > Wybo > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > LogiLogi-list mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/logilogi-list > Happy Xmas to you too. Hope the next year will bring you happiness and prosperity. I will be happy to help on the french translation. All the best Martine |
|
From: Bhupendra M. <bhu...@gm...> - 2009-12-22 03:54:13
|
Happy Xmas to all of you Cheers On 12/20/09, Wybo Wiersma <ma...@wy...> wrote: > I'm almost finished with my PhD applications, and am now going home > for Christmas (by ferry)... Time in the UK so far has been great, but > quite busy. > > Will be working on making LogiLogi translateable over the coming > week(s), especially in the evenings... > > greetings, > > Wybo > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > LogiLogi-list mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/logilogi-list > |
|
From: Wybo W. <ma...@wy...> - 2009-12-19 18:55:16
|
I'm almost finished with my PhD applications, and am now going home for Christmas (by ferry)... Time in the UK so far has been great, but quite busy. Will be working on making LogiLogi translateable over the coming week(s), especially in the evenings... greetings, Wybo |
|
From: Wybo W. <ma...@wy...> - 2009-12-14 21:18:50
|
> I would like to be admin on our site. There is already one but I do not
> know the password and it is not written in clear in the DB. How could I
> be the admin of the system ?
I've changed the password and e-mailed it to you privately.
It can be done with:
cd /var/www/logilogi/fr/current
sudo su www-data
script/console production (opening the Rails console with the
production db)
u = User.find_by_name('Admin User')
u.password = u.password_confirmation = 'mynewpassword' (setting
both the password and the password_confirmation fields)
u.save
greetings,
Wybo
> Tack
>
> Martine
>
> ------------------------------------------------------------------------------
> Return on Information:
> Google Enterprise Search pays you back
> Get the facts.
> http://p.sf.net/sfu/google-dev2dev
> _______________________________________________
> LogiLogi-list mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/logilogi-list
--
::Student:
- MA in Digital Humanities at King's College London
- 3 BAs 1st cl. hons in Humanities Computing, History and Philosophy
::Secretary of the Members Council of Goodenough College:
- Room 2150, Goodenough College, Mecklenburgh Square, London WC1N 2AB, UK
::Free Software and Open Source Developer:
- http://www.LogiLogi.org, Cumulative, shared commenting, publication and
idea sharing: Philosophy beyond the Book...
|
|
From: hornby <mar...@li...> - 2009-12-14 19:24:59
|
I would like to be admin on our site. There is already one but I do not know the password and it is not written in clear in the DB. How could I be the admin of the system ? Tack Martine |
|
From: Wybo W. <ma...@wy...> - 2009-12-14 19:10:05
|
> That is quick ! Thanks. > > Would you mind reminding me how to start the indexing deamon (I am not > sure that is the right denomination for it)? What I mean is that the > search tags are not working >From your development-copy's trunk run: rake server:daemons:restart But in this case more was going on, as there were 2 deamons running at the same time, which corrupted the index. I did (from my development copy): rake server:daemons:stop then logged into the server and ran ps aux | grep logi killed the remaining daemon supervisor and daemon with sudo kill -KILL <pid of daemon> then re-created the index with cd /var/www/logilogi/fr/current sudo su www-data rake index:redo then started the deamon again rake server:daemons:start Is now working. greetings, Wybo PS: Have to work on a presentation now, and then on PhD applications later this week, so won't be as quick with responses for now... > Martine > > Wybo Wiersma a écrit : > >> When an account is created, the following message is sent : > >> > > > > Thanks for the bug-report. Was a Rails bug, but added a monkey- > > patch for it to LogiLogi so it works now. > > > > (also updated your server) > > > > Wybo > > > > > >> Net::SMTPSyntaxError in UsersController#create > >> > >> 501 <LogiLogi Notifier <no...@lo... <mailto:no...@lo...>>>: "@" or "." expected after "LogiLogi" > >> > >> |RAILS_ROOT: /var/www/logilogi/fr/releases/20091211232027| > >> > >> Application Trace <http://logilogi.lirmm.fr/do/users#> | Framework Trace > >> <http://logilogi.lirmm.fr/do/users#> | Full Trace > >> <http://logilogi.lirmm.fr/do/users#> > >> > > > > ------------------------------------------------------------------------------ > > Return on Information: > > Google Enterprise Search pays you back > > Get the facts. > > http://p.sf.net/sfu/google-dev2dev > > _______________________________________________ > > LogiLogi-list mailing list > > Log...@li... > > https://lists.sourceforge.net/lists/listinfo/logilogi-list > > > ------------------------------------------------------------------------------ > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > _______________________________________________ > LogiLogi-list mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/logilogi-list -- ::Student: - MA in Digital Humanities at King's College London - 3 BAs 1st cl. hons in Humanities Computing, History and Philosophy ::Secretary of the Members Council of Goodenough College: - Room 2150, Goodenough College, Mecklenburgh Square, London WC1N 2AB, UK ::Free Software and Open Source Developer: - http://www.LogiLogi.org, Cumulative, shared commenting, publication and idea sharing: Philosophy beyond the Book... |
|
From: hornby <mar...@li...> - 2009-12-14 18:10:43
|
That is quick ! Thanks. Would you mind reminding me how to start the indexing deamon (I am not sure that is the right denomination for it)? What I mean is that the search tags are not working Martine Wybo Wiersma a écrit : >> When an account is created, the following message is sent : >> > > Thanks for the bug-report. Was a Rails bug, but added a monkey- > patch for it to LogiLogi so it works now. > > (also updated your server) > > Wybo > > >> Net::SMTPSyntaxError in UsersController#create >> >> 501 <LogiLogi Notifier <no...@lo... <mailto:no...@lo...>>>: "@" or "." expected after "LogiLogi" >> >> |RAILS_ROOT: /var/www/logilogi/fr/releases/20091211232027| >> >> Application Trace <http://logilogi.lirmm.fr/do/users#> | Framework Trace >> <http://logilogi.lirmm.fr/do/users#> | Full Trace >> <http://logilogi.lirmm.fr/do/users#> >> > > ------------------------------------------------------------------------------ > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > _______________________________________________ > LogiLogi-list mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/logilogi-list > |
|
From: Wybo W. <ma...@wy...> - 2009-12-14 18:04:16
|
> When an account is created, the following message is sent : Thanks for the bug-report. Was a Rails bug, but added a monkey- patch for it to LogiLogi so it works now. (also updated your server) Wybo > Net::SMTPSyntaxError in UsersController#create > > 501 <LogiLogi Notifier <no...@lo... <mailto:no...@lo...>>>: "@" or "." expected after "LogiLogi" > > |RAILS_ROOT: /var/www/logilogi/fr/releases/20091211232027| > > Application Trace <http://logilogi.lirmm.fr/do/users#> | Framework Trace > <http://logilogi.lirmm.fr/do/users#> | Full Trace > <http://logilogi.lirmm.fr/do/users#> |
|
From: hornby <mar...@li...> - 2009-12-14 17:45:32
|
When an account is created, the following message is sent : Net::SMTPSyntaxError in UsersController#create 501 <LogiLogi Notifier <no...@lo... <mailto:no...@lo...>>>: "@" or "." expected after "LogiLogi" |RAILS_ROOT: /var/www/logilogi/fr/releases/20091211232027| Application Trace <http://logilogi.lirmm.fr/do/users#> | Framework Trace <http://logilogi.lirmm.fr/do/users#> | Full Trace <http://logilogi.lirmm.fr/do/users#> |/usr/lib/ruby/1.8/net/smtp.rb:680:in `check_response' /usr/lib/ruby/1.8/net/smtp.rb:653:in `getok' /usr/lib/ruby/1.8/net/smtp.rb:631:in `mailfrom' /usr/lib/ruby/1.8/net/smtp.rb:544:in `send0' /usr/lib/ruby/1.8/net/smtp.rb:472:in `sendmail' /usr/lib/ruby/gems/1.8/gems/actionmailer-2.3.5/lib/action_mailer/base.rb:684:in `perform_delivery_smtp' /usr/lib/ruby/1.8/net/smtp.rb:379:in `start' /usr/lib/ruby/gems/1.8/gems/actionmailer-2.3.5/lib/action_mailer/base.rb:682:in `perform_delivery_smtp' /usr/lib/ruby/gems/1.8/gems/actionmailer-2.3.5/lib/action_mailer/base.rb:523:in `__send__' /usr/lib/ruby/gems/1.8/gems/actionmailer-2.3.5/lib/action_mailer/base.rb:523:in `deliver!' /usr/lib/ruby/gems/1.8/gems/actionmailer-2.3.5/lib/action_mailer/base.rb:395:in `method_missing' /var/www/logilogi/fr/releases/20091211232027/app/models/user.rb:148:in `deliver_welcome!' /var/www/logilogi/fr/releases/20091211232027/app/controllers/users_controller.rb:54:in `create' /var/www/logilogi/fr/releases/20091211232027/app/controllers/users_controller.rb:52:in `create'| |/usr/lib/ruby/1.8/net/smtp.rb:680:in `check_response' /usr/lib/ruby/1.8/net/smtp.rb:653:in `getok' /usr/lib/ruby/1.8/net/smtp.rb:631:in `mailfrom' /usr/lib/ruby/1.8/net/smtp.rb:544:in `send0' /usr/lib/ruby/1.8/net/smtp.rb:472:in `sendmail' /usr/lib/ruby/gems/1.8/gems/actionmailer-2.3.5/lib/action_mailer/base.rb:684:in `perform_delivery_smtp' /usr/lib/ruby/1.8/net/smtp.rb:379:in `start' /usr/lib/ruby/gems/1.8/gems/actionmailer-2.3.5/lib/action_mailer/base.rb:682:in `perform_delivery_smtp' /usr/lib/ruby/gems/1.8/gems/actionmailer-2.3.5/lib/action_mailer/base.rb:523:in `__send__' /usr/lib/ruby/gems/1.8/gems/actionmailer-2.3.5/lib/action_mailer/base.rb:523:in `deliver!' /usr/lib/ruby/gems/1.8/gems/actionmailer-2.3.5/lib/action_mailer/base.rb:395:in `method_missing' /usr/lib/ruby/gems/1.8/gems/authlogic-oid-1.0.4/lib/authlogic_openid/acts_as_authentic.rb:75:in `save' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/base.rb:1331:in `send' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/base.rb:1331:in `perform_action_without_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/filters.rb:617:in `call_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/filters.rb:610:in `perform_action_without_benchmark' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/core_ext/benchmark.rb:17:in `ms' /usr/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/core_ext/benchmark.rb:10:in `realtime' /usr/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/core_ext/benchmark.rb:17:in `ms' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/rescue.rb:160:in `perform_action_without_flash' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/flash.rb:146:in `perform_action' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/base.rb:532:in `send' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/base.rb:532:in `process_without_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/filters.rb:606:in `process' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/base.rb:391:in `process' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/base.rb:386:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/routing/route_set.rb:437:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/dispatcher.rb:87:in `dispatch' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/dispatcher.rb:121:in `_call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/dispatcher.rb:130:in `build_middleware_stack' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/string_coercion.rb:25:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/string_coercion.rb:25:in `call' /usr/lib/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/head.rb:9:in `call' /usr/lib/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/methodoverride.rb:24:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/params_parser.rb:15:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/session/abstract_store.rb:122:in `call' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/active_record/query_cache.rb:29:in `call' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in `cache' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/active_record/query_cache.rb:9:in `cache' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/active_record/query_cache.rb:28:in `call' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/active_record/connection_adapters/abstract/connection_pool.rb:361:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/failsafe.rb:26:in `call' /usr/lib/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/lock.rb:11:in `call' /usr/lib/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/lock.rb:11:in `synchronize' /usr/lib/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/lock.rb:11:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/dispatcher.rb:106:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/cgi_process.rb:44:in `dispatch_cgi' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/dispatcher.rb:101:in `dispatch_cgi' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/dispatcher.rb:27:in `dispatch' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/rails.rb:76:in `process' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/rails.rb:74:in `synchronize' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/rails.rb:74:in `process' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:159:in `process_client' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:158:in `each' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:158:in `process_client' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `initialize' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `new' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in `initialize' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in `new' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/configurator.rb:282:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/configurator.rb:281:in `each' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/configurator.rb:281:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:128:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/command.rb:212:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:281| |/usr/lib/ruby/1.8/net/smtp.rb:680:in `check_response' /usr/lib/ruby/1.8/net/smtp.rb:653:in `getok' /usr/lib/ruby/1.8/net/smtp.rb:631:in `mailfrom' /usr/lib/ruby/1.8/net/smtp.rb:544:in `send0' /usr/lib/ruby/1.8/net/smtp.rb:472:in `sendmail' /usr/lib/ruby/gems/1.8/gems/actionmailer-2.3.5/lib/action_mailer/base.rb:684:in `perform_delivery_smtp' /usr/lib/ruby/1.8/net/smtp.rb:379:in `start' /usr/lib/ruby/gems/1.8/gems/actionmailer-2.3.5/lib/action_mailer/base.rb:682:in `perform_delivery_smtp' /usr/lib/ruby/gems/1.8/gems/actionmailer-2.3.5/lib/action_mailer/base.rb:523:in `__send__' /usr/lib/ruby/gems/1.8/gems/actionmailer-2.3.5/lib/action_mailer/base.rb:523:in `deliver!' /usr/lib/ruby/gems/1.8/gems/actionmailer-2.3.5/lib/action_mailer/base.rb:395:in `method_missing' /var/www/logilogi/fr/releases/20091211232027/app/models/user.rb:148:in `deliver_welcome!' /var/www/logilogi/fr/releases/20091211232027/app/controllers/users_controller.rb:54:in `create' /usr/lib/ruby/gems/1.8/gems/authlogic-oid-1.0.4/lib/authlogic_openid/acts_as_authentic.rb:75:in `save' /var/www/logilogi/fr/releases/20091211232027/app/controllers/users_controller.rb:52:in `create' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/base.rb:1331:in `send' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/base.rb:1331:in `perform_action_without_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/filters.rb:617:in `call_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/filters.rb:610:in `perform_action_without_benchmark' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/core_ext/benchmark.rb:17:in `ms' /usr/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/core_ext/benchmark.rb:10:in `realtime' /usr/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/core_ext/benchmark.rb:17:in `ms' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/rescue.rb:160:in `perform_action_without_flash' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/flash.rb:146:in `perform_action' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/base.rb:532:in `send' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/base.rb:532:in `process_without_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/filters.rb:606:in `process' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/base.rb:391:in `process' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/base.rb:386:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/routing/route_set.rb:437:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/dispatcher.rb:87:in `dispatch' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/dispatcher.rb:121:in `_call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/dispatcher.rb:130:in `build_middleware_stack' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/string_coercion.rb:25:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/string_coercion.rb:25:in `call' /usr/lib/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/head.rb:9:in `call' /usr/lib/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/methodoverride.rb:24:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/params_parser.rb:15:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/session/abstract_store.rb:122:in `call' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/active_record/query_cache.rb:29:in `call' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in `cache' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/active_record/query_cache.rb:9:in `cache' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/active_record/query_cache.rb:28:in `call' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/active_record/connection_adapters/abstract/connection_pool.rb:361:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/failsafe.rb:26:in `call' /usr/lib/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/lock.rb:11:in `call' /usr/lib/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/lock.rb:11:in `synchronize' /usr/lib/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/lock.rb:11:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/dispatcher.rb:106:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/cgi_process.rb:44:in `dispatch_cgi' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/dispatcher.rb:101:in `dispatch_cgi' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/dispatcher.rb:27:in `dispatch' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/rails.rb:76:in `process' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/rails.rb:74:in `synchronize' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/rails.rb:74:in `process' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:159:in `process_client' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:158:in `each' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:158:in `process_client' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `initialize' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `new' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in `initialize' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in `new' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/configurator.rb:282:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/configurator.rb:281:in `each' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/configurator.rb:281:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:128:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/command.rb:212:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:281 /usr/bin/mongrel_rails:19:in `load' /usr/bin/mongrel_rails:19| Request *Parameters*: {"user"=>{"name"=>"Christopher Dartnell", "password_confirmation"=>xxxx "password"=>xxxx "email"=>"chr...@gm... <mailto:chr...@gm...>"}} Show session dump <http://logilogi.lirmm.fr/do/users#> --- Response *Headers*: {"Content-Type"=>"", "Cache-Control"=>"no-cache", "Set-Cookie"=>["user_credentials=9449eef6ec81cc741cdb2144482d0b794b07800607275b017792c24280da1e4d1158e419659b4dbab82a7f3f1555c2d150c201bdc7d7a05c74d39f70208afbc3%3A%3A; path=/", "user_credentials=9449eef6ec81cc741cdb2144482d0b794b07800607275b017792c24280da1e4d1158e419659b4dbab82a7f3f1555c2d150c201bdc7d7a05c74d39f70208afbc3%3A%3A5; path=/"]} |
|
From: Wybo W. <ma...@wy...> - 2009-12-11 23:24:00
|
I went in and updated your production-server for you. As it was not properly updated. See below. > > Sorry, but will come back to this on saturday evening (will try > > to reproduce the bug then). > > > > I have to finish an essay before saturday morning. > > > > Hope it is not urgent (how will it be used ?), > > Jean wants to use LogiLogi to write a research proposal. The dead line > is friday 18th. So Jean would like different researchers to take part in > a debate in order to have a sound collaborative proposal. > At the moment the last update of LL has quite a few bugs. On top of > this, I am encountering a server problem: 404. I do not know what > causes it. Because of how bad the 404 and the other bugs sounded I decided to look at it now, delaying the essay. However I was/am unable to reproduce any of the bugs you mentioned in your last few posts, except for a small javascript error in magick_corners causing a 'this.runs[] is empty' error in IE only (fixed that). And then I looked again at the .pdf you sent me yesterday, and saw that whatever it is, it is not a screenshot the latest version of LogiLogi. And most likely of a version that is a few weeks old, as I changed remarks to annotations weeks ago. Compare the insert tabs in the .pdf with: http://en.logilogi.org/Logi_Logi=Admin_User_4/do/logi_inserts/new Thus it must be that more went wrong with the than you detected. (Also note that in order to update your production environment, and not just your local development-copy you need to run rake server:production:deploy_full, as described in the instruction- e-mail I sent to you for this on the 19th of September). I have now done this from a local copy configured to update the logilogi.lirmm.fr server. When updating (which confirmed that it was still an old version) I also noted that the newest rails gem was not yet installed, so I don't know what you did when I asked you to update them, but I hope it works now. (can't access the VPN in any easy way, so I leave it to you to check if the UI is up and all fine now) Wybo > Have a nice weekend > Martine > > Wybo > > > > > > > > ------------------------------------------------------------------------------ > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > _______________________________________________ > LogiLogi-list mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/logilogi-list -- ::Student: - MA in Digital Humanities at King's College London - 3 BAs 1st cl. hons in Humanities Computing, History and Philosophy ::Secretary of the Members Council of Goodenough College: - Room 2150, Goodenough College, Mecklenburgh Square, London WC1N 2AB, UK ::Free Software and Open Source Developer: - http://www.LogiLogi.org, Cumulative, shared commenting, publication and idea sharing: Philosophy beyond the Book... |
|
From: Bruno S. <bs...@gm...> - 2009-12-11 13:15:14
|
On Wed, Dec 9, 2009 at 2:23 PM, Wybo Wiersma <ma...@wy...> wrote: > > I'm really happy about this, as after all these months and years of > development it is great to be able to deploy LogiLogi for an existing > community! > Great news indeed! Congratulations Wybo and all! -- Bruno |
|
From: hornby <mar...@li...> - 2009-12-11 13:01:06
|
Sorry, but will come back to this on saturday evening (will try > to reproduce the bug then). > > I have to finish an essay before saturday morning. > > Hope it is not urgent (how will it be used ?), > Jean wants to use LogiLogi to write a research proposal. The dead line is friday 18th. So Jean would like different researchers to take part in a debate in order to have a sound collaborative proposal. At the moment the last update of LL has quite a few bugs. On top of this, I am encountering a server problem: 404. I do not know what causes it. Have a nice weekend Martine > Wybo > > > |
|
From: Wybo W. <ma...@wy...> - 2009-12-11 00:06:10
|
Sorry, but will come back to this on saturday evening (will try to reproduce the bug then). I have to finish an essay before saturday morning. Hope it is not urgent (how will it be used ?), Wybo > Hi Wybo, > > Wybo Wiersma a écrit : >>> See attached pdf file describing the problem >>> >> >> The 'Xapian database not opened' error is given because the xapian >> index is not initialized. >> >> You most likely started with a fresh trunk, or removed files inside >> db/search_index, and did not run db:initialize again after this ? >> >> rake index:create should fix your problem. >> > I have just done this but bugs remain. For example, I cannot edit an > existing logi. > It refuses to add an valid external link. Or the GUI looks funny. See > attached pdf > > bye > > Martine >> I updated the docs at: >> http://www.logilogi.org/pub/doc/app/ >> to contain a FAQ item on it, and to better explain what db:initialize >> exactly does. >> >> (run another svn update to get the newest docs in doc/README_FOR_APP) >> >> I hope everything is working fine now, but if it doesn't further >> questions are welcome, and please let us know about bugs. >> >> greetings, >> >> Wybo >> >> ------------------------------------------------------------------------------ >> Return on Information: >> Google Enterprise Search pays you back >> Get the facts. >> http://p.sf.net/sfu/google-dev2dev >> _______________________________________________ >> LogiLogi-list mailing list >> Log...@li... >> https://lists.sourceforge.net/lists/listinfo/logilogi-list >> > ------------------------------------------------------------------------------ > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > _______________________________________________ > LogiLogi-list mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/logilogi-list -- ::Student: - MA in Digital Humanities at King's College London - 3 BAs 1st cl. hons in Humanities Computing, History and Philosophy ::Secretary of the Members Council of Goodenough College: - Room 2150, Goodenough College, Mecklenburgh Square, London WC1N 2AB, UK ::Free Software and Open Source Developer: - http://www.LogiLogi.org, Cumulative, shared commenting, publication and idea sharing: Philosophy beyond the Book... |
|
From: hornby <mar...@li...> - 2009-12-10 15:55:54
|
Hi Wybo, Wybo Wiersma a écrit : >> See attached pdf file describing the problem >> > > The 'Xapian database not opened' error is given because the xapian > index is not initialized. > > You most likely started with a fresh trunk, or removed files inside > db/search_index, and did not run db:initialize again after this ? > > rake index:create should fix your problem. > I have just done this but bugs remain. For example, I cannot edit an existing logi. It refuses to add an valid external link. Or the GUI looks funny. See attached pdf bye Martine > I updated the docs at: > http://www.logilogi.org/pub/doc/app/ > to contain a FAQ item on it, and to better explain what db:initialize > exactly does. > > (run another svn update to get the newest docs in doc/README_FOR_APP) > > I hope everything is working fine now, but if it doesn't further > questions are welcome, and please let us know about bugs. > > greetings, > > Wybo > > ------------------------------------------------------------------------------ > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > _______________________________________________ > LogiLogi-list mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/logilogi-list > |
|
From: Wybo W. <ma...@wy...> - 2009-12-09 17:24:16
|
First of all, I've received good news last Monday, and that is that it was confirmed that LogiLogi will be used by the German Journal Der Blaue Reiter (http://www.derblauereiter.de/). It will be a one-year trial, during which they will be allowing their readers to discuss articles on LogiLogi. We will be hosting and maintaining it for them under dbr.logilogi.org, and they will be having their own header, and css-file. I'm really happy about this, as after all these months and years of development it is great to be able to deploy LogiLogi for an existing community! --- Over the last few weeks I have applied a few minor updates to LogiLogi. The main thing being (initially suggested by Claire at the LIRMM) that annotations and remarks are now separate things, with separate names, making their function much more intuitive to users. In addition a sensible tab-order was implemented for most forms and buttons (allowing one to jump from field to field by pressing tab). Should work in Firefox at least. Besides this LogiLogi is now Rails 2.3.5 ready. You will need to run sudo gem update to get the latest rails version after updating. greetings, Wybo |
|
From: Wybo W. <ma...@wy...> - 2009-12-09 16:24:34
|
> See attached pdf file describing the problem The 'Xapian database not opened' error is given because the xapian index is not initialized. You most likely started with a fresh trunk, or removed files inside db/search_index, and did not run db:initialize again after this ? rake index:create should fix your problem. I updated the docs at: http://www.logilogi.org/pub/doc/app/ to contain a FAQ item on it, and to better explain what db:initialize exactly does. (run another svn update to get the newest docs in doc/README_FOR_APP) I hope everything is working fine now, but if it doesn't further questions are welcome, and please let us know about bugs. greetings, Wybo |
|
From: hornby <mar...@li...> - 2009-12-09 14:10:06
|
See attached pdf file describing the problem |
|
From: hornby <mar...@li...> - 2009-12-09 14:09:31
|
See attached pdf file describing the problem |
|
From: Wybo W. <wy...@lo...> - 2009-12-08 12:47:43
|
I have posted this response to the LogiLogi list also, as it's better to do these issues through the mailing-list, because then other people that might run into the same thing, they can get help from it. Would you please join the list if not already on there and post questions to there: http://lists.sourceforge.net/mailman/listinfo/logilogi-list > Hi Wybo, > > If you have a little more time, a clue would be most appreciated. I looked into it, but > 1) I have changed the config.rb to match the template that goes with the > latest update, as instructed (in fact as there is a template per > version, I check them all and they are not that different) There should be only one. > 2) I had svn update > 3) I drop the db rake db:initialize also drops the database. > 4) I then ran > rake db:initialize RAILS_ENV=production > > 5) I counted the number of users (=2), the number of logis (=6) > So this shows that the db is initialise with basic information It is then indeed. > 6) when I go to htpp://logilogi.lirmm.fr > I get a dump (see attached pdf) This error is very strange, as it supposes there is no context set. > 7) I tryed to restart the server by doing rake server:daemons:restart > but it failed. So maybe the new config.rb has not been taken into account. > > root@logilogi:/var/www/logilogi/fr/current/lib/tasks# rake > server:daemons:restart > (in /var/www/logilogi/fr/releases/20091021101933) > cap global:daemons:restart -S stage=production > rake aborted! > Command failed with status (127): [cap global:daemons:restart -S > stage=produc...] > > (See full trace by running task with --trace) > root@logilogi:/var/www/logilogi/fr/current/lib/tasks# cd .. > root@logilogi:/var/www/logilogi/fr/current/lib# cd .. > root@logilogi:/var/www/logilogi/fr/current# svn update > svn: Expected 'log' to be a directory but found a file > > 8)I can see that there is a synchronisation problem but I do not know > what version to use to avoid it. If you want SVN to get the last version for a file, the most sure way to know you have the latest is deleting all versions, and then do svn update again. This will restore the file using the newest version. But it should be noted that getting synchronisation problems with SVN should not happen unless someone has been editing/updating files on the server, and it might be a good idea to find out why this was done, and whether you want to maintain or commit the changes. So I suggest you do this, then try again, and let me know how it went. As it is working here. > Any clues ? Not beyond this, but I'm happy to help. Wybo > Martine -- ::Student: - MA in Digital Humanities at King's College London - 3 BAs 1st cl. hons in Humanities Computing, History and Philosophy ::Secretary of the Members Council of Goodenough College: - Room 2150, Goodenough College, Mecklenburgh Square, London WC1N 2AB, UK ::Free Software and Open Source Developer: - http://www.LogiLogi.org, Cumulative, shared commenting, publication and idea sharing: Philosophy beyond the Book... |
|
From: Bruno S. <bs...@gm...> - 2009-11-03 03:20:21
|
Wybo, I've been away/busy, just read this mail very quickly. I saw LL improvements, it's amazing, you did it!!! reading paths, congratulations, LL is growing mature!!!! again, congratulations!!! greetings! On Sun, Nov 1, 2009 at 11:46 PM, Wybo Wiersma <ma...@wy...> wrote: > > Move to London and thesis on LogiLogi: > > http://foundation.logilogi.org/2009/11/2/logilogi-in-london-king-s-thesis > > (you can try out the read-paths on the thesis) > > greetings, > > Wybo > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > LogiLogi-list mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/logilogi-list -- Bruno |
|
From: Wybo W. <ma...@wy...> - 2009-11-02 02:13:02
|
Move to London and thesis on LogiLogi: http://foundation.logilogi.org/2009/11/2/logilogi-in-london-king-s-thesis (you can try out the read-paths on the thesis) greetings, Wybo |
|
From: Wybo W. <wy...@lo...> - 2009-10-26 23:28:08
|
I've written a proposal for a poster at the DH 2010 conference today. In short it is about trying to get a critical mass of users on LogiLogi. In other words; finally bringing LogiLogi to life :-) You can read it here: http://logilogi.svn.sourceforge.net/viewvc/logilogi/docs/papers/DH2010/paper.pdf Besides I have been quite busy over the last few weeks here in London. But in some evening-hours I managed to get the alert-system working; so people are notified if a remark or a vote is given on their logi the previous day. In addition I added a first implementation of read-paths. So people can read chains of logis, such as this one: http://en.logilogi.org/Logi_Logi/Beyond_Paper/Introduction=Wybo_Wiersma_84 Will write a blog-post on it some time soon, Wybo |
|
From: Wybo W. <wy...@lo...> - 2009-09-08 21:40:31
|
> Hi Wybo and all, > > On Tue, Sep 8, 2009 at 4:52 AM, Wybo Wiersma<wyb...@ya...> wrote: > > I'm posting it to the list, so Bruno can also read along if he might have time. > > Thanks Wybo! :-) > > We have been bug-fixing so far (as of yesterday edge.logilogi.org > > should be practically bug-free :-), and they have hired a local > > professional designer (for 2 days or so) to look at the design of > > the UI of LL. She was mostly positive, though she gave some good > > remarks for improvement and simplification. In all we (& esp. > > Bruno) did a very good design last year! > > We actually did got the new UI out and running back then... those > where good old LogiLogi deving days. :-) About the designer; they already had hired her before I knew they wanted to hire anyone, so I am sorry for not being able to send them to you. > It's very nice that new people will be working on LL and the UI, it's > the beauty of Free Software! Indeed, though we the old guys can also still do our thing :-) & they say they will be working with LL at the LIRMM lab in various projects for the coming 2 years, at least. > > Today I will be working on the alerts-system (loglog), so users > > receive an e-mail every day (+ RSS feed) which shows what replies > > and remarks their logis got, and what new logis were created. > > Thanks for forwarding about this to the list. Np. Miguel, did you find the description from my previous e-mail of the account-generation process clear enough ? The idea is that user- objects are created & stored with names & email-addresses from a yaml file. Welcome-e-mails are then sent out automatically (is already implemented for normal users, so is easy to do). About the Chinese portraits; someone here has already created the basic files and the db-layout (ChinesePortrait class, and an Answers class, one instance for each question). When showing the user's answers in the user's homepage, the idea is that the answers are not really inside the logi, but just shown inside the same div, so the user gets the impression they are. I will be in the IRC all day tomorrow (not in the evening; we have a goodbye-meeting then in the city), working on the alerts system, greetings, Wybo > Greetings all! > -- > Bruno |
|
From: Bruno S. <bs...@gm...> - 2009-09-08 19:15:59
|
Hi Wybo and alll, On Tue, Sep 8, 2009 at 4:52 AM, Wybo Wiersma<wyb...@ya...> wrote: > I'm posting it to the list, so Bruno can also read along if he might have time. > Thanks Wybo! > @Miguel: Sorry & great you can help! The LIRMM lab is a really fascinating place, and Jean Sallatin, the lab-director: Michele Robert, and many others are enthausiastic about LogiLogi. > > They want to use LogiLogi as of the 1st of October to discuss the mission-statement and the future direction that the lab should take. About 350 people work and study in the lab (180 staff, and the rest PhD's and masters) so it will be quite a group. > So great! > We have been bug-fixing so far (as of yesterday edge.logilogi.org should be practically bug-free :-), and they have hired a local professional designer (for 2 days or so) to look at the design of the UI of LL. She was mostly positive, though she gave some good remarks for improvement and simplification. In all we (& esp. Bruno) did a very good design last year! > We actually did got the new UI out and running back then... those where good old LogiLogi deving days. It's very nice that new people will be working on LL and the UI, it's the beauty of Free Software! > Today I will be working on the alerts-system (loglog), so users receive an e-mail every day (+ RSS feed) which shows what replies and remarks their logis got, and what new logis were created. Thanks for forwarding about this to the list. Greetings all! -- Bruno |
|
From: Wybo W. <wyb...@ya...> - 2009-09-08 07:52:29
|
I'm posting it to the list, so Bruno can also read along if he might have time. > As I told you before I was gone, I was in Spain > for a long weekend and I didn't have internet. I'm > back in Grenoble now and I would like to help out. I would > have to share my time between work and LogiLogi, I work > until 6 pm. so I could help after work. @Miguel: Sorry & great you can help! The LIRMM lab is a really fascinating place, and Jean Sallatin, the lab-director: Michele Robert, and many others are enthausiastic about LogiLogi. They want to use LogiLogi as of the 1st of October to discuss the mission-statement and the future direction that the lab should take. About 350 people work and study in the lab (180 staff, and the rest PhD's and masters) so it will be quite a group. We have been bug-fixing so far (as of yesterday edge.logilogi.org should be practically bug-free :-), and they have hired a local professional designer (for 2 days or so) to look at the design of the UI of LL. She was mostly positive, though she gave some good remarks for improvement and simplification. In all we (& esp. Bruno) did a very good design last year! Today I will be working on the alerts-system (loglog), so users receive an e-mail every day (+ RSS feed) which shows what replies and remarks their logis got, and what new logis were created. Something else they need is a rake-task to automatically give everyone in the lab an account. This can be done by simply reading in a yaml-file (see lib/daemons/logilogi_ctl for an example of reading a yaml) containing all the e-mail addresses + names of the lab-employees, and then creating users with those details (+ random passwords). This would be something with which you could help us. Also because the deadline is really tight, and I will already be going home on the 10th, and then on to England. It would be very good too if you were able to help them out too during the project, as I may be very busy the coming weeks when my masters starts & to settle in London & might not always have time & in the lab there's no one yet who has good XP with Ruby & Rails. Could you also e-mail me your mobile phone-nr, so we (& Jean Sallatin) can call you to discuss things ? greetings, Wybo PS: The lab might be a good place to apply to do a PhD next year (they are funded) if you want to pursue one & work on LL or similar projects. > I hope I can be useful > Miguel > > On Fri, Sep 4, 2009 at 11:46 AM, > Wybo Wiersma <wyb...@ya...> > wrote: > > Hi, I > just introduced you to them, and they wonder if you have > time this week to work on LL. Don't know yet what they |
7 messages has been excluded from this view by a project administrator.