OK, cool. In future then, should I email yourself with patches and CC openwrt-devel as well?
On Sat, 2016-02-13 at 02:48 +0100, pau wrote: > Hey I just said this is how we normally work. If you don't want to use > github, I (or other people from openwrt-routing) can apply your patch. I > never refused this option, the pull request is just more confortable. > > On 13 febrer de 2016 1:09:38 CET, Bob Ham <r...@settrans.net> wrote: > >On Fri, 2016-02-12 at 20:52 +0100, Pau wrote: > >> Please, fork the project in github and send a pull request. This is > >the > >> way we normally work in openwrt-routing. > > > >GitHub is a problem because it's proprietary. Are you refusing to > >apply > >patches unless they come from GitHub pull requests? Because if so, > >that's a real big problem. By requiring that contributors use > >proprietary development tools, it undermines our freedom. There is a > >good essay about this by Benjamin Mako Hill: > > > > https://mako.cc/writing/hill-free_tools.html > > > > > >The openwrt.org organisers have infrastructure for mailing lists and I > >imagine they would be open to hosting lists for feed projects. Would > >the routing group be willing to make use of a development mailing list > >if openwrt.org offered to host one for them? That way you could accept > >contributions for the routing feed without requiring the use of GitHub > >but also without having to monitor the main, high-volume openwrt-devel > >mailing list. > > > >I've CC'd the openwrt-devel list again in this email as I would expect > >the administrators of openwrt.org will be present and I hope they might > >be willing to chime in. > > > >Kind regards, > > > >Bob Ham >
signature.asc
Description: This is a digitally signed message part
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
