Hi;

I recommend separating things out into using free software versus
writing free software.

If the code you are writing is only interesting to a specific
customer, and you give the customer access to the code, you are
creating free software. You don't need to put it on a public Github.

So I suggest keeping those separate aspects in consideration.
Convincing people to depend on Linux, Python, etc. (and giving back
any bug / fixes to existing public codebases) is a relatively easy
step and moves things in the right direction.

Regards,

-Keith

---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscr...@apache.org
For additional commands, e-mail: community-h...@apache.org

Reply via email to