On 11/05/2017 02:44 AM, Shlomi Fish wrote:
Hi,
On Sat, 4 Nov 2017 14:02:35 -0700
ToddAndMargo <toddandma...@zoho.com> wrote:
On 11/04/2017 02:19 AM, Shlomi Fish wrote:
Hi,
On Fri, 3 Nov 2017 14:38:05 -0700
ToddAndMargo <toddandma...@zoho.com> wrote:
On 11/03/2017 02:34 AM, Shlomi Fish wrote:
because i believe that
otherwise viewing such encumbered code may taint one's future software dev
work.
What do you mean by the above line?
See the discussion at
https://slashdot.org/story/04/02/12/2114228/windows-2000-windows-nt-4-source-code-leaks
.
Thank you for the heads up.
Also, I do frequently post modules I have written.
Should I stop the practice?
Not if you explicitly place them under a FOSS licence.
Hi Shlomi,
I am looking at your link to FOSS:
https://en.wikipedia.org/wiki/Free_and_open-source_software
It sound perfect.
I am not seeing how to actually register something as FOSS.
Do I need a lawyer? (I can not afford that kind of stuff.)
No, see http://choosealicense.com/ .
Regards,
Shlomi
Many thanks,
-T
It says to "Create a text file (typically named LICENSE or
LICENSE.txt) in the root of your source code and copy the
text of the license into the file"
I am wondering if it would not be better to just copy
the license straight into the pm6 ? #`{ license ..}
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
