Closed rossabaker closed 2 years ago
Definitely raising my hand for spire, if you'll have me! And possibly some other projects, depending on other volunteers and whether they are important enough to be spared archival.
@armanbilge you should talk to @cquiroz about Spire. He has been working on the Scala 3 port.
Great. Spire is (probably?) the most starred of these, and I'd love to see it continue strong. I see @cquiroz has been active lately as well.
Spire is the library that introduced me to the typelevel ecosystem actually (and where I learned to program Scala tbh) :) Yep, I've been following along with @cquiroz efforts!
For fun, here's me giving a talk about spire once upon a time ago 😆 https://twitter.com/ScalaAtTheSea/status/950927583289290752
@rossabaker I am interested in the maintenance of simulacrum 👍
@rossabaker I'd be happy to help with maintaining mouse
, I'm in love with fold
on boolean for years :) Also, I'm interested in maintaining semigroups
and monoids
if possible.
Eager to help with any, most likely cats-collections
and/or cats-time
.
@rossabaker I am also interested in the following maintenance:
I wrote most of the original cats-collections data structures along with stew, but it seems that we both are not committed to maintaining it. I hope someone does it and keeps it alive.
I would be glad to help out with something like cats-time
and/or cats-collections
.
Would be glad to help with cats-collections & may be semigroups
I'd like to help on spire
given my work on the scala 3 port and cats-time
as it interacts with Scala-java-time
Does algebra
have maintainers? If not I could help there as well
I could try to help on frameless
@rossabaker I'm also interested in keeping frameless up to date. In the most recent work of upgrading https://github.com/locationtech/rasterframes up to the fresh Spark it turned out to be a lifesaver. Cc @cchantep
Wonderful. A couple of these projects are quite small and got multiple volunteers. There's not going to be enough trivial work on all of them, but some are probably ripe for feature work. There's always more collections, there's always more instances, etc. Having a partner will be great for reviews. If you feel redundant on any of these projects, please speak up and we will find you more work!
The projects are on this list because Lars had done the recent work and nobody picked it up since. Most of them have longtime maintainers who are still around the community. It would be both polite and wise to try to talk to these people before any major changes:
If I tagged you above, but you didn't get a GitHub invite, please ping me. I was doing a lot at once and the dog has decided to stop sleeping through the night this week. :zzz:
Since most of you have a partner, I'm not merging anything I see rolling in. I'm interested to watch new teams and new leaders. But if anybody wants my review or otherwise gets stuck, please don't hesitate to tag me.
@cquiroz There's an open PR about folding Algebra into Cats. It was controversial at the time and I haven't caught up with where it's at, but the answer depends on that resolution.
Right, I don't really have an opinion about it. I mostly care about algebra
as requirement for spire
@cquiroz @rossabaker that's my PR actually https://github.com/typelevel/cats/pull/3918, would be really great if it could get merged. I think the controversy is also now on hiatus, unless someone wants to volunteer for that ;)
I volunteer to maintain discipline-specs2
, it is a dependency of Cats Effect.
@rossabaker I can help out! I'm familiar with most of them; I can volunteer for the ones that have no one assigned.
I volunteer for simulacrum
and simulacrum-scalafix
@rossabaker I'd love to help out with discipline-scalatest, thanks
@danicheg Your help on mouse
would be welcome, thank you!
@rossabaker you might have mislabeled the first post,
Yep, caught it, was fixing it, got called into a meeting. 😓 You and @gagandeepkalra should both be set now.
@regadas We got at least one volunteer for everything but cats-testkit-scalatest.
If this continues to go well, there are some that have been mostly Lars and me lately that I'd love help on. There may be a sequel ticket.
Hello! Sorry for jumping late on this thread. We definitely need more help with frameless so it’s great to have one more on the team! I want to get back and help more as well. Thank you Marios
On Wed, Aug 25, 2021 at 11:54 AM Ross A. Baker @.***> wrote:
@regadas https://github.com/regadas We got at least one volunteer for everything but cats-testkit-scalatest.
If this continues to go well, there are some that have been mostly Lars and me lately that I'd love help on. There may be a sequel ticket.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/typelevel/general/issues/111#issuecomment-905790244, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABUTCD7I3NL6EV74VK6ZTYTT6U37JANCNFSM5CYDEDUQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .
Hey @rossabaker , since I am new to open source, can I be part of this ?
I would love to help out with Spire
and cats-effect-testing
. Thank you.
To keep project health up across the board, I'd like to focus first on making sure we have at least two active maintainers everywhere. This issue was bootstrapped with The Lars Projects, but I'll plan on adding some more soon. I unchecked the ones that still have just one volunteer.
Of course, all these projects appreciate contributions. If you're specifically interested in Spire or one of the others, please jump in with comments and PRs!
@rossabaker I am also interested in the following maintenance 👍
@rossabaker I would love to help with munit-cats-effect
. Also, I do a lot of spark at work so at some stage wouldn't mind lending a hand in the future with frameless
.
Caveat is I am relatively new to the Typelevel eco system but keen to ramp up on it so what better than helping here.
In addition to the above projects I am very experienced with GitHub Actions so any help with the typelevel worlds ci bulid side of things I would love to help.
Thank you for the opportunity.
I would like to help with munit-cats-effect
, thanks!
We already have coverage on munit-cats-effect
and frameless
. I'd love to get some more maintainer coverage on the others that are unchecked above. Would any of those be appealing? Of course, as noted above, all of these projects would love to get contributions, where you have specific interests.
@softinio There is a lot of build debt around the ecosystem, so that would be a great place to get involved in general. There are sbt-spiewak and sbt-davenverse projects that are both excellent for providing batteries-included builds, and I think it would be swell if someone sat them down and reconciled the differences and it resulted in an sbt-typelevel. A way to make incremental progress would be sbt-github-actions, which is used by both, to replace any lingering Travis CI builds or projects without builds.
@rossabaker Definitely down for helping with the build debt around the ecosystem and replacing the ones still using Travis.
| There are sbt-spiewak and sbt-davenverse projects that are both excellent for providing batteries-included builds, and I think it would be swell if someone sat them down and reconciled the differences and it resulted in an sbt-typelevel.
Down for that too. Totally my element :-) Excited for this, thanks for the great idea.
Do you have a particular preference with which repo I should start with?
Else when I get a moment will take a look at all the repos and try to figure out the state of each.
Thanks!
It looks like we've done a better job getting off Travis CI than I realized: I can't find any .travis.yml
files. I wonder whether there's a way to query for projects without a .github/workflows/ci.yml
? And as a second tier, projects whose workflows aren't generated by sbt-github-actions?
The build that most recently caused me pain was kind-projector's, because I had to publish locally. It has sbt-github-actions already, so progress there would depend on a merger between sbt-spiewak / sbt-davenverse, unless we just picked one for now.
👍 to an sbt-typelevel
. It helps a lot with contributing when builds tend to work the same way :)
So thinking out loud to work towards an sbt-typelevel
and to standardize our builds it probably would be useful to as I iterate to test and try new ideas on one single repo. So one thought is I put my hand up to maintain one of the remaining projects with no maintainer and in addition to helping with maintenance I use that as the guinea pig edge build repo to test and to show.
If you agree with this thought maybe I can help maintain scalacheck-effect
that seems still available. Will help me learn cats-effect
as a side effect (pun intended 🤣) too.
@rossabaker I'd be happy to help with projects that still require maintainers. Unfortunately, I don't have much experience contributing to open source projects, so would be grateful for some initial guidance
If you're new to contributing at all, I would try submitting a PR before focusing on maintaining a library. Then you'll be familiar with the process from the other side. I would take a look at the good first issues open in Typelevel and comment on any that catch your eye. A maintainer should then either assign it to you, or realize it's stale (sometimes we fall behind grooming issues) and politely suggest looking for another one.
Maintainers: the "good first issue" tag is your friend!
There are many good first issues in Cats Effect, this one is begging for a PR! https://github.com/typelevel/cats-effect/issues/587
I am interested in helping with maintaining the kind-projector
if there are no willing contributors.
@rossabaker I am also interested in the following maintenance 👍
@vendamere is already keeping simulacrum-scalafix fresh, but it's nice to have double coverage, especially if either if you start enhancing it.
Claimant had been marked as "no maintenance intended", but you're welcome to revive it if you've got ideas.
Declaring victory. We'll handle ongoing calls in individual projects, or broad initiatives in governance.
There's no replacing Lars, but their open source hiatus has left a handful of projects with lagging maintenance. This is a tremendous opportunity for new maintainers to step forward. Responsibilities include:
If you're interested in learning the above, but unsure you're ready, we will help you.
The following projects have most recently maintained been carried by Lars. Please comment if you're interested in keeping any of them going. Projects that nobody speaks for may be considered candidates for archival:
These have one active person, and would benefit from a second. Much of the recent work is keeping up with dependencies: