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

Enable all submitted organisations on production instance #1951

Closed
3 tasks done
spwoodcock opened this issue Dec 4, 2024 · 8 comments
Closed
3 tasks done

Enable all submitted organisations on production instance #1951

spwoodcock opened this issue Dec 4, 2024 · 8 comments
Assignees
Labels
devops Related to deployment or configuration effort:low Likely a few hours enhancement New feature or request priority:low Backlog of tasks that will be addressed in time

Comments

@spwoodcock
Copy link
Member

spwoodcock commented Dec 4, 2024

Todo

  • Approve organisations that have been created by people on prod.
  • Set the default ODK creds as the HOT instance.
  • Test creating a project as a different org than HOTOSM.
@spwoodcock spwoodcock added devops Related to deployment or configuration effort:low Likely a few hours enhancement New feature or request priority:low Backlog of tasks that will be addressed in time labels Dec 4, 2024
@spwoodcock spwoodcock added this to the (v2025.1.0) future release milestone Dec 4, 2024
@spwoodcock spwoodcock self-assigned this Dec 4, 2024
@manjitapandey
Copy link
Contributor

1st and third point is already done and is functional.

@spwoodcock
Copy link
Member Author

I will finalise this now by adding ODK Central users for each requested org 👍

Note that we previously had a bug where the created_by requesting user was not recorded!

Image

So we don't know who requested creation of these orgs, to assign them org admin. We might have to find out via informal means such as asking in the slack community.

@manjitapandey
Copy link
Contributor

This is bad, How do we reach to them for now?? All we need is osm usernames of those who requested organisation right??

@spwoodcock
Copy link
Member Author

We have no easy way of knowing who created the org (org creation shouldn't have been enabled until we implemented it properly, but we are where we are now 😅 ).

It's not a huge deal, as long as people know how to contact us (slack channel).

We can either:

  • Wait for the org creator to contact us and we update their permissions
  • Delete the orgs without an admin, to allow them to re-create it.

@spwoodcock
Copy link
Member Author

Anyways, this is complete now.

As of now, we have these orgs approved:

Image

@manjitapandey
Copy link
Contributor

Hi @spwoodcock , I have seen the list of FMTM users and I have recognised some (as they mentioned it on their osm profile) and msged them for their confirmation. Lets see if that works.
If they confirmed, we can update them to organisation admin of respective orgs right??

@spwoodcock
Copy link
Member Author

Good idea, thank you!

Yep, we can make them org managers if we know the OSM user id 👍

@manjitapandey
Copy link
Contributor

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devops Related to deployment or configuration effort:low Likely a few hours enhancement New feature or request priority:low Backlog of tasks that will be addressed in time
Projects
Development

No branches or pull requests

2 participants