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

Sensible library categories #57

Open
Cellane opened this issue Jun 27, 2018 · 6 comments
Open

Sensible library categories #57

Cellane opened this issue Jun 27, 2018 · 6 comments

Comments

@Cellane
Copy link
Collaborator

Cellane commented Jun 27, 2018

Seeing as the list is nicely growing both in terms of entries and in terms of popularity1 (thank you! 🙇 ✨), I think it’s time to start thinking about splitting the list of Vapor libraries into relevant categories. And since I’m notoriously bad at making creative decisions like these myself, I’d love to invite the community to participate in the process of decision-making.

In your opinion, what sort of categories would reasonably separate the libraries currently present on the list, and hopefully not require too many changes in the future?

From my point of view, the ideal situation would look like this:

  • categories are distinct enough that each library can without any reasonable doubt belong to one category only;
  • categories are intuitive enough that if I’m searching for a solution of a particular problem, I should immediately know which category will likely contain libraries solving my problem just by looking at the category list in the table of contents;
  • categories are generic enough to describe not only current state of the list, but hopefully also future state.

I’d love to hear what other people think and in a week or two’s time, make a final decision based on the feedback I receive by then (if any).

Footnotes

  1. It’s only a bit sad that my PR (Add Vapor sindresorhus/awesome#1313) to have Awesome Vapor added to the list of Awesome lists was still not merged 😢

@InukVT
Copy link

InukVT commented Jun 27, 2018

I can actually only think of three currently:
DB: This is where FluentQuery, Firebase and other DB'ing libraries go
Storage: Here goes all the S3 libraries, as well as other libraries that do some or most of the same things
Misc: Is an important one, this is where Sugar goes, as well as libraries that yet has their own category.

@MrLotU
Copy link

MrLotU commented Jun 27, 2018

Adding to Inuk's list, I'd say get a category for utils, so:
DB: DB stuff (fluent, firebase, whatever)
Storage: Storage stuff
Util: Utility packages, small things that just make life easier
Misc: All the other stuff

@InukVT
Copy link

InukVT commented Jun 27, 2018

Would Util be where libs as Sugar goes? 🤔
It's important that Storage goes after db, as db is a sort of storage at it's core, as to distinguish these better 😄

@MrLotU
Copy link

MrLotU commented Jun 27, 2018

Yeah

@InukVT
Copy link

InukVT commented Jun 27, 2018

I see a lot of Auth libs, so they can be spun into their own category, or sub category of Utils?

Guys we're bikeshedding, let's keep it up!

@InukVT
Copy link

InukVT commented Jun 27, 2018

I made a pull request with a draft of cats to be used 😄

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

No branches or pull requests

3 participants