-
Notifications
You must be signed in to change notification settings - Fork 229
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
Open Source Applications #28
Comments
Merged
nex3
pushed a commit
that referenced
this issue
Jun 23, 2023
[consistent-sass-formatting] Make sure properties are written consistently (remove nesting)
asaf400
pushed a commit
to asaf400/ass-site
that referenced
this issue
Apr 18, 2024
[consistent-sass-formatting] Make sure properties are written consistently (remove nesting)
asaf400
pushed a commit
to asaf400/ass-site
that referenced
this issue
Apr 18, 2024
[consistent-sass-formatting] Make sure properties are written consistently (remove nesting)
Friendly-users
added a commit
to Friendly-users/sass-site
that referenced
this issue
Jun 27, 2024
----- It is inappropriate to include political and offensive content in public code repositories. Public code repositories should be neutral spaces for collaboration and community, free from personal or political views that could alienate or discriminate against others. Political content, especially that which targets or disparages minority groups, can be harmful and divisive. It can make people feel unwelcome and unsafe, and it can create a hostile work environment. Please refrain from adding such content to public code repositories. --- sass#1 sass#2 sass#3 sass#4 sass#5 sass#6 sass#7 sass#8 sass#9 sass#10 sass#11 sass#12 sass#13 sass#14 sass#15 sass#16 sass#17 sass#18 sass#19 sass#20 sass#21 sass#22 sass#23 sass#24 sass#25 sass#26 sass#27 sass#28 sass#29 sass#30 sass#31 sass#32 sass#33 sass#34 sass#35 sass#36 sass#37 sass#38 sass#39 sass#40 sass#41 sass#42 sass#43 sass#44 sass#45 sass#46 sass#47 sass#48 sass#49 sass#50 sass#51 sass#52 sass#53 sass#54 sass#55 sass#56 sass#57 sass#58 sass#59 sass#60 sass#61 sass#62 sass#63 sass#64 sass#65 sass#66 sass#67 sass#68 sass#69 sass#70 sass#71 sass#72 sass#73 sass#74 sass#75 sass#76 sass#77 sass#78 sass#79 sass#80 sass#81 sass#82 sass#83 sass#84 sass#85 sass#86 sass#87 sass#88 sass#89 sass#90 sass#91 sass#92 sass#93 sass#94 sass#95 sass#96 sass#97 sass#98 sass#98 sass#99
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While we want to support all applications that use Sass, we are an open source project, and promoting paid/closed applications that don't directly support the project can be problematic. In the current configuration, the very first link is to go pay someone else, unrelated to the project, on the "Install Sass" guide, when there are good open source versions. A user might click on that thinking there is an official relationship, or that Sass costs money.
I get that alphabetical was used to try and be fair, and that's fine, but we need it to be very, very, very clear what is paid and what is open source. It can't be subtle.
I have a pull request I am going to do that tries to address this. The greyed out, subtle "paid" icon we have now is just not enough. Another approach is to group free / paid (with an indicator for open source).
We need to support, not necessarily promote, the Sass application ecosystem.
The text was updated successfully, but these errors were encountered: