Policy on replacing a link? #132

New Issue

2025-11-06T15:07:23-06:00

GiteaMirror commented

2025-11-06 15:07:23 -06:00

Originally created by @vmbrasseur on GitHub (Sep 23, 2017).

The Speaking entry currently points to matteofigus' repo, but the Public_Speaking repo is more comprehensive (and in fact includes the matteofigus one) and also comes with a community for providing assistance.

Is there a policy about replacing a link? I don't see one in contributing.md, but perhaps it's elsewhere?

Originally created by @vmbrasseur on GitHub (Sep 23, 2017). The Speaking entry currently points to [matteofigus' repo](https://github.com/matteofigus/awesome-speaking), but the [Public_Speaking repo](https://github.com/vmbrasseur/Public_Speaking) is more comprehensive (and in fact includes the matteofigus one) and also comes with a community for providing assistance. Is there a policy about replacing a link? I don't see one in contributing.md, but perhaps it's elsewhere?

GiteaMirror commented

2025-11-06 15:07:25 -06:00

@sindresorhus commented on GitHub (Oct 11, 2017):

Maybe you and @matteofigus can find a way to work together?

@sindresorhus commented on GitHub (Oct 11, 2017): Maybe you and @matteofigus can find a way to work together?

GiteaMirror commented

2025-11-06 15:07:25 -06:00

@matteofigus commented on GitHub (Oct 11, 2017):

Hi, thanks for tagging me @sindresorhus.

This is the first time I hear about this repo, it's good, well done! @vmbrasseur what do you recon being the best way to collaborate on this?
In the meanwhile, would it be possible to include both links?

@matteofigus commented on GitHub (Oct 11, 2017): Hi, thanks for tagging me @sindresorhus. This is the first time I hear about this repo, it's good, well done! @vmbrasseur what do you recon being the best way to collaborate on this? In the meanwhile, would it be possible to include both links?

GiteaMirror commented

2025-11-06 15:07:25 -06:00

@vmbrasseur commented on GitHub (Oct 17, 2017):

Including both sounds good, but that's @sindresorhus's call to make.

@matteofigus, I'm likely just to focus on my one repo. We have a community growing up around it (#public_speaking on Freenode) and have started adding translations (pt-br so far, es-mx planned). We welcome collaborators & pull requests, though, if you're interested in merging and joining our community?

@vmbrasseur commented on GitHub (Oct 17, 2017): Including both sounds good, but that's @sindresorhus's call to make. @matteofigus, I'm likely just to focus on my one repo. We have a community growing up around it (#public_speaking on Freenode) and have started adding translations (pt-br so far, es-mx planned). We welcome collaborators & pull requests, though, if you're interested in merging and joining our community?