Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

Revise the New Project form #4130

Merged
merged 14 commits into from
Dec 9, 2016
Merged

Conversation

mattbk
Copy link
Contributor

@mattbk mattbk commented Sep 22, 2016

Derived from #4123.

Stubbing this out, need to be on front of a local install before I can do more (aside from learning Aspen).

@chadwhitacre
Copy link
Contributor

🌻 💃

@mattbk
Copy link
Contributor Author

mattbk commented Sep 25, 2016

Hmm.
screen shot 2016-09-24 at 8 34 45 pm

This will be harder than I thought.

@mattbk
Copy link
Contributor Author

mattbk commented Oct 10, 2016

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:

We should keep track of those projects that are already "open work" approved, so we can grandfather them in when we get to that (which I suppose could just be a list on a ticket somewhere, rather than dumping it into the database right now).

In light of #4135, though, we might as well keep open work as the beginning of the levels idea, and add an open_work database field so we can show/rank those teams on the homepage.

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.

@mattbk
Copy link
Contributor Author

mattbk commented Oct 10, 2016

So it could be something like:

  • Basics (required)
    • Team name
    • Image
    • Product or service
    • Homepage
    • Agree to public review
      • Include why this is, link to TOS/brand guidelines.
    • Agree to TOS
  • Open work fields (optional)
    • Include short sentence explaining open work, with links. Open work criteria will be reviewed after project is approved, but is no longer required for a project to be approved.
    • Onboarding URL
    • Todo URL
  • TWYW fields (optional)
    • TWYW doesn't exist yet under Gratipay 2.0. Check this box if you're interested in being notified.
    • Agree to Payroll TWYW payouts

@chadwhitacre
Copy link
Contributor

Rebased on latest master. Previous head was 2b458cd.

@JessaWitzel Wanna work on this one together with @mattbk? :-)

@chadwhitacre
Copy link
Contributor

TWYW fields (optional)

I think we should kill this part entirely, because we're so far away from bringing that back.

Todo URL

Let's drop this per #4166.

That should leave onboarding as the only optional field, ya?

@JessaWitzel
Copy link
Contributor

How can I help?

@mattbk
Copy link
Contributor Author

mattbk commented Nov 28, 2016

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

@chadwhitacre chadwhitacre mentioned this pull request Nov 30, 2016
2 tasks
@chadwhitacre
Copy link
Contributor

Bringing over from #4166:

The three separate checkboxes. Why not implicitly tick them (with the wording "When you click on 'Apply', you agree to x, y and z" when the user clicks on 'Apply'? Reference: http://ux.stackexchange.com/questions/55571/auto-agreement-to-the-tos-by-clicking-sign-up-button-in-sign-up-form

@chadwhitacre
Copy link
Contributor

chadwhitacre commented Nov 30, 2016

TWYW fields (optional)

I think we should kill this part entirely, because we're so far away from bringing that back.

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.

@mattbk
Copy link
Contributor Author

mattbk commented Dec 1, 2016

Is this PR necessary if we have #4214?

I'm a little confused as to what needs to be done now.

@JessaWitzel
Copy link
Contributor

@whit537 are projects different than teams?

@mattbk
Copy link
Contributor Author

mattbk commented Dec 2, 2016

Teams are being renamed to projects.

@chadwhitacre chadwhitacre changed the base branch from master to relax-open-work-requirement December 2, 2016 21:23
@chadwhitacre chadwhitacre mentioned this pull request Dec 6, 2016
21 tasks
@chadwhitacre
Copy link
Contributor

Rebased; was 565dac0.

@chadwhitacre chadwhitacre changed the base branch from relax-open-work-requirement to remove-todo-url December 6, 2016 13:50
@chadwhitacre
Copy link
Contributor

Base changed to remove-todo-url (#4214) since that is scheduled to land in #4221 first.

@chadwhitacre
Copy link
Contributor

Of course that means Travis won't see us again ... :/

@mattbk mattbk added the Review label Dec 9, 2016
@mattbk
Copy link
Contributor Author

mattbk commented Dec 9, 2016

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')
Copy link
Contributor

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

@chadwhitacre
Copy link
Contributor

Hmm ... Travis failures?

@chadwhitacre
Copy link
Contributor

They're all choking on oniguruma when installing marky-markdown (except for one which is weird).

@chadwhitacre
Copy link
Contributor

Did oniguruma just put out a new version?

@chadwhitacre
Copy link
Contributor

Version 6.1.1 worked in the one build that worked.

https://travis-ci.org/gratipay/gratipay.com/builds/182613635

screen shot 2016-12-09 at 11 07 17 am

@chadwhitacre
Copy link
Contributor

travis-ci/travis-ci#4771 😖

@chadwhitacre
Copy link
Contributor

Fail!

Latest

gyp WARN install got an error, rolling back install
gyp ERR! configure error 
gyp ERR! stack Error: 522 status code downloading tarball
gyp ERR! stack     at Request.<anonymous> (/home/travis/.nvm/v0.10.36/lib/node_modules/npm/node_modules/node-gyp/lib/install.js:246:14)
gyp ERR! stack     at Request.emit (events.js:117:20)
gyp ERR! stack     at Request.onResponse (/home/travis/.nvm/v0.10.36/lib/node_modules/npm/node_modules/request/request.js:1085:10)
gyp ERR! stack     at ClientRequest.g (events.js:180:16)
gyp ERR! stack     at ClientRequest.emit (events.js:95:17)
gyp ERR! stack     at HTTPParser.parserOnIncomingClient (http.js:1693:21)
gyp ERR! stack     at HTTPParser.parserOnHeadersComplete [as onHeadersComplete] (http.js:122:23)
gyp ERR! stack     at Socket.socketOnData (http.js:1588:20)
gyp ERR! stack     at TCP.onread (net.js:528:27)

Earliest

gyp WARN install got an error, rolling back install
gyp ERR! configure error 
gyp ERR! stack Error: node-v0.10.36.tar.gz local checksum 6fd25f1e62f2e0d257a8c1ad8df2da088ebd4b1cd9e188a2fca510a31a559de7 not match remote b9d7d1d0294bce46686b13a05da6fc5b1e7743b597544aa888e8e64a9f178c81
gyp ERR! stack     at deref (/home/travis/.nvm/v0.10.36/lib/node_modules/npm/node_modules/node-gyp/lib/install.js:299:20)
gyp ERR! stack     at IncomingMessage.<anonymous> (/home/travis/.nvm/v0.10.36/lib/node_modules/npm/node_modules/node-gyp/lib/install.js:340:13)
gyp ERR! stack     at IncomingMessage.emit (events.js:117:20)
gyp ERR! stack     at _stream_readable.js:944:16
gyp ERR! stack     at process._tickCallback (node.js:442:13)

@chadwhitacre
Copy link
Contributor

Alright, so it looks like it's a problem downloading the tarball, not building it. Backing out 5bc1bc0

@chadwhitacre
Copy link
Contributor

nodejs/node-gyp#693 ?

@chadwhitacre
Copy link
Contributor

build error
182606728 node-v0.10.36.tar.gz local checksum [] not match remote []
182606710 node-v0.10.36.tar.gz local checksum [] not match remote []
182613462 node-v0.10.36.tar.gz local checksum [] not match remote []
182613635
182622559 Completion callback never invoked!
182622533 node-v0.10.36.tar.gz local checksum [] not match remote []
182623387 node-v0.10.36.tar.gz local checksum [] not match remote []
182635391 522 status code downloading tarball

@chadwhitacre
Copy link
Contributor

http://status.npmjs.org/ shows green

@chadwhitacre
Copy link
Contributor

The local checksum is different in all of the checksum failed cases, while the remote is the same in all cases.

@chadwhitacre
Copy link
Contributor

Why are we using such an ancient version of node?

@chadwhitacre
Copy link
Contributor

It's probably the system version on whatever Ubuntu we get there? Let's try installing a more recent version ...

@chadwhitacre
Copy link
Contributor

we are having issues with our download service right now. hoping to have it sorted out very soon

nodejs/node-gyp#693 (comment)

@chadwhitacre
Copy link
Contributor

The build passed! But not because of 4295843; I only see python in the "Build system information" there (and it seems multiple languages aren't directly supported: travis-ci/travis-ci#4090). Gonna push that off and see if we still pass.

@chadwhitacre
Copy link
Contributor

Still passing! Merging while we have a chance. ;-)

@chadwhitacre chadwhitacre merged commit 53146a6 into relax-open-work-requirement Dec 9, 2016
@chadwhitacre
Copy link
Contributor

!m @mattbk

chadwhitacre pushed a commit that referenced this pull request Dec 9, 2016
@chadwhitacre chadwhitacre deleted the new-project branch December 13, 2016 03:07
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants