[OpenWrt-Devel] [PROPOSAL] move OpenWrt codebase to Git and GitHub

Luka Perkov luka at openwrt.org
Wed May 25 12:46:27 EDT 2016

On Tue, May 24, 2016 at 10:29:30AM -0700, David Lang wrote:
> OpenWRT has already moved to using Git instead of SVN,

No, it has not. To users is exposed the Git frontend while the commits
are made to the SVN repo.

> so why do they need to move from hosting the git repository themselves to
> having it hosted on github?

See the reasons below.

> There can be a mirror of the repo on github (remember that git is a
> Decentralized VCS)

Also, we have discussed of having a mirror on our server and this is something
that we can do. If everything happens on GitHub then I don't see a point in
having clone on GitHub instead of a having the main repo on GitHub and having
clone elsewhere.

> > * GitHub and similar services will allow us to integrate more easily
> > with other projects
> > 
> > Here specifically I mean integration with modern CI. Here is an example
> > of integration with drone.io [3][4]. At the moment this is only in the
> > POC stage but what I'd like to do down the line is to:
> > 
> > - build OpenWrt images for all architectures for every pull request
> > - build OpenWrt package binary for every package pull request for all
> > architectures and make it available for download
> > 
> > - build and host OpenWrt qemu and/or Docker image for every pull request
> the build farm isn't large enough to do this

Current one is not.
> It's also not neccessary to move to github to be able to do this, it just
> needs more systems in the build farm to be able to build things fast enough.

With GitHub it will be able to see compile status of each pull request. If it
is not GitHub or simmilar service then this would need to be developed and I
think we have better things to do then that :)

> > This will allow easy review of the work since flags will be shown in the
> > pull request if the build was sucessful or not. Also, this will allow
> > people to test changes without building the image and thus lowering the
> > time that needs to be spent on maintenance work.
> > 
> > If this proposal gets accepted I'll be sending out an email to get
> > access to more build servers so this new build infrastructure can
> > properly support the project in a timely fashion.
> why should providing more build servers be contingent on moving to a
> commercial hosting provider vs running things themselves?

IMO move to GitHub will allow us to manage contributions more easily and handle
them in timely fashion. This, combined with other perks explained in my
previous email is possible today without need to develop the features that
others provide today.

openwrt-devel mailing list
openwrt-devel at lists.openwrt.org

More information about the openwrt-devel mailing list