Yarko: thanks for your answer, I'll reply bellow: On Sat, May 28, 2011 at 5:44 PM, Yarko Tymciurak <[email protected]> wrote: > Mariano - > Here are my thoughts about this: > > You have changed the code fairly significantly, as I recall;
Yes and no, the code evolved, some old stuff was removed, some remains, even the layout and configuration are the same. I've just clean up the code, divided db.py in several files, renamed some tables, etc. Also I've updated some ancient code (t2, pdf generation with reportlab), to newer plugins or libraries supported by web2py. You can see each change starting from googlecode clone, so in my opinion is the same code base: http://code.google.com/r/reingart-web2conf/source/list > I think - to keep from confusion between the original launchpad-web2conf, > and it's pointers to google code's web2conf: > > You should create a new repository on google code (and set all licensing, > etc. appropriately) > Massimo has done the same with his updates / re-factored conference tool > (conf2py) > This will keep confusion (about the evolution) to a minimum > > If you have no better ideas on naming your new repository, you might > consider one of these: > > web2conf2 (the second version, second person driving) > nweb2conf (from old unix naming schemes: nSomething == New Something) I would prefer not to create a new project, I think it would cause more confusion, ending with at least 3 projects for conference software with web2py., with a project inactive? what for? This is not the same case as Massimos' conf2py, my clone is not a full rewrite, it has the same codebase as stated earlier. Projects don't create new projects for each version, as the wording suggests, it is not logical, I don't think that is a good signal for our community. I think it is better to manage branches in the repository, managing old and new code in the same place. Although it is true that web2py advances quickly, showing understanding, stability and commitment to long term projects is a good sign. IMHO Best regards, Mariano Reingart http://www.sistemasagiles.com.ar http://reingart.blogspot.com
