CircuitPython working on the PicoCalc

[Neusse]

nothing to see here any more

[DNSGeek]

This looks really cool. I’m looking forward to trying this out.

[jblanked]

Make sure to give credit where credit is due.

[jblanked]

What I meant is, you’re just copying files from Picoware. It’d be courteous to at least source where you got it from at the top of the file or mention in the README where you got it from.

If you were just going to copy most of Picoware, you should just fork the repository and submit pull requests.

[Neusse]

Just so it is clear to everyone. Nothing in my repo is compatible or can be used in PicoWare or vice versa. Nothing written for CircuitPython like is shown here is capable of running in the PicoWare ecosystem in any way. CircuitPython is not compatible with MicroPython especially with displaying graphics.

[jblanked]

@Neusse

I did not copy/paste Picoware files and “convert” them line-for-line

src/MicroPython/picoware/system/LED.py

vs

lib/picocalc_led.py

[jblanked]

@Neusse

Just so it is clear to everyone. Nothing in my repo is compatible or can be used in PicoWare or vice versa.

@Neusse

I did not copy/paste Picoware files and “convert” them line-for-line.

@Neusse

The CircuitPython pieces (display/input flow, how the loop runs, how it chains from my launcher and returns, etc.) were built for CircuitPython and aren’t taken or even could be taken directly from Picoware.

You even have my constants file completely unchanged

Picoware/src/MicroPython/PicoCalc/picoware_keyboard at main · jblanked/Picoware

vs

Circuitpython_on_Picocalc/CircuitPython_build/usermods/picoware_CP_keyboard at...

[jblanked]

@Neusse

I did not copy/paste Picoware files and “convert” them line-for-line.

builds/MicroPython/apps_unfrozen/screensavers/spiro.py

vs

picocalc_spiro.py

I converted this one into the Arduino IDE version of Picoware many months ago, and then eventually translated it into python.

To make it worse, after you got caught, you changed the file names instead of giving proper credit

GPL 3.0 Section 4 requires you to keep intact all copyright notices. You must include attribution to the original Picoware project in the files you copied, even if you made modifications

LICENSE

DMCA

[Neusse]

the filenames changed because the source changed they are no longer picoware source files.

They now are unique and are inline with the circuitpython build.

[Codiator]

Just one question: jblanked shows identical code parts, while you say you didn’t copy anything.

How does that fit together?

[jblanked]

15 days ago

@Neusse

OK I have the southbridge working on a Circuit Python Build. I took the southbridge code from the Micro python picoware user module. I added that to Circuit Python and had to do some tweaks. I

17 hours ago

@Neusse

I did not copy/paste Picoware files and “convert” them line-for-line.

a few hours later

@Neusse

I did copy the keyboard code that allows circuitpython to talk to the keyboard.

[jblanked]

@Neusse

Nothing in my repo is compatible or can be used in PicoWare or vice versa.

@Neusse

But I did not copy line for line and pull requests would not be compatible as was suggested.

That is exactly what you did, and just changing the name of the file and/or driver name doesnt qualify it as “your work”.

bring it all under picocalc.

LICENSE

@Neusse

But after all this I will make sure there is not any of his code in my picocalc project.

Then you’ll need to delete that entire folder and write yours over by scratch, or do the just thing and add sources to the top of your file, like you mentioned you would do:

@Neusse

That said, you’re also right that if Picoware influenced my approach, I should credit it explicitly. I’ll add a clear note in the README and a short header comment in the relevant files along the lines of “inspired by Picoware’s concept/feature set” (and link to the repo), plus any license notices that apply.

[Duewester]

Dang, I was/am looking forward to Circuitpython on this. It would/will give me a reason to retrieve it from the closet.

[tabemann]

@jblanked Congratulations on successfully defending your intellectual property rights. Now we can rest well assured that we won’t end up accidentally executing code from Picoware™ except as part of Genuine Picoware Technology™.

How dare someone write anything other than purely unique code, and how dare someone use someone else’s code as a guide! And that includes things like CMakeLists.txt and listings of constants too, of course ─ there is no excuse for not always writing those from scratch. Ideally one ought to come to those from first principles, as simply seeing someone else’s CMakeLists.txt or someone else’s constants would make one’s code a derived work.

Seriously, free software licenses are an unfortunate reality necessitated only by “intellectual property rights” being foisted on us by the powers that be combined with the risk of getting sued if someone uses one’s code in a medical device or piece of heavy machinery or like that then ends up killing someone and one does not have a disclaimer. In an ideal world there would be no copyrights, no patents, and no need for disclaimers in the first place, and hence no licenses.

[Marsupial]

The Circuit Python project git is no longer available.

That’s a shame.

Did jblanked just bullied a dev out of a cool picocalc project?

[jblanked]

@tabemann

Seriously, free software licenses are an unfortunate reality necessitated only by “intellectual property rights” being foisted on us by the powers that be combined with the risk of getting sued if someone uses one’s code in a medical device or piece of heavy machinery or like that then ends up killing someone and one does not have a disclaimer. In an ideal world there would be no copyrights, no patents, and no need for disclaimers in the first place, and hence no licenses.

@Marsupial

The Circuit Python project git is no longer available.

That’s a shame.

Did jblanked just bullied a dev out of a cool picocalc project?

What? Are we reading the same thread? All I asked for is:

@jblanked

It’d be courteous to at least source where you got it from at the top of the file or mention in the README where you got it from.

I’ve given credit where due in Picoware

[adcockm]

This whole thread is strange to me. Seems like it was two people who focused more on being right or “winning” the argument than actually communicating, trying to understand each other, or sharing with the community. (Why was there even an argument to begin with?) Could have just been a polite ask for proper credit and an update to the repo. Instead it devolved into proving who was right or wrong, and also hinted at an implied urgency and distrust to it all that didn’t make sense.

Maybe it was just bad timing and everyone was already stressed out and having a bad day and being defensive. It’s a shame a petty argument that didn’t even need to be an argument caused a loss for the community. And it’s also a shame that it makes the community look far less welcoming, especially since new projects seem to have slowed down since the new year.

[maple]

not the first time jblanked bullies other devs unfortunately

[Codiator]

I see it in a more nuanced way.

Open source projects are valuable and a powerful driver of progress and better software. But intellectual property is just as important and valuable. This applies both in the direct commercial sphere and in open source projects, where the creators are at least entitled to respect and recognition as authors.

I think it’s very unfortunate when source code appears that is not correctly labeled. From what I’ve observed, that was the only thing jblanked asked for.

[jblanked]

Thank you. I don’t even understand how people see otherwise. Welcome to the community