-
-
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 Open Hardware #2266
Add Open Hardware #2266
Conversation
unicorn |
Co-authored-by: Michael Paul Coder <[email protected]>
Thank you @IAmCoder for the proposed fix, I like it! |
The |
Thanks Philip! |
It was crying to request I have a computer in mind and there’s an app that
can access it next-door and I want it to stop that’s what I was trying to
request some type of security so they can no longer access wires access to
my mind and my private thoughts yes the capability is there now and the
medical community here knows it it’s on read me MD & I don’t know if they
don’t realize that there’s anything to make it stop with it can’t be
stopped but it’s there now and it’s a program that anyone can access I
think it’s for free and that puts me at risk trying to find a human rights
organization to help me stop this.
…On Sat, Jun 11, 2022 at 9:14 PM, Тажымаматов Жениш ***@***.***> wrote:
Ayzat
—
Reply to this email directly, view it on GitHub
<#2266 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASQ44362Z63XWYIQ34QZ6Q3VOVB2FANCNFSM5WOT4Y3A>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Awesome Open Hardware
The awesome Open Hardware list is made for people wanting to learn more about open source hardware (projects). On the one hand it has the most awesome example project for people to get inspired. On the other hand it has more in depth papers and background information about the topic.
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.
I reviewed #2265
and #2257
Add Name of List
.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 Travis for list 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.