-
Notifications
You must be signed in to change notification settings - Fork 24
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
maintenance, fork/copies #25
Comments
Hi Laurent,
Thanks for reaching out. I'm not actively supporting the codebase (I sadly
rarely code these days) and I don't think Improbable is either. If you find
it useful feel free to reuse it in whatever fashion the existing license
permits
Thanks
Michal
…On Wed, 15 Jul 2020, 22:44 Laurent Demailly, ***@***.***> wrote:
hi @mwitkow <https://github.com/mwitkow> sorry to bug you.
I was curious if I could get your permission to take some/most of the
go-flagz code and integrate it into a slightly different format (for
instance using std go flags pattern and naming, a different logging/error
handling etc...) probably as a new package in fortio (
https://github.com/fortio/fortio) obviously I would preserve your name in
the credits and copyright header but curious to get your blessing or hear
objections? (do you plan on maintaining go-flagz further? is improbable-io
going to?)
ps: if you want we can talk via email or twitter or linked in if that
feels better
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#25>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACJVNI5Y6NC4M65RBIHFKJDR3YIMFANCNFSM4O26HYVQ>
.
|
Thank you for the reply, appreciated! will do and keep the Apache-2.0 license and your initial copyright and credit. |
here is the outcome: hope it's ok |
I rewrote most of the code using generics and made additional improvements, also just moved it to a standalone package with minimal dependencies: |
hi @mwitkow sorry to bug you.
I was curious if I could get your permission to take some/most of the go-flagz code and integrate it into a slightly different format (for instance using std go flags pattern and naming, a different logging/error handling etc...) probably as a new package in fortio (https://github.com/fortio/fortio) obviously I would preserve your name in the credits and copyright header but curious to get your blessing or hear objections? (do you plan on maintaining go-flagz further? is improbable-io going to?)
ps: if you want we can talk via email or twitter or linked in if that feels better
The text was updated successfully, but these errors were encountered: