Improving this repository

[lauris]

I've assembled some things I'd like to do to improve this repository. This list includes things from other issues posted recently, as well as other popular awesome lists on Github. One example of a good list is awesome-go.

• Make list more easy to read by removing stars, hourglass and bold. It make the list appear more messy. The rationale here is that all packages included in this list should note worthy and up to date. Metadata script that is needed to display stars also increases friction for new contributions.

• Make sure that entries are sorted alphabetically. Enforce it by adding travis integration.

• Cleanup old/niche packages with no stars. If package has very few stars, seems deprecated or not suited for this list it should be removed. Quality over quantity.

• Add better structure, for example, sub-categories for large sections like Database.

• Make it easy to submit correct PRs - add contribution guide, travis integration and tests for basic rule checking.

Notes: Stuff like star count, days since last activity could be added as part of a separate website. I don't think that Github repo is best suites for adding dynamic content to the README.md file.

[lauris]

I've started making these changes in a new branch improve-441.

[fshp]

Save the stars. The stars show a community size.

[jiminhsieh]

If we want to continue to use the stars, we may consider using the badge. Otherwise, the total number of starts of project are all outdated.

For example, we could use this - .

[lauris]

Agreed. There is a service called shields.io that provide the badges in svg format. That seems to be the most convenient way to add dynamic star counts to the readme.

Example:

[jiminhsieh]

I want to improve this one. I have a question about the result of adding the badges.

Here is the example of new version:

• Anorm - - Simple SQL data access

Here is the original version:

• Anorm ★ 135 - Simple SQL data access.

Is the new version fine for you all? Thanks.

[jiminhsieh]

@lauris Do you have any thoughts about the above comment? Thanks.

[lauris]

I'd prefer the badge, but it would be great if the badge aligned with each entry. Perhaps there are different badge layouts/sizes we can use?

The badge is a good options because it will be most up to date.

[jiminhsieh]

it would be great if the badge aligned with each entry. Perhaps there are different badge layouts/sizes we can use?

I cannot find any things helped in https://shields.io/.
They do have ?logoWidth=40, it will change the badge and I don't see any difference.

• Befter applying ?logoWidth=40
  
• After applying ?logoWidth=40
  
• Another project with ?logoWidth=40
  

However, I did find another similar site that offers badge too.
https://githubbadges.com

• 
• 
• 

Although I don't see much of that star of the project, it does serve our purpose that the badge will have a good alignment.

[benash]

I'd like to help with this issue. How about a table format?

Name	Description	GitHub Stats
Cassovary	A simple big graph processing library for the JVM
Cats	Lightweight, modular, and extensible library for functional programming.
Chimney	Scala library for boilerplate-free data transformations.
Dsl.scala	A framework to create embedded Domain-Specific Languages in Scala

We'd also have the option of including other repo info, like this:

Name	Description	GitHub Stats
Cassovary	A simple big graph processing library for the JVM
Cats	Lightweight, modular, and extensible library for functional programming.

What do you think?

[benash]

@lauris Any thoughts, positive or negative, on the above?

[SethTisue]

#481 updates the automation for updating the star counts from time to time