I don't know if feature requests, PEPs or which other scheme may be the better fit. I do believe that having a way of documenting feature requests would be useful. But I also think that the board should agree with that for having something positive going on, and that doesn't seem to be the case. So I guess that's pretty much it. Cheers, Andrés Hernán Morales Durand escribió:
2010/12/8 Stéphane Ducasse <stephane.ducasse@inria.fr>:
I know Andrés did a lot of good work in and for Smalltalk, he shouldn't need to present any credentials here. And besides there must be a nice way to make people listened and to considerate their claims. I know him too and this is not the problem of trust or achievement as a programmer. We consider claim and expectations this is why we sent calls in the past.
Now the key question is: is it productive to discuss features if by construction we know that we will not have the manpower to do something?
Considering the extreme and embarrassing success of, for example, Python (even with their crappy syntax and methodologies) over Smalltalk, I think yes it is productive to learn from succesfully software projects.
What's wrong with the revisions and improvements process described in my previous mail? Why nobody considerate it?
See for example:
What is a PEP? ==============
PEP stands for Python Enhancement Proposal. A PEP is a design document providing information to the Python community, or describing a new feature for Python or its processes or environment. The PEP should provide a concise technical specification of the feature and a rationale for the feature.
We intend PEPs to be the primary mechanisms for proposing new features, for collecting community input on an issue, and for documenting the design decisions that have gone into Python. The PEP author is responsible for building consensus within the community and documenting dissenting opinions.
Because the PEPs are maintained as text files in a versioned repository, their revision history is the historical record of the feature proposal
(from http://svn.python.org/projects/peps/trunk/pep-0001.txt)
We can dream and talk but at the end of the day if we say ok it costs 4 man months and changing all the vms (which I would love to see happening).
I have a huge wish list, believe me and the result is gorgeous now the only thing that I can do is to take one of the item and beat it to death and doing it and go to the next one. And I frustrate a lot because these are a lot of tiny steps.
Ok, what I'm saying is why don't start organizing the proposals, evaluations, coordination, decisions, etc. and then the people will come. Cheers,