avelino / awesome-go

A curated list of awesome Go frameworks, libraries and software
https://awesome-go.com
MIT License
133.51k stars 11.95k forks source link

Investigate repositories with more than 1 year without update - 2023-12-11 #5136

Open alexbozhenko opened 11 months ago

alexbozhenko commented 11 months ago
alexbozhenko commented 11 months ago

@avelino this was created by running stale repos test. Please take a look at description here: https://github.com/avelino/awesome-go/pull/5127

Mackinassdre commented 11 months ago
Mackinassdre commented 10 months ago
GSWSN commented 10 months ago

https://github.com/labstack/gommon/tree/master/color this repository might no longer exist! (status code >= 400 returned)

Think it may be my runaway program Status code >=400 Possibly redirects to \@../@/

looking for help with development

BellaBijl commented 8 months ago

Blessed be

Lexa77Q commented 6 months ago

griggsca91 commented 3 months ago

As things get removed or investigated, should we update this issue identifying the packages that have been handled?

For example https://github.com/avelino/awesome-go/pull/5381 removed https://github.com/wesovilabs/beyond, should we check that off?

alexbozhenko commented 3 months ago

I feel like proper way would be automating creating of such PRs, so maintainers can merge them with the least amount of effort.

griggsca91 commented 3 months ago

More than happy to give that a shot. I imagine it would be using GitHub’s actions that run on a cron.

Any issues if I give it a shot?

avelino commented 3 months ago

Any issues if I give it a shot?

@griggsca91 I didn't understand what you're trying to do listing outdated packages is 'cool', but I think it's important to have jobs with more execution, e.g.:

this type of initiative helps us keep awesome-go updated, but just listing how this issue is doesn't help much - that's why it had almost no interaction

griggsca91 commented 3 months ago

Not sure I’m following. I been looking at some of the packages in this list and investigating if they’re still maintained, used, or have active development.

If not I’m just submitting a pr with its removal and some evidence of the project no longer being active. My understanding was to help reduce the number of packages in this list that no longer are used and provide a high quality list of active and supported projects.

appologies for misunderstandings, but based on a suggestion above, my thinking was to build some automation to create a PR or issue at least for projects that have had no activity for a certain time so it’s easier to review and merge them.

let me know if there is any clarification needed or is this issue not something that the project doesn’t want done.

avelino commented 3 months ago

I made the previous comment because the process doesn't "scale" and will be very labor-intensive.

appologies for misunderstandings, but based on a suggestion above, my thinking was to build some automation to create a PR or issue at least for projects that have had no activity for a certain time so it’s easier to review and merge them.

this path is where I can see automating the periodic review of the packages listed in awesome-go I know we will have cases that will be false positives, but it will probably be easier to deal with than the hassle of keeping outdated packages on the list

phanirithvij commented 3 months ago

Somewhat related, the inclusion crietria needs a revision as well avelino, see https://github.com/avelino/awesome-go/pull/5374

griggsca91 commented 3 months ago

Agreed @avelino . I was offering to see if I can attempt at creating something like that, at least a starting point to have an automation for such a thing

avelino commented 3 months ago

@griggsca91 of course you can, all contributions are welcome. It's worth opening an issue describing what you envision for the implementation, so we can contribute to having a solution that covers as many cases as possible.

griggsca91 commented 3 months ago

Sure I’ll make a separate issue for this then

griggsca91 commented 3 months ago

@avelino @alexbozhenko @phanirithvij accidently made a discussion instead :D https://github.com/avelino/awesome-go/discussions/5383

I can make it an issue if you guys want or we can have the discussion there

GSWSN commented 3 months ago

couldn't you automate this via git actions and workflows. say for instance, a dependabot.yml to configure alerts for merges and and another bot config to trigger PR'sOn Aug 15, 2024, at 11:20 AM, Alex Bozhenko @.***> wrote: I feel like proper way would be automating creating of such PRs, so maintainers can merge them with the least amount of effort.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

42atomys commented 3 months ago

Hi for the repository https://github.com/Masterminds/sprig, I already do the investigation and open a PR, all are listed in it : https://github.com/avelino/awesome-go/pull/5384

phanirithvij commented 3 months ago

@42atomys merged. Thanks for maintaining it.