Support for giving multiple team members publishing permissions

[nebrelbug]

Is your feature request related to a problem? If so, please describe.
I would love to use Nest.land, but would like to allow others to become maintainers and have publishing permissions.

Describe the solution you'd like
It would be great if module "admins" (creators) were able to add other module admins

[t8]

Hi Ben, thanks for reaching out. This is a great idea! We are investigating the possibility of building this for organizations specifically.

Organization support itself will be an MVP 3 priority. We're currently working towards our MVP 2, so know this is on the horizon!

[michael-spengler]

I can imagine that this makes things much more complicated.

From my experience as a "Product Owner" in other contexts I can recommend to wait with the implementation of this until someone pays an appropriate amout of ETH for this - e.g. via https://gitcoin.co/

Things like that cost from my perspective much more than the benefit is worth.
Modules shall anyhow be finegranular from my perspective.
People who trust each other as a team could share their corresponding key file which they use for this - as a workaround.

@nebrelbug: If I'm having a lack of understanding here, feel free to let me know. I love to learn.

[nebrelbug]

@michael-spengler this feature would be important for me specifically because I'm going to have to transfer several of my packages to community in around 2 months, and will be unable to access the internet for some time afterward. I'd rather not give my personal token to someone for several years if I can't verify that they're using it in good faith.

🤷‍♂️ I understand that this could be quite a difficult feature to implement, though

[michael-spengler]

@nebrelbug thanks for the additional background infos. I can understand that. One more question from my side:
Would it also be cool, if you could revoke your current API Key and regenerate a new one for specific modules which you then share with the people who will take care of the modules long term?

We used this approach for some of our Telegram Chatbots - meaning only sharing some API keys / Tokens

[nebrelbug]

@michael-spengler I would probably be ok doing that... I guess I'm a little cautious because of the docs 🤣

Do not share your API key with anyone.

If you want others to be able to publish a new version of your module, don't worry. We're working on a better solution!

[michael-spengler]

:) I understand - ... it's good to have some options on the radar now and I'm pretty sure Tate & friends will choose wisely when the time is right :)

[t8]

Organization support is something we look forward to bringing to Nest.land, but I don't know when we'd be able to do it (lots of other plans too!).

An alternative option might be setting up some CI for your repositories to automatically publish to Nest.land on releases?

See:
Our repo for doing this: https://github.com/nestdotland/eggs-ci
An example: https://github.com/halvardssm/deno-nessie/blob/master/.github/workflows/publish_nest.yml
Another example: https://github.com/asos-craigmorten/opine/blob/main/.github/workflows/publish-egg.yml

Let me know if this helps!

[nebrelbug]

@t8 ah, I think I'll end up doing that for now. Thanks!