"Open Publication License" link gives a 403 error.

RESOLVED FIXED

Status

Developer Documentation
General
RESOLVED FIXED
14 years ago
5 years ago

People

(Reporter: justdave, Assigned: Dawn Endico)

Tracking

Details

(URL)

At the bottom of the page where it discusses the discussion on a copyright
policy, one of the suggested licenses that is under discussion is the Open
Publication License.  The link to it reports a 403 Forbidden error.

(This is an off-site link - perhaps this exists at another location now?)

Comment 1

14 years ago
Note that there is a book published (pdf, html) on mozilla.org which has the
same dead link. I'm not interested in playing with the license. I believe that I
could modify the book, but i'd have to clearly indicate that i fixed the license
link which seems like a real waste of time and bits.
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → FIXED
Please explain to me how that fixes this bug?

I'm not interested in whether an existing license links to it.  This is an
information section about proposed licenses I'm talking about.  I want
information about this license, so we should link to a working URL that explains
it.  Whether the original "official" url is correct or not, it's still dead.

Perhaps it's not supposed to be dead, but until someone at opencontent.org fixes
that, this bug still isn't fixed.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
OK, next time you fix a bug, please tell us you fixed it instead of just marking
it fixed.

The only comment you made indicated that you were NOT fixing it.

The link on the contribute page now works.
Status: REOPENED → RESOLVED
Last Resolved: 14 years ago14 years ago
Resolution: --- → FIXED
Component: Mozilla Developer → Documentation Requests
Product: Documentation → Mozilla Developer Center
Component: Documentation Requests → Documentation
Product: Mozilla Developer Network → Mozilla Developer Network
Component: Documentation → General
Product: Mozilla Developer Network → Developer Documentation
You need to log in before you can comment on or make changes to this bug.