-
Notifications
You must be signed in to change notification settings - Fork 313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename http to https #913
Rename http to https #913
Changes from all commits
df9d5b5
00d0c23
852ab7f
b62dbdf
a1af622
8aa44ef
cf2b1d7
408b546
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -12,7 +12,7 @@ To run userscripts on Chromium, you normally need a manager extension such as Ta | |
|
||
[githubFavicon]: https://assets-cdn.github.com/favicon.ico | ||
[oujsFavicon]: https://raw.githubusercontent.com/OpenUserJs/OpenUserJS.org/master/public/images/favicon16.png | ||
[chromiumBrowser]: http://dev.chromium.org/Home | ||
[wikipediaChromium]: http://www.wikipedia.org/wiki/Chromium_%28web_browser%29 | ||
[chromiumBrowser]: https://dev.chromium.org/Home | ||
[wikipediaChromium]: https://www.wikipedia.org/wiki/Chromium_%28web_browser%29 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This site has a preference of upgrading to secure. +1 Comment by @Martii |
||
[chromiumSupport]: https://code.google.com/p/chromium/issues/list | ||
[tampermonkeyForChromium]: Tampermonkey-for-Chromium |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -38,15 +38,15 @@ Within moderation we understand the occasional necessity to conserve device stor | |
|
||
#### Default Code Licensing | ||
|
||
* User Scripts have an implied license of [MIT License (Expat)](http://opensource.org/licenses/MIT) if the `@license` *(including the alternate spelling of `@licence`)* metadata block key is absent. | ||
* Library Scripts need to include one reference to their [acceptable license(s)](#acceptable-licensing) either via a License Header *([sample MPL header](https://www.mozilla.org/MPL/headers/) if that license is chosen)*, a cross-site compatible metadata block with at least one `@license` or `@licence` key **and** one `@exclude *`, or full License text *(full text is not recommended for storage constraints on portable devices)*. Libraries also have an implied license of [MIT License (Expat)](http://opensource.org/licenses/MIT) in the absence of any licensing *(however this should not happen)*. It may also be useful to indicate in the source that it is a library and not a userscript. If the type of script is unclear the library may be subject to removal. | ||
* User Scripts have an implied license of [MIT License (Expat)](https://opensource.org/licenses/MIT) if the `@license` *(including the alternate spelling of `@licence`)* metadata block key is absent. | ||
* Library Scripts need to include one reference to their [acceptable license(s)](#acceptable-licensing) either via a License Header *([sample MPL header](https://www.mozilla.org/MPL/headers/) if that license is chosen)*, a cross-site compatible metadata block with at least one `@license` or `@licence` key **and** one `@exclude *`, or full License text *(full text is not recommended for storage constraints on portable devices)*. Libraries also have an implied license of [MIT License (Expat)](https://opensource.org/licenses/MIT) in the absence of any licensing *(however this should not happen)*. It may also be useful to indicate in the source that it is a library and not a userscript. If the type of script is unclear the library may be subject to removal. | ||
|
||
#### Acceptable Licensing | ||
* Licensing must be [Open Source Initiative *(OSI)* approved](http://opensource.org/licenses/category) and declared with the name of the License in the Source Code for all published works. e.g. `@license` or `@licence` keys, License Header or full License text *(full text is not recommended for storage constraints on portable devices)* | ||
* Licensing must be [Open Source Initiative *(OSI)* approved](https://opensource.org/licenses/category) and declared with the name of the License in the Source Code for all published works. e.g. `@license` or `@licence` keys, License Header or full License text *(full text is not recommended for storage constraints on portable devices)* | ||
* If a Content only license is included then the [Default Code Licensing](#default-code-licensing) will be applied with licensing arbitration, but may not always be visibly indicated on a script home page. | ||
* Any license that prohibits derivatives is eligible for removal. | ||
* Non-reusable licenses, of course, may not be used. | ||
* [Public domain type](http://opensource.org/faq#public-domain) licenses may mean different things in different jurisdictions and therefore are not allowed and eligible for removal. | ||
* [Public domain type](https://opensource.org/faq#public-domain) licenses may mean different things in different jurisdictions and therefore are not allowed and eligible for removal. | ||
* Any attempt to unlicense a published work will be eligible for removal. | ||
* In the event of any code licensing dispute resolution the [Default Code Licensing](#default-code-licensing) shall prevail if previously undeclared and/or undocumented. | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 4 comments on commit df9d5b5 @Martii @Martii @GreenLunar @GreenLunar As far as I am concerned, I have done what I wanted to be done. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
That's why issues should be made first... then discuss... etc... as I described at the PR itself first. That way you won't be doing repetitive actions e.g. unnecessary work. You did find one enhancement for wikipedia so that is something you could do with a probably +1 support for merging... issue first though. Sidebar: With wikipedia links always watch that the link is language neutral too. Typically here in the US it will redirect to https://en.wikipedia.org and we shouldn't be linking to outside en only pages if they have their own browser language detection when possible. Same goes for Mozilla links and any others that apply. |
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This site has a preference of http with optional https. -1
Comment by @Martii
Originally posted at https://github.com/GreenLunar/OpenUserJS.org/commit/df9d5b50022cdbecfeb96fcf1daca1a07459ef16#commitcomment-16372957
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LOL Sorry about the posting on the Commits (your repo) instead of the Files (this repo)... makes mental note to pay more attention to GHs ever changing features :)