On Sat, 2009-01-24 at 23:49 +0000, Andrew Church wrote: > Francesco, now that we have a Mercurial repository (thanks Joern!)
Yup, Thanks Joern! :) > what's your thought on how to manage it? Given the berlios.de site, > I could see a few ways of doing things: [...] > - Keep on using hg.exit1.org as the main source repository, but set it up > to automatically push changes to berlios.de, and use the HTTP server > there for anonymous read access. This one is a good match. My plan (of course susceptible to discussion and adjustements) is to use hg.berlios.de as reference repository, hosting stable branches, official tarballs, announcements. etc. To make a long story short, I see berlios as our frontend to the public. The backend, the place where actual development, discussion, proposals, experimental code, will still be hg.exit1.org. Originarily I had different plans, e.g. to move almost everything on berlios.de; but Joern (if I understood correctly :)) is still happy to host us, and since we've moved or we're moving the heaviest and resource consuming pieces on berlios, I think it's better to stay here for a little more. The rationale for this decision is that here on exit1 we got more freedom (e.g. for custom configurations), we got direct line with the root of the box :), and we already have the infrastructure set; moreovere, I never planned to move the MLs, so I think it still makes sense to host some development here. (Of course if Joern still agrees! :) Moreover, given the fact we're switching on hg, moving enterely on berlios, if this needs arises, should'nt be a big deal. So, I think the option quoted above is the best one :) As for forwarding changes, either forward them automatically or manually push from stable branch from time to time is fine for me. > - Thank Joern profusely for providing a server for so long (: and shift > everything over to berlios.de. Of course I'll do this in any case. [...] > One downside of this structure is that it takes up tons of disk space. (: > So what I'm thinking would be useful is to: > (1) Move everything from transcode/trunk/ up to the root directory. [...] I 99% agree. The only 1% left is that I'd like to have the chance to host different subtrees on the same repo (see svn on berlios.de for example, the tcrund and transcode trees). In other words, I'd like to not be forced to start a new repo for a related project, e.g. tcrund. I've to admit that I've not yet grasped HG enterely (not even finished the hg book :( ), so it's possible my concern has no real foundation. Full ack for (2) and (3). > How does this sound? If it's okay with you, I think it might be best to > just export everything and create a new repository from scratch with the > new layout, so people don't have to worry about files being in different > places depending on what version they're looking at. I can do that on > my end and then provide a copy of the new repository to Joern (or to you > for berlios, depending on where you want to put the final repository), > so just let me know your thoughts and I'll get started on it. Fine for me with the above concern. As for forwarding changes to berlios, I've no strong opionions yet. *Perhaps* is better to start pushing manually. Bests, -- Francesco Romani // Ikitt http://fromani.exit1.org ::: transcode homepage http://tcforge.berlios.de ::: transcode experimental forge
