STEPS:
If you log in
And click on About menu option
And click on the first order (if you have one)
And click "Delivered to Hub" radiobutton
Then you get this message in the "Message Box"

• Change "Delivered to Hub" and "Your request is estimated to arrive at your location on this date [enter date here]." to "Delivery" and replace [enter date here] with variable as specified in new wireframes.

Add rspec specs for:

1. orders_controller's create method with bad order params
2. orders_controller's update method with bad order params
3. orders_controller's GET show method
4. users_controller's current method (unclear how to use)
5. application_controller's root method (unclear how to use)
6. registrations_controller's update method (model not found)

Just added pending specs for the first three.

Here is some background material on writing controller specs.

This will also include a revision history of design changes based on discussions and decisions made by both the client (PC Patrick) and the team.

We're doing a weird mishmash of Angular and Rails views right now. It'd be simpler to move all the routing client-side.

@pstoica: I'm assigning you this since you're our de facto Angular guru, but I'd be glad to learn a little bit about this and implement things myself if you can give me some direction. Just let me know.

See also #30?

Based on requirements discussion with Patrick Choquette this afternoon we should remove this radio button selection.

Should I register a Freenode channel for the project? This gives us some advantages, as a central communication. It would also let us set up the Github & Travis (eventually) IRC bots for realtime notification of new commits and pass/fail results for the spec tests.

PREVIOUS SUBJECT LINE: Email confirmations for order request, order fulfillment, lost password.

We need to send emails confirming order placement, notifying a user of order fulfillment, and in the event of a lost password.

I created a touch test suite using Cucumber on the https://github.com/atlrug/atlrug4
repo and it has served us well. I will start of this tomorrow.

This task will serve to teach me the app and hopefully have a better
sense of "polished and stable version of the features."

Added pcmedlink.org to my free http://www.montastic.com/ monitoring (every 30 minutes) list.

Move away from WEBrick - thin, unicorn, something?

I have a running list of requirements that I compiled during the weekend and would like to post them up here for people to add to. I am planning on putting it up on the wiki but if there is a better place to post it so others can add let me know.

Also, would you like two separate lists? One for front end and one for back end?

We need:

• JSON endpoints in the orders controller
• Angular views to consume that JSON

Quick fix for #31 for tech demo. Logo will redirect to root route.

We probably don't need to change the github repo name itself, but should brand the project wherever convenient.

I'm getting the above error in the papertrail logs. Not sure yet where it's coming from.

Needs votes!

MIT? BSD? GPL?

Any other suggestions?

Since the app will go into regions of the world with poor internet, how do we make sure that the performance is appropriate?

Original Title: Global Navigation for PCV, PCMO, Admin User types

We are missing global navigation for the web browser experience.

Edit: this is functionally complete, but needs to be styled once we have a design.

Appears that when you click on the Gear icon and then "About",
you do not get information about the app.

Please save the current table output ("#/orders") in some other option.

Need to make the phone number and twilio account credentials configurable.

My personal Twilio account creds are set as environment variables ( I need to remove them soon ), and the phone number is hard-coded into the app.

Currently there's no visual cue that when select boxes are focused.

We need:

• JSON endpoints in the orders controller
• Angular views to consume that JSON

Fulfillment should trigger an email and text message to the requesting user.

From @jamesdabbs: @jasnow: do you want to get & set up "pcmedlink.org" as well? I can do it &/or pitch in some money for it if that'd be helpful.

This cover the future of this domain: www.pcmedicalsupplies.org

Steps:

1. Configure channel with proper flags
2. Register unique nick for the github bot
3. Test

Users should be able to edit their password, email, country. Any other improvements to the default devise views would be good.

Since this page has been redesigned a bit I am going to make this the catch all for all missing/misspelled text that appears as a default for the radio buttons.

This is related to issue #29

The following could use some UI love:

• Devise generated views (note flash messages)
• Email templates

Feel free to edit if there are others

During the hackathon, @jasnow and @jamesdabbs briefly mentioned continuous integration.

Is this something that will be valuable to the project and we should consider utilizing?

Think RHOK wiki pages should be part of rhok-rails project (not atlrug4 project) so I am going to move them.

Change radio button label from from "other" to "Special Instructions".

I only have login credentials to "act" like a peace corps volunteer but I need one that will allow me access to all the screens that a Peace Corps Medical Officer would interact with. Can anyone help me?

If you log in
And click on Gear/About menu option
And click on the first order
And click "Delivered to Hub" radio button
Then you get this message in the "Message Box": "Please pick up your request at this by this date."

Note that it appears to be be missing a word after "this"

This is also true for "Contact PCMO" radiobutton.

If someone tells me what the word is, I will change the code.

We need a way to easily administrate users, including creation of other user accounts and management of access roles. Preferably 3 roles: admin, pcmo, pcv. These roles are non-exclusive, so the UI needs to also handle that in a sane way.

This issue is currently blocking issue #32.
Could potentially utilize the same view as issue #4, but with heightened permissions.

Maybe use the list in LICENSE file to update README file

Would everyone be alright with putting the JSON controllers in /api/ so we can use HTML5 pushstate instead of hashbang URLs?

Administrative

I would encourage everyone that has select "NO EMAIL" for Google Group to think about
once-a-day

• Abridged Email - send a summary of new activity each day
• Digest Email - send all new messages in a single daily email

Unfortunately didn't get to do any client-side testing, so it'd be reassuring to focus on that (and do some refactoring too) for the next round and integrate it with CI.

We're getting this beast:

ActiveRecord::StatementInvalid: PG::Error: ERROR: non-integer constant in ORDER BYLINE 1: ...= "orders"."id" WHERE "orders"."user_id" = 11 ORDER BY '--- ^: SELECT "orders"."id" AS t0_r0, "orders"."user_id" AS t0_r1, "orders"."confirmed" AS t0_r2, "orders"."fulfilled" AS t0_r3, "orders"."phone" AS t0_r4, "orders"."email" AS t0_r5, "orders"."extra" AS t0_r6, "orders"."created_at" AS t0_r7, "orders"."updated_at" AS t0_r8, "orders"."instructions" AS t0_r9, "users"."id" AS t1_r0, "users"."email" AS t1_r1, "users"."encrypted_password" AS t1_r2, "users"."reset_password_token" AS t1_r3, "users"."reset_password_sent_at" AS t1_r4, "users"."remember_created_at" AS t1_r5, "users"."sign_in_count" AS t1_r6, "users"."current_sign_in_at" AS t1_r7, "users"."last_sign_in_at" AS t1_r8, "users"."current_sign_in_ip" AS t1_r9, "users"."last_sign_in_ip" AS t1_r10, "users"."created_at" AS t1_r11, "users"."updated_at" AS t1_r12, "users"."phone" AS t1_r13, "users"."first_name" AS t1_r14, "users"."last_name" AS t1_r15, "users"."pcv_id" AS t1_r16, "users"."country_id" AS t1_r17, "users"."role" AS t1_r18, "users"."city" AS t1_r19, "requests"."id" AS t2_r0, "requests"."supply_id" AS t2_r1, "requests"."dose" AS t2_r2, "requests"."quantity" AS t2_r3, "requests"."created_at" AS t2_r4, "requests"."updated_at" AS t2_r5, "requests"."order_id" AS t2_r6 FROM "orders" LEFT OUTER JOIN "users" ON "users"."id" = "orders"."user_id" LEFT OUTER JOIN "requests" ON "requests"."order_id" = "orders"."id" WHERE "orders"."user_id" = 11 ORDER BY '--- :orders: created_at DESC'

from calling User#accesible_orders. It looks to be some bad interaction between the two default scopes on orders.

Please Twillio from Clint to Peace Corps account

Decide on (and work) RHOK_RAILS project submital to NDOCH at http://hackforchange.org/submit

After logging in, when I click on Gear/"Setting" then click on (Gear/"Help" or
Gear/"About") the "Edit User" fields just moves down but do not disappear.

As a github newbie, I'm confused about where to post design documentation that is critical path for launch. I have never used github before and I'm a little confused about where UX stuff goes. Thanks for any help on this.

When I try to use Gear/Settings/"Edit User", I get the following but those field are not on the screen.
-- City can't be blank
-- First name can't be blank
-- Last name can't be blank

I know we discussed this briefly on Wednesday night 6/12/13 but I don't remember us coming to conclusion on this one.