eZ running on Git / Discussions / Forums - Share eZ Publish! The eZ Publish Community

Forums / Discussions / eZ running on Git

Thursday 03 June 2010 6:00:42 am - 8 replies

Introduction

EDIT : eZ Publish Community Project's git repository can now be found here : http://github.com/ezsystems/ezpublish

Big news today, concerning all of us keeping an eye on eZ Publish's code frequently : eZ is migrating to Git!

8 replies

Author	Message
Philippe VINCENT-ROYOL	Thursday 03 June 2010 6:10:21 am Great :) Should we have old source code for eZ or only support source code? Certified Developer (4.1): http://auth.ez.no/certification/verify/272607 Certified Developer (4.4): http://auth.ez.no/certification/verify/377321 G+ : http://plus.tl/dspe Twitter : http://twitter.com/dspe
Ole Morten Halvorsen	Thursday 03 June 2010 6:18:18 am Excellent news! Senior Software Engineer - Vision with Technology http://www.visionwt.com http://www.omh.cc http://www.twitter.com/omh eZ Certified Developer http://ez.no/certification/verify/358441 http://ez.no/certification/verify/272578
Patrick Allaert	Thursday 03 June 2010 6:28:37 am " Great :) Should we have old source code for eZ or only support source code? " I am not sure I understood your question. The full history, branches and tags available in subversion will be converted and available through GitHub. Only the code of eZ Publish, available publicly at: http://pubsvn.ez.no/nextgen/, will be moved to GitHub, projects and extensions are not impacted by this migration. Does it answers your question? Patrick ALLAERT http://patrickallaert.blogspot.com/
Gaetano Giunta	Friday 04 June 2010 4:58:30 am @pa: 1. do I understand correctly that all branches except "trunk" will not be migrated? 2. for web interface, will github be used (ie. no more websvn/viewvc on pubsvn)? 3. is someone preparing the migration of the pubsvn scripts so that the code tarballs and doxygen docs are generated daily from the git sources starting day 1 after migration? thx ciao Principal Consultant International Business Member of the Community Project Board
Patrick Allaert	Friday 04 June 2010 5:50:55 am " @pa: 1. do I understand correctly that all branches except "trunk" will not be migrated? 2. for web interface, will github be used (ie. no more websvn/viewvc on pubsvn)? 3. is someone preparing the migration of the pubsvn scripts so that the code tarballs and doxygen docs are generated daily from the git sources starting day 1 after migration? thx ciao " Not at all, as said in previous reply, all branches and tags will be available on GitHub. The same is true for the whole history. Yes, GitHub is providing many web features on top of the remote repository: viewing the repository as a filesystem (like viewvc/websvn), atom feeds to follow changes to one of more branches, searching inside the source code and many more!) Feel free to communicate missing feature or recommendations so that we investigate them! I think that most of the feature provided by pubsvn will be handled by GitHub directly. We don't need the generation of tarballs ourself as it is possible through GitHub to download a zip or a tar of every branches. Correct me if I am wrong. Doxygen docs generation have not been planned yet, this should be probably handled at the same time than switching to PHPDoc. As you may know, every new piece of code is documented using PHPDoc as well as methods which are being modified. It does mean Doxygen docs become less and less useful with the time. Any suggestion to how the migration process can be improved is welcome! Cheers. Patrick ALLAERT http://patrickallaert.blogspot.com/
Gaetano Giunta	Friday 04 June 2010 6:04:03 am Thanks for the clarifications! About the api docs: while I really appreciate the effort underway, currently phpdoc-style comments are a minority - by a wide margin. I'd rather not have to wait until the migration is complete (I might be missing something here - is anybody working on converting all existing doxygen-style comments?) to have the docs updated again. This means I propose to: - keep pubsvn alive (migrated or not) - tweak doc building scripts to fetch source from github - add scripts that build docs via php-doc besides the current doxygen ones (and yes, I'm willing to participate in implementing that) Principal Consultant International Business Member of the Community Project Board
Geoff Bentley	Tuesday 08 June 2010 4:25:47 am Are there implications for http://projects.ez.no? Do you see these projects being slowly shifted off onto github or similar, offering new projects the choice of SVN or Git?
Paul Borgermans	Tuesday 08 June 2010 9:36:08 am " Are there implications for http://projects.ez.no? Do you see these projects being slowly shifted off onto github or similar, offering new projects the choice of SVN or Git? " Implications: not at this moment, but you can already host your project on github and still register it on projects.ez.no. Just use the github url for the "external" url in the project meta-data. What will happen with projects.ez.no and its source code hosting is not decided yet Regards Paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans

You must be logged in to post messages in this topic!