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.

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

Looking for new maintainer #43

Closed
bd82 opened this issue Mar 25, 2021 · 14 comments
Closed

Looking for new maintainer #43

bd82 opened this issue Mar 25, 2021 · 14 comments

Comments

@bd82
Copy link
Contributor

bd82 commented Mar 25, 2021

I no longer have time to maintain this project.
If anyone is interested in taking over this project please reply in this thread.

@aminya
Copy link

aminya commented Oct 2, 2021

I can publish the package on npm if that is the issue.

@bd82
Copy link
Contributor Author

bd82 commented Oct 6, 2021

This is about accepting responsibiliy for and maintaining the project longer term.
publishing to npm should already be automated...

@JounQin
Copy link
Member

JounQin commented Jul 11, 2023

@bd82 Hi, I'd like to help here, I'm also maintaining some prettier plugins at https://github.com/un-ts/prettier.

@bd82
Copy link
Contributor Author

bd82 commented Jul 13, 2023

Hello @JounQin

How would you want to proceed?

  • Fork + new package names, e.g prettier-plugin-toml-new

Or

  • Attempt to transfer permissions to existing names/namespaces?
    • I am not sure how to transfer permissions on none scoped npm packages...

@bd82
Copy link
Contributor Author

bd82 commented Jul 13, 2023

And do you want to move this code into your mono-repo in https://github.com/un-ts/prettier?
or keep it as a separate repo?

@JounQin
Copy link
Member

JounQin commented Jul 13, 2023

@bd82 Thanks for reply.

I'd prefer to keep the npm package name if permitted.

For the repo, I'd like to keep it separate for now and would you mind to transfer it to a new organization like @un-ts? That would make permissions transfer easier I think.

For the npm package, it can be easily done by npm owner add <username> command, see also https://docs.npmjs.com/transferring-a-package-from-a-user-account-to-another-user-account if you prefer web UI. My npm account is @jounqin.

@bd82
Copy link
Contributor Author

bd82 commented Jul 19, 2023

It seems I need permissions to create new repos on un-ts for the transfer to be initiated

image

@bd82
Copy link
Contributor Author

bd82 commented Jul 19, 2023

I sent you (jounqin) an invite to the @toml-tools scope on npmjs.com

@bd82
Copy link
Contributor Author

bd82 commented Jul 19, 2023

@JounQin I invited you as a maintainer for prettier-plugin-toml package on npmjs.com

@bd82
Copy link
Contributor Author

bd82 commented Jul 19, 2023

And I also invited you as collaborator on this repo.
But I do not think this will suffice to make the transfer.

I suspect I will need temporary create repo permissions on un-ts to perform the transfer

@JounQin
Copy link
Member

JounQin commented Jul 21, 2023

@bd82 I've invited you to @un-ts.

@bd82
Copy link
Contributor Author

bd82 commented Aug 1, 2023

@JounQin

I am not seeing any invite, perhaps it timed out.
Anyhow I moved the repo to a new temp org (toml-tools-temp) and sent you an invite
for OWNER permissions on this new org.

Once you move the repo to your org, I will delete this temp org...

@JounQin
Copy link
Member

JounQin commented Aug 1, 2023

Thanks @bd82 ! I've transferred the repository and deleted the temp organization.

@JounQin JounQin closed this as completed Aug 1, 2023
@JounQin
Copy link
Member

JounQin commented Aug 2, 2023

Hi, @bd82 do you have time to change my role on npm org toml-tools?

image

@JounQin JounQin unpinned this issue Aug 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants