-
Notifications
You must be signed in to change notification settings - Fork 308
Conversation
🌻 💃 |
I'm reversing what I said over at #4123 (comment) (and not only because it's less work to leave all the fields in place). Although if we leave the onboarding and TWYW fields (as optional), we'll need to adjust what "Approved" means, and tie approval only to TOS+fit; this still applies:
In light of #4135, though, we might as well keep open work as the beginning of the levels idea, and add an This is happening at the same time as we're moving toward #BackTheStack (corporate sponsorship of projects), but I think it's important to keep this long tail going. |
So it could be something like:
|
Rebased on latest master. Previous head was 2b458cd. @JessaWitzel Wanna work on this one together with @mattbk? :-) |
I think we should kill this part entirely, because we're so far away from bringing that back.
Let's drop this per #4166. That should leave onboarding as the only optional field, ya? |
2b458cd
to
565dac0
Compare
How can I help? |
@JessaWitzel, it looks like the onboarding field needs to go back in (revert part of 565dac0), and then the other checklist items in the first post, if you agree with them. I'm not the greatest with tests. Feel free to jump in and make commits. |
Bringing over from #4166:
|
This takes us down to two checkboxes. I think the public review thing is unusual enough that it's worth elevating to its own checkbox. We could tweak the wording of the second to say "other terms of service." Nobody reads the terms because they assume there won't be any surprises, but we have some weird stuff in ours. |
Is this PR necessary if we have #4214? I'm a little confused as to what needs to be done now. |
@whit537 are projects different than teams? |
Teams are being renamed to projects. |
Rebased; was 565dac0. |
565dac0
to
046ae64
Compare
Of course that means Travis won't see us again ... :/ |
ec21796
to
8db0601
Compare
I left it in the database. Everything else is pulled out. |
@@ -53,7 +53,7 @@ for field in data.keys(): | |||
if not value: | |||
raise Response(400, _("Please fill out the '{}' field.", field_names[field])) | |||
|
|||
if (field in ('homepage', 'onboarding_url') | |||
if (field in ('homepage') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is now the same as field in 'homepage'
because of the way parens work in Python (without a comma they're used for grouping, with a comma they make a tuple). Probably should rework to just be if field == 'homepage'
.
Hmm ... Travis failures? |
They're all choking on oniguruma when installing marky-markdown (except for one which is weird). |
Did oniguruma just put out a new version? |
Version 6.1.1 worked in the one build that worked. https://travis-ci.org/gratipay/gratipay.com/builds/182613635 |
Fail! Latest
Earliest
|
Alright, so it looks like it's a problem downloading the tarball, not building it. Backing out 5bc1bc0 … |
5bc1bc0
to
102ab69
Compare
|
http://status.npmjs.org/ shows green |
The local checksum is different in all of the checksum failed cases, while the remote is the same in all cases. |
Why are we using such an ancient version of node? |
It's probably the system version on whatever Ubuntu we get there? Let's try installing a more recent version ... |
|
The build passed! But not because of 4295843; I only see |
4295843
to
102ab69
Compare
Still passing! Merging while we have a chance. ;-) |
!m @mattbk |
Derived from #4123.
Stubbing this out, need to be on front of a local install before I can do more (aside from learning Aspen).
teamproject editing while retaining those fields forteamsprojects that already exist.