[rancid] Collaborative development for rancid (e.g. git / github)

[Buchan Milne]

Is there a reason why the development of rancid is not done in a more
collaborative fashion?

Having submitted a basic fix, and not knowing what it's future will be,
I checked to see if there is a public VCS repository for rancid. I
searched on github, and found that there were a few repositories created
by users who imported some version of rancid, some with a few commits,
but some with a few hundred:

https://github.com/dotwaffle/rancid-git
https://github.com/reca/rancid
https://github.com/ssinyagin/rancid-ssi
https://github.com/supine/rancid-bzr-git-multihop
https://github.com/jahkeup/rancid3-git
https://github.com/jalmeida/rancid-3.1
https://github.com/codeout/rancid
https://github.com/onlight/rancid

There are also a few git repos on github that just contain additional
scripts for rancid:

https://github.com/JeroenvHeugten/rancid-huawei
https://github.com/b225ccc/rancid-linerate
https://github.com/ajschroeder/rancid


And in other git repos too:
https://bitbucket.org/aquerubin/rancid-vyatta


Wouldn't it make sense to have a public repo for rancid, preferably git,
and if there is no other infrastructure planned, github is probably the
easiest.

I see someone at Facebook has also made a tac_plus repo:
https://github.com/facebook/tac_plus



Regards,
Buchan

[Nick Hilliard]

Post by Buchan Milne
Wouldn't it make sense to have a public repo for rancid, preferably git,
and if there is no other infrastructure planned, github is probably the
easiest.

couldn't agree more.

Nick

[Alex DEKKER]

Post by Buchan Milne
Wouldn't it make sense to have a public repo for rancid, preferably git,
and if there is no other infrastructure planned, github is probably the
easiest.

Did this ever get anywhere? I want to work on adding a new device type
and would like to start with the latest source.

alexd

[heasley]

Post by Alex DEKKER

Post by Buchan Milne
Wouldn't it make sense to have a public repo for rancid, preferably git,
and if there is no other infrastructure planned, github is probably the
easiest.

Did this ever get anywhere? I want to work on adding a new device type
and would like to start with the latest source.
alexd

We have decided, today, that we will make available an interface to the
repo. I first need to separate some proprietary info from the repo that
can not be made public.

We need to decided which method is easiest for us; it will either be an
interface to the svn repo, to which git has a builtin "bridge" as git
calls it in the docs, or i'll push to github on a regular basis.

In the meantime, ftp://ftp.shrubbery.net/pub/rancid/alpah/ is kept
reasonably up to date with HEAD.

[Alex DEKKER]

Post by heasley
We have decided, today, that we will make available an interface to the
repo. I first need to separate some proprietary info from the repo that
can not be made public.
We need to decided which method is easiest for us; it will either be an
interface to the svn repo, to which git has a builtin "bridge" as git
calls it in the docs, or i'll push to github on a regular basis.
In the meantime, ftp://ftp.shrubbery.net/pub/rancid/alpah/ is kept
reasonably up to date with HEAD.

Great stuff!

alexd

[Jason Biel]

Github would be the best idea. Would easily allow for syncing of module
changes/additions for devices.

Post by heasley
We have decided, today, that we will make available an interface to the
repo. I first need to separate some proprietary info from the repo that
can not be made public.
We need to decided which method is easiest for us; it will either be an
interface to the svn repo, to which git has a builtin "bridge" as git
calls it in the docs, or i'll push to github on a regular basis.
In the meantime, ftp://ftp.shrubbery.net/pub/rancid/alpah/ is kept
reasonably up to date with HEAD.
Great stuff!

alexd
_______________________________________________
Rancid-discuss mailing list
http://www.shrubbery.net/mailman/listinfo/rancid-discuss

[Jason Biel]

Any progress on this?

Post by Jason Biel
Github would be the best idea. Would easily allow for syncing of module
changes/additions for devices.

Post by heasley
We have decided, today, that we will make available an interface to the
repo. I first need to separate some proprietary info from the repo that
can not be made public.
We need to decided which method is easiest for us; it will either be an
interface to the svn repo, to which git has a builtin "bridge" as git
calls it in the docs, or i'll push to github on a regular basis.
In the meantime, ftp://ftp.shrubbery.net/pub/rancid/alpah/ is kept
reasonably up to date with HEAD.
Great stuff!

alexd
_______________________________________________
Rancid-discuss mailing list
http://www.shrubbery.net/mailman/listinfo/rancid-discuss

--
Jason

[heasley]

Post by heasley

Post by Alex DEKKER

Post by Buchan Milne
Wouldn't it make sense to have a public repo for rancid, preferably git,
and if there is no other infrastructure planned, github is probably the
easiest.

Did this ever get anywhere? I want to work on adding a new device type
and would like to start with the latest source.
alexd

We have decided, today, that we will make available an interface to the
repo. I first need to separate some proprietary info from the repo that
can not be made public.
We need to decided which method is easiest for us; it will either be an
interface to the svn repo, to which git has a builtin "bridge" as git
calls it in the docs, or i'll push to github on a regular basis.

I tried doing this by checkout with git svn from the canonical repo and
pushing to github, but this had some unpleasant side-effects that did
not seem easily resolved (and I dont have time to screw with this
endlessly) and ultimitely I expect would just create grief if we switched
to git later. I could push the trunk only to github (no tags, no branches),
if enough folk are interested.

The svn dav is available here:
dev head: http://rancid.shrubbery.net/rancid/svn/rancid/trunk/rancid
release tags: http://rancid.shrubbery.net/rancid/svn/rancid/tags

If you must have your git, you can use git svn against the svn dav;
eg: git svn clone http://rancid.shrubbery.net/rancid/svn/rancid
If we migrate the repo to git in the future, we'll push to github.