4 ms·
Cool new project – I think it might become very helpful one day. Documentation for a lot of open source projects is pretty bad and having to figure out a new co
by metakermit 10y ago
Cool new project – I think it might become very helpful one day. Documentation for a lot of open source projects is pretty bad and having to figure out a new contributing workflow every time just to hop in and help a bit is quite problematic. Hopefully, the unified interface SO users are used to will give docs writing a big boost.
That said, I still hope they output some sort of GitHub repo of all the accepted changes to make it a bit less walled-gardeny. A CC license is nice and all, but having the content in a repo as well would put my mind at ease.
- aalear 10y agoWe have plans to eventually add Documentation to the data dump we already produce of the Q&A content (and hook it into the API, etc.) If for some reason Documentation doesn't really take off or work and we end up scrapping the project, we'll produce a final dump of all content at that point.
- mattip 10y agoThe CC license used for stack overflow content is horrible. I have asked multiple lawyers what it means for cut-and-pasted code, and have yet to recieve a clear a definitive answer - is it viral when compiled into a binary, or when used in scripts? - how to attribute?
- wool_gather 10y agoThe license for code changed earlier this year: http://meta.stackexchange.com/questions/271080/the-mit-license-clarity-on-using-code-on-stack-overflow-and-stack-exchange http://meta.stackexchange.com/questions/271080/the-mit-licen... to MIT. It's not retroactive, though.
- deleted 10y ago[deleted]
- deleted 10y ago[deleted]