Is it ok to remove derived acknowledgements when document is now original?

The windows.WindowState documentation was originally derived from Chromium code, but we have now changed 100% of the content except the actual API values. Is it ok to remove the line “This documentation is derived from windows.json in the Chromium code.” since it is no longer derived from it?

If, literally, the entire article has been discarded and replaced with all-new content, I would personally think it makes sense to remove the original document stuff. However, I’m not directly involved with the extensions documentation, so I’d wait for @wbamberg to weigh in, probably, since he handled setting that stuff up in the beginning.

Thanks for updating the docs!

Sorry, I don’t know the intricacies of when it’s OK to remove acknowledgements like this when the content changes. I can’t imagine anyone would care but my imagination isn’t a very reliable guide.

I do know that this bit:

Microsoft Edge compatibility data is supplied by Microsoft Corporation and is included here under the Creative Commons Attribution 3.0 United States License.

should never have been included, and can and should be removed.

1 Like