Let's merge

[konsumer]

Hi,
I published mindwave and you published mindwave2. It's been years since I worked with it, but I just got a support-request via email, and realized there is kind of a cluster of a mess around link-back and support. You submitted a PR to my repo that makes npm show your repo as the source for the package I published, but I am pretty sure I wrote the original code in my repo. You also removed the fork marker from the github repo, which obfuscates track-back for people trying to figure out "Who made this?"

Here is the merge I propose:

• Update mindwave2 on npm to point back to mindwave in README ("deprecated: use mindwave instead")
• You archive your github fork (that isn't marked as a fork) with deprecation stuff in README
• I merge any unmerged updates you have into git repo I think they are all in the original PR, and probly outdated, but we should get it all up-to-date, in either case
• I make you a maintainer of my repo so you have control of updates and can help with support, if you want.
• I publish changes to npm, so it points back to our shared repo and has all the updates it needs

It's probably not intentional, but it really feels like you were trying to strip my authorship from the library, by forking and removing the fork-linkage in github, and publishing on npm as a new package, also by modifying how package.json points back to your repo, not mine. I'm fully willing to assume this was all a series of innocent mistakes, I could see how it could happen unintentionally, for sure.

In the future, let's just totally co-maintain it in a shared repo, and we can communicate with each other directly, if we need to make changes, and little things like deps can just be updated and published.

[konsumer]

For now, I'm going to make sure mindwave is up-to-date in my repo, make the change back in package.json, and re-publish it, but I sincerely hope we can merge the 2, as it's just confusing for end-users, with no real benefit.

[elsehow]

Thank you for opening this issue, @konsumer.

It's probably not intentional, but it really feels like you were trying to strip my authorship from the library, by forking and removing the fork-linkage in github, and publishing on npm as a new package, also by modifying how package.json points back to your repo, not mine. I'm fully willing to assume this was all a series of innocent mistakes, I could see how it could happen unintentionally, for sure.

That was absolutely not my intention, and I am so sorry that my actions gave you that impression. I was (1) unaware with the norms around fork-linkage (I will have to educate myself on this term, which is unfamiliar to me) and (2) needed to solve a particular problem in a hurry, which caused me to take less care in reaching out to you (and educating myself about norms around forks) than you deserved. I hope you'll accept my apologies.

In the future, let's just totally co-maintain it in a shared repo, and we can communicate with each other directly, if we need to make changes, and little things like deps can just be updated and published.

Yes, I am happy to co-maintain this repo with you, and thank you for the offer.

• Update mindwave2 on npm to point back to mindwave in README ("deprecated: use mindwave instead")
• You archive your github fork (that isn't marked as a fork) with deprecation stuff in README

I will do this as soon as I can - probably North America's tomorrow, but EOW at the latest.

• I merge any unmerged updates you have into git repo I think they are all in the original PR, and probly outdated, but we should get it all up-to-date, in either case
• I make you a maintainer of my repo so you have control of updates and can help with support, if you want.
• I publish changes to npm, so it points back to our shared repo and has all the updates it needs

These sound like items you can do without my help, but please let me know if that's not the case.

Thank you again. This is a great learning experience for me, and I appreciate your understanding---and benefit of the doubt. I look forward to co-maintaining this repo with you!

[konsumer]

These sound like items you can do without my help, but please let me know if that's not the case.

Yep, totally. Working on it now.

Thank you again. This is a great learning experience for me, and I appreciate your understanding---and benefit of the doubt. I look forward to co-maintaining this repo with you!

Totally! Completely understand. I'll add you now.

[konsumer]

There is also a npm deprecate command to checkout, which will log a message when a user tries to install it. Might be a good idea for mindwave2.

I think the syntax will be this:

npm deprecate mindwave2@1.0.0 "Development is dead here. Use mindwave package, instead."

[konsumer]

Ok, everything is updated, with 0 vuln-warnings and all latest libs, and I added you as a co-maintainer. Feel free to close this issue when the other stuff is done.

[konsumer]

I also added you as a co-owner on npm (you might have to click a verify link in email) so you can even publish to npm mindwave.