On Fri, Jan 7, 2022 at 1:38 AM Paul Spooren <m...@aparcar.org> wrote: > > Hi all, > > Back at the Hamburg meeting in 2019 and a succeeding vote we decided to > migrate over to a self-hosted GitLab instance. Some years passed and nothing > really happened so I’d like to give this another go. > > None of the OpenWrt project members is willing to setup and maintain a GitLab > instance and there were multiple vetos again gitlab.com. > > Our current bug tracker at bugs.openwrt.org is used by a minority of users > (and devs), all community repositories (LuCI, packages, …) use GitHub for > issue tracking. Instead of maintaining flyspray and the server, I’d like to > export all flyspray issues, migrate them to GitHub and open GitHub issues for > openwrt/openwrt to the public. A static or read-only version of flyspray > could be hosted for the near future. > > Secondly I’d like to give the CI of the main repository another go. Our CI to > build Docker images is currently on gitlab.com, I’d migrate that over to > GitHub. Also I’d suggest to add similar CI checks as added to the packages > (and routing and video and LuCI) repository. We could compile targets and > tooling, check checksums etc, even build snapshots to lower the resource > usage of our Buildbot infrastructure. > > During a recent _poll_ in #openwrt-adm multiple members liked the idea, > however before doing or voting on anything, I’d like to ask for more comments. +1 for github.
https://www.gnu.org/software/repo-criteria-evaluation.html seems to be complete garbage. Seems the higher the criteria, the less users. > > Thanks for all feedback, > Paul > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
