Infrastructure/ipsilon-fedora
3
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Status of the "cla" OpenID extension #4

New issue
Open
opened 2020-09-23 11:35:36 +00:00 by abompard · 1 comment
abompard commented 2020-09-23 11:35:36 +00:00
Copy link

I'm dumping this here before I forget. At the moment we have an OpenID extension called cla that will let app request whether the connecting user has signed a particular CLA. The list of predefined CLAs is in openid_cla, there's one for Fedora, one for Red Hat, one for Intel, one for Dell, one for IBM, etc.
The Ipsilon openid extension will just return {'CLA': 'yes'} if the user has signed all the requested CLAs.

It has the advantage of not informing the app of a users' other signed CLAs. In the new system they are all available through the agreements key.

Do we need to bring back this feature? Do we have an app that currently uses it and needs not to switch to OIDC?

I'm dumping this here before I forget. At the moment we have an OpenID extension called `cla` that will let app request whether the connecting user has signed a particular CLA. The list of predefined CLAs is in `openid_cla`, there's one for Fedora, one for Red Hat, one for Intel, one for Dell, one for IBM, etc. The Ipsilon openid extension will just return `{'CLA': 'yes'}` if the user has signed all the requested CLAs. It has the advantage of not informing the app of a users' other signed CLAs. In the new system they are all available through the `agreements` key. Do we need to bring back this feature? Do we have an app that currently uses it and needs not to switch to OIDC?
abompard commented 2020-09-23 11:37:47 +00:00
Author
Copy link

Also, the infofas info plugin will deduce which CLAs have been signed from membership in the corresponding groups. I guess we can mimic that in the infofasjson if necessary (based on agreements this time, not group membership).

Also, the `infofas` info plugin will deduce which CLAs have been signed from membership in the corresponding groups. I guess we can mimic that in the `infofasjson` if necessary (based on agreements this time, not group membership).
rcallwoo added this to the Unified backlog project 2025-08-07 01:50:20 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
production
dev
staging
No results found.
Labels
Clear labels
  
blocked

Indicates the work cannot proceed. There is a dependency or an issue that is preventing the team from completing the task. This is a flag for the Scrum Master to help unblock the team.

  
Bug

The software is not behaving as expected. It could be an error, a crash, or an incorrect result. Bugs often need to be prioritized based on their severity and business impact

  
Chore

Tasks that are necessary but don't directly deliver new value to the end-user. These are internal tasks like updating a library, managing user accounts, or setting up a new service.

  
Feature

It's something that a user would be able to see or interact with, such as a new button, a new page, or an improved workflow.

  
in-progress

This label is for work that a developer is actively working on. This is usually what you'll see on the "In Progress" column of your project board.

  
points:1

A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points:13

Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint.

  
points:2

This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points:3

medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points:5

a significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points:8

complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
priority:high

This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
priority:low

This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
priority:medium

This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
ready

indicates that an issue has been fully refined, has a story point value, and is ready to be pulled into a sprint. It has all the information needed for a developer to start working on it immediately.

  
review

This indicates that the work is complete, but it is now in a review state. This could mean a peer code review, a QA check, or a review by the Product Owner.

  
Technical Debt

work that improves the codebase without adding new features. It's work that pays down the "debt" you've accumulated, such as refactoring a messy piece of code, improving test coverage.

No labels
blocked
Bug
Chore
Feature
in-progress
points:1
points:13
points:2
points:3
points:5
points:8
priority:high
priority:low
priority:medium
ready
review
Technical Debt
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Unified backlog
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Infrastructure/ipsilon-fedora#4
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?