OpenSees Cloud
OpenSees AMI
El viejo y los mares abiertos
Original Post - 28 Aug 2022 - Michael H. Scott
Visit Structural Analysis Is Simple on Substack.
Although most of the posts in this blog are about OpenSees, the blog is not affiliated with UC Berkeley, who retains the copyright to OpenSees. Because it is free to use for research and education, some people feel they can do whatever they want with OpenSees, even for commercial purposes, despite an easy to understand copyright statement. This is not my problem.
But the blog–all the words, all the code, and all the figures–is my jawn.
From the instant I hit “Publish”, I hold the copyright to every post. Let’s see what that means through a few examples:
- You want to link to a post from your personal, research, education, or even commercial website? No problem, go right ahead!
- You want to share a post with your Twitter, LinkedIn, or other social media platform followers? Yes, no problem! Just add a little bit of context to your post and @ me if you would like.
- You want to copy Python code from a post and use it in your scripts? No problem, go for it! I only use snippets in the posts anyway as fully functional blocks of code would make the posts unbearably long and boring.
- You want to copy a figure from a post and use it on your website, in a document, or in a presentation? You can do that only if you provide a citation and a live URL back to the source post. Give full credit.
- You want to make a video where you show a post in its original form and do a voice over explanation in English or in another language? No problem, that would be cool! But also provide a live URL back to the source post.
- You want to re-post my posts in another language, using Google Translate? No, you cannot do that without my permission.
- You want to re-post my posts in another language, but do the translation yourself because Google Translate cannot handle general purpose nouns like “jawn” or titles like “More than You or Eigen Chew”? No, you cannot do that either, not without my permission.
If the foregoing list does not contain your planned use case, ask about it and let’s discuss.
These situations do arise though. Recently, someone asked if they can translate my posts to another language and re-post their version on their website. I said “No”, but offered alternatives. I also found someone who re-posted Google Translated versions of my posts on their website. I left them an informal cease and desist order in the comments section and the posts were removed. Thanks for not ignoring me!
As a real world common sense example, my copy of El viejo y el mar was written by Ernest Hemingway; la traducción fue escrito por Lino Novás Calvo–él no es el autor. No, I’m not comparing my work to Hemingway’s.
I’m not naïve though. I know that for every one that asks, there are ten more that don’t. And for every one that I find, there are ten more that I won’t.
The odds of discovery are low and the consequences are not enforceable. I only ask that you apply a little common sense and decency before you decide to build Portugal Digital “from the ground up” and claim the work as your own.