On 5.8.2011 16.11, "ext Hugo Parente Lima" <[email protected]> wrote: > >I'm still not convinced about the need of a PSEP for this but I can >(will) >write one if it is required. PSEP means open design process, but the >absence >of an PSEP doesn't mean a closed design process, it can be open as it is >at >the moment, just with less bureaucracy.
If you omit doing the PSEP and work in a "non-bureaucracy" mode, you still need to write proper documentation for the APIs, so in the end you save no work. Also, from the openness point of view, there's a definite difference between the PSEP mode, in which you need to have the discussion in the public and reach a concensus before something is done, and you collecting suggestions and then making the design decisions among the core dev team. >I'm also *not* against the PSEP idea, it's a good idea, I just have the >opinion that PSEPs should take care of PySide Python API only, not the >internal ecosystem surrounding the bindings generation/runtime. But the module we're discussing _would_, for all intents and purposes, be a PySide Python API, and not about the internal ecosystem. ma. _______________________________________________ PySide mailing list [email protected] http://lists.pyside.org/listinfo/pyside
