We lack docs and references on how jclouds is used by other projects. We're a nexus for multiple different projects (jenkins to openstack, maginatics to s3, etc). We should highlight this more in the website so that it compels projects to integrate with various iaas's through jclouds so they gain portability. At this point the main website is too technical for most audiences, and doesn't paint a compelling story to pull others in.
Otherwise, I think the layout is pretty good, it's better than most opensource projects with the same number of active contributors. I believe as we grow and recruit more talent into our community, we can find ways to improve it. On Tue, May 28, 2013 at 6:12 PM, Becca Wood <silky...@apache.org> wrote: > Hi everyone, > > There are currently several conversations going on about docs, and the > statements from some folks are blindsiding me as I read from thread to > thread. > > It would be great to have a discussion around what everyone does not like > about the current docs process and why and how it should be changed. It > would also be good to address the aesthetic and navigability of the > website. Since I am responsible for a good deal of the current docs > process on GitHub and the way the current website looks, it would be great > to get some feedback on the strengths and weaknesses of both. > > The aim of this discussion is to help us collect our thoughts in one place > and create a more solid and contributor friendly process moving forward. > > I don't want to be a hinderance or the single point of failure in our docs > process, so if anyone is confused or has concerns about the current > process, please let me know. > > Thanks, > > Becca >
