Skip to content
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

Move to DT #19

Open
SimonSchick opened this issue Dec 2, 2017 · 15 comments
Open

Move to DT #19

SimonSchick opened this issue Dec 2, 2017 · 15 comments

Comments

@SimonSchick
Copy link

I think it would be a good idea to move this repo to DefinitelyTyped.

@dashmug
Copy link

dashmug commented Dec 4, 2017

I agree.

@moberemk
Copy link
Contributor

Any movement on this? It'd be nice to be able to install this like more traditional type libraries; alternatively the types here could be added to the core mysql2 library via PR if you're alright with that.

@tbjers
Copy link

tbjers commented Mar 15, 2018

+1

1 similar comment
@breitsmiley
Copy link

+1

@blakeembrey
Copy link
Contributor

@felixfbecker This is your decision 😄 It might make sense to authorize someone to copy the definition and hand off maintenance to DefinitelyTyped.

For everyone here, note that a lot of people in @types spent a lot of time creating high quality definitions that ultimately were incompatible with the TypeScript operating model because we don't want to work on DefinitelyTyped (hard to iterate, hard to respond to issues, giant mono repo lacking individual ownership, etc) and this resulted in a lot of burn out (especially personally, I dropped OSS for the past year).

@moberemk
Copy link
Contributor

@blakeembrey I feel you for sure on your issues with DT; that's why personally I prefer moving the definitions from here over into the actual mysql2 library. Assuming @sidorares is comfortable with that addition to the repository, I generally feel that including types with the actual package is a superior option to any external source of truth; see the neverending discussion around the Stripe library's types for an example of why.

@sidorares
Copy link

@moberemk @blakeembrey yes, happy to have type definitions in repo

@dashmug
Copy link

dashmug commented Mar 19, 2018

yes, happy to have type definitions in repo

Best news I read this morning! Thanks @sidorares!

@moberemk
Copy link
Contributor

Worth noting that, as things are now, that would mean including @types/mysql as an added dependency for mysql2. If that's not an issue then we should be good to go on this.

@melroy89
Copy link

Any update?

@sidorares
Copy link

@Danger89 I haven't done anything myself. Happy to review PRs on this

@Kosta-Github
Copy link

any updates on this one? would be very much appreciated!

@mike-marcacci
Copy link

It sounds like we've got a green light from everybody involved, and are just waiting on someone to make a PR. Is this correct @sidorares @felixfbecker?

Types for mysql2 will be needed on a large project that I'm helping modernize, so I can champion this.

As ISC and MIT are largely compatible (IANAL but this is a widely held perspective), we can probably just embed this entire codebase in a types directory and add both licenses to the mysql2 license file. However, for the sake of simplicity, @felixfbecker would you mind re-licensing this under MIT (again, IANAL but attestation here is probably sufficient) and allow us to simply use the mysql2 license as written (given its existing "and contributors" copyright) or perhaps just add your name to the copyright?

@felixfbecker
Copy link
Contributor

You're welcome to do whatever with it. Pretty sure ISC and MIT are equivalent.

@sidorares
Copy link

Is this correct

@mike-marcacci yes, I'm just observer here, happy to merge types if quality looks good enough but I'm not the best person to author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests