3 ms·
That post has an update at the top that the license change was delayed until March 1, 2016 and a link to a follow-up post: http://meta.stackexchange.com/questio
by computronus 10y ago
That post has an update at the top that the license change was delayed until March 1, 2016 and a link to a follow-up post: http://meta.stackexchange.com/questions/272956/a-new-code-license-the-mit-this-time-with-attribution-required?cb=1 http://meta.stackexchange.com/questions/272956/a-new-code-li...
That follow-up post says that they're "going to delay the implementation", so I assume that today it's still all CC-SA. I haven't found any further information, but would love to know it, or be corrected on my assumption.
My company is struggling with the code license situation and I'm stuck with dealing with it for my project. Clear, up-to-date information about it would be fantastic.
- daenney 10y agoOh nice catch, I missed that part. And I feel your pain. Starting a similar project here to inventory 3rd party code etc., it's going to be hard.