>> The lib directory will also contain >> some basic modules like Gitweb::Repo, Gitweb::Commit which will make >> developing further functionalities easier. > > Beware, this might be an awful can of worms. The previous gitweb SoC > project failed to get merged in part due to trying to do something like > this. > > I recommend to avoid any large architectural changes and just shuffle > around all the utility routines to lib/Gitweb.pm or so. Yeah sure. >> d) Usage of the client: >> >> This client can be used in 2 ways. >> >> * Install a local version using instaweb - The gitweb will be only >> accessible by you. You can browse through the git repository using >> read modules and simultaneously work on them using write modules. >> * Install on intranet - A company when installs this gitweb along with >> some other login and account managing scripts will be able to order >> their employees to login and ask them to work on the code with out the >> security risk of providing ssh access to the git repository host. The >> authentication support can be implemented as an optional part of my >> proposal. >> * Install on web - Just like normal gitweb, or enable write modules to >> look like gist.github.com > > Note that for the latter two, operation mode without working copy is > essential; I have not seen you address it anywhere. I am not planning to write the "operation mode without working copy" during GSoC due to reasons I mentioned earlier. But I would like to add it as an optional part for GSoC along with the authentication wrapper. So, When I complete the main parts of my GSoC proposal, you will be able to use it in your localhost working on your local repos. If I have time during GSoC I will complete the auth wrapper and "without working copy" mode. Otherwise I will develop them after GSoC. Then you can use the write functionalities in repo.or.cz without actual working copies. :-) Thanks -pavan -- 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