codeforamerica / apply

If you can read this, you should apply for a 2016 @codeforamerica fellowship! Ask current and former fellows questions at https://github.com/codeforamerica/apply/issues
28 stars 2 forks source link

Application Part Two #17

Closed qwo closed 9 years ago

qwo commented 9 years ago

Am I missing some context here?

The email said to go here, edit your application and fill in these questions but its referring to "upload some source code" but was there some prompt we were suppose to complete?

In reality, I think it is suppose to be uploading one of your projects or pointing the github URL and talking about it, but I guess I need a sanity check.

Any help?

screenshot 2014-07-19 10 27 02

alexanderstran commented 9 years ago

Hi @stanzheng. You can't see the questions until you click the blue button that lets you edit. Then you can do all the things. screen shot 2014-07-19 at 8 11 25 am

Let me know if that makes sense!

qwo commented 9 years ago

Phew ok :) Ill look at clicking it soon, the "click edit" and actually seeing filling out those form fields soon.

I got nervous when i saw a bunch of blank fields that I hadn't seen before. Looking forward to filling this out tonight then.

Thanks @robotmongol!

alexanderstran commented 9 years ago

No problem man! I know it looks confusing but we're learning too about using Screendoor. Thx.

migurski commented 9 years ago

That is definitely a weird-looking UI. Cc @adamjacobbecker.

ajb commented 9 years ago

Thanks @migurski for looping me in. Unfortunately I don't have an easy answer -- to borrow a programing term, Screendoor doesn't quite support multi-stage applications as "first-class citizens", so CfA is using the additional fields + edit workaround.

For now, I think instructing folks that they'll need to hit the "Edit response" button is the best we can do. We definitely want to add some kind of support for multi-stage application processes into Screendoor, and CfA will be our first call when we start to research building that feature.

alexanderstran commented 9 years ago

@migurski @adamjacobbecker agreed, @stanzheng thanks for checking it out and identifying things we can improve.

qwo commented 9 years ago

no problem.

didn't mean to cause a buzz :)

The only other nitpicking thing was that the second time around the strict 200 word count text validation was actually enforced and I had to cut a few words out parts of my application to proceed forward.

Anyway thanks I'll hack out my prompt and hope for the best

shuhblam commented 9 years ago

I have found an issue where I do not have this edit button for an option. I have sent a request to be able to edit my application.

qwo commented 9 years ago

@coleGillespie the letter did state that you may only edit once, and after I had submitted mine my button disappeared.

Had you clicked the edit button before?

shuhblam commented 9 years ago

I did click the edit button once then my machine froze. I reset and then it was gone.

qwo commented 9 years ago

that maybe the problem the "edit once" must of been taken literally.

i would try to email fellowship-staff@codeforamerica.org if it doesn't get resolved soon but github is like batsignals for @robotmongol and @migurski

shuhblam commented 9 years ago

perhaps my luck has ran out @stanzheng :-)

qwo commented 9 years ago

ah you'll be fine :). 11:59 pacific.. you still got 6 hours! you can do it

shuhblam commented 9 years ago

only if I can get an admin to unlock the app

migurski commented 9 years ago

@robotmongol sounds like a thing for you.

alexanderstran commented 9 years ago

@coleGillespie and I figured it out a while ago I believe. Let me know if it still doesn't work!

shuhblam commented 9 years ago

@robotmongol i was able to get in and submit my gists. thanks for your help. usually a js guy but python is really great for csv parsing :)

qwo commented 9 years ago

:thumbsup: thanks for all the support and since part two is over I'll close my issue.