Hi Martin,
>
> If you read my proposal carefully, you will have noticed that I would in fact
> like to have different visions being pursued, in different branches, of
> course.
>
You might be right there. Although technically I would call it a
fork... Semantics. But that might indeed be the bes
Dear Martin,
I have not responded to your proposal yet because it has taken me some
time to consider. But I think now I have settled on my position.
I do not believe that a vote is necessary, in any strong sense of the
term. I would much rather, as William Sit so eloquently wrote on the
Wiki pa
Martin Rubey <[EMAIL PROTECTED]> writes:
| Dear Ayal,
|
| Ayal <[EMAIL PROTECTED]> writes:
|
| > A democracy is not always the best approach.
To some extent, I agree with Ayal -- judging from my own experience
and involvement in some large scale open source projects (eg. GCC).
Though I can al
Dear Ayal,
Ayal <[EMAIL PROTECTED]> writes:
> A democracy is not always the best approach.
I only claim that it would be the best for axiom, because of many differing,
and very strong opinions, and because it is at the moment, and probably even in
future, just not necessary to have only one ver
Hi,
As a fellow maintainer of a competing CAS system (Yacas) I have been
following recent discussions on this mailing list with great interest. It
is not unlikely that I might run in to similar problems in the future.
For what it is worth, here are a few thoughts I had.
Democracy in an open-sour
Ondrej has already answered for the emotional side. I try to add a tiny bit on
the rational side:
> Lets try a thought experiment.
> Suppose you propose that Fricas should now be democratic.
I would not suggest that FriCAS should become democratic. I said I would in
fact like to have democrat
[EMAIL PROTECTED] writes:
> You've made the claim twice that the gclweb change broke code. Please give
> an example of something that broke due to the gclweb change.
LaTeX style chunk delimiters break
* Definitively mmm-mode for editing pamphlets.
* Possibly they break nested chunks.
* Possib
[EMAIL PROTECTED] writes:
> In a model that encourages 97 branches (I have more than a dozen
> locally) and any one branch can be the next Gold, how do you
> propose that a developer contribute a change? Where would they
> contribute it to?
To any branch she likes. In fact, fortunately axiom is
[EMAIL PROTECTED] writes:
> There are 97 people subscribed to the Axiom mailing list.
> Please explain how you plan to garner 49 votes for anything.
It is quite OK to abstain. I'd suggest to
* have no vote for trivial patches (fix typos, for example) or if nobody
disagrees.
* have a short vo
