The Saturday before we went open source with DEV, I had the sudden realization of all the last-minute details with our license to get right. I knew enough to know we had to settle on some things, but we had punted on nailing down the details and nobody in our company had a better understanding than me.
And I was at a wedding that weekend. No environment for a lot of last minute research.
And then someone walks into the the wedding ceremony wearing a GNU t-shirt. It's a bold fashion choice for a wedding. Nobody wears a GNU t-shirt to a wedding without also being seriously willing to talk about open source licenses. I knew we wanted to go GLP but I had a lot of questions.
I don't believe in god, but when that man walked into that church I felt some belief wash over me.
The Saturday before we went open source with DEV, I had the sudden realization of all the last-minute details with our license to get right. I knew enough to know we had to settle on some things, but we had punted on nailing down the details and nobody in our company had a better understanding than me.
And I was at a wedding that weekend. No environment for a lot of last minute research.
And then someone walks into the the wedding ceremony wearing a GNU t-shirt. It's a bold fashion choice for a wedding. Nobody wears a GNU t-shirt to a wedding without also being seriously willing to talk about open source licenses. I knew we wanted to go GLP but I had a lot of questions.
I don't believe in god, but when that man walked into that church I felt some belief wash over me.
I'd love to know more about the decision to use AGPL over MIT! What was the primary motivating feature of AGPL that made you go with it?