-
Notifications
You must be signed in to change notification settings - Fork 32
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
Give NPM publishing permissions to me and/or deprecate this library #38
Comments
Please add a comment here if you end up deciding to fork it and publish on npm. I'm also looking forward to having types for this library. In case anyone needs types, here's the patch-package file react-accessible-treeview+2.1.4.patch
|
Hi @dgreene1 I'm down to do a full transfer, but you need to delete or rename your fork for github to be able to do it, and I also need your npm alias. |
@lissitz thank you so much. I have deleted my fork. |
@lissitz looks like the repo name changed but I will need publishing right too. So when you have the time, please run the command line snippet in https://docs.npmjs.com/transferring-a-package-from-a-user-account-to-another-user-account Thanks again for your time and generosity. |
Is your npm username also dgreene1? |
Hi @lissitz, we’re going to try to publish this soon but we (@mellis481 and I) don’t know how to update the Netlify site. Are those stored as secrets in Travis? Either way, can you add me as a user to your Travis build server and to Netlify? As an alternative, we could consider making a new website (like through Github pages) and then you (or us) could add a redirect from the old Netlify site to the proposed Github Pages site. |
Hi @dgreene1 , the Travis server was only used to check the build didn't fail. I think it is not active anymore. For the Netlify site, I think the easiest way is to make a personal transfer https://answers.netlify.com/t/support-guide-how-to-transfer-a-netlify-site-to-a-new-owner/3866. For that I need an email that is associated with a netlify account. In the meantime, the netlify site deploys automatically after every commit, but the |
@lissitz if you give me your email I can email you mine. I don’t want to list my email here. Or you can DM me at https://www.linkedin.com/in/thedangreene and then I can reply with my email. |
@lissitz What actually triggers the Netlify deployment because we just did a release, but the Netlify documentation was not updated. |
Once we get Netlify access we will redirect that to our new Github Pages site. But since we have access to (new) documentation and to deploy via NPM, we’ll close this ticket. |
Hi @lissitz, I'd like to formerly request (a) to be made admin of this repo and (b) to be given NPM publishing access. This is a continuing from the conversation in #23 (comment) where you said:
My team and I have made significant updates to this library and have motivation to continue maintaining it for the foreseeable future. But in order for us to do that, we need to be able to publish it whenever we have a business objective or a customer commitment. Having to rely on someone outside of our team causes us to miss those deadlines. For example, we have PRs that haven't been released in 20 days as of this writing.
So @lissitz, please choose whichever option is best for you. The options I see are as follows (in order of my preference):
I want to emphasize that the choice is yours. I want this to feel like we're here to support you and to celebrate your wonderful accomplishments of creating (what I believe is) the only accessible tree view for React. Well done! You've done great work so now you should be able to rest on those laurels and let us take it into maintenance mode.
The text was updated successfully, but these errors were encountered: