heads-up: migrating to github

Federico Schwindt fgsch at lodoss.net
Thu Dec 18 00:28:24 CET 2014


I appreciate this is a somewhat controversial topic so I wanted to mention
it well in advance.

We're planning to migrate the varnish-cache repository to github.
The exact date is not defined yet and will depend on a number of factors
but I don't expect this to take place before mid February as the earliest.

There are many reasons for this but the main reasons are simplicity and
manageability, not only for the repository itself but also for the
companion tools (issues, wiki, pull requests, etc.) and for integration
with third-party services.

The plan is not finalised yet but we're aiming to have a seamless
migration. If you believe something is missing please let me know.

The following series of QAs will hopefully cover most of the questions.
While we all have our preferences I will appreciate if we concentrate on
the specifics and leave the bike shedding for another day.

Q. Why migrating it?
A. Simplicity. Less things to manage for us, better tools available, easier
for users to collaborate.

Q. What will be migrated?
A. wiki, issues and repository.

Q. Why github and not <insert your favourite provider>?
A. Again, the main reason here is simplicity. We're already hosting a
mirror there and switching to it, both from the user and our point of view,
should be easy. We have several other projects hosted there also so makes
for a common place to manage them all.
A few less important reasons include the companion tools, the integration
with third-party services and the user base.

Q. Does this mean that github is better than <insert other provider>?
A. Not at all. I haven't done a comparison with other providers and quite
frankly neither want nor have the time to do it. If you think it's
important and have the time please send us your findings but please ensure
we can cover the 3 items I mentioned before.

Q. Would this break the repo I cloned off from git.varnish-cache.org?
A. No, we will mirror from github for the foreseeable future.

Q. What will happen with trac?
A. The existing tickets will be migrated to github.

Q. What will happen with the wiki?
A. We will switch to github. I'm not entirely sure if there is any value on
migrating all the existing content but if we decide to keep all/some of it
this will be migrated as well.

Q. What will happen with the existing link to <insert a link>?
A. Redirects will be put in place for the foreseeable future.

Q. When will this happen?
A. We don't have a date yet. Not sooner than mid February but probably much
later than that.
It will likely be done in stages following the kiss principle.

Q. How this will affect me?
A. It should be transparent for you unless you have something other than
read-only access to the repository or trac. You will need a user and github
and change the origin for the former or some magic from our side for the

Q. Why are you sending this?
A. It seems a lot of people care beyond "git remote set-url ...". If you
don't please ignore this

See you space cowboy!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-dev/attachments/20141217/e3a9660e/attachment.html>

More information about the varnish-dev mailing list