Hi Jerry... I agree with you, sorry I am not a committer in this cool project but I am watching what you are doing and I am very interested in it. Again, I agree with you, my recommendation is to do was what is done with Logging which is creating different sub-projects for each version of Libcloud based on the language used.
On Sun, May 16, 2010 at 8:00 AM, Jerry Chen <[email protected]> wrote: > > On May 14, 2010, at 3:46 PM, Eric Woods wrote: > > > As noted earlier, we've targeted a very strong mapping between the > existing > > Python design and the Java implementation. Aside from Python's design > being > > minimal and extensible, this will make it easy to port existing adapters > to > > Java since it's the same structure and model. This will also provide the > > same look and usage to the user of libcloud adapters for faster adoption. > > > > Feedback is welcome and appreciated. > > How do we reconcile the fact that for all intents and purposes, the > Libcloud community is geared towards Python developers? > > I'm not opposed to a Java port of Libcloud at all, but merely questioning > its placement within the same repository. From a committer's standpoint, I > have far less of an ability to review, to test and to sign off on Java code > than I do for Python. > > What does everyone think? > > Cheers, > Jerry -- Thanks - Mohammad Nour - LinkedIn: http://www.linkedin.com/in/mnour ---- "Life is like riding a bicycle. To keep your balance you must keep moving" - Albert Einstein "Writing clean code is what you must do in order to call yourself a professional. There is no reasonable excuse for doing anything less than your best." - Clean Code: A Handbook of Agile Software Craftsmanship
