On Sat, May 7, 2011 at 5:31 PM, john pradeep <yehohan...@gmail.com> wrote: > I have restructured the modules, I still haven't moved the python modules > though. > Tried to configure hudson for nuvem but looks like I don't have > enough privilege to create new hudson jobs, waiting for Luciano to give me > the access. > > > Regards, > John > > > On Sat, May 7, 2011 at 7:54 PM, john pradeep <yehohan...@gmail.com> wrote: > >> Hi All, >> I created a branch "branches/before_restructure" to backup existing nuvem >> structure so that I can start re-structuring the code base in trunk and >> later configure hudson for each project. >> >> The structure will appear as we decided sometime back, but with few >> additions for python projects as Jean started working on python support. >> Each feature will exist as a defined package in every platform specific >> project. >> >> Jean, Are you ok with the naming convention for python projects? >> >> nuvem-api >> nuvem-commons >> nuvem-google >> nuvem-azure >> nuvem-ibm >> nuvem-standalone >> >> nuvem-python-google >> nuvem-python-standalone >> >> >> nuvem-samples >> store-commons >> store-ibm >> store-google >> store-standalone >> >> >> Regards, >> John >> >
Hi John, The new structure for Java projects looks good to me. With respect to the Java vs Python modules, I find it strange to name the Python projects *-python-* and not name all the Java projects *-java-*. On the other hand, it'd be nice to keep the names simple and not pollute them all with *-java-*, like you've done here. If you're a Java user or a Python user, I think you want to pick a set of modules once for all and don't need their naming convention to remind you which programming language you're using :) In the long term and if the Python work picks up some steam, I'd suggest different top level directories for Java and Python, like this: nuvem/java/trunk/nuvem-api nuvem/java/trunk/nuvem-commons ... nuvem/java/branches/ ... nuvem/python/trunk/nuvem-api nuvem/python/trunk/nuvem-commons ... nuvem/python/branches/ ... For the shorter term, nuvem-parallel is the only Python module and doesn't conflict with the other modules, so how about simply keeping it as is at the same level as the others? I'm happy to revisit that when there's more modules. What do you guys think? -- Jean-Sebastien
