ckan/ckanext-pose_ecosystem_catalog

Access control

Open

#130 opened on Feb 12, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)HTML (0 forks)github user discovery
help wanted

Repository metrics

Stars
 (6 stars)
PR merge metrics
 (PR metrics pending)

Description

Sure, Access granted! also since we have maintainer metadata, we should consider implementing automatic privilege granting for maintainers on sign-up

Originally posted by @a5dur in #108

Access control for 'extensions' would be a straight approach since we have the maintainers github id available. 'sites' edit access is a topic we'll need to brainstorm.

Probably, if the user could verify using the domain email, that'd be ideal

Contributor guide

Research direction
Investigate how to use maintainer GitHub IDs from metadata to auto grant access for extensions, and explore domain email verification for site edit access.
Tech stack
pythonhtml
Domain
backendauthenticationauthorization
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitCKAN basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60