I'd have suggested dw_styles, but since that comm has limited posting access, here we are.
Anyway, Mercurial is the version control system Dreamwidth is using. There's a page on the Wiki that provides a little more information about it, but it's basically a distributed system with multiple repositories instead of just one (like LJ uses). About six months ago, afuna set up a Dreamhack for the Styles team to use, complete with its own repository. This made sense because there were 6-8 of us on the team working with different components of Core2, so we all needed commit access. We could all kick stuff around without disrupting the "main" repository. However, there aren't as many of us doing active S2 development now, so we're not really using the s2team repository any more. As I mentioned up-thread to yvi, I'll probably need to try setting up a development environment and follow the established workflow for generating patch files. Am I making sense?
no subject
Anyway, Mercurial is the version control system Dreamwidth is using. There's a page on the Wiki that provides a little more information about it, but it's basically a distributed system with multiple repositories instead of just one (like LJ uses). About six months ago,
However, there aren't as many of us doing active S2 development now, so we're not really using the s2team repository any more. As I mentioned up-thread to