Introducing //TODO for companies that are committed to open source
1–10 of 33 posts
Re: Introducing //TODO for companies that are committed to open source
#2Re: Introducing //TODO for companies that are committed to open source
#3After reading this announcement, I have no clue what this is or why my company might want to join it.
Re: Introducing //TODO for companies that are committed to open source
#4After reading this announcement, I have no clue what this is or why my company might want to join it.
Re: Introducing //TODO for companies that are committed to open source
#5After reading this announcement, I have no clue what this is or why my company might want to join it.
Re: Introducing //TODO for companies that are committed to open source
#6After reading this announcement, I have no clue what this is or why my company might want to join it.
Re: Introducing //TODO for companies that are committed to open source
#7After reading this announcement, I have no clue what this is or why my company might want to join it.
I suppose that this is neutral at worst. I had the fleeting, whimsical thought that Apple and Samsung ought to both join.
Re: Introducing //TODO for companies that are committed to open source
#8Re: Introducing //TODO for companies that are committed to open source
#9After reading this announcement, I have no clue what this is or why my company might want to join it.
Re: Introducing //TODO for companies that are committed to open source
#101. It is for companies with dedicated resources for open source projects.
2. The person signing on has to mention the company he is with, so ideally a person from the "dedicated resource" or open source department of a prospective company?
3. They exist to discuss "how to shift ownership of projects from companies to the community".
So as a person of an open source department at their company, one is expected to join this to help their company render their department useless?
They should bake it better and present it to the right person.