I agree Ted. I think I would expand upon what you are saying by defining the different stages by which someone becomes involved in the community. It would seem to me that we would want to serve each of these stages.
Experimental User: When someone first approaches a project they need to feel confident about it. This can be done by providing a professional first impression that imbues confidence. It is also important to provide quick and easy access to binaries and documentation. If you have to get 3-4 clicks from the homepage to get the product, that isn't good for user morale. We are currently only 2 clicks to download (that's good). We could improve this by providing more prevalent download buttons to get to docs and binaries for the different implementations. Established User: For established users it's good to have regular and meaningful releases, a responsive user list and Issue Tracking (we have an amazing support community) Contributor : For contributors it's good to have issue tracking that is intuitive and maintained. I think we do both of those rather well. I'm sure i'm not addressing something. But, this is a quick brain dump. What is cool is that I think we have most of these things in the bag. The only area I see room for improvement is to adjust to site to provide clear paths for the different levels of involvement in iBATIS. Brandon On 3/5/07, Ted Husted <[EMAIL PROTECTED]> wrote:
On 3/5/07, Brandon Goodin <[EMAIL PROTECTED]> wrote: > Should we launch a discussion on who the site for? Developers, CTOs, > Managers, etc? How do we feel these different groups would perceive iBATIS > if they visited for the first time? > > Brandon From an ASF perspective, the site should be designed so that it meets our own needs and the needs of other potential volunteers. Other stakeholders (CTOs, Managers, journalists) are only important as a means to an end. The end being attracting new volunteers to contribute code or documentation to the project. The site, and every aspect of our infrastructure, should be designed first to foster collaboration. The volunteer contributors are our only true customers. If all the world used iBATIS, or Struts, or HTTPD, but we didn't have three volunteers to do the work, the project would be a failure. -Ted.
