[License-discuss] Questions Regarding Open Source Hardware Licenses

[Michael Bretti]

To Russel Nelson,

Thank you very much for your suggestions and feedback. I have not heard of
The Incredible Secret Money Machine, but I will definitely look into it.
Also, I think your suggestion on extensive publication falls in line very
well already with my current activities and goals. Right now, I publish
everything I work on extensively and openly across multiple public social
media platforms in great detail, and have been working to synonymize this
new area of ultra-low cost satellite propulsion with the Applied Ion
Systems effort and branding. It does seem like people in industry are
taking notice, and being a relatively small field, word can get around
quick. I would definitely like to be successful, and I think a big part of
that is tackling this interesting grey area of open source hardware
development with a very unconventional approach from the standard accepted
practices in the field. I also feel that being very engaged and involved
with the community, as well as growing a community and following around
these efforts itself will help set this effort apart more uniquely than the
typically high barriers raised by traditional players in the field.
Ultimately, the goal is to advance accessibility of the technology so that
any sized or funding-level nanosatellite team has an opportunity to learn
and work with electric propulsion, as well as students and the
hobbyist/maker community. And a big piece of that is getting this work out
there and noticed. What I lack in funding, I can gain with collaboration,
sharing, and an extremely fast and efficient maker approach!

Sincerely,

Michael


On Fri, Mar 6, 2020 at 4:13 PM Russell Nelson <nelson at crynwr.com> wrote:

> On 3/4/20 2:30 PM, Michael Bretti wrote:
> > 4. How can open source innovation be protected? Especially in my case
> > were I am working on very high-tech systems in a highly competitive,
> > and normally very secretive and non-transparent field, how can I make
> > sure that I get credit, or protect myself from others patenting my
> > designs, and ultimately using them against me, or worst case,
> > completely legally locking me out of working on them myself?
>
> Publish, publish, publish. The better-known your innovation becomes, the
> harder it is for someone to take credit from you or patent your design.
>
> Basically, be successful. That works for two reasons. First, that's what
> you want to do. Second, the more successful you are, the less likely it
> will be that someone will try to steal your ideas. They'll think they
> can do better than you. They'll view your ideas as a challenge to them,
> and they will be unwilling to use your ideas. Lastly, if your idea is
> *really* good, you'll have to push it on people.
>
>
>
> _______________________________________________
> License-discuss mailing list
> License-discuss at lists.opensource.org
>
> http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org
>

On Fri, Mar 6, 2020 at 4:13 PM Russell Nelson <nelson at crynwr.com> wrote:

> On 3/4/20 2:30 PM, Michael Bretti wrote:
> > 4. How can open source innovation be protected? Especially in my case
> > were I am working on very high-tech systems in a highly competitive,
> > and normally very secretive and non-transparent field, how can I make
> > sure that I get credit, or protect myself from others patenting my
> > designs, and ultimately using them against me, or worst case,
> > completely legally locking me out of working on them myself?
>
> Publish, publish, publish. The better-known your innovation becomes, the
> harder it is for someone to take credit from you or patent your design.
>
> Basically, be successful. That works for two reasons. First, that's what
> you want to do. Second, the more successful you are, the less likely it
> will be that someone will try to steal your ideas. They'll think they
> can do better than you. They'll view your ideas as a challenge to them,
> and they will be unwilling to use your ideas. Lastly, if your idea is
> *really* good, you'll have to push it on people.
>
>
>
> _______________________________________________
> License-discuss mailing list
> License-discuss at lists.opensource.org
>
> http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20200306/29d8e6cb/attachment-0001.html>