On 30.08.2011 01:06, ext Hugo Parente Lima wrote:
Well.. no issues were raised since the last PSEP version 17 days ago, not a
single word since your "Looking pretty good already" and the release wont be
made today or tomorrow but in one month so the PSEP implementation is into the
current sprint, I don't if you review it but it's there.
If you check the mail you were referring to:
http://lists.pyside.org/pipermail/pyside/2011-August/002794.html
You'll notice that I have plenty of comments there which need to be
addressed. Either you may argue convincingly enough that the changes I
proposed are unnecessary, or incorporate them in your PSEP.
Please re-read the PSEP process [1]. The PSEP Author (here, you) is
responsible for gathering community consensus for the PSEP contents and
modifying it accordingly, after which it is reviewed by the core dev
team and me. Only after the PSEP has been accepted, the reference
implementation may be integrated.
[1] http://www.pyside.org/docs/pseps/psep-0001.html
Anyway if the PSEP still a draft during the whole month until the release I
can revert the commits before the release and raise the arm of the winner,
bureaucracy... more than a month to decide an API with 7 plain functions, but
fortunately I think this wont gonna happen.
It may well be that the process is too heavy for the PySide project, but
in that case I very much would like to get proposals for replacement.
The replacement process should be open and non-preferential (core
developers use the same process as everyone else), it should ensure
widespread agreement for the design, and it should be sufficiently
detailed to provide design documentation as outcome of the process.
ma.
_______________________________________________
PySide mailing list
[email protected]
http://lists.pyside.org/listinfo/pyside
