On 2017-12-29, Dinesh Thirumurthy <dinesh.thirumur...@gmail.com> wrote: > OpenBSD is great project. It should reach every country equally.
It does. Full repository with commit history is available and, very unusually for an OS, this is not dependent on the USA. Now that most open source projects provide repository access it's easy to forget, but open repo access was not the norm - OpenBSD pioneered it. https://www.openbsd.org/papers/anoncvs-paper.pdf > Have a look at this picture today > > https://github.com/hakrtech/readme/blob/master/global-outlook.png > > If you provide git protocol access to USA and Canada. > I want git protocol access for Australia, Russia, Japan, Congo, Netherlands > and Rest of the World. Why focus on the access method? The code and history are the important things. So the git conversion is an experimental conversion of part of the information in the cvs repository (no branches/tags) which is pushed to github. It's not using OpenBSD project resources for hosting and I doubt it would be publically available if we had to deal with actually hosting it. Hosting a large git repository is not trivial, it uses far more server resources (memory and cpu time) than an anoncvs/cvsync/rsync mirror, and OpenBSD src/ (or even just ports/) is *huge* for a git repo. It works better on Linux where things are more separated. Even *just the kernel* is split across multiple repos. > Since we cannot provide equal access. Equal access to the git conversion would be trivial. Just delete it. There, now nobody has access, it's equal. Anyway, has anyone fetched your openbsd-src0-test repo from github while crossing crypto export boundaries? That has the exact same issue, except that now as it's your repo, it may well be considered that it's *you* that is responsible for exporting it. I'm not sure if your suggestion of a server in Germany would help. Have you looked into export regulations from there? (Not sure which are relevant but things like the Wassenaar Arrangement would be the place to start looking).
