At 18:37 Uhr -0500 6.1.2001, Ross Wm. Rader wrote on dev-list:
>< I think the OpenSRS approach to software releases needs a bit of
>< reexamination. Why go to the trouble of doing things one way,
>< only to have RSP's tell you it's not what _they_ had in mind?
>< This surely must end up requiring more work in the long run,
>< leading to more delays in feature releases.
>< Why not lay your cards on the table and publish timelines and
>< planned features? Missing release deadlines isn't so bad as
>< keeping RSP's guessing as to when features will happen
>< and then surprising them with the results.
>
>Actually Jim, the current renewals process is based on feedback culled from
>heavy consultation with the denizens of this very list. Scott spent a great
>deal of time working through the various issues with our resellers. For full
>details, check back through the archives.
OpenSRS would improve our common business a lot
if decisions and timelines where only kept as a secret
in exceptional cases, not as the norm.
for example, is there or was there a plan to improve the mailing lists ?
is there a timeline for RSP to RSP transfers or for handles ?
what about giving feedback after your regular planning sessions ?
i know it's contrary to conventional business principles,
but hey, that would create a community and a heck of a business :-)
kind regards philippe, http://open-management.com/
