I don't remember which repo those were stored in. There used to be a poorly maintained list of repositories in the wiki, but I suspect that's been culled (since it was usually incomplete).
Keep in mind those legalcode pages are static and the organizational commitment is to *not* change them once they're published. NRY On Mon, Jun 24, 2013 at 9:08 AM, Jonas Öberg <[email protected]> wrote: > I was poking around on http://code.creativecommons.org/viewgit/ to see if I > could find where the actual templates are that introduce those links, but I > couldn't find them. Is there an overview of the different repositories > anywhere? (I saw the deeds in cc.engine, but not the licenses itself). > > Sincerely, > Jonas > > > On Mon, Jun 24, 2013 at 5:58 PM, Maarten Zeinstra <[email protected]> wrote: >> >> Refactor all links from a form like >> >> http://www.creat.. >> >> to >> >> //www.creat… >> >> I don't know if that notation is backward compatible with most browsers >> though. >> >> -- >> Kennisland >> | www.kennisland.nl | t +31205756720 | m +31643053919 | @mzeinstra >> >> >> >> >> On Jun 24, 2013, at 17:57 , Jonas Öberg <[email protected]> wrote: >> >> Hi Maarten, >> >> I don't see why this shouldn't be protocol relative. >> What is needed to be done to revise this? >> >> Sincerely, >> Jonas >> >> >> On Mon, Jun 24, 2013 at 5:54 PM, Maarten Zeinstra <[email protected]> wrote: >>> >>> Hi all, >>> >>> I use the HTTPS everywhere plugin for Chrome and that messes up some of >>> the CreativeCommons.org pages. Chrome doesn't allow loading .js and .css >>> files from HTTP links within HTTPS pages anymore. This severely messes up >>> pages like all legalcode pages and the namespace page. >>> >>> I already discussed this with Nathan Kinkade, but he indicated that he >>> will not have time to work on it and it seems to be something that is >>> possibly only the case in the newest Chrome browser a problem. Chrome >>> doesn't seem to try to resolve those links in https. >>> >>> However I think that more browser will follow Chrome's lead in this and >>> that we should (re)work these pages to either be protocol relative or force >>> https. >>> >>> Would we agree? >>> >>> Cheers, >>> >>> Maarten >>> >>> >>> -- >>> Kennisland >>> | www.kennisland.nl | t +31205756720 | m +31643053919 | @mzeinstra >>> >>> >>> >>> >>> >>> _______________________________________________ >>> cc-devel mailing list >>> [email protected] >>> http://lists.ibiblio.org/mailman/listinfo/cc-devel >>> >> >> > > > _______________________________________________ > cc-devel mailing list > [email protected] > http://lists.ibiblio.org/mailman/listinfo/cc-devel > _______________________________________________ cc-devel mailing list [email protected] http://lists.ibiblio.org/mailman/listinfo/cc-devel
