-
-
Notifications
You must be signed in to change notification settings - Fork 28.3k
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 macOS Admin Tools #1339
Add macOS Admin Tools #1339
Conversation
Please go through the checklist.
The format with images is uncommon. Proposal create a "usual" awesomelist in This entry of your list doesn't seem to be awesome, is it? |
RE pictures, I based my list off of the Awesome macOS Screensavers list, which also has large images. I felt the illustration of the tools helps show how awesome they are, which is why they are included. I will review the other items. Thanks for the feedback. |
Excerpt from the curated list of screensavers for Mac OS X Title, Description, linked Image Your list: I would remove cost and add the link to the image/animated gif. So you have the same format and the list would appear very lean. |
I actually had it that way initially, but got feedback from users of the list that it wasn't inherent that clicking the images triggered a link. Users also asked for cost to be more clearly established in the list. They were added largely for accessibility reasons, especially for those that are visually impaired and use screen readers and other assistance tools. If adding items for accessibility reasons doesn't make this list eligible to be "awesome" I'll just leave it unlisted and continue to share within the macadmin community via social media and other means. |
I'd propose to fix the other things and then ask the maintainer of this
list.
Refs
#1323 (comment)
emily <[email protected]> schrieb am Do., 21. Juni 2018, 19:53:
… I actually had it that way initially, but got feedback from users of the
list that it wasn't inherent that clicking the images triggered a link.
Users also asked for cost to be more clearly established in the list. They
were added largely for accessibility reasons, especially for those that are
visually impaired and use screen readers and other assistance tools.
If adding items for accessibility reasons doesn't make this list eligible
to be "awesome" I'll just leave it unlisted and continue to share within
the macadmin community via social media and other means.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1339 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABTafhRdAgDV0SOqdoFmZHmJ65Nop2r1ks5t-92jgaJpZM4UyHW3>
.
|
Hey, sorry for the lack of response, please see #1363. |
|
Can you fix the merge conflict? |
@@ -84,6 +84,7 @@ | |||
- [macOS](https://github.com/iCHAIT/awesome-macOS) | |||
- [Command-Line](https://github.com/herrbischoff/awesome-macos-command-line) | |||
- [Screensavers](https://github.com/agarrharr/awesome-macos-screensavers) | |||
- [Macadmin Tools](https://github.com/smashism/awesome-macadmin-tools) |
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.
- [Macadmin Tools](https://github.com/smashism/awesome-macadmin-tools) | |
- [Admin Tools](https://github.com/smashism/awesome-macadmin-tools#readme) |
You should rename the repo from |
Closing for lack of response. |
https://github.com/smashism/awesome-macadmin-tools
This list is the best of the best tools available, free, paid, or open source, for people who admin Macs at organizations.
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.md
orAdd 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
&awesome
as 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
, notNodeJS
ornode.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.