Consider setting up a GitHub organisation instead of hosting on a single user account

[GrahamCampbell]

This would enable expansion of the core team easily in the future, and reduce the "bus factor".

[PhilipHazel]

This is currently beyond my competence, but thanks for the suggestion.

[flyfishzy]

@GrahamCampbell I agree with you! But someone has created an organization with the same name https://github.com/PCRE .

[GrahamCampbell]

pcre2 is free. https://github.com/pcre2/pcre2 would be a good home for this.

[ltrzesniewski]

I don't really see the need for an organization unless there are several repos.

[GrahamCampbell]

The point of the organization is to indicate that it is the source of truth, and not just a repo on a single user account. Organizations can verify ownership of domains, too, another important step in indicating that the repo is the authority. People might otherwise mistake https://github.com/PCRE for the repo, and this poses a security risk.

[GrahamCampbell]

The other advantage of organizations is multiple users can be true administrators on the repo, so the longevity of a repo is not tied to a single user.

[PhilipHazel]

1. I regret that I was not aware of Git organizations when the PCRE2 repo was moved to GitHub. I'm still a pretty clueless newbie. I agree that using an organization does make sense.

2. It is almost time to think about the next release. Perhaps after that has happened (in the next month?) would be a good time to pursue this issue. There is no major development going on at the moment.

3. I am getting older (yet another birthday approaching) and won't be around for ever. It would be good to get something in place that will make it easier for others to take over in due course.

4. I hope others can help with the move when the time comes. Presumably it will have to be widely advertised as people will have to change configurations (again).

[ltrzesniewski]

Presumably it will have to be widely advertised as people will have to change configurations (again).

FYI: If you transfer the repository, GitHub will redirect old links to the new location as long as you don't create another repository at PhilipHazel/pcre2.

This means you'll have to be particularly careful not to fork the pcre2/pcre2 repository (for instance) under the pcre2 name, as that would stop the redirection taking place. This shouldn't really be a problem since you'll have write access to the repository under the organization 's account, so there should be no real need to fork.

[PhilipHazel]

I have now created an organization called PCRE2Project and transferred the pcre2 project to it.