[License-discuss] Questions Regarding Open Source Hardware Licenses

[Michael Bretti]

Nigel,

Thank you very much for your input. I hadn't thought about publishing at
something like IEEE Aerospace, but it is something certainly worth looking
into, and definitely would establish a higher level of peer-reviewed
credibility. Also, I greatly appreciate your offer to pass along my
information to others you may know in the field who might be interested in
collaboration. At this point I am very open to discussing collaboration
with others, and would certainly be willing to talk with contacts in the
field you may have.

Sincerely,

Michael


On Sat, Mar 7, 2020 at 8:36 AM Nigel T <nigel.2048 at gmail.com> wrote:

> I suggest publishing at IEEE Aerospace.  I haven’t been in a couple years
> but there were several EP papers then.
>
> You just missed an CFP on open hardware but contact the editors:
>
>
> https://www.computer.org/digital-library/magazines/mi/call-for-papers-special-issue-on-agile-and-open-source-hardware
>
> If nothing else they can point you at people even if they can’t accept
> another abstract.
>
> Most of the papers will be for open chip design so yours would stand out
> but they might point you at Aerospace instead.
>
> Publishing in social media is great but something like IEEE aerospace is
> better for documenting what you’ve done and getting a DOI someone can
> cite.  That helps a lot in establishing your expertise...especially in
> something as niche as EP.
>
> I can pass you along to a couple folks if you are interested in
> collaboration.  I don’t know any folks working EP at APL but that doesn’t
> mean there aren’t any.
>
> Sent from my iPhone
>
> On Mar 6, 2020, at 11:42 PM, Michael Bretti <appliedionsystems at gmail.com>
> wrote:
>
> 
> 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
>>
> _______________________________________________
> 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/20200307/f97817d5/attachment.html>