El original en inglés sí es accesible (desde el enlace de la página oficial). Es la traducción en español lo que no se puede ver de momento.
Viene a decir que la mayoría de la contribuciones que recibía generaban inestabilidad, o no eran compatibles con versiones anteriores, o tenían otro tipo de problemas, y los autores de esas contribuciones muchas veces no las resolvían, por lo que se veía obligado a rechazarlas.
Incluso en algunos casos eran trozos de código sacados de libros u otros (con copyright).
Pero lo que peor le sentó fue cuando alguien publicó una versión del programa con un parche que él había rechazado. Por eso lo cerró, para que nadie pudiera publicar otra vez el programa con un parche no aprobado por él.
El texto original en inglés:
---------------------------
About Harbour MiniGUI 2.0
I've created Harbour MiniGUI to be a different xBase GUI system from conventional ones.
I've was (and still being) inspired by the Harbour team and other talented men works like Kevin Diggins (BCX author) and Alexander Kresin (HWGUI author).
From the beginning I've was absolutely sure that Harbour MiniGUI should be absolutely free and should not be tied in any way to commercial products. That is is the reason to my preference for Harbour compiler and (now) for MingW compiler.
My initial policy about code contributions was extremely open and many people has contributed code from the beginning of the project.
In many cases the contributed code was defective (generating instability) or was not consistent with MiniGUI command syntax or code style. Even without regarding about backwards compatibility when modifications were made.
In other cases the contributors (when problems were reported) were NOT ABLE to solve it or simply IGNORED the requests.
Even more: Some contributions contained parts copied from COPYRIGHTED (non free) MATERIAL extracted from books or other publications (of course, in such cases I've rejected the code too).
Such situation obligated me to be EXTREMELY careful about code contributions, specially when it affected library CORE.
Sadly, some of those rejected contributions were recently published along Harbour MiniGUI code.
That was extremely shocking for me and I've looked for a solution that protect to the project and the project users from this type of actions.
The decision I've made was to distribute Harbour MiniGUI new version in the form of FREEWARE. This
way, the library should be protected from this kind of alterations.
This decision was not understood by part of the users, and that was shocking to me too.
I'm evaluating an alternate solution that allows protect the library and satisfy users expectations about the availability of sources.
El efecto Barrapunto, supongo
(Puntos:1)Viene a decir que la mayoría de la contribuciones que recibía generaban inestabilidad, o no eran compatibles con versiones anteriores, o tenían otro tipo de problemas, y los autores de esas contribuciones muchas veces no las resolvían, por lo que se veía obligado a rechazarlas.
Incluso en algunos casos eran trozos de código sacados de libros u otros (con copyright).
Pero lo que peor le sentó fue cuando alguien publicó una versión del programa con un parche que él había rechazado. Por eso lo cerró, para que nadie pudiera publicar otra vez el programa con un parche no aprobado por él.
El texto original en inglés:
---------------------------
About Harbour MiniGUI 2.0
I've created Harbour MiniGUI to be a different xBase GUI system from conventional ones.
I've was (and still being) inspired by the Harbour team and other talented men works like Kevin Diggins (BCX author) and Alexander Kresin (HWGUI author).
From the beginning I've was absolutely sure that Harbour MiniGUI should be absolutely free and should not be tied in any way to commercial products. That is is the reason to my preference for Harbour compiler and (now) for MingW compiler.
My initial policy about code contributions was extremely open and many people has contributed code from the beginning of the project.
In many cases the contributed code was defective (generating instability) or was not consistent with MiniGUI command syntax or code style. Even without regarding about backwards compatibility when modifications were made.
In other cases the contributors (when problems were reported) were NOT ABLE to solve it or simply IGNORED the requests.
Even more: Some contributions contained parts copied from COPYRIGHTED (non free) MATERIAL extracted from books or other publications (of course, in such cases I've rejected the code too).
Such situation obligated me to be EXTREMELY careful about code contributions, specially when it affected library CORE.
Sadly, some of those rejected contributions were recently published along Harbour MiniGUI code.
That was extremely shocking for me and I've looked for a solution that protect to the project and the project users from this type of actions.
The decision I've made was to distribute Harbour MiniGUI new version in the form of FREEWARE. This
way, the library should be protected from this kind of alterations.
This decision was not understood by part of the users, and that was shocking to me too.
I'm evaluating an alternate solution that allows protect the library and satisfy users expectations about the availability of sources.
Roberto Lopez.
---------------------------------------