Eli Zaretskii <eliz@gnu.org> writes: >> From: Payas Relekar <relekarpayas@gmail.com> >> Cc: philipk@posteo.net, stefankangas@gmail.com, johnw@gnu.org, >> monnier@iro.umontreal.ca, emacs-devel@gnu.org >> Date: Wed, 16 Nov 2022 20:59:26 +0530 >> >> Eli Zaretskii <eliz@gnu.org> writes: >> >> >> From: Payas Relekar <relekarpayas@gmail.com> >> > >> >> Once it is merged and ELPA starts tracking use-package from core, >> >> we should probably ask John to mark the repo as archived on Github as an >> >> added incentive to direct people to emacs-devel as well as prevent >> >> people from creating new bugs/PRs on Github. Does that sound like a good >> >> idea? >> > >> > Yes, I think so. >> >> This is thinking ahead, but we'll want to think about existing open >> issues and PRs before making repo archived. > > I don't understand why. Even if archived, it is accessible, no? AFAIK you cannot respond to an issue on GH when the repository is archived, so that would make it difficult to tackle any issues that would require feedback or discussion in general.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4