[VOTE] Use GitHub issues instead of bugs.openwrt.org

Fernando Frediani fhfrediani at gmail.com
Wed Jan 19 13:38:05 PST 2022

Although the user interface to report issues from GitHub is nice and 
easy to use one thing I really don't like about it is that Microsoft 
seems to not be concerned at all in bringing IPv6 support to it.

Some may say that is a minor thing but I am one of those who believe 
people who understand there is still a general neglect about IPv6 to 
"leave it for another time" should refuse to use products that still 
don't support IPv6 until they do. I think there are no much 
justifications that can be used for not having it at this stage in 2022.
I know also some people only want to use a tool they are used to and 
don't care about IPv6, but I still believe in the refuse to use as a way 
to send a message to those who didn't organize themselves enough to have 
IPv6 fully available on their services.

As such other platforms mentioned in other messages that support it 
would very good candidates comparing themselves by other features.


On 19/01/2022 13:25, Petr Štetiar wrote:
> Paul Spooren <mail at aparcar.org> [2022-01-19 10:59:50]:
> Hi Paul,
>> A migration of existing issues is not planed, instead new issues should be
>> created.
> so we're going to start from scratch just because of that API request limit
> (I've read about in your other email)?  Or is there anything else preventing
> us to migrate all issues to the new platform of choice? AFAIR you was able to
> migrate all issues, even closed ones, during our evaluation of GitLab[1].
>> [X] No, please find another solution
> I prefer to use, improve and promote FOSS solutions.
> 1. https://gitlab.com/openwrt/gitlab-evaluation/-/blob/master/flyspray/fs2gitlab.py
> Cheers,
> Petr
> _______________________________________________
> openwrt-adm mailing list
> openwrt-adm at lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-adm

More information about the openwrt-adm mailing list