-
-
Notifications
You must be signed in to change notification settings - Fork 28.1k
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
Add High Performance Computing #2640
Conversation
Thanks for making an Awesome list! 🙌 It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome. |
|
@akail In accordance with the guidelines, it is also required that you review a minimum of two Pull Requests within this repository. Please provide the links to your reviews in the comments. |
Only costomaizine vivo 1933 used |
1 similar comment
Only costomaizine vivo 1933 used |
Use system editing only vivo 1933 seva all odr |
@asapelkin The links were included with the PR. Included below:
|
https://github.com/dstdev/awesome-hpc/blob/main/LICENSE CC0 and CC-BY-SA-3.0 are not the same. CC0 is a public domain dedication that allows creators to give up all their copyright and related rights, essentially placing their works in the public domain. It's as close to "no rights reserved" as you can get under copyright law. CC-BY-SA-3.0, on the other hand, is a Creative Commons Attribution-ShareAlike license. This means anyone can use, share, or modify the work, even for commercial purposes, as long as they provide attribution to the original creator and distribute any derivative works under the same license. So while both licenses are Creative Commons licenses, they offer different levels of freedom and impose different requirements on the user. |
@awesome-doge Thanks for pointing that out. When I originally created the list I copied from another list including the license they used. Its been updated. |
@sindresorhus Just checking in to see if there are any other changes that need to be made. I've checked it over several times now and don't see anything else I can do. Thanks |
* Add Steam Deck (sindresorhus#2743) * Update link to Awesome Mastodon (sindresorhus#2739) * Add Pest (sindresorhus#2601) * Add HPC (sindresorhus#2640) * Update guidelines * Add Biological Image Analysis (sindresorhus#2620) Co-authored-by: Sindre Sorhus <sindresorhus@gmail.com> * Move Esolangs into "Programming Languages" section (sindresorhus#2799) * Add Prompt Injection (sindresorhus#2734) * Meta tweaks * Add Complexity (sindresorhus#2389) * Fix typo (sindresorhus#2834) * Fix typos (sindresorhus#2835) * Meta tweaks --------- Co-authored-by: Francesco Sardone <francesco@airscript.it> Co-authored-by: Edwin Kofler <edwin@kofler.dev> Co-authored-by: Tomas Tauber <2410580+tomtau@users.noreply.github.com> Co-authored-by: akail <andrew.a.kail@gmail.com> Co-authored-by: Sindre Sorhus <sindresorhus@gmail.com> Co-authored-by: Hallvard A. Wæhler <60000604+hallvaaw@users.noreply.github.com> Co-authored-by: Sam Partington <sampart@github.com> Co-authored-by: Hazana <hazanasec@gmail.com> Co-authored-by: Diamantis Sellis <sellisd@gmail.com> Co-authored-by: Vivek Gurudutt K <127002789+VivekGuruduttK28@users.noreply.github.com> Co-authored-by: S A G A R <110724849+tmsagarofficial@users.noreply.github.com>
https://github.com/dstdev/awesome-hpc
A collection of tools an resources for High Performance Computing systems.
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
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions. Comments pointing out lint violation are allowed, but does not count as a review.
Reviewed PRs
Add Name of List
. It should not contain the wordAwesome
.Add Swift
Add Software Architecture
Update readme.md
Add Awesome Swift
Add swift
add Swift
Adding Swift
Added Swift
- [iOS](…) - Mobile operating system for Apple phones and tablets.
- [Framer](…) - Prototyping interactive UI designs.
- [iOS](…) - Resources and tools for iOS development.
- [Framer](…)
- [Framer](…) - prototyping interactive UI designs
#readme
.- [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.
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-lint
on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.main
, notmaster
.Mobile operating system for Apple phones and tablets.
Prototyping interactive UI designs.
Resources and tools for iOS development.
Awesome Framer packages and tools.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
awesome-name-of-list
.awesome-swift
awesome-web-typography
awesome-Swift
AwesomeWebTypography
# Awesome Name of List
.# Awesome Swift
# Awesome Web Typography
# awesome-swift
# AwesomeSwift
awesome-list
&awesome
as GitHub topics. I encourage you to add more relevant topics.Contents
, notTable of Contents
.Contributing
orFootnotes
sections.https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0
(replace<user>
and<repo>
accordingly).license
orLICENSE
in the repo root with the license text.Licence
section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.unicorn
.contributing.md
. Casing is up to you.Contributing
, positioned at the top or bottom of the main content.Footnotes
section at the bottom of the readme. The section should not be present in the Table of Contents.Example:
- [AVA](…) - JavaScript test runner.
Node.js
, notNodeJS
ornode.js
.You can still use a CI for linting, but the badge has no value in the readme.
Inspired by awesome-foo
orInspired by the Awesome project
kinda link at the top of the readme. The Awesome badge is enough.Go to the top and read it again.