-
Notifications
You must be signed in to change notification settings - Fork 309
Conversation
This is the capitalization we're using on the About pages.
In #3677 we decided not to use these questions anymore.
Rebased on master. |
|
Right direction, @mattbk et al.? |
I like it. |
I propose that we land this without "How to Review Team Applications," and then once we write that we link "publicly reviewed" there instead of to the applications issue tracker. |
I keep waffling about the "Issues" term. Waddya think?
|
I like something more general, like TODO or Work Available, because it leaves open the specific tooling in use. |
"Work Available" is clear. |
"To-do" is a pretty common term (I don't think it's limited to geeks, is it? TODO would be, but To-do I think is okay). And it's what I used for the field name, |
I would avoid TODO because it looks like an acronym to non-coders. |
@mattbk How about if it's spelled "To-do" instead (see my previous comment)? |
Another thought: Teams are in between. On the one hand a Team page should appeal to ~users who want to give payments to the Team, and on the other to ~users who want to do work and take payroll. Out of scope for this PR but something to keep in mind when we're able to circle back around to #3248. |
Okay! I think this PR is ready for final review. Deployment notes:
|
Can you give me access? |
@mattbk I would expect that you can simply click and start editing. No? |
I looked for a "sharing" setting and didn't see it ... |
I get "Unauthorized [403]" and I am logged in with github. |
Interesting! Okay, one sec ... |
"Demo expires in in 49 minutes." Hurry! 💃 |
I charged through a bunch of them, but have to run now. |
!m @mattbk |
Hmmm ... I think we should keep the |
I manually updated eight |
I added a little script to that gist, for generating SQL updates from the CSV. |
Alright. Going for it ... |
revise the Team application
Closes #3677.