Hi,
--- On Mon, Jul 12, 2010 at 12:10 AM, Gaurav Menghani
<gaurav.menghani(a)gmail.com> wrote:
| The system should associate
| each accepted proposal with a code repository, and periodically notify the
| mentor when a commit is made, and put up some commit info on the 'Code
| Repository' section in the Project.
\--
IMO, you could just provide a field to just identify the location of
the project repository, and leave it at that. This allows you to:
1. Put the handling of version control repositories to hosting
websites that do only this job, and do that very well. You only focus
on facilitating the workflow between students, and mentors.
2. Not all project necessarily use git, and it is best to leave the
choice of Version Control System (git, hg, svn, cvs, or any other) to
the project/mentor.
3. You could give an option for hosting project repositories, but,
then one needs to then think about which VCS, and not force any team
to use your VCS. You also then need a proper backup policy and disk
space for the repositories.
4. If the project hosting website has an RSS feed, then you can
subscribe to it, and send e-mail to mentors/project mailing lists when
a new commit happens. See RSS feed parsing, for example:
http://ruby-toolbox.com/categories/rss_feed_parsing.html
---
| The plan was to keep the URL of the .git files, use an appropriate git
| command periodically to find the commit info remotely, then notify the
| mentor when a new commit is made,
\--
Leave this to the code hosting website for the above mentioned reasons.
SK
--
Shakthi Kannan
http://www.shakthimaan.com