Skip to content
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

Spring Cleaning #50

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Spring Cleaning #50

wants to merge 1 commit into from

Conversation

PixelHir
Copy link
Member

@PixelHir PixelHir commented May 9, 2024

There's a few things I'd like to get done and to decide on some matters.

  • Due to the age of the list, many entries have become obsolete/deprecated. Should these get a new separate category for obsolete stuff or should we remove them completely?
  • I've had an issue brought up about some entries potentially breaking Riot TOS (like Added LeagueAutoAccept #49). Should we start policing these?
  • deciding order in which entries are sorted? alphabetical, time of adding, something else?
  • potentially refactoring the way we categorize entries?
  • switching the branch from master to main (technically an official requirement if we ever wanna be added to awesome-list repo)

This is something I'd love to get a feedback about from everyone, contributor or not, readers, feel free to drop your input

@PixelHir PixelHir self-assigned this May 9, 2024
@rico-vz
Copy link
Contributor

rico-vz commented May 9, 2024

There's a few things I'd like to get done and to decide on some matters.

  • Due to the age of the list, many entries have become obsolete/deprecated. Should these get a new separate category for obsolete stuff or should we remove them completely?
  • I've had an issue brought up about some entries potentially breaking Riot TOS (like Added LeagueAutoAccept #49). Should we start policing these?
  • deciding order in which entries are sorted? alphabetical, time of adding, something else?
  • potentially refactoring the way we categorize entries?
  • switching the branch from master to main (technically an official requirement if we ever wanna be added to awesome-list repo)

This is something I'd love to get a feedback about from everyone, contributor or not, readers, feel free to drop your input

My personal thoughts on these points:

  1. Remove them completely, or perhaps have a deprecated/legacy.md for them.
  2. Perhaps to an extent, but in that case where would the line be drawn for fine/no-no. I'm not sure, it also kind of depends on the impact the tool would have. I don't think tools that might be likely to get the player banned should be a listed (don't think any of the current listed fall under that). So... 🤷‍♂️?
  3. Alphabetical or maybe by stars.
  4. Distinguishing the "Applications" and "External Apps" more wouldn't be a bad idea so that there are no more websites under "Applications". And for ones that offer both, like Blitz for example, you could list them under both as long as it provides value for both (e.g. don't put something under "External Apps"/"Websites" if the website is like Nemo, where the website purpose is just to provide the download & contact info)
  5. No real reason not to do this

Something else: Maybe it'd be a nice idea to let listings that have a website URL but are also open-source have a little :octocat: GH icon next to it linking to the repository. (Like https://mimic.lol/ and https://github.com/molenzwiebel/mimic)

Maybe it'd even be an idea to have open-source and closed-source as 2 "main" categories, with the other categories underneath? Or an icon/emoji next to the listing indicating whether it's open sourced or not? Curious what others think about this 😄

@BlossomiShymae
Copy link
Contributor

  • deciding order in which entries are sorted? alphabetical, time of adding, something else?

When I first contributed, I was a bit confused about how I should add my entry based on the ordering. Maybe it's best to have them sorted alphabetically. x3

  • I've had an issue brought up about some entries potentially breaking Riot TOS (like Added LeagueAutoAccept #49). Should we start policing these?

I'm more on the side of policing because just having apps like these here implies that it's being endorsed. I just don't know how to go on about it though. :>

@Hi-Ray
Copy link
Member

Hi-Ray commented May 11, 2024

I've had an issue brought up about some entries potentially breaking Riot TOS (like #49). Should we start policing these?

I agree with @BlossomiShymae on this one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants