Improving this repository about awesome-scala HOT 29 CLOSED

Save the stars. The stars show a community size.

from awesome-scala.

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 - .

from awesome-scala.

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?

from awesome-scala.

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.

from awesome-scala.

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:

from awesome-scala.

from awesome-scala.

Also my apologies for not being around and participating for the past xx years, was deep down some other rabbit holes.

And of course big shout out to @SethTisue for carrying this project ❤️

from awesome-scala.

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

from awesome-scala.

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

from awesome-scala.

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.

from awesome-scala.

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.

from awesome-scala.

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

from awesome-scala.

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

from awesome-scala.

@benash your proposed change LGTM. in the absence of any feedback from @lauris, I'd be happy to review/merge a PR on this

from awesome-scala.

I also tried contacting @lauris privately and didn't hear back.

I don't want to be the de facto owner and maintainer of this repo indefinitely, so honestly at this point I'm inclined to just archive it, and figure that if anyone wants to fork it and revive it under a different user/org, great.

from awesome-scala.

Oh, my access rights aren't sufficient to use the "archive" feature, actually.

I guess the closest thing would be to put a banner at the top of the readme with a notice explaining where things stand, linking to this ticket.

If nothing has changed by, uh, let's say May 1, then I intend to do that.

from awesome-scala.

@SethTisue would you like help maintaining this?

from awesome-scala.

Depends on what you mean by “help” :-)

Only @lauris can anoint new maintainers. I’m only a backup maintainer — I don’t feel I have time to be a primary maintainer, I have too many other OSS commitments.

If we don’t hear from him by May 1, then if you want to be the primary maintainer of a fork, I would be happy to help you with that, but it would me helping you, not vice versa — make sense?

from awesome-scala.

Yep makes sense.

I'm willing to create a fork if we don't hear back from @lauris my May 1.

I feel like Scaladex should be the go to place for finding libraries rather than this list. I wonder how many of the libraries on here are not in the Scaladex?

There is still a need for a curated list of other Scala resources like tutorials, books, blogs, courses, conferences, meetups etc. I'm not even sure whether this list is the best for that.

I also like subscribing to this repo as a way of discovering new Scala libraries. There is scalacenter/scaladex#437 which potentially solves that.

from awesome-scala.

There is still a need for a curated list of other Scala resources like tutorials, books, blogs, courses, conferences, meetups etc. I'm not even sure whether this list is the best for that.

(I'm partial to https://www.scala-lang.org/community/ for that)

from awesome-scala.

Nice! I'll admit, I didn't know that page existed.

I wonder if a bit of consolidation is in order:

1. Contribute to Scaladex to help get a notification system in place.
2. Remove all the libraries from here that are in the Scaladex.
3. Have a hard look at what is left to see if it is worth keeping or helping to get into the Scaladex.
4. Remove other links from here that are already on https://www.scala-lang.org/community/
5. See if anything that is left over is worth moving to https://www.scala-lang.org/community/ (exercism.io, coursera course...)

That mostly just leaves the books and the blogs.

from awesome-scala.

@steinybot ready to go ahead with forking?

from awesome-scala.

@steinybot interested in returning to this?

from awesome-scala.

At this point if I could I would simply archive the repo, but I don't have sufficient rights to do that.

Is there another volunteer interested in taking charge of this repo...? (If so, we could make another attempt to contact @lauris, perhaps by trying to figure out where he works?)

from awesome-scala.

Hey everyone, just to let you know that we are close to release a new "Awesome Scala" page in Scaladex. It is not yet officially released but it is already visible here: https://index.scala-lang.org/awesome

If you see anything that could be improved, please open an issue or a discussion in https://github.com/scalacenter/scaladex

from awesome-scala.

Adrien's new blog post on this: https://scala-lang.org/blog/2022/03/08/finding-awesome-libraries.html

from awesome-scala.

I suggest we update the README in this repo to consist only of a link to https://index.scala-lang.org/awesome, a link to the blog post, and then also a link to a file containing a final snapshot of the links list.

And also stop accepting new submissions, since no new maintainer has stepped forward and I personally don't want to continue with it.

from awesome-scala.

First of all congrats on the new Scaladex site - it looks really cool.

I (and hopefully other Scala devs) still find this repository valuable and wouldn't like to see it being destroyed. I like the simple format of Github awesome-lists. If @SethTisue no longer wants to maintain the PRs that's alright. I will continue maintaining this repository as a legacy archive.

Cheers.

from awesome-scala.

@lauris oh hello 👋 — sure, SGTM

from awesome-scala.