<div dir="ltr"><div>I think this is a great idea! I very much support a move to Github;
despite it's issues, it's just where development is happening today. Keeping a non-Github channel for submitting patches is also a great idea I think.<br><br>My
free-software side worries about using something non-free like <a href="http://drone.io">drone.io</a>
for CI but this is a huge task certainly and I'm not sure a free tool would meet everyone's needs (plus there's the huge added burden of maintenance).<br><br></div>Eric<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 24, 2016 at 9:06 AM, Luka Perkov <span dir="ltr"><<a href="mailto:luka@openwrt.org" target="_blank">luka@openwrt.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear OpenWrt mailing list readers,<br>
<br>
as the subject says I'd like to make proposal to move the OpenWrt<br>
codebase to Git. This was already discussed before [1] and now when<br>
there are no blockers [2] for this change I'd like that we as a<br>
community move forward with this switch.<br>
<br>
Also, I'd like to propose that we move the project to GitHub and here<br>
are the reasons why I see this as a good decision:<br>
<br>
* GitHub will allow people to contribute more easily<br>
<br>
The bigger amount of contributions has already happened and can be seen<br>
on the packages feed which is already hosted on GitHub. With this I'm<br>
also hoping to avoid comments regarding invalid patches on the mailing<br>
list.<br>
<br>
For now I am proposing that the current development workflow is also<br>
accepted - aka. patches that are sent to the mailing list are also<br>
accepted.<br>
<br>
* GitHub and similar services will allow us to integrate more easily<br>
with other projects<br>
<br>
Here specifically I mean integration with modern CI. Here is an example<br>
of integration with <a href="http://drone.io" rel="noreferrer" target="_blank">drone.io</a> [3][4]. At the moment this is only in the<br>
POC stage but what I'd like to do down the line is to:<br>
<br>
- build OpenWrt images for all architectures for every pull request<br>
<br>
- build OpenWrt package binary for every package pull request for all<br>
architectures and make it available for download<br>
<br>
- build and host OpenWrt qemu and/or Docker image for every pull request<br>
<br>
This will allow easy review of the work since flags will be shown in the<br>
pull request if the build was sucessful or not. Also, this will allow<br>
people to test changes without building the image and thus lowering the<br>
time that needs to be spent on maintenance work.<br>
<br>
If this proposal gets accepted I'll be sending out an email to get<br>
access to more build servers so this new build infrastructure can<br>
properly support the project in a timely fashion.<br>
<br>
Please share your thoughts regarding this proposal.<br>
<br>
Regards,<br>
Luka<br>
<br>
[1] <a href="https://lists.openwrt.org/pipermail/openwrt-devel/2015-October/036390.html" rel="noreferrer" target="_blank">https://lists.openwrt.org/pipermail/openwrt-devel/2015-October/036390.html</a><br>
[2] <a href="https://lists.openwrt.org/pipermail/openwrt-devel/2016-May/041329.html" rel="noreferrer" target="_blank">https://lists.openwrt.org/pipermail/openwrt-devel/2016-May/041329.html</a><br>
[3] <a href="https://github.com/makkrnic/openwrt-qemu-x86" rel="noreferrer" target="_blank">https://github.com/makkrnic/openwrt-qemu-x86</a><br>
[4] <a href="http://sartura-drone.makkrnic.com/makkrnic/openwrt-qemu-x86/5" rel="noreferrer" target="_blank">http://sartura-drone.makkrnic.com/makkrnic/openwrt-qemu-x86/5</a><br>
_______________________________________________<br>
openwrt-devel mailing list<br>
<a href="mailto:openwrt-devel@lists.openwrt.org">openwrt-devel@lists.openwrt.org</a><br>
<a href="https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel" rel="noreferrer" target="_blank">https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr">Eric Schultz, Community Manager, prpl Foundation<br><a href="http://www.prplfoundation.org" target="_blank">http://www.prplfoundation.org</a><br><a href="mailto:eschultz@prplfoundation.org" target="_blank">eschultz@prplfoundation.org</a><br>cell: 920-539-0404<br>skype: ericschultzwi<br>@EricPrpl</div></div>
</div>