Hello
I am looking for some AOP Stuff in Ruby.
aspectr seems not to be alive anymore.
are there any other frameworks for Ruby and AOP ??
I also found
http://www.rubygarden.org/ruby?AspectOrientedRuby
bis this is only a discussion about the future AOP features of Ruby 2.
thanks in advance.
regards
markus
Markus Jais wrote:
Hello
I am looking for some AOP Stuff in Ruby.
aspectr seems not to be alive anymore.
AspectR was more of a hack to try it out; it’s very small anyone can
probably pick it up and adapt to their needs if you want.
Regards,
Robert Feldt
ObjectTeams is an ambitious implementation of (a richer-than-usual model of)
aspects.
“Markus Jais” markusjais@yahoo.de wrote in message
news:c445vf$2dk962$1@ID-75083.news.uni-berlin.de…
Hello
I am looking for some AOP Stuff in Ruby.
aspectr seems not to be alive anymore.are there any other frameworks for Ruby and AOP ??
I also found
http://www.rubygarden.org/ruby?AspectOrientedRubybis this is only a discussion about the future AOP features of Ruby 2.
thanks in advance.
regards
markus
On Sun, 28 Mar 2004 01:36:10 +0900, Robert Feldt
feldt@ce.chalmers.se wrote (more or less):
Markus Jais wrote:
I am looking for some AOP Stuff in Ruby.
aspectr seems not to be alive anymore.AspectR was more of a hack to try it out; it’s very small anyone can
probably pick it up and adapt to their needs if you want.
RAA & RubyForge initiatives going dormant is not uncommon.
Do either of these have facilities for ‘dormancy’ checking, and
automatic advertising for new hands at the helm of a given project?
(Sometimes when someone does stop working on a one-person project,
they just don’t go back to it, rather than going back and announcing
that they won’t be working on it further.
Perhaps the sites could send an e-mail to the nominal project manager
after a period of dormancy*, and if they hear nothing back, could put
up an ad saying ‘new PM wanted for this project’?
Is this already in place? If not, what do folk think of putting it in
place?
Cheers,
Euan
Gawnsoft: http://www.gawnsoft.co.sr
Symbian/Epoc wiki: http://html.dnsalias.net:1122
Smalltalk links (harvested from comp.lang.smalltalk) http://html.dnsalias.net/gawnsoft/smalltalk
RAA & RubyForge initiatives going dormant is not uncommon.
Do either of these have facilities for ‘dormancy’ checking, and
automatic advertising for new hands at the helm of a given project?
RubyForge doesn’t at the moment.
Perhaps the sites could send an e-mail to the nominal project manager
after a period of dormancy*, and if they hear nothing back, could put
up an ad saying ‘new PM wanted for this project’?
- and this could be defined by the PM, up to a maximum of, say, 9
months.
The tricky part might be defining what “dormant” means - no commits? No
downloads?
I think the way they do this on SourceForge is that if someone wants to
take over an apparently dormant project and the author is not
responding, they send a note to the site admins and get it sorted out.
This hasn’t come up yet on RubyForge, but that’s probably how it’d be
handled - someone sends us a note, we post to ruby-talk, no objections
for a couple days, project changes hands. Something like that.
Yours,
Tom
On Sun, 2004-03-28 at 06:04, Gawnsoft wrote:
Gawnsoft xlucid@users.sourceforge.remove.this.antispam.net wrote in message news:dtbd60ttumtsrb3p2nmadnr3026i902g5g@4ax.com…
RAA & RubyForge initiatives going dormant is not uncommon.
Do either of these have facilities for ‘dormancy’ checking, and
automatic advertising for new hands at the helm of a given project?
…
Perhaps the sites could send an e-mail to the nominal project manager
after a period of dormancy*, and if they hear nothing back, could put
up an ad saying ‘new PM wanted for this project’?
…
Is this already in place? If not, what do folk think of putting it in
place?
No offense, but I think it is a pretty awful idea. Under what
circumstances would mutiny be a better choice than forking? I would
generally rather see projects removed than usurped.
[snip]
Perhaps the sites could send an e-mail to the nominal project manager
after a period of dormancy*, and if they hear nothing back, could put
up an ad saying ‘new PM wanted for this project’?
- and this could be defined by the PM, up to a maximum of, say, 9
months.The tricky part might be defining what “dormant” means - no commits? No
downloads?
Maybe one could calculate a ‘dormant’ value, so that visitors easily
can distinguish alive and kicking projects from the dead ones:
How could such index be calculated?
1=dead
…
5=healthy
A small testsuite
ruby test_dormant.rb
Loaded suite TestDormant
Started
…
Finished in 0.001374 seconds.
1 tests, 1 assertions, 0 failures, 0 errors
expand -t2 test_dormant.rb
require ‘test/unit’
class TestDormant < Test::Unit::TestCase
def calc(days_since_last_commit, days_since_last_release)
1
end
def test_healty1
assert_equal(true, true)
end
end
require ‘test/unit/ui/console/testrunner’
Test::Unit::UI::Console::TestRunner.run(TestDormant)
ok… just realized that this isn’t easy.
On Wed, 31 Mar 2004 08:17:26 +0900, Tom Copeland wrote:
On Sun, 2004-03-28 at 06:04, Gawnsoft wrote:
–
Simon Strandgaard
On 30 Mar 2004 22:00:02 -0800, hatespyware@yahoo.com (anon luker)
wrote (more or less):
Under what
circumstances would mutiny be a better choice than forking? I would
generally rather see projects removed than usurped.
Most circumstances, imo.
Teh thing about libraries is that they become known due to reputation,
which tends to spread through both w.o.m. and personal experience.
Both of these can have significant latencies inherent in them.
(Again imo) Ruby does best when the community gathers around canonical
libraries for given purposes.
Surely that’s better than having a given purpose spawn a dozen equally
feature-incomplete, dormant libraries.
Cheers,
Euan
Gawnsoft: http://www.gawnsoft.co.sr
Symbian/Epoc wiki: http://html.dnsalias.net:1122
Smalltalk links (harvested from comp.lang.smalltalk) http://html.dnsalias.net/gawnsoft/smalltalk
Something I suggested a package manager include is separate “last
modified” and “last certified active” fields, so that users could
distinguish between an abandoned/dormant project and one that was
simply feature complete and needed no additional modifications to
it. The “last certified active” field should be pretty trivial to
keep updated if this is indeed an active project, and will handle
the (somewhat disconcerting) case of libraries that have modified
dates several years old, but which are in reality perfectly alive
and being used.
martin
Simon Strandgaard neoneye@adslhome.dk wrote:
Maybe one could calculate a ‘dormant’ value, so that visitors easily
can distinguish alive and kicking projects from the dead ones:
- no upload via scp to the homepage.
- no commits.
- no file releases
- no downloads
- no closed tracker items.
Under what
circumstances would mutiny be a better choice than forking? I would
generally rather see projects removed than usurped.Most circumstances, imo.
Teh thing about libraries is that they become known due to reputation,
which tends to spread through both w.o.m. and personal experience.
What is the same, had better keep the same name to prevent confusion.
What is note the same, or destined to become something else, should take
another name.
I very much agree with you (other posting) that you want to catch
certain kinds of dormant projects.
I am however opposed to taking over a project in a few days
(the term Tom Copeland suggested).
I know some parts of this world have two weeks holiday per year, but I
disappear every now and then for about three weeks, regular holiday (and
if it is up to me, that will only be longer in the future). There will
always be people that know I’m gone, especially other members of my
projects, if there are other members. But still.
The Software we’re talking about, by its very nature, is written in
people’s free time, for no compensation but the scratching of their own
itch, can be left alone for extended periods of time for many reasons.
That doesn’t mean it’s ditched, so don’t go about assuming that.
After the question is raised about a project being dead, you’ll have to
wait for, dunno, half a year? more? to give the owner time to respond.
I know I would be extremely pissed if I find a project of mine taken over
when I return from a holiday.
Bye,
Kero.
PS: this all of course within reason; if there’s enough comments from
other people that are supposed to know, don’t seem to have a grudge, etc,
etc, then there is no problem handing over a project to someone else on
shorter term. But this would be the secondary way of handling it, not the
primary.
PS2: Tools like bitkeeper are probably an easier way to keep separate
repositories than CVS, allowing projects to evolve without
explicitely forking or taking over. Note that I am not expecting rubyforge
to switch to that (unless money can be raised for that somehow?).
±-- Kero ----------------------- kero@chello.nl —+
all the meaningless and empty words I spoke |
Promises – The Cranberries |
±-- M38c — http://httpd.chello.nl/k.vangelder —+
On Wed, 31 Mar 2004 09:38:01 GMT, Martin DeMello
martindemello@yahoo.com wrote (more or less):
Maybe one could calculate a ‘dormant’ value, so that visitors easily
can distinguish alive and kicking projects from the dead ones:
- no upload via scp to the homepage.
- no commits.
- no file releases
- no downloads
- no closed tracker items.
Something I suggested a package manager include is separate “last
modified” and “last certified active” fields, so that users could
distinguish between an abandoned/dormant project and one that was
simply feature complete and needed no additional modifications to
it. The “last certified active” field should be pretty trivial to
keep updated if this is indeed an active project, and will handle
the (somewhat disconcerting) case of libraries that have modified
dates several years old, but which are in reality perfectly alive
and being used.
Sounds good to me.
If there’s a programmatic ‘ping’ (with a default of every three or
four (or six or eight) months) to the last registered keeper.
System has a default period, project leader can override with
whichever value s/he prefers, up to say 12 months max.
The minimum should be a quick check back over the project’s listing
entry/ homepage, and a confirmation of
‘yep, it’s dormant because it’d sufficiently feature-complete.’
‘it’s dormant because I’ve done all I want to, but it’s /mine/
goddammit, so non-one else touch’
‘it’s dormant because I’ve ended having my time gobbled up by other
demands - and you know what, thinking about it, I reckon I’m not going
to have any time to devote for quite a while longer. Best if any
interested party takes it on for a while’
‘it’s dormant because I’ve ended having my time gobbled up by other
demands - and I just haven’t had time to let anyone know that I don’t
have any time to spare for it’
It’s these last categories that I’d like to trap - the projects which
are useful and extendable, but which the originators haven’t realised
have been de facto abandoned, or have been abandoned without there
being spare attention & time to notify the community.
And for these categories, I think it’s better the project repositories
track the dormant time and prompt the project leaders, than we expect
the leaders to track dormancy.
Cheers,
Euan
Gawnsoft: http://www.gawnsoft.co.sr
Symbian/Epoc wiki: http://html.dnsalias.net:1122
Smalltalk links (harvested from comp.lang.smalltalk) http://html.dnsalias.net/gawnsoft/smalltalk
Simon Strandgaard neoneye@adslhome.dk wrote:
Kero wrote:
The Software we’re talking about, by its very nature, is written in
people’s free time, for no compensation but the scratching of their own
itch, can be left alone for extended periods of time for many reasons.
That doesn’t mean it’s ditched, so don’t go about assuming that.
After the question is raised about a project being dead, you’ll have to
wait for, dunno, half a year? more? to give the owner time to respond.
Hear, hear. I can think of a dozen ruby packages I use on a regular
basis that haven’t been
updated for a couple of years. Either they’re ‘finished’, or maybe the
guys who wrote them
are in prison? I don’t care, they work well.
Asking someone to ‘ping’ RAA once a fortnight is unreasonable IMO.
PS2: Tools like bitkeeper
ACK! Heresy!
I like SubVersion myself 
PS2: Tools like bitkeeper
ACK! Heresy!
that’s what the ‘like’ is for , avoiding heresy 
I like SubVersion myself
If I understod right some talks on #ruby-lang it seem that subversion,
while being generally better than cvs, still suffer from the basic
problem of being a centralized VCS.
BitKeeper and gnuarch OTOH, allows multiple fork/branch of the same
project to live in diferent places, but still allowing re-merge of the
branches at any time.
This is interesting:
http://common-lisp.net/pipermail/bese-devel/2004-March/000073.html
Btw, matz just said in ruby-core 2730 that ruby development will
switch to using DARCS, I wonder if this relates to his choice to adopt
the glasgow haskell compiler has the default backend for Rite.
il Thu, 1 Apr 2004 10:26:00 +0900, Dick Davies rasputnik@hellooperator.net ha scritto::
gabriele renzi wrote:
il Thu, 1 Apr 2004 10:26:00 +0900, Dick Davies
I like SubVersion myself
For small values of ‘like’…
If I understod right some talks on #ruby-lang it seem that subversion,
while being generally better than cvs, still suffer from the basic
problem of being a centralized VCS.
True, but that’s not a killer for me. I hate its slew of dependencies,
not least apache2 and db4.
Nice if you like that kind of thing, but it means you have to svn dump
your repos to
get them into another system, and it takes an afternoon to install it. yuk.
BitKeeper and gnuarch OTOH, allows multiple fork/branch of the same
project to live in diferent places, but still allowing re-merge of the
branches at any time.
Is it called gnuarch this week? Last time I looked it was larch, before
that arch.
arch was promising but I don’t like the bazillion commands you have to use.
At least svn is mostly cvs command line compatible (except for copy,
move and other additions).
Sigh. All hardware sucks, all software sucks, etc…
This is interesting:
[Bese-devel] Compilation errof for mod_lisp.c
Btw, matz just said in ruby-core 2730 that ruby development will
switch to using DARCS, I wonder if this relates to his choice to adopt
the glasgow haskell compiler has the default backend for Rite.
Another one to try - cool, thanks.
Anyone else got a favourite?
Anyone has ever tried monotone (http://www.venge.net/monotone/)?
It seems to have a nice number of features (check
Better SCM Initiative - CVS Alternativen).
Regards,
Andre
On Thu, 2004-04-01 at 15:54, Dick Davies wrote:
Another one to try - cool, thanks.
Anyone else got a favourite?
–
C for yourself.
Using the svnserve network server avoids the need for Apache 2 (though
obviously not BerkeleyDB, which is fundamental to how Subversion stores
data). If you use svnserve, setting up a public server is quite simple: do
the ‘./configure ; make ; make install’ dance steps, and then add a line to
inetd.conf to run svnserve on the standard port.
–amk
On Fri, 2 Apr 2004 03:54:31 +0900, Dick Davies rasputnik@hellooperator.net wrote:
True, but that’s not a killer for me. I hate its slew of dependencies,
not least apache2 and db4.
[courtesy cc of this posting sent to cited author via email]
In article 406C6518.1080504@hellooperator.net,
Is it called gnuarch this week? Last time I looked it was larch, before
that arch.
arch was promising but I don’t like the bazillion commands you have to use.
At least svn is mostly cvs command line compatible (except for copy,
move and other additions).
Well, GNU arch is the official name as it is now a GNU project. Arch is
more the name of the concept and larch/tla/arX are the implementations.
larch is the original shellscript based project from Tom. tla is a complete
rewrite in C by Tom helped by many contributors. ArX is a fork of larch
with many modules in C++.
tla is now pretty stable and has many more features than when you
apparently tried it. It has GPG signed archives for security & integrity
for example. The command-line interface is still full of
very-long-commands but shell completion and aba (a wrapper around tla
commands) help a lot.
Ollivier ROBERT -=- EEC/AMI -=- ollivier.robert@eurocontrol.int
Usenet Canal Historique FreeBSD: The Power to Serve!
gabriele renzi wrote:
If I understod right some talks on #ruby-lang it seem that subversion,
while being generally better than cvs, still suffer from the basic
problem of being a centralized VCS.
True, but that’s not a killer for me. I hate its slew of dependencies,
not least apache2 and db4. Nice if you like that kind of thing, but it
means you have to svn dump your repos to get them into another system,
and it takes an afternoon to install it. yuk.
Actually, svk (I think that’s the name) implements a distributed form of
svn. I haven’t played with it, but it looks okay.
This is interesting:
http://common-lisp.net/pipermail/bese-devel/2004-March/000073.html
Btw, matz just said in ruby-core 2730 that ruby development will switch
to using DARCS, I wonder if this relates to his choice to adopt the
glasgow haskell compiler has the default backend for Rite.
Another one to try - cool, thanks.
Anyone else got a favourite?
How well does DARCS work with Windows? I know that one of the nice
advantages to both Subversion and CVS at this point is that they have strong
Windows integration provided through the Tortoise(CVS|SVN) projects.
I know that I’ve looked at a wide variety of [VS]C systems and have rejected
most of them because they either cannot work on Windows at all or have
significant issues in working on Windows or cannot be a server on Windows.
-austin
The db4 dependency is not going away, but you can run SVN in a standalone
mode without using Apache2 and WebDAV. That’s how I run SVN now.
-austin
On Fri, 2 Apr 2004 03:54:31 +0900, Dick Davies wrote:
True, but that’s not a killer for me. I hate its slew of dependencies,
not least apache2 and db4. Nice if you like that kind of thing, but it
means you have to svn dump your repos to get them into another system,
and it takes an afternoon to install it. yuk.
–
austin ziegler * austin@halostatue.ca * Toronto, ON, Canada
software designer * pragmatic programmer * 2004.04.22
* 07.31.18
I remember someone mentioning (I think it was on the OpenBSD lists)
that subversion will eventually have support for using the filesystem
instead of berkeleydb, and that inital commits have already been done
to add this support.
This would be very nice IMO…
Regards,
Andre
On Thu, 2004-04-22 at 08:32, Austin Ziegler wrote:
The db4 dependency is not going away, but you can run SVN in a standalone
mode without using Apache2 and WebDAV. That’s how I run SVN now.