mike-jumper commented on PR #896: URL: https://github.com/apache/guacamole-client/pull/896#issuecomment-1795505304
@everflux Sadly, it looks like the `guacamole` name is already taken at the org level, so `apache-guacamole` or a similar variant might be all that's possible (unless the owner of that org/username is willing to relinquish it): https://www.npmjs.com/org/guacamole As for the package itself, I think a reasonable path forward might be to get in contact with @padarom, the individual that produced and maintains an NPM-ified fork of guacamole-common-js: https://www.npmjs.com/package/guacamole-common-js If we can take over ownership and maintenance of that package within NPM, then existing users of the established NPM package would be able to continue using it without interruption, and former users of the original pure-Maven package looking to migrate to NPM would have the benefit of familiar package naming. @padarom, any thoughts? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
