Re: [PEPr] +1 for VersionControl::VersionControl_Git

Thanks for your voting and encouragement! My first PEAR package, VersionControl_Git got 9 votes! Christian Weiske gave me some advices, and three people agreed with him. > - Git/Util/Command.php: "You must specified" -> You must specify > - Git.php: initialRepository() -> initRepository() > - fixtures.tar.gz is way too big Thease are already fixed in my Git repository. Thanks for your feedback! - Git/Util/Command.php: "You must specified" -> You must specify http://github.com/ebihara/VersionControl_Git/issues/closed#issue/4 - Git.php: initialRepository() -> initRepository() http://github.com/ebihara/VersionControl_Git/issues/closed#issue/5 - fixtures.tar.gz is way too big http://github.com/ebihara/VersionControl_Git/issues/closed#issue/6 However, there is very big topic: about adding common API with VersionControl_SVN. It is very difficult. Because, as you know, SVN and Git don't share cultures. Normally, a user who want to use Git repository via this library, knows about Git cultures. He will be able to use the VersionControl_Git easy. I think that the current VersionControl_Git is already satisfiedable. Releasing current source code is good as first step of this library. Adding common API with other VersionControl_* is fit for the next step. (I'm already thinking about this: http://gist.github.com/292815) I want to discuss about this with PEAR develpers (especially, developer of VersionControl_SVN). Do you have any ideas? And I planned roadmap of this plugin: 0.4.x : Current 0.6.x : My TODO (Refactoring VersionControl_Git_Object_Commit, remove using VersionControl_Git_Util_Command::addDoubleDash() and adding VersionControl_Git_Object_Tag) will be done 0.8.x : Add common API with other VersionControl_* 1.0.x : First stable release -- Kousuke Ebihara