Hello, I had made a proposal for the Git.pm project in GSoC. The proposal did not get accepted, however, I see that no one in the GSoC accepted list is actually working on the Git.pm project. If some of you could give me some of your time in terms of advice on what exactly is needed for the module, I am willing to work over the summer to get this module production-ready. I can probably put in 15-20 hours a week on this project from May to August. I believe that will be enough time to roughly complete all that I had enumerated in my GSoC proposal. This of course will be strictly outside the GSoC framework. I plan to start coding on the project by 7th May and use the time from then to now to investigate what code is there/ what is to be done etc. I had made an approximate timeline for the GSoC proposal and I would like to follow it - ---> [By 15th May] Get the current perl code, to use another mechanism of throwing errors(Try:Tiny) ---> [By August] Get in place a more robust perl wrapper ie. expand the code have a couple of more objects, Git::Repo, Git::Config etc. ---> If all goes well, then by the beginning of August, get the perl module ready for CPANfication I also had a couple of questions - ---> Do I base my code revisions on the master branch of the Git codebase[https://github.com/git/git]? Or is there some other repository which might be more recent. ---> I saw gitweb-caching code from a previous GSoC project, the perl module there seems to have been developed beyond what is there in the master brach? However, these changes are atleast a couple of years old and havent been incorporated in the main codebase... Is there any particular reason for that? ---> I see in the code that it says that the API is experimental. Is there any absolute need for backward compatibility, or can I try to redesign the API somewhat extensively? Also, any suggestions and tips you can give me about the project will be very helpful. Cheers, Subho. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html