I would like to add my Open Science Resources list to the Awesome list, since there appears to be no specific precursor for it. It is intended to be cross-disciplinary, and has many links to open science data and many other resources. Thanks for any consideration!
There is no cross-disciplinary list for doing open science in general already present. Much of the barrier to working with open science data or using open science tools is simple ignorance of the depth and breadth of such resources. By compiling these resources together, including other meta-resources, I've tried to provide a good starting place for any scientists interested in hunting for open data in their field, or anyone who is interested in contributing to a field.
Note: I'd like to mention that the below contribution instructions aren't the same as what's on the main Contribution Guidelines page? The below list has some extra recommendations that would be useful to add to that.
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
This pull request has a descriptive title. For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should:
Include a short description about the project/theme of the list. It should not describe the list itself. Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish..
Be added at the bottom of the appropriate category.
The list I'm submitting complies with these requirements:
Requirements for your Awesome list
Has been around for at least 30 days. That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
It's the result of hard work and the best I could possibly produce.
Non-generated Markdown file in a GitHub repo.
Includes a succinct description of the project/theme at the top of the readme.(Example)
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate.
Only has awesome items. Awesome lists are curations of the best, not everything.
Includes a project logo/illustration whenever possible.
Either fullwidth or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.
Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
The file should be named contributing.md. Casing is up to you.
Has consistent formatting and proper spelling/grammar.
The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
Doesn't include a Travis badge. You can still use Travis for list linting, but the badge has no value in the readme.
Go to the top and read it again.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/sindresorhus/awesome/pull/1284
**Author:** [@asoplata](https://github.com/asoplata)
**Created:** 4/30/2018
**Status:** ❌ Closed
**Base:** `master` ← **Head:** `patch-2`
---
### 📝 Commits (3)
- [`fe91018`](https://github.com/sindresorhus/awesome/commit/fe91018e341eda609de860c4e9b522b4dad9a619) Add Open Science Resources
- [`4e285f2`](https://github.com/sindresorhus/awesome/commit/4e285f2d971a151a3d11c056b2772ab762b5cf5c) Describe content of list
- [`fb18814`](https://github.com/sindresorhus/awesome/commit/fb18814e2e1136556017f7044c18287d3375b218) Describe open science more clearly
### 📊 Changes
**1 file changed** (+1 additions, -1 deletions)
<details>
<summary>View changed files</summary>
📝 `readme.md` (+1 -1)
</details>
### 📄 Description
I would like to add my [Open Science Resources](https://github.com/asoplata/open-science-resources) list to the Awesome list, since there appears to be no specific precursor for it. It is intended to be cross-disciplinary, and has many links to open science data and many other resources. Thanks for any consideration!
<!-- Congrats on creating an Awesome list! 🎉 -->
<!-- Please fill in the below placeholders -->
**https://github.com/asoplata/open-science-resources**
**There is no cross-disciplinary list for doing open science in general already present. Much of the barrier to working with open science data or using open science tools is simple ignorance of the depth and breadth of such resources. By compiling these resources together, including other meta-resources, I've tried to provide a good starting place for any scientists interested in hunting for open data in their field, or anyone who is interested in contributing to a field.**
Note: I'd like to mention that the below contribution instructions aren't the same as what's on the main [Contribution Guidelines](https://github.com/sindresorhus/awesome/blob/master/contributing.md) page? The below list has some extra recommendations that would be useful to add to that.
### By submitting this pull request I confirm I've read and complied with the below requirements 🖖
**Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.**
## Requirements for your pull request
- I have read and understood the [contribution guidelines](https://github.com/sindresorhus/awesome/blob/master/contributing.md) and the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/master/create-list.md).
- This pull request has a descriptive title.<br>For example, `Add Name of List`, not `Update readme.md` or `Add awesome list`.
- The entry in the Awesome list should:
- Include a short description about the project/theme of the list. **It should not describe the list itself.**<br>Example: `- [Fish](…) - User-friendly shell.`, not `- [Fish](…) - Resources for Fish.`.
- Be added at the bottom of the appropriate category.
- The list I'm submitting complies with these requirements:
## Requirements for your Awesome list
- **Has been around for at least 30 days.**<br>That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
- It's the result of hard work and the best I could possibly produce.
- Non-generated Markdown file in a GitHub repo.
- **Includes a succinct description of the project/theme at the top of the readme.** [(Example)](https://github.com/willempienaar/awesome-quantified-self)
- The repo should have `awesome-list` & `awesome` as [GitHub topics](https://help.github.com/articles/about-topics). I encourage you to add more relevant topics.
- Not a duplicate.
- Only has awesome items. Awesome lists are curations of the best, not everything.
- Includes a project logo/illustration whenever possible.
- Either fullwidth or placed at the top-right of the readme. [(Example)](https://github.com/sindresorhus/awesome-electron)
- The image should link to the project website or any relevant website.
- The image should be high-DPI. Set it to maximum half the width of the original image.
- Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
- Includes the [Awesome badge](https://github.com/sindresorhus/awesome/blob/master/awesome.md#awesome-badge).
- Should be placed on the right side of the readme heading.
- Should link back to this list.
- Has a Table of Contents section.
- Should be named `Contents`, not `Table of Contents`.
- Should be the first section in the list.
- Should only have one level of sub-lists, preferably none.
- Has an [appropriate license](https://github.com/sindresorhus/awesome/blob/master/awesome.md#choose-an-appropriate-license).
- That means something like CC0, **not a code licence like MIT, BSD, Apache, etc.**
- [WTFPL](http://www.wtfpl.net) and [Unlicense](http://unlicense.org) are not acceptable licenses.
- If you use a license badge, it should be SVG, not PNG.
- Has [contribution guidelines](https://github.com/sindresorhus/awesome/blob/master/awesome.md#include-contribution-guidelines).
- The file should be named `contributing.md`. Casing is up to you.
- Has consistent formatting and proper spelling/grammar.
- The link and description are separated by a dash. <br>Example: `- [AVA](…) - JavaScript test runner.`
- The description starts with an uppercase character and ends with a period.
- Consistent and correct naming. For example, `Node.js`, not `NodeJS` or `node.js`.
- Doesn't include a Travis badge.<br>You can still use Travis for list linting, but the badge has no value in the readme.
Go to the top and read it again.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/sindresorhus/awesome/pull/1284
Author: @asoplata
Created: 4/30/2018
Status: ❌ Closed
Base:
master← Head:patch-2📝 Commits (3)
fe91018Add Open Science Resources4e285f2Describe content of listfb18814Describe open science more clearly📊 Changes
1 file changed (+1 additions, -1 deletions)
View changed files
📝
readme.md(+1 -1)📄 Description
I would like to add my Open Science Resources list to the Awesome list, since there appears to be no specific precursor for it. It is intended to be cross-disciplinary, and has many links to open science data and many other resources. Thanks for any consideration!
https://github.com/asoplata/open-science-resources
There is no cross-disciplinary list for doing open science in general already present. Much of the barrier to working with open science data or using open science tools is simple ignorance of the depth and breadth of such resources. By compiling these resources together, including other meta-resources, I've tried to provide a good starting place for any scientists interested in hunting for open data in their field, or anyone who is interested in contributing to a field.
Note: I'd like to mention that the below contribution instructions aren't the same as what's on the main Contribution Guidelines page? The below list has some extra recommendations that would be useful to add to that.
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request
For example,
Add Name of List, notUpdate readme.mdorAdd awesome list.Example:
- [Fish](…) - User-friendly shell., not- [Fish](…) - Resources for Fish..Requirements for your Awesome list
That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
awesome-list&awesomeas GitHub topics. I encourage you to add more relevant topics.Contents, notTable of Contents.contributing.md. Casing is up to you.Example:
- [AVA](…) - JavaScript test runner.Node.js, notNodeJSornode.js.You can still use Travis for list linting, but the badge has no value in the readme.
Go to the top and read it again.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.