From: Martin P. <ma...@pe...> - 2008-03-29 00:34:49
|
There was a suggestion that I should put website sources in the source code repository. I agree, but where to put them? I think there are few options: 1) In new subdirectory in the source code tree: 1a) website 1b) src/website 2) As new CVS module (named website) 3) Sourceforge provides SVN too. Put the website in SVN (of course current sources and development would remain in CVS - only website would end up in SVN). I vote for 2 or 3. What are your opinions? Once the place where website should go is agreed, I'll start putting it there. Any changes done in the repository will have to be manually uploaded by me to the website, but that should be improved in the future. I won't put in old unused scripts, archived communication from old non-public mailing list, config file with SQL password and such things. Question also is, whether to put in the repository also wikka (the wiki we use) source code (which is somewhat modified from the version I originally installed) and mantis (which is only slightly modified) Martin Petricek -- GPG/PGP Public key: http://www.petricek.net/petricm.pgp Fingerprint 6AA8 FFCE C061 1CB2 55F0 A1F3 3AA9 EB4F BD50 C1B8 /------------------------------------------------------------\ | WWW: http://www.petricek.net/ | \------------------------------------------------------------/ |
From: Michal H. <ms...@gm...> - 2008-03-29 13:01:49
|
On Sat, Mar 29, 2008 at 01:34:41AM +0100, Martin Petricek wrote: > There was a suggestion that I should put website sources in the source code > repository. I agree, but where to put them? > > I think there are few options: > 1) In new subdirectory in the source code tree: > 1a) website > 1b) src/website > 2) As new CVS module (named website) Does SourceForge enable multiple modules in the one project? I am not sure (and haven't looked at it yet), but I don't think that it is possible. > 3) Sourceforge provides SVN too. Put the website in SVN > (of course current sources and development would remain > in CVS - only website would end up in SVN). Don't think that it is a good idea to maintain our stuff in two different revision control systems. > > I vote for 2 or 3. What are your opinions? If separate module is possible then I wote for 2, otherwise I wote for 1a. > > Once the place where website should go is agreed, I'll start putting it > there. Any changes done in the repository will have to be manually uploaded > by me to the website, but that should be improved in the future. OK. I think that we can publish our changes in devel list and you can commit and upload them, so that nothing is forgotten. > > I won't put in old unused scripts, archived communication from old > non-public mailing list, config file with SQL password and such things. > Question also is, whether to put in the repository also wikka (the wiki we > use) source code (which is somewhat modified from the version I originally > installed) and mantis (which is only slightly modified) OK. My ACK. -- Michal Hocko |
From: Michal H. <ms...@gm...> - 2008-03-30 11:12:30
|
On Sat, Mar 29, 2008 at 02:01:46PM +0100, Michal Hocko wrote: > On Sat, Mar 29, 2008 at 01:34:41AM +0100, Martin Petricek wrote: > > There was a suggestion that I should put website sources in the source code > > repository. I agree, but where to put them? > > > > I think there are few options: > > 1) In new subdirectory in the source code tree: > > 1a) website > > 1b) src/website > > 2) As new CVS module (named website) > > Does SourceForge enable multiple modules in the one project? > I am not sure (and haven't looked at it yet), but I don't think that it > is possible. There is no mention about multiple modules in sf.net CVS, so I assume not-forbidden-means-allowed. Feel free to add module and we will see. > [...] -- Michal Hocko |