Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Require contributors to fill out hours & teams before being displayed? #93

Closed
iandunn opened this issue Nov 8, 2019 · 3 comments · Fixed by #127
Closed

Require contributors to fill out hours & teams before being displayed? #93

iandunn opened this issue Nov 8, 2019 · 3 comments · Fixed by #127

Comments

@iandunn
Copy link
Member

iandunn commented Nov 8, 2019

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

@ryelle
Copy link
Contributor

ryelle commented Nov 8, 2019

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".

Screen Shot 2019-11-08 at 4 17 11 PM

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.

@iandunn
Copy link
Member Author

iandunn commented Nov 10, 2019

Those are really good ideas!

@andreamiddleton
Copy link

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. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment