JFYI
----- Forwarded message from Richard Kilmer <rich(a)infoether.com> -----
Date: Tue, 27 Oct 2009 09:27:31 +0900
From: Richard Kilmer <rich(a)infoether.com>
To: Ruby Talk <ruby-talk(a)ruby-lang.org>,
Ruby Core <ruby-core(a)ruby-lang.org>
Reply-To: ruby-core(a)ruby-lang.org
Subject: [ruby-core:26344] RubyForge and RubyGems and GemCutter...
Hi all -
This has been announced in various forums, but we should have sent a
message here in the initial flurry. To summarize, some major gem
indexes are going to be consolidated - GemCutter and
gems.rubyforge.org will move to rubygems.org and form one massive gem
index. This index will be fronted by Nick Quaranto's excellent
GemCutter rails app. This app will be running on Ruby Central's
infrastructure at Rackspace.
The entire announcement, more details, and a comment thread with some
discussions here:
http://update.gemcutter.org/2009/10/26/transition.html
As part of this transition, RubyForge is going to be slowly stood
down. It won't simply be turned off, of course; we could see it
staying in read-only mode for quite a while. But that's where things
are headed. The community hub functions of RubyForge will not go
away. Community features that RubyForge uniquely provides (or should
provide) will be added to the source base of the app that GemCutter
started with and will be maintained on github.
This is a change; but it's one that we at Ruby Central feel is
important. We want to provide the community with what it needs. With
services that Github, the new SourceForge and Google Code provide we
feel that source management, mailing lists and bug tracking are being
better provided by others. We want to focus on community features.
We will be developing those quickly and that will all hub at
RubyGems.org.
Yours,
Rich Kilmer
Ruby Central
----- End forwarded message -----
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-ruby+help(a)opensuse.org
Hi,
Here is my summary of my documentation tour experimenting.
1) I improve readme of rest-service. If you find that there is missing some
essential information, please add it.
2) I test few tools to generate doc and here is result:
a) classic rdoc - http://w3.suse.de/~jreidinger/webservice
It is mature and working documentation tool without problems, but generated
pages is not nice and user-friendly.
b) yard - http://w3.suse.de/~jreidinger/webservice-yard/
Contain some advance features and is compatible with rdoc. I found problems
if generated for whole git (as you can see it is not finded any
README_FOR_APP). Also it doesn't generate links which is in rest-service
README_FOR_APP. I try contact authors.
c) new rdoc - http://w3.suse.de/~jreidinger/webservice-nrdoc/
New version contains better UI and also few good features like quick search,
but it looks like some items is not showed (like just few files, few classes).
Search functionality is nice. Clickable sources is also quite good.
I welcome your opinions which one we should use for our generated
documentation. new rdoc and yard is not in distribution, so it should be add
if we use it.
--
Josef Reidinger
YaST team
maintainer of perl-Bootloader, YaST2-Repair, webyast modules language and time
--
To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-ruby+help(a)opensuse.org
Here's a nice tutorial and link collection about Ruby metaprogramming:
http://ruby-metaprogramming.heroku.com/
Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-ruby+help(a)opensuse.org
This book looks very promising, esp. with the co-authors Martin Fowler
and Kent Beck. Having read Martin Fowlers "Refactoring" book, I can
almost blindly recommend this Ruby Edition:
http://www.pearsonhighered.com/educator/product/Refactoring-Ruby-Edition/97…
Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-ruby+help(a)opensuse.org
This looks useful for browser-based tests
http://bddcasts.com/series/tools/episodes/using-selenium-with-webrat-and-cu…
Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-ruby+help(a)opensuse.org
Hi,
I watched quite intersting Rails video last week
(http://goruco2009.confreaks.com/30-may-2009-14-45-into-the-heart-of-darknes…),
here are the most interesting suggestions I remember:
1) Know APIs - it is very important to know the standard Ruby library and Rails
enhancements to avoid reinventing wheel in your code and write the code
efficiently.
See http://ruby-doc.org/corehttp://ruby-doc.org/stdlibhttp://api.rubyonrails.org
2) Learn common Ruby constructs like
value ||= 1234 (instead of: value = 1234 if value.nil?)
if value ... (instead of: if not value.nil?)
3) Define a common coding style and document it, ensure that new team members read
it and are familiar with it. Document every decision you make.
4) Use tools like 'reek' to check the quality of the code
5) Write useful tests (do not test components outside your application)
6) Use a build server (like Integrity or Hudson)
The video contains more tips, it's worth of seeing.
--
Best Regards
Ladislav Slezák
Yast Developer
------------------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz
Lihovarská 1060/12 tel: +420 284 028 960
190 00 Prague 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz/
--
To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-ruby+help(a)opensuse.org
I just got the question of what does something like this means:
some_method(*foo)
This is the splat or expand operator (not a real operator), so if foo is an
array, every element becomes an argument
So some_method(*[1,2,3]) is equivalent to some_method(1,2,3)
Or you can for example create an array from an element and another array:
[1, *[2,3,4]] is equivalent to [1,2,3,4]
def some_method(arg1, *args)
end
is used in parameters to implement variable number of arguments. Ruby matches
normal parameters, then parameters with defaults and the rest goes to the
array argument.
If you call some_method(1,2,3,4) -> arg1=1 args=[2,3,4]
You can read about this in Ruby Programming Language, section 6.4.3
http://books.google.de/books?id=jcUbTcr5XWwC&pg=PA187&lpg=PA187&dq=ruby+arr…
Duncan
--
To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-ruby+help(a)opensuse.org
Some gems put the ext/ source directory inside the gem, causing 2 types of
warning/errors:
- the source .c files get inside the gem, causing rpmlint to complain
- sometimes the library gets duplicated in ext and lib
/usr/lib64/ruby/gems/1.8/gems/nokogiri-1.3.3/lib/nokogiri/nokogiri.so
/usr/lib64/ruby/gems/1.8/gems/nokogiri-1.3.3/ext/nokogiri/nokogiri.so
because it is build in one and installed in the other. The ext/ one is useless
and ignored, but makes the buildid extractor dizzy when creating debuginfo
packages.
As all rpm gems contain:
%gem_install %{S:0}
%gem_cleanup
Shouldn't %gem_cleanup do rm -rf
%{buildroot}/%{_libdir}/ruby/gems/%{rb_ver}/gems/%{mod_name}-%{version}/ext ?
(I am doing this in a couple of gems already)
--
Duncan Mac-Vicar P. - Engineering Manager, YaST
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
--
To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-ruby+help(a)opensuse.org
Hi,
I just have sent a report about Rails videos via email. What about a summary wiki
page? With short description and rating for each video or blog article?
I mean sending an email is OK, but it's lost in time, if you have spare time and you
would like to watch a video or read a blog it would be nice just to look at a wiki
page and select one which is rated well and is relevant to you or looks interesting
to you.
What do you think about it?
--
Best Regards
Ladislav Slezák
Yast Developer
------------------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz
Lihovarská 1060/12 tel: +420 284 028 960
190 00 Prague 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz/
--
To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-ruby+help(a)opensuse.org
I just have watched "Into the Heart of Darkness: Rails Anti-Patterns" Rails video:
Anti-patterns are wrong solutions which people do again and again when solving a
common problem.
This video describes how to avoid anti-patterns in Rails - study standard libraries
in Ruby and Rails, do code review in team, discuss/set common rules and document
them, use metrics to check the code (reek or metric_fu), use a build server, don't
write useless tests...
A must-see video, describes how to avoid common problems in Rails.
--
Best Regards
Ladislav Slezák
Yast Developer
------------------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz
Lihovarská 1060/12 tel: +420 284 028 960
190 00 Prague 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz/
--
To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-ruby+help(a)opensuse.org