quality/testdays-web
6
0
Fork 0
Code Issues 11 Pull requests 3 Projects Releases Packages Wiki Activity Actions

Events with just a mandatory login? #43

New issue
Open
opened 2025-04-17 06:37:27 +00:00 by kparal · 4 comments
kparal commented 2025-04-17 06:37:27 +00:00
Owner
Copy link

It's great that we now support OIDC login. I wonder if we should add an option to the event creation page that allows us to force users to be logged in, in order to submit results to that particular event.

In order to combat spam, it could be an effective strategy to require login for most of our common test days, and only allow anonymous login on special test days that will likely bring a lot of contributors without a Fedora account (could be e.g. a CoreOS community, Libreoffice community, IoT, I don't know, Sumantro probably has a better idea).

Do we want this, or do we want to wait first to see if we have spam issues again?

It's great that we now support OIDC login. I wonder if we should add an option to the event creation page that allows us to force users to be logged in, in order to submit results to that particular event. In order to combat spam, it could be an effective strategy to require login for most of our common test days, and only allow anonymous login on special test days that will likely bring a lot of contributors without a Fedora account (could be e.g. a CoreOS community, Libreoffice community, IoT, I don't know, Sumantro probably has a better idea). Do we want this, or do we want to wait first to see if we have spam issues again?
jskladan commented 2025-04-17 07:04:19 +00:00
Contributor
Copy link
  1. The spam issues are not really repeating
  2. I'm not sure we want to limit our audience to "people with FAS"
  3. If you wanted to discourage anonymous results, but still allow them, I'd rather add the captcha (as is on the login form) to the result submission login too. Trust me, solving captcha gets old fast :D

Also, on a technical level, it is now way easier to delete unwanted data from the app too.

1) The spam issues are not really repeating 2) I'm not sure we want to limit our audience to "people with FAS" 3) If you wanted to discourage anonymous results, but still allow them, I'd rather add the captcha (as is on the login form) to the result submission login too. Trust me, solving captcha gets old fast :D Also, on a technical level, it is now way easier to delete unwanted data from the app too.
kparal commented 2025-04-17 07:16:31 +00:00
Author
Owner
Copy link

I don't really want to discourage anonymous results. I just wonder whether our assumption that "we often get results from non-fedora contributors" is valid. And whether we want to have the logged-in-only functionality available in advance as a precaution, to flip it on immediately when we see issues.

I don't really want to discourage anonymous results. I just wonder whether our assumption that "we often get results from non-fedora contributors" is valid. And whether we want to have the logged-in-only functionality available in advance as a precaution, to flip it on immediately when we see issues.
jskladan commented 2025-04-17 08:42:25 +00:00
Contributor
Copy link

That can now be easily quantified, after couple testdays :)

That can now be easily quantified, after couple testdays :)
kparal commented 2025-09-03 13:06:45 +00:00
Author
Owner
Copy link

Metadata Update from @kparal:

  • Custom field story_points adjusted to 5
**Metadata Update from @kparal**: - Custom field story_points adjusted to 5
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
feature/82-remove-resultsdb-references
fix/135-mock-event-results-submission
fix/132-accessibility-review
master
staging
feature/fasusername
feature/faslogin_as_db_username
v1.2
v1.1
v1.0
0.0.4
Labels
Clear labels   
Closed As
Duplicate
 Closed with the reason of Duplicate

  
Closed As
Fixed
 Closed with the reason of Fixed

  
Closed As
Invalid
 Closed with the reason of Invalid

  
easyfix

   
enhancement
  
ai-review-please
Request AI review for a pull request

  
Backlog Status
Needs Review
 Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  
Backlog Status
Ready
 Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and can be worked on immediately when capacity is available.

  
chore
Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

  
documentation
Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

  
points
01
 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
02
 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
03
 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
05
 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
08
 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.

  
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 and should be broken down.

  
pr2jira
Sync this pull request to Jira for Agility tracking. Only use for PRs without a corresponding ticket.

  
Priority
Critical
 This is for work that is urgent and of critical importance and so and must be addressed immediately with a higher priority than all other work, even if not originally planned for the current sprint.

  
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.

  
Sprint Status
Blocked
 Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

  
Sprint Status
Done
 Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
 Work items currently being worked on by a team member. Active development, research, or implementation is happening.

  
Sprint Status
Review
 Work items that are complete but need review, testing, or approval before being marked as done.

  
Sprint Status
To Do
 Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  
Technical Debt
Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

  
Work Item
Bug
 Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic
 Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  
Work Item
Spike
 Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

  
Work Item
Task
 Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

  
Work Item
User Story
 User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

No labels
Closed As
Duplicate
Closed As
Fixed
Closed As
Invalid
easyfix
enhancement
ai-review-please
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
pr2jira
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
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
quality/testdays-web#43
No description provided.