Re: Where is the source code repo?

[Ricardo Bánffy]

I understand there is an existing process that has worked for a very long time, but, sometimes, it may be for the good of the project to adopt a tool that lowers the bar on cooperation. Can we talk about what would make this change possible?

On Fri, Jun 26, 2020 at 8:06 PM Jeffrey Walton <noloader@gmail.com> wrote:

On Tue, Jun 23, 2020 at 6:22 PM Thomas Dickey <dickey@his.com> wrote:
>
> ----- Original Message -----
> | From: "noloader" <noloader@gmail.com>
> | To: "Ncurses Mailing List" <bug-ncurses@gnu.org>
> | Sent: Sunday, June 21, 2020 8:56:09 PM
> | Subject: Where is the source code repo?
>
> | Hi Everyone,
> |
> | I can find the tarball download at
> | https://invisible-island.net/ncurses/#download_ncurses. I can't seem
> | to find the source code repo.
> |
> | Where is the source code repo?
>
> https://invisible-island.net/personal/git-exports.html

I think you are responsible for the problem listed under the section
Problems. You left a void and others filled it. This has happened time
and time again with countless projects, and it is to be expected.
Here's another example where someone squatted the GPG and GnuPG name:
https://github.com/gpg/gnupg

The excuse that using "CVS (or whatever) ... would take away
development time and be expensive" is pretty lame. I think it is
disingenuous. A well maintained public repository should get the
community involved which should free the maintainer's time.

This is pretty lame too: "Developers who use my programs are
accustomed to using patches and tarballs to track changes to these
files, using their own procedures." I want nothing to do with custom
procedures and layers of patches. I want to clone, configure and make.

You should publish your source code somewhere to avoid the problems.
You pick the place. GitHub and GitLab are popular. You also have
Savannah. Consider, if there was a public repo you'd already have a
pull request with the changes to fix the pcre2 configure problem. No
public repo, no pull request.

With a proper source code repository you can then add CI integration
so problems like missing pcre2 libraries and broken builds when using
--disable-leaks can be detected before they are released to the
public.

Jeff

--

Ricardo Bánffy
http://about.me/rbanffy