Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
alexbozhenko opened this issue Dec 12, 2023 · 20 comments
Open

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

alexbozhenko opened this issue Dec 12, 2023 · 20 comments
Labels
good-first-issue

Comments

@alexbozhenko
Copy link
Contributor

@alexbozhenko alexbozhenko mentioned this issue Dec 12, 2023
Merged
@alexbozhenko
Copy link
Contributor Author

@avelino this was created by running stale repos test.
Please take a look at description here:
#5127

@avelino avelino closed this as completed Dec 21, 2023
@phanirithvij phanirithvij reopened this Dec 22, 2023
@Mackinassdre
Copy link

@Mackinassdre
Copy link

Mackinassdre commented Jan 12, 2024 •
edited by phanirithvij
Loading

@GSWSN

This comment has been minimized.

Sign in to view
@BellaBijl

This comment was marked as spam.

Sign in to view
@Lexa77Q

This comment was marked as spam.

Sign in to view
@griggsca91
Copy link
Contributor

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

For example #5381 removed https://github.com/wesovilabs/beyond, should we check that off?

griggsca91 added a commit to griggsca91/awesome-go that referenced this issue Aug 15, 2024
@griggsca91
Remove github.com/olebedev/config
9b389ef 
Repo - https://github.com/olebedev/config

- [x] The project has not made an official release within the last year and has open issues.
    - It has been 2 years since an update to the repo
- [x] The project is not responding to bug reports issued within 6 months of submission.
   - https://github.com/olebedev/config/issues?q=is%3Aissue+is%3Aclosed last closed issue was in 2018
- [ ] The project is not meeting quality standards as indicated by the Go Report Card or Code Coverage tests.
- [ ] The quality standard links have been removed from the documentation.
- [ ] The project is no longer open-sourced.
- [ ] The project is incompatible with any Go version issued within the last year (there is hopefully an open PR about this at the project).


Related issue: avelino#5136
This was referenced Aug 15, 2024
Closed
Merged
yassinebenaid pushed a commit that referenced this issue Aug 15, 2024
@griggsca91
Remove github.com/olebedev/config (#5382)
89e0a2e 
Repo - https://github.com/olebedev/config

- [x] The project has not made an official release within the last year and has open issues.
    - It has been 2 years since an update to the repo
- [x] The project is not responding to bug reports issued within 6 months of submission.
   - https://github.com/olebedev/config/issues?q=is%3Aissue+is%3Aclosed last closed issue was in 2018
- [ ] The project is not meeting quality standards as indicated by the Go Report Card or Code Coverage tests.
- [ ] The quality standard links have been removed from the documentation.
- [ ] The project is no longer open-sourced.
- [ ] The project is incompatible with any Go version issued within the last year (there is hopefully an open PR about this at the project).


Related issue: #5136
@alexbozhenko
Copy link
Contributor Author

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

@griggsca91
Copy link
Contributor

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
Copy link
Owner

avelino commented Aug 15, 2024

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

  • open a PR removing the outdated package - automatically for the maintainers to review the PR
  • open an issue in the awesome-go repo with a possible quality problem in a project that is listed in awesome-go, but tagging the project's maintainers in the issue

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
Copy link
Contributor

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
Copy link
Owner

avelino commented Aug 15, 2024

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
Copy link
Collaborator

phanirithvij commented Aug 15, 2024 •
edited
Loading

Somewhat related, the inclusion crietria needs a revision as well avelino, see #5374

@griggsca91
Copy link
Contributor

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
Copy link
Owner

avelino commented Aug 15, 2024

@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
Copy link
Contributor

Sure I’ll make a separate issue for this then

@griggsca91
Copy link
Contributor

@avelino @alexbozhenko @phanirithvij accidently made a discussion instead :D #5383

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

Repository owner deleted a comment from Layer13w9 Aug 16, 2024
Repository owner deleted a comment from Layer13w9 Aug 16, 2024
@GSWSN
Copy link

GSWSN commented Aug 16, 2024 via email

@42atomys
Copy link
Contributor

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

@phanirithvij
Copy link
Collaborator

@42atomys merged. Thanks for maintaining it.

@Lexa77Q Lexa77Q mentioned this issue Aug 20, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good-first-issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
10 participants
@avelino @cassiobotaro @alexbozhenko @griggsca91 @42atomys @phanirithvij @GSWSN @Mackinassdre @BellaBijl @Lexa77Q