search

rpetrich / mysqlpp

mysql++ mirror
GNU Lesser General Public License v2.1
6 stars 8 forks source link

Consider forking official mirror #3

Open tangentsoft opened 5 years ago

tangentsoft commented 5 years ago

Hi, I'm the MySQL++ maintainer. MySQL++ lives in a Fossil repository which is now mirrored on GitHub. It looks like you have only one substantial checkin here, and that's been done in the upstream project also. I suggest that you replace this unofficial mirror with a fork of my mirror so you get such improvements for free.

This GitHub mirror is just that, a mirror only, not the primary development channel, so if you have substantial improvements to commit, it's best to do them through Fossil. We have a developer's forum where you can discuss such things.

Thanks!

rpetrich commented 5 years ago

Thanks for reporting. This was originally setup to be used as a git submodule for a project that has long since ended. I think the best option is to archive this repository as read only with a readme that points to upstream. Which is the best link to provide?

rpetrich commented 5 years ago

Also, while I have you: thanks for building mysql++. It was a joy to work with!

tangentsoft commented 5 years ago

Part of the reason I've bothered you about this is that your repo was one of the top results in a web search here, which suggests people are linking to it. So, what we definitely should not do is remove this clone.

I don't have strong opinions on the question of making this repo read-only vs deleting it and forking the "official" repo under the same name to preserve the Google juice. I suggested the latter primarily because doing so works with GitHub's internal linking system: it guides users back to the main project naturally.

If you'd prefer the README-and-archive path, then point to the Fossil repo. The official project home page links back to the new GitHub mirror. That's better than pointing straight to the GitHub mirror because there's currently no link back from that to the Fossil repo.

tangentsoft commented 5 years ago

For what it's worth, the top-level MySQL++ README now points back to the Fossil home, so that is no longer a consideration in deciding the best way forward. It's also been converted to Markdown for nicer formatting.