Who is working on each of these tasks and what is their status?
* establishing email notification of SVN commits
* getting the web site to update from SVN rather than CVS
-mental
mental@...3... wrote:
Who is working on each of these tasks and what is their status?
I've started chipping away at this.
- establishing email notification of SVN commits
I don't know how the old system worked, could someone give me an overview? Might we desire to use something like svnmailer [http://opensource.perlig.de/svnmailer/%5D?
- getting the web site to update from SVN rather than CVS
Bob started this, and I made a little more progress. I think it would help if people who have been involved in the web took a look.
I've started by moving directories that were not kept in cvs out of inkscape_web and into web_extra and putting symlinks in their places. I am unable to move macosx-snap which is owned by irisson. And I have noticed that there are a number of files that need to be purged (files created by cvs confilcts) or should be placed into svn:
.#download.php.1.37 .#download.php.1.39 .#download.php.1.40 .#download.php.1.44 .#download.php.1.45 .#.htaccess.1.3 index.html.bak .#index.php.1.198 .#index.php.1.212 .#index.php.1.213 .#index.php.1.215 .#index.php.1.216 .#index.php.1.54 index-wp.php inkscape-logo.png inkscape-logo-small-blue.png inkscape-logo-small.gif inkscape-logo-small.png inkscape.rss news-en.inc news-en.inc-old news.inc.backup
I've only examined the root directory. Who would like to take care of these files? SVN isn't going to be bothered when I put symlinks into the directory, is it?
Aaron Spike
Oh, I forgot doxygen. How does that work? When I swap the directories is there something I need to do to re generate that?
Right now inkscape_web is cvs and inkscape_web_new is svn. htdocs is a symlink to inkscape_web. I had in mind to mv inkscape_web out of the way and mv inkscape_web_new into its place. I would guess any scripts people have should continue to work then.
Aaron Spike
On Wed, Jan 18, 2006 at 10:03:33AM -0600, Aaron Spike wrote:
Oh, I forgot doxygen. How does that work? When I swap the directories is there something I need to do to re generate that?
I believe Ted is running the cron job that generates this, so either he will need to revise it accordingly, or you could set up a new cron job to do it.
It occurs to me that maybe we should have an inkscape_admin SF user account for sharing access to cron jobs and so forth...
Right now inkscape_web is cvs and inkscape_web_new is svn. htdocs is a symlink to inkscape_web. I had in mind to mv inkscape_web out of the way and mv inkscape_web_new into its place. I would guess any scripts people have should continue to work then.
Go for it. It's possible some stuff might break, but as long as the important pages are present, we can get those fixed up in time.
Bryce
Bryce Harrington wrote:
On Wed, Jan 18, 2006 at 10:03:33AM -0600, Aaron Spike wrote:
Oh, I forgot doxygen. How does that work? When I swap the directories is there something I need to do to re generate that?
I believe Ted is running the cron job that generates this, so either he will need to revise it accordingly, or you could set up a new cron job to do it.
It occurs to me that maybe we should have an inkscape_admin SF user account for sharing access to cron jobs and so forth...
Well, it isn't me anymore. Originally it was done under my sourceforge account, but then they started restricting cron. I believe that today it is done by Kees. I'm not sure if the restrictions at sourceforge have changed, but it would be nice if it was all generated there. (seems like a feature most projects would use, or at least should use ;)
--Ted
Bryce Harrington wrote:
On Wed, Jan 18, 2006 at 10:03:33AM -0600, Aaron Spike wrote:
Right now inkscape_web is cvs and inkscape_web_new is svn. htdocs is a symlink to inkscape_web. I had in mind to mv inkscape_web out of the way and mv inkscape_web_new into its place. I would guess any scripts people have should continue to work then.
Go for it. It's possible some stuff might break, but as long as the important pages are present, we can get those fixed up in time.
Well, I went for it. Inkscape.org is now being fed from an svn checkout. It seems there are some images that aren't healthy. Unfortunately they don't look healthy to me in cvs or svn, but seem to be intact on shell.sourceforge.net still. I fixed the images that appear on the front page by svn deleting them copying them from the old web and commiting them again. There are probably more broken images hiding there.
I invite everyone to chip in surfing the website looking for breakage. Also if you are willing do a svn checkout and browse the old cruft for things that need to be archived and removed.
Aaron Spike
On Wed, Jan 18, 2006 at 09:38:27AM -0600, Aaron Spike wrote:
mental@...3... wrote:
Who is working on each of these tasks and what is their status?
I've started chipping away at this.
- establishing email notification of SVN commits
I don't know how the old system worked, could someone give me an overview? Might we desire to use something like svnmailer [http://opensource.perlig.de/svnmailer/%5D?
Yeah I set this up. If you check out the CVSROOT module, look in the loginfo file. There's a line at the end that causes notices to be sent to the inkscape-cvs list. I also had to tweak the subscription settings for the notifier so it could send mail but not receive any mail, etc.
- getting the web site to update from SVN rather than CVS
Bob started this, and I made a little more progress. I think it would help if people who have been involved in the web took a look.
I've started by moving directories that were not kept in cvs out of inkscape_web and into web_extra and putting symlinks in their places. I am unable to move macosx-snap which is owned by irisson. And I have noticed that there are a number of files that need to be purged (files created by cvs confilcts) or should be placed into svn:
.#download.php.1.37 .#download.php.1.39 .#download.php.1.40 .#download.php.1.44 .#download.php.1.45 .#.htaccess.1.3 index.html.bak .#index.php.1.198 .#index.php.1.212 .#index.php.1.213 .#index.php.1.215 .#index.php.1.216 .#index.php.1.54 index-wp.php inkscape-logo.png inkscape-logo-small-blue.png inkscape-logo-small.gif inkscape-logo-small.png inkscape.rss news-en.inc news-en.inc-old news.inc.backup
I've only examined the root directory. Who would like to take care of these files? SVN isn't going to be bothered when I put symlinks into the directory, is it?
Create a new tree with the files you need, then we can move the bits of the old tree we can't just delete to /tmp or something (or ask the sf admins to delete them). Make sure to set the group write permission for all of these files.
Bryce
mental@...3... wrote:
Who is working on each of these tasks and what is their status?
- establishing email notification of SVN commits
Ok. Bob and Jon took care of this evidently there was just a button in the admin interface that turns this on. Who knew it could be that easy!
Thanks guys.
Aaron Spike
participants (3)
-
unknown＠example.com -
Aaron Spike -
Bryce Harrington