Biggest problem we have is this. Try clicking here https://wiki.apache.org/jclouds/Best%20Practices Then, try logging in. Then, try updating something while you are logged in.
We need a better place to collaborate on best practices. and also we should stop using the word "best" for now :) We have current practice and some of that is far from best. For example, plastering fallback on 404 without reading docs is a bad practice. -A On Thu, Nov 13, 2014 at 2:59 PM, Everett Toews <everett.to...@rackspace.com> wrote: > Lack of easily identifiable best practices for jclouds makes it difficult for > both new and experienced developers to contribute. > > It’s impossible to tell what jclouds best practices are at any given moment. > It depends entirely on who the reviewers are and if they happen to be > familiar with the best practice for the code under review. > > All jclouds reviewers operate on a PR by PR way to communicate what they > perceive to be the best practices, whether or not that aligns with what > others perceive to be the best practices. We attempted to address this with > the Best Practices [1] wiki page but we didn’t do a good job of promoting its > use or contributing to it. I would like to change that. > > I just added a simple section about Mock Tests [2] along with an example. If > you would like to improve that section, go for it. > > Who wants to add a section about domain classes and auto-value? > > Regards, > Everett > > [1] https://wiki.apache.org/jclouds/Best%20Practices > [2] https://wiki.apache.org/jclouds/Best%20Practices#Mock_Tests
