[Nix-dev] distributed version control system

[Michael Raskin]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/23/2010 10:27 AM, Yury G. Kudryashov wrote:
> 1. Are there any objections?

Well, there are some features that SVN has and many DVCS lack.

a) checking out only a subdirectory. Most VCSes have branch granularity
for checkouts.

b) checking out only a specified revision.

The question here is also about being able to commit after such partial
checkouts..

> 2. Which dvcs system will we use? I use git but I have no strong 
> preferences. I know that Michael Raskin doesn't like git.

I guess we should enumerate the requirements first..

Do we consider commit authorship spoofing a bug or a feature?
Do we want anything like signed expressions? Can we profit from
offloading this functionality to VCS?
Do we need branches in the full sense?
What merge schemes are the most relevant for us?
What recurring merge conflicts did we have earlier?
What textual merge cases are relevant for us?
Are we going to make buildfarm test run information accessible via VCS?
How much information do we want to make accessible this way?

What else?

> 3. Which hosting to use? If using git, I propose gitorious.org.

I think "The official main repository" should be in nixos.org domain and
be hosted in the project's hosting University.

Voting on the best external mirror(s) can be delayed... After all,
merging in-sync copies of one branch between mirrors is not that hard.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJL0UzXAAoJEE6tnN0aWvw3rTEH/i4BDwb+dzhsUlN1dYYJ04O0
jsfMydpc4ST0qkqew9L5juih+n9zTgrNzjgdW9cxWrzUqSDkpCDPWiGmFAp3BH2J
fLNKfcKN1frWrxOYcBYv53ZhdpAfbQwSNEgZqmv0FFUElS3SJECXUVaMp97phTyx
ne0iFIbLs8fIqEpMaAe7oOXNOOeRveWBfK98OBkfDMD5yp39CV/0iNS3+efVq9J/
TcGyxt4YbqHlOpEZn3mAa3I2nmpwucv4a7h184dX+cY0Mr/UfwhZZtMPDoBd7voU
jCfZH5Uyq0Nd5YOsXbGPH8GZgu64dPMUP6YAVPD0UTT+n7ND9yjrhfVUx1ktF8c=
=bWui
-----END PGP SIGNATURE-----