Skip to content

switching xarray away from a global token #58

Closed

Description

@keewis

As requested in #57 (and as a separate issue in order not to hijack that one), I've been looking at switching the xarray token to something that is not global. However, I couldn't find any documentation on how to do that (nor figure it out myself). Note that the global xarray token that was still active was replaced by a personal token about 4 months ago, and it is now revoked.

Somewhat relatedly, I've also not been a member of the xarray group, but this I could easily fix since I had been a member of the global organization (I'd be fine with relinquishing that additional power, which I don't really need).

Can anyone explain to me what needs to be done to migrate the token?

Activity

  1. matthewfeickert commented on Jan 24, 2024

    @matthewfeickert
    Member

    Thanks @keewis! I think that @tupui can probably give you a good short summary here of how to move forward.

  2. tupui commented on Jan 24, 2024

    @tupui
    Member

    Hi @keewis, thanks for the fast reply 😃

    I will remove you from the admins then as to keep the list more "manageable" and have more separation of responsibilities between all of us. Which is the goal of having teams.

    To create your personal token you need to be connected with your account

    1. on the top right corner check that you are on your profile, you can click on Switch to... if that's not the case
    2. Under settings/Access you can create a token
    3. Create the token with proper scope and expiry (ideally not rotate every year or so.)
    Screenshot 2024-01-25 at 00 18 25

    The doc is here https://scientific-python.org/specs/spec-0004/#process-for-adding-new-projects
    Let me know if something is not clear and once you have done the change so that I can remove the old token. Thanks in advance 🚀

  3. tupui commented on Jan 24, 2024

    @tupui
    Member

    Actually seems like someone (hopefully you) already removed your global token. So I will close this issue.

  4. keewis commented on Jan 24, 2024

    @keewis
    Author

    yep, that was me (see the access log). Turns out we had done the migration already, and that token was unused.

    The doc is here https://scientific-python.org/specs/spec-0004/#process-for-adding-new-projects

    Might I suggest to update the readme of this repository to either point there or say the same thing? That would have made that information easier to find.

    I will remove you from the admins then as to keep the list more "manageable" and have more separation of responsibilities between all of us.

    When I joined the organization I also added @kmuehlbauer (and @jhamman? not sure) as a global admin. Before leaving the organization I added both to the xarray team, so I believe you should also be able to remove them from the global admins (once again, not sure, because there might be other reasons they're in that list – but you should have a better view of that than I do).

  5. tupui commented on Jan 25, 2024

    @tupui
    Member

    Thank you 🙏

    I don't know for the other admins. I will bring that up in the next meeting.

  6. tupui commented on Jan 25, 2024

    @tupui
    Member

    And yes good suggestion for the readme

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions