Some days ago Frieder wrote:
> I started the class struggle some years ago .. and I see that
> it is scaling
> down - the
I always liked the eiffel class struggle because it was one of the
three things (the other ones are elj-daily and the eiffel-forum)
that brought eiffel developers closer to each other.
So I think the class struggle is still important.
But I'd like to see some modifications:
Today I think it is not appropriate anymore that people are
developing software for a year and nobody knows about it until
it appears in the class struggle (BTW: it might not appear at
all since people could think their software is not mature enough
or they were not able to do it all without help).
It could be the case that other people have been working on exactly
the same topic for that year or could have used the code of the other
developer for his own stuff.
So I suggest that software for the cluss struggle should be written
right from the beginning as open source, available from sourceforge
for example or any other server preferrably accessible through cvs.
It does not mean that every entry for the class struggle has to create
it's own sourceforge project. It could be one project and each entry
could go in it's own module.
These are the criteria to the '98 class struggle (I'm not sure
if it changed since):
- How useful is the application or library?
- How well has it been designed?
- How attractive is the style?
- Have object-oriented design principles been applied?
- How readable is the software?
- How portable is the software?
- How much effort has been invested?
So the open source criteria could be added to this list.
As already suggested another one I would add is
- How much 'GOBO complient' is the software ?
This way we would support the GOBO project already and
do not have to wait for next year.
- Sven
|
