Hello!
Let me say right at the beginning that I'm very interested in the continued existance and development of the SME server product.
I have been using SME server since about e-Smith version 4.splot! In and around where I live and work I have 7 SME servers in production environments, and 5 of these have never been rebooted since installation - the longest is close on 4 years without intervention. I have another 8 - 10 SME servers in support/test/evaluation modes and they too are behaving flawlessly.
I have to say that only VAX/VMS or Alpha/VMS machines have demonstrated this kind of reliability to date and so I'm very much a fan of the SME box. Also, there's no detailed GUI and so inquisitive users/owners simple don't have the ability to 'go poking around in the works' - a definite plus for me!
I suppose I'm much like many users. I like there to be 'official releases' from time to time as these always provide anchor points in the continued development of the product. I like the 'contribs.org' as well. I don't think in all my 35+ years in the IT industry that I ever got such fast responses to problems that I've encountered. I like too that I can 'do my own thing' from time to time AND I can post these efforts into an open area where other people can make what they will of them.
I expect too that I'm one of these people who always expect there to be some sort of 'organisation' behind a project like SME server and it can come as a bit of a shock to realize that the organisation is, in reality, very thin and held together by nothing much more than a will to keep something that is good going!
So what would I like to see? Well, it would help if I knew more about some of the 'grandees' involved. I see - and have communicated with - names like Charley Brady, Greg Swallow, RequestedDeletion, smeghead, slord (to name the first 5 that came into my head), but I don't know where these guys fit into the 'organisation'. For users like me, knowing what folk do and where they fit in is all part of the confidence building exercise that is needed for me to build the confidence in the product that I then pass on to potential end users.
I suppose too that I would like there to be some sort of a controlling body that decided what went into an official release. Such a body need not necessarily consist of 'king coders' but should probably comprise of one or two experienced administrators with technical knowledge who had available to them some sort of a testing team to ensure that the official releases were stable and as fault free as possible.
Finally, the existing contribs.org simply needs to be maintained. It seems to me that the raw material for 'official releases' is almost always to be found in the various sections of 'contribs' and so the controlling body OUGHT (??) to have a relatively easy time when deciding when to move to a new release.
As for development, I rather suspect that this would take place 'automagically' under such a simple yet well defined structure. It's been my experience over may years that the best developments are usually in very small areas and are often done by dedicated programmers/analysts who simply find themselves in a bind and resolve their problem by doing a bit of development work. I think in all my working life I've met only 4 or 5 people prepared to take on the development of a whole system voluntarily!! - and they didn't seem to have home lives!
I voted for option 1. I like the idea of adopting a system that already works. Because it would be adopting a working system, it would also be adapting a working system and so option 2 is really tightly bound to option 1 (in my mind). Also, option 1 already had more votes and so I chose to strengthen the case for adopting something positive rather than doing nothing.
So, these are my rambling, disconnected thoughts - but it proves I'm interested, at least!
Regards,
Dave
