Gerald Pfeifer wrote, On Monday 18 February 2013 02:17 AM:
On Thu, 24 Jan 2013, Richard Biener wrote:
There are technical details of the maintaining part - like would the
material reside in SVN? Or in the CVS where we keep our webpages? Or
somewhere else public (github?)? Would we want to have an official
maintainer and use the usual patch / review / approve mechanism for
changes? Which raises the question of the format the courseware is in?
Gerald? David?
Whatever works for Uday and team, I'd say. With a strong recommendation
to go for SVN since that is our primary tool for version control (and a
stronger recommendation against CVS which I'd really love to migrate also
the web pages away from).
I am absolutely fine with SVN because that's what I use :-)
However, we need some clarity on exactly what will go in SVN. We will have
things like:
* Text files such as html files (absolutely fine with SVN).
* PDF slides (unsuitable for SVN because they are binary files). I don't
mind uploading the LaTeX sources and associated Makefiles for creating
pdf.However, we will need to test them out on a few machines that I
have never touched to make sure that they don't depend on some local
installations that I have stopped noticing. These slides do have some
.epsi images that will also have to be added to the SVN repo.
* Videos of lectures. I guess these are best kept in the form of links
to our servers because we have high definition recordings (we will
also make more space efficient videos) so a streaming option is best.
So the most critical question is: Do we want to give LaTeX sources of slides or
only the PDF files only. I am okay with both the options.
Yeah, I know - the obvious link from the gcc.gnu.org page to click for a
newcomer is 'contribute', but that page is awkward enough to scare off a
possible contributor ;)
True. Any ideas/suggestions? Happy to make changes...
I'll try to come up with some concrete suggestions on how they can be
reorganized.
Uday.
