search

jcs-legacy / helm-file-preview

Preview the current helm file selection.
GNU General Public License v3.0
11 stars 5 forks source link

Move repos to orphanage #6

Open jcs090218 opened 2 years ago

jcs090218 commented 2 years ago

Hi @tarsius!

I would like to move some of my repos to Emacs Orphange, (they are all on melpa)

I have less interest maintaining these packages so I would like to maintain it over there. Can you give me the permission to do so? Thanks! 🙏

Another trivial question, I was in the org but got removed afterward w hile. Are people now allow to be in the org due to some policy? Just curious. It benefits me to link to the org under my profile page, much convenience. 😅

tarsius commented 2 years ago

I would like to move some of my repos to Emacs Orphange, (they are all on melpa) I have less interest maintaining these packages so I would like to maintain it over there.

That isn't the purpose of the orphanage. It should only be used for packages that aren't being maintained anymore. While you have lost interested in these packages, you are still willing to maintain them, which is applaudable. IMO it would be better to leave them where they are now, but add a disclaimer at the beginning of the readme and commentary, stating that they are only in maintenance mode.

We can discuss this further, but in general adding packages isn't a goal. Finding new maintainers and ideally in a second step moving these repositories out of the orphanage again, that is the goal. (Though we aren't very good at the second step, so I now tend to favor transferring abandoned repositories directly to a new maintainer, instead of taking a detour through the orphanage.)

I was in the org but got removed afterward while. Are people now allow to be in the org due to some policy?

I am not sure about this, but in the past I might have added people, who volunteered to maintain a few packages, as members of the organization. Nowadays we only have two owners (@purcell and me) and one additional member (@phikal). If I had added you as a member before, then I removed you because that position is now reserved for people who help maintain the orphanage as a whole.

People who maintain individual repositories are now "outside contributors". Their permissions are managed for each repository individually (though that was already the case before). Currently there are 17 such contributors. Most of them only have access to a single repository, five of them have access to multiple repositories.

You currently have the maintain permission for these repositories: applescript-mode, fontawesome, git-gutter, haxe-mode, helm-ag, helm-gtags, helm-themes, manage-minor-mode, popwin, quickrun, sound-wav, undohist, yascroll, zoom-window. Let me know if you lost access to a repository, which you are still willing to maintain.

tarsius commented 2 years ago

Oh, and we now have a place for such suggestions: https://github.com/emacsorphanage/.github.

That repository is pinned at https://github.com/emacsorphanage with the description "Talk and learn about the Emacsorphanage", but I will have to make that more visible and explicit.

jcs090218 commented 2 years ago

Thanks for the explanation!

While you have lost interested in these packages, you are still willing to maintain them

Sorry, I wasn't clear enough in my first post. I don't want to maintain these packages anymore, but I can keep maintaining it until someone willing to take over or step up as the new maintainer. Would this fulfill the statement (from emacsorphanage/.github)?

  • If you no longer want to maintain a package, then transferring it to the orphanage is an alternative to just archiving the repository. That way, we can keep it usable, and if someone volunteers to become the new maintainer, you do not have to be involved in the process.

LMKWYT?

IMO it would be better to leave them where they are now, but add a disclaimer at the beginning of the readme and commentary, stating that they are only in maintenance mode.

I think Emacs orphanage is a better place to keep these packages (packages need new maintainer) instead having it under my own name (jcs-elpa, jcs090218, etc). It should give these packages more exposure about looking for new maintainers.