New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Community engagement for adoption of our fork #68
Comments
Seems worth considering for sure, even today. There are real bug fixes in
`gofrs/uuid` that those consumers should want.
…On Wed, Jan 30, 2019, 10:35 AM Tim Heckman ***@***.***> wrote:
This is an issue to gather input about doing an engagement of some larger
projects who use github.com/satori/go.uuid to get them moved over to our
repo. Should we wait until the Modules stuff shakes out/we cut the next
major version?
The idea would be to open issues on the projects, at a minimum, to suggest
they change. We could additionally then issue PRs, time permitting, to some
of those projects to update them to point to us. All worth considering /
discussing.
@gofrs/all <https://github.com/orgs/gofrs/teams/all> thoughts?
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
<#68>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQ9re-drBjE6r_71KOq8VMqdQBBYNgzaks5vIcm-gaJpZM4aalkj>
.
|
Let's start here: https://godoc.org/github.com/satori/go.uuid?importers |
Go modules are not experimental anymore. That was the first thing I noticed when looking for a uuid package/module on I know this doesn't have anything to do with the project's actual implementation, and in fact, if this project has moved forward and implemented more RFCs, it should have enough appeal to have users of the original repo switch. Maybe you guys could open an issue on those repos asking for them to consider moving. |
Like what? |
Sorry, I just saw you guys implement the same RFCs. I thought this project implemented more, but in reality it improves upon the original repo. To me that is reason enough to open an issue on projects that could move to using this fork. |
This is an issue to gather input about doing an engagement of some larger projects who use
github.com/satori/go.uuid
to get them moved over to our repo. Should we wait until the Modules stuff shakes out/we cut the next major version?The idea would be to open issues on the projects, at a minimum, to suggest they change. We could additionally then issue PRs, time permitting, to some of those projects to update them to point to us. All worth considering / discussing.
@gofrs/all thoughts?
The text was updated successfully, but these errors were encountered: