New gem release site dominated by one organization about rubygems.org HOT 12 OPEN

I understood your frustration. But It's hard to define criteria for hiding targeted gems.

I'm +1 to collapse(not hide) with paginate UI like tencentcloud-* or aws-sdk-* or something.

from rubygems.org.

Do you point tencentcloud-sdk-*?

Yes!
It would be nice to see all the other different gems in the list.

Update: Now it's 18:40 in Japan and half of the tencent gems are not on the release page anymore.

from rubygems.org.

Apologies, I accidentally liked these from my work account.

I think that an additional scope would be handy. I feel like organizing by pusher would be a great way to condense the large projects that are receiving a lot of pushes.

Also agree with @Largo that it would be cool to have a sort of spotlight for smaller creators that would allow them to get some exposure through the site. I think the problem would come down to how we determine how authors are getting featured. I think it would be difficult to create a fair system for doing this.

For the time being moving forward with adding the pusher scope is sufficient. I would even say that it would be a good default scope for the new releases page. Not sure how you all would feel about that. But I think it is something to consider.

from rubygems.org.

@stirlhoss feel free to take a look. Per my understanding nobody is working on this currently. UI wise I think you can just add other tab as I suggested, group releases (versions) per pusher_id and render somehow. I can help on frontend stuff in the PR.

from rubygems.org.

Do you point tencentcloud-sdk-*?

from rubygems.org.

14:25 JST: Now page 1 to 10 are all tencentcloud-sdk-*

One option would be to only show X releases by the same author on those pages.
But maybe it makes more sense to hide all tencentcloud-sdk-*?

Almost all of these releases are just a change in version number..

from rubygems.org.

I don't understand what's the problem in here. https://rubygems.org/releases just enumerates latest gem releases. And indeed some gem maintainers do bulk push of various gems at the same time during release time including tencentcloud, aws-sdk, opentelemetry, ... Those are usually monorepos split into smaller pieces released individually. In my eyes this page works exactly as intended.

To address original complain, would it be enough to add another scope and group latest gems by pusher? That way it would be possible to see something like:

• awscloud pushed 20 gems (gem1, gem2, ...)
• other_maintainer pushed 1 gem (other_gem)
• ...

New scope could be added to this part of the page.

@Largo @stirling-hostetter would that work for you? 🤔

from rubygems.org.

@simi I just think that it should be possible to see the newest releases of unique gems on the website for some time, maybe three days? It looks like if it wasn't for these mentioned gems then that would be the case.

I think that it would be nicer to authors of smaller gems to give people a better chance for people to find them. After all there are a lot of old and not updated gems on rubygems.

I think your proposal is okay. 👍

from rubygems.org.

Is there anyone who is wanting to work on this? I can probably do the backend stuff but I am not too handy on the front end (though I could likely figure it out). I could open a draft PR to start organising this at least.

Are there any other thoughts or considerations we should be taking into account?

from rubygems.org.

@caden-jarrett Do you have any interest in working on this with me?

from rubygems.org.

@stirlhoss yeah looks solvable for sure, just let me know when!

from rubygems.org.

@stirlhoss @caden-jarrett if you need help, feel free to join us at Slack (link at the bottom of https://bundler.io/).

from rubygems.org.