Opened 12 days ago
Closed 12 days ago
#8302 closed enhancement (wontfix)
Set a realistic maximum limit for the "Time commitment" field in Profiles / 5ftF
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Component: | Profiles | Keywords: | |
| Cc: |
Description
In the profile settings, where users specify the amount of time they spend contributing to WordPress, the input field allows them to set a maximum of 168 hours per week.
Since a week has exactly 168 hours, it is physically impossible for a person to contribute 24 hours a day, 7 days a week, without sleeping.
The system should impose a realistic weekly maximum limit (for example, a maximum of 40 hours per week) so that the profile data is accurate and meaningful.
Attachments (1)
Change History (2)
Note: See
TracTickets for help on using
tickets.
Thanks for the report! This is intentional, so closing as wontfix; here's the reasoning.
The field is capped at 168 in three places (the input's max, the stepper's clamp, and a server-side min( 168, absint( $hours ) ) on save), so nonsense values above a week's worth of hours are already rejected. 168 is the physical bound of a week, which makes it a principled limit rather than an arbitrary one.
A lower "realistic" cap like 40 would reject honest data: full-time sponsored contributors are at exactly 40, and plenty of maintainers and agency owners genuinely put in more across sponsored and self-directed time combined. Any threshold we pick above 40 and below 168 is a judgment call about other people's work weeks, and the field is self-reported intent either way, so a tighter cap adds false precision without making the data more truthful. The public profile shows the total and the split, and unrealistic self-reports reflect on the profile owner rather than the platform.