You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should we display contributors on pledges if they haven't filled out their # of hours per week that they contribute, and the teams that they contribute to?
It seems like that's an essential step in the process, because if it's skipped then teams can't reach out to them for help with projects, etc, because they won't show up in resources like #69.
If we do shift to not displaying them until that's done, then we could email everyone who would be affected so that they can easily fill it out and be displayed again.
So we have the "Please update your profile with the number of hours per week that you contribute, and the teams that you contribute to." notification now, which directs folks over to the profiles site to update this. Right now it's very easy to ignore and just click "Join Organization".
If we're going to make the hours/teams info a blocker to being displayed, I think it needs a better flow to enter that information.
I like the idea of making the "things to fill out" fields more readily available on the My Pledges page. I think disabling the button might work well, to force the behavior we're looking for. Just a note that this will probably be a one-time-per-user issue. :)
Should we display contributors on pledges if they haven't filled out their # of hours per week that they contribute, and the teams that they contribute to?
It seems like that's an essential step in the process, because if it's skipped then teams can't reach out to them for help with projects, etc, because they won't show up in resources like #69.
If we do shift to not displaying them until that's done, then we could email everyone who would be affected so that they can easily fill it out and be displayed again.
Props @coreymckrill for the idea.
cc @andreamiddleton, @ryelle
The text was updated successfully, but these errors were encountered: