[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Call to NOT move to github or gitlab
From: |
Ricardo Bánffy |
Subject: |
Re: Call to NOT move to github or gitlab |
Date: |
Sun, 12 Jun 2022 09:11:07 +0100 |
On Sat, Jun 11, 2022 at 8:43 PM Thomas Dickey <dickey@his.com> wrote:
> I find and fix almost all of the issues.
I think this would be the strongest reason to lower entry barriers by
adopting a workflow that's friendly towards the younger audience -
it's not easy to file or fix issues and, maybe, there is someone out
there who could help but just doesn't have the time to understand how.
I know there are a lot of drawbacks in changing workflows, but I'm
glad we are having this discussion. Even if nothing changes, at least
we have explored options and understand the reasoning behind them.
- Re: Call to move to github or gitlab, (continued)
- Re: Call to move to github or gitlab, Benno Schulenberg, 2022/06/09
- Re: Call to move to github or gitlab, Tomasz Kłoczko, 2022/06/09
- Re: Call to move to github or gitlab, Dennis Clarke, 2022/06/09
- Re: Call to NOT move to github or gitlab, Benno Schulenberg, 2022/06/10
- Re: Call to NOT move to github or gitlab, Dennis Clarke, 2022/06/10
- Re: Call to NOT move to github or gitlab, Steve Litt, 2022/06/10
- Re: Call to NOT move to github or gitlab, Ricardo Bánffy, 2022/06/10
- Re: Call to NOT move to github or gitlab, Steve Litt, 2022/06/10
- Re: Call to NOT move to github or gitlab, Bill Gray, 2022/06/11
- Re: Call to NOT move to github or gitlab, Thomas Dickey, 2022/06/11
- Re: Call to NOT move to github or gitlab,
Ricardo Bánffy <=
- Re: Call to NOT move to github or gitlab, Thomas Dickey, 2022/06/12
- Re: Call to NOT move to github or gitlab, Thomas Dickey, 2022/06/12
- Re: Call to NOT move to github or gitlab, Thomas Dickey, 2022/06/12
- Re: Call to move to github or gitlab, Dennis Clarke, 2022/06/09