Copyright notice from HomeSeer: Please take this repo down

[jldubz]

Hello,

This content is currently copyrighted material from HomeSeer which has been redistributed using an open-source MIT license which it was not originally distributed with. This material is not permitted to be redistributed in this manner, and we would appreciate it if you would take this repository down as soon as possible.

We are publishing new content to GitHub and NuGet and would like to avoid confusing anyone about what is official and what is not.

Thank you.

Regards,

The HomeSeer team.

[alexdresko]

Please explain specifically which material I need to bring down and I'll comply (if it makes sense). I've written most of this myself, so back off with your blanket "take this repo down" stuff. It's not going to happen.

[alexdresko]

Also, try being nice. You'll get further.

[jldubz]

The code contained within Connector.cs, HSPIBase.cs, HSPIBase2.cs, and Options.cs was taken directly from HomeSeer published content. I can map a one-to-one relationship with that code and HomeSeer code.

This request has been made with the interest of avoiding confusing people in the community. If this is something you do not care about, that is fine. I will follow up with a DMCA takedown request with GitHub directly. My apologies for asking you first.

[alexdresko]

Where does it say that Connector.cs, HSPIBase.cs, HSPIBase2.cs, and Options.cs is copyright material and what about all of the other instances of this code on github? Are you having those taken down as well?

I'm not against doing what is right. I just need to make sure I do the right thing. And taking this repo down drastically undermines the community's desire for easier HS3 plugin development.

Don't make HS out to be a jerk of a company. I'm a respectful developer, but there's just too much work here that has nothing to with your copyright claims. I'd like to figure out how to resolve this in a win-win scenario.

[alekslyse]

So this mean people who developed open source plugins with this framework now will get a DMCA from HS?

[alexdresko]

@alekslyse right? That's what I'm wondering.

[jldubz]

There is a difference between the content distributed by HomeSeer for the purpose of plugin development and a package that redistributes that same content without giving credit to the original authors and then relicensed as open-sourced. This package has not been updated since November of 2018, and is severely out of date with the existing HS3 platform as it is. I looked through all of the resources I could find on this, and it all looks dead. The related help documentation and websites do not look maintained and even allude to the fact that this package is inoperable, or as you put it, disheveled.

I'm happy to open up a line of communication to continue support for this if you can point me in the direction of any currently maintained plugins that are using this package, but that support is still going to be short-lived; as this content will be deprecated in the coming months with HS4.

The development of open-source plugins using the plugin API components published by HomeSeer are not at risk at all.

[alexdresko]

a package that redistributes that same content without giving credit to the original authors and then relicensed as open-sourced

But I thought I did provide the source of that code. Is there something else I need to do to provide the valid credit necessary?

The related help documentation and websites do not look maintained and even allude to the fact that this package is inoperable, or as you put it, disheveled.

My repo's activity (or at least the activity that can be measured) doesn't have anything to do with this copyright claim.

Your original desire was that developers not get confused with the new that's being published. It would be really easy to make sure developers aren't confused without resorting to taking down a large body of work.

[alexdresko]

I'm happy to open up a line of communication to continue support for this if you can point me in the direction of any currently maintained plugins that are using this package,

Also doesn't matter.

[jldubz]

I'd really like to avoid mincing words here in an unproductive back-and-forth with you. I apologize if I was coming across as rude in the initial request, but I fail to see how this was the case when the request was made using phrases like, "we would appreciate it if you would..."

There was no ultimatum established or communicated in the original post, and yet you reacted as if there was.

I am entirely sympathetic to the desire to not throw away work and am not opposed to you restructuring the package to make its use clearer if you are interested in having a civil discussion. You have not given me the impression that you are interested in working WITH us to get to a win-win scenario. You have repetitively responded with rudeness.

[dpmurphy]

I use it in the mysensors plugging.......while not in the updater is posted in the forums and being used.

I also am aware of moskus c# example version of the HS basic plugin uses it....

On Sep 6, 2019, at 2:18 PM, Alex Dresko notifications@github.com wrote:

a package that redistributes that same content without giving credit to the original authors and then relicensed as open-sourced

But I thought I did https://hspi.readthedocs.io/en/latest/features.html#vb-net provide the source of that code. Is there something else I need to do to provide the valid credit necessary?

The related help documentation and websites do not look maintained and even allude to the fact that this package is inoperable, or as you put it, disheveled.

My repo's activity (or at least the activity that can be measured) doesn't have anything to do with this copyright claim.

Your original desire was that developers not get confused with the new that's being published. It would be really easy to make sure developers aren't confused without resorting to taking down a large body of work.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/alexdresko/HSPI/issues/111?email_source=notifications&email_token=ABEDFAHPC6EUHJSAZ7HJHQLQIKNGFA5CNFSM4IUK5J42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6DUZAY#issuecomment-528960643, or mute the thread https://github.com/notifications/unsubscribe-auth/ABEDFAF2CZIB567E2QWIOALQIKNGFANCNFSM4IUK5J4Q.

[alexdresko]

There was no ultimatum established or communicated in the original post, and yet you reacted as if there was.

I interpreted it as an ultimatum.

I am entirely sympathetic to the desire to not throw away work and am not opposed to you restructuring the package to make its use clearer if you are interested in having a civil discussion. You have not given me the impression that you are interested in working WITH us to get to a win-win scenario. You have repetitively responded with rudeness.

I said, "I'd like to figure out how to resolve this in a win-win scenario." and "I'm not against doing what is right." and "Is there something else I need to do to provide the valid credit necessary?"

You said, "Please take this repo down".

Now that we're on the same page about not removing the whole repo, please just tell me what you would like to see changed, specifically, as a developer would want to read.

[dpmurphy]

Also this active thread is another layer....

https://forums.homeseer.com/forum/developer-support/programming-plug-in-development/1289533-yet-another-hspi-plugin-library https://forums.homeseer.com/forum/developer-support/programming-plug-in-development/1289533-yet-another-hspi-plugin-library

Jon all of these activities spawned from a need to make it easier to use HS plugin API....and different folks had slightly different spins on how best to achieve this.

Dan. PS I didn’t develop any of this, I just happily used it, and I don’t want to get into a spat, but you asked who might be using it....

On Sep 6, 2019, at 2:42 PM, Alex Dresko notifications@github.com wrote:

You also said, "if this is something you do not care about, that is fine. I will follow up with a DMCA takedown request with GitHub directly. My apologies for asking you first."

Were you really trying to be friendly there?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/alexdresko/HSPI/issues/111?email_source=notifications&email_token=ABEDFAB2R3KXJATI3FKYJ6TQIKQAXA5CNFSM4IUK5J42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6DW3YA#issuecomment-528969184, or mute the thread https://github.com/notifications/unsubscribe-auth/ABEDFABJSQ5WEVKMGLSVPUDQIKQAXANCNFSM4IUK5J4Q.

[alexdresko]

And while we're talking about it, I'll be one of those people who updates to HS4. If I personally do not like the HS4 API and I want to make it easier for other HS4 developers to create plugins, what is the appropriate way to do that?

[oesolberg]

Even though this code has not been touched in a while it still works when developing a plugin for HomeSeer. I have maded 4 plugins so far and they run fine on my machine with the latest version of HomeSeer.

[jldubz]

Dan,

I'm not interested in a spat either. I want to understand the playing field, and I want to have a civil discussion.

Thank you for providing this information.

Believe me, I totally understand the desire to make HS3 plugin development easier, and it looks like I did not dig far enough to determine how popular this package was. The last updates I see are calling this "disheveled," and that sounds like this is not currently helpful to many people if anyone at all. I apologize for miscommunicating and misreading the situation.

I would like to make it very clear that this was not a "ban-hammer" approach to the repo, and I am sure you can understand a request to take something, that actively looks under-maintained and out-of-date, out of the central circulation of resources used by plugin developers using the only mechanism we have to do such a thing: copywrite infringement claims.

I love open-source and am an avid supporter of it. I am personally taking it upon myself to make the entire PluginSDK for HS4 open-sourced because I believe it will benefit everyone. @alexdresko I will be sure to link you to that as soon as it is up so you can help contribute to shaping it according to how you feel developers will want to use it.

For the time being, please clearly denote that this is for HS3 development ONLY and properly link to related source material from HomeSeer, such as https://homeseer.com/developer-support/ which links to all of the resources a developer may need to get going with HS3 plugin development. We would also appreciate it if you provided a link from your readme to the HomeSeer website so people know what platform this is for and see that you are extending content provided through HomeSeer.

[alexdresko]

Thank you. This was nicely written.

I am sure you can understand a request to take something, that actively looks under-maintained and out-of-date, out of the central circulation of resources used by plugin developers using the only mechanism we have to do such a thing: copywrite infringement claims.

I get it. You have a product, and an "image", and you're trying to make money. And my efforts show up more significantly because I snagged the "homeseer" nuget package. And my repo pops up first in GH when you search homeseer. But I see that I haven't made it clear enough that it's not official code. I chose those names because, for years, there was no OSS activity from the official HS team, so I didn't ever think it would matter. I get that you want to be first.

But I'm glad there are better options, now.

I will comply with these requests over the weekend:

• clearly denote that this is for HS3 development ONLY

• properly link to related source material from HomeSeer, such as https://homeseer.com/developer-support/ which links to all of the resources a developer may need to get going with HS3 plugin development

• [provide] a link from your readme to the HomeSeer website so people know what platform this is for and see that you are extending content provided through HomeSeer.

• I will try to rename the repo and assets to reflect the fact that it's for HS3

And I'm excited about the future of HS4.

[dpmurphy]

Sound good guys looking forward to HS 4

On Sep 6, 2019, at 3:48 PM, Alex Dresko notifications@github.com wrote:

Thank you. This was nicely written.

I am sure you can understand a request to take something, that actively looks under-maintained and out-of-date, out of the central circulation of resources used by plugin developers using the only mechanism we have to do such a thing: copywrite infringement claims.

I get it. You have a product, and an "image", and you're trying to make money. And my efforts show up more significantly because I snagged the "homeseer" nuget package. And my repo pops up first in GH when you search homeseer. But I see that I haven't made it clear enough that it's not official code. I chose those names because, for years, there was no OSS activity from the official HS team, so I didn't ever think it would matter. I get that you want to be first.

But I'm glad there are better options, now.

I will comply with these requests over the weekend:

clearly denote that this is for HS3 development ONLY

properly link to related source material from HomeSeer, such as https://homeseer.com/developer-support/ which links to all of the resources a developer may need to get going with HS3 plugin development

[provide] a link from your readme to the HomeSeer website so people know what platform this is for and see that you are extending content provided through HomeSeer.

And I'm excited about the future of HS4.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.