aeropython / awesome-scientific-computing Goto Github PK

Dears,

I've notice that this awesome list of scientific computing goes beyond the theoretical knowledge and also contains information about scientific programming languages. At the moment, there is only Python, which is kinda lost among the other scientific topics. I would like to contribute with the contents with the programming language that I am use for science (Python, Matlab, Julia, and R). However, it seems a little tangled if put a new topic among other purely theoretical topic (e.g., Linear Algebra).

Shouldn't it better to split the table of contents between scientific programming languages and field of knowledge? In that way we could separate the theoretical topics from contents that concerns the programming language itself.

Maybe I will be interesting to add a tutorial to the CONTRIBUTING.md file on how to make a pull request in order to add a new link .

i.e. https://github.com/sindresorhus/awesome
Here is a copypasta of the checklist

I have read and understood the contribution guidelines and the instructions for creating a list.

• 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 list project/theme. It should not describe the list itself.
  • Example: - Fish - User-friendly shell.
  • Be added at the bottom of the appropriate category.
• The list I'm submitting complies with these requirements:
  • 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.
  • The repo should have the following GitHub topics set: awesome-list, awesome, list. I encourage you to add more relevant topics.
  • Not a duplicate.
  • Includes a succinct description of the project/theme at the top of the readme. (Example)
  • Only has awesome items. Awesome lists are curations of the best, not everything.
  • Includes a project logo/illustration whenever possible.
    • 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.
  • Has the Awesome badge on the right side of the list heading,
  • Has a Table of Contents section.
    • Should be named Contents, not Table of Contents.
    • Should be the first section in the list.
  • Has an appropriate license.
    • That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
    • If you use a license badge, it should be SVG, not PNG.
  • Has contribution guidelines.
    • The file should be named contributing.md. Casing is up to you.
  • Has consistent formatting and proper spelling/grammar.
    • Each link description starts with an uppercase character and ends with a period.
    • Example: - AVA - JavaScript test runner.
    • Drop all the A / An prefixes in the descriptions.
    • Consistent 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.