2012/4/17 Michael J. Flickinger <[email protected]>:
> This is ridiculous, you should have started an organic mailing list
> discussion.  I'm planning on a rewrite, which I WILL do and
> maintain.

Jesus, *another* rewrite? We don't need more rewrites. We already have
one. Stick to the one we have. Don't start another rewrite that will
also get abandoned. Don't put up a webpage saying that you want
certain code to be done and then tell the person who wants to do that
work that they shouldn't be doing it. At least update the webpages.

> Rewrites take time and planning, sorry.

Enough planning. *Code*. Your planning isn't generating any *code*.

> Having a student work on python code which a project's maintainer is
> uncomfortable with does not fix a project, sorry.

There is no maintainer. Scattered commits here and there are a ghost
town. Starting another rewrite is starting another ghost town. To
paraphrase my countryman Zapata, "la tierra es de quien la trabaja",
code belongs to the one working on it.

I'm going to keep working on the Python rewrite. If you accept back
the changes, great, the project has been revived. If you don't, then
it's a fork. I'll let you know of my progress and the repository from
which you can pull my changes.

- Jordi G. H.

_______________________________________________
Savane-dev mailing list
[email protected]
https://mail.gna.org/listinfo/savane-dev

Reply via email to