search

LoopieLLC / Washer-Driver-Portal

The Loopie LLC Washer and Driver Portal to open a communication channel between Loopie washers and drivers.
https://www.loopiewasherportal.com
0 stars 0 forks source link

Header updates #30

Closed brandonparis closed 5 years ago

brandonparis commented 5 years ago

Cleans up the header CSS and what displays a bit. We should discuss what else should go in the header for a washer/driver

johncburns1 commented 5 years ago

Lemme look over these commits when I get home. I know that I have to chat with Simon, our other front-end guy and get you on the same page because he has been doing some work on the CSS as well. So I want to make sure that before I merge that none of your code or his code are conflicting/being written over.

best,

Jack Burns

On Thu, Oct 25, 2018 at 3:24 PM Brandon Paris notifications@github.com wrote:

Cleans up the header CSS and what displays a bit. We should discuss what else should go in the header for a washer/driver

You can view, comment on, or merge this pull request online at:

https://github.com/LoopieLLC/WasherPortal/pull/30 Commit Summary

  • Modifying look/feel of washer_session pagE
  • Updating footer of login portal
  • Modifications to driver/washer login pages
  • Conditionally link to either washer/driver sign-in depending on role
  • Check if user exists before rendering conditional user links
  • minor header changes
  • removing errant ruby tags
  • Merge branch 'master' into header-updates
  • Add elsif clause to login links
  • Merge branch 'master' into washer-login-css-updates
  • Resize logo
  • Merge branch 'washer-login-css-updates' into header-updates
  • Fix display of navbar submenu

File Changes

Patch Links:

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30, or mute the thread https://github.com/notifications/unsubscribe-auth/AJA3zFHdRRdsRoMcj9OtJRniA21Tg0WBks5uojo6gaJpZM4X7N_z .

brandonparis commented 5 years ago

Sounds good. If Simon is routinely committing / merging in master it shouldn't be an issue. Have you guys thought about using a story tracker like pivotal or jira? It'd be a good tool to use to track issues and features so that I don't start working on something that Simon is already working on.

B

On Thu, Oct 25, 2018, 19:07 Jack Burns notifications@github.com wrote:

Lemme look over these commits when I get home. I know that I have to chat with Simon, our other front-end guy and get you on the same page because he has been doing some work on the CSS as well. So I want to make sure that before I merge that none of your code or his code are conflicting/being written over.

best,

Jack Burns

On Thu, Oct 25, 2018 at 3:24 PM Brandon Paris notifications@github.com wrote:

Cleans up the header CSS and what displays a bit. We should discuss what else should go in the header for a washer/driver

You can view, comment on, or merge this pull request online at:

https://github.com/LoopieLLC/WasherPortal/pull/30 Commit Summary

  • Modifying look/feel of washer_session pagE
  • Updating footer of login portal
  • Modifications to driver/washer login pages
  • Conditionally link to either washer/driver sign-in depending on role
  • Check if user exists before rendering conditional user links
  • minor header changes
  • removing errant ruby tags
  • Merge branch 'master' into header-updates
  • Add elsif clause to login links
  • Merge branch 'master' into washer-login-css-updates
  • Resize logo
  • Merge branch 'washer-login-css-updates' into header-updates
  • Fix display of navbar submenu

File Changes

Patch Links:

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30, or mute the thread < https://github.com/notifications/unsubscribe-auth/AJA3zFHdRRdsRoMcj9OtJRniA21Tg0WBks5uojo6gaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433234732, or mute the thread https://github.com/notifications/unsubscribe-auth/AQipF0lGBmuJ0MFshAo0q_ZlLgbyWhn-ks5uokQvgaJpZM4X7N_z .

johncburns1 commented 5 years ago

No I have not but that is a great idea! I have been really slacking on documentation because I have been doing a lot of the code myself or directly with others but it is getting chaotic so that is my goal for tomorrow.

Best,

Jack Burns

On Thu, Oct 25, 2018 at 16:20 Brandon Paris notifications@github.com wrote:

Sounds good. If Simon is routinely committing / merging in master it shouldn't be an issue. Have you guys thought about using a story tracker like pivotal or jira? It'd be a good tool to use to track issues and features so that I don't start working on something that Simon is already working on.

B

On Thu, Oct 25, 2018, 19:07 Jack Burns notifications@github.com wrote:

Lemme look over these commits when I get home. I know that I have to chat with Simon, our other front-end guy and get you on the same page because he has been doing some work on the CSS as well. So I want to make sure that before I merge that none of your code or his code are conflicting/being written over.

best,

Jack Burns

On Thu, Oct 25, 2018 at 3:24 PM Brandon Paris notifications@github.com wrote:

Cleans up the header CSS and what displays a bit. We should discuss what else should go in the header for a washer/driver

You can view, comment on, or merge this pull request online at:

https://github.com/LoopieLLC/WasherPortal/pull/30 Commit Summary

  • Modifying look/feel of washer_session pagE
  • Updating footer of login portal
  • Modifications to driver/washer login pages
  • Conditionally link to either washer/driver sign-in depending on role
  • Check if user exists before rendering conditional user links
  • minor header changes
  • removing errant ruby tags
  • Merge branch 'master' into header-updates
  • Add elsif clause to login links
  • Merge branch 'master' into washer-login-css-updates
  • Resize logo
  • Merge branch 'washer-login-css-updates' into header-updates
  • Fix display of navbar submenu

File Changes

Patch Links:

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zFHdRRdsRoMcj9OtJRniA21Tg0WBks5uojo6gaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433234732>, or mute the thread < https://github.com/notifications/unsubscribe-auth/AQipF0lGBmuJ0MFshAo0q_ZlLgbyWhn-ks5uokQvgaJpZM4X7N_z

.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433236985, or mute the thread https://github.com/notifications/unsubscribe-auth/AJA3zFbIaiQ-AdJ4g-M3XEnvgO1bW7Sbks5uokchgaJpZM4X7N_z .

brandonparis commented 5 years ago

Let me know if you want assistance setting things up, I've used a few different project management tools; they're all pretty straight forward so you'll be fine, let me know if you want help writing "stories."

On Thu, Oct 25, 2018, 19:31 Jack Burns notifications@github.com wrote:

No I have not but that is a great idea! I have been really slacking on documentation because I have been doing a lot of the code myself or directly with others but it is getting chaotic so that is my goal for tomorrow.

Best,

Jack Burns

On Thu, Oct 25, 2018 at 16:20 Brandon Paris notifications@github.com wrote:

Sounds good. If Simon is routinely committing / merging in master it shouldn't be an issue. Have you guys thought about using a story tracker like pivotal or jira? It'd be a good tool to use to track issues and features so that I don't start working on something that Simon is already working on.

B

On Thu, Oct 25, 2018, 19:07 Jack Burns notifications@github.com wrote:

Lemme look over these commits when I get home. I know that I have to chat with Simon, our other front-end guy and get you on the same page because he has been doing some work on the CSS as well. So I want to make sure that before I merge that none of your code or his code are conflicting/being written over.

best,

Jack Burns

On Thu, Oct 25, 2018 at 3:24 PM Brandon Paris < notifications@github.com> wrote:

Cleans up the header CSS and what displays a bit. We should discuss what else should go in the header for a washer/driver

You can view, comment on, or merge this pull request online at:

https://github.com/LoopieLLC/WasherPortal/pull/30 Commit Summary

  • Modifying look/feel of washer_session pagE
  • Updating footer of login portal
  • Modifications to driver/washer login pages
  • Conditionally link to either washer/driver sign-in depending on role
  • Check if user exists before rendering conditional user links
  • minor header changes
  • removing errant ruby tags
  • Merge branch 'master' into header-updates
  • Add elsif clause to login links
  • Merge branch 'master' into washer-login-css-updates
  • Resize logo
  • Merge branch 'washer-login-css-updates' into header-updates
  • Fix display of navbar submenu

File Changes

Patch Links:

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zFHdRRdsRoMcj9OtJRniA21Tg0WBks5uojo6gaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433234732 , or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipF0lGBmuJ0MFshAo0q_ZlLgbyWhn-ks5uokQvgaJpZM4X7N_z

.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub < https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433236985>, or mute the thread < https://github.com/notifications/unsubscribe-auth/AJA3zFbIaiQ-AdJ4g-M3XEnvgO1bW7Sbks5uokchgaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433238987, or mute the thread https://github.com/notifications/unsubscribe-auth/AQipFx-_PlVNwalGxNihvF6ZmcHpCdETks5uoknIgaJpZM4X7N_z .

brandonparis commented 5 years ago

Hey Jack,

I'm having a hard time being productive when I sit down to do some work on the portal. I think I could crank out a lot of front-end work if I had a better notion of where the UI was headed and what kinds of tasks still needed to be done. I understand that might be an as-you-go type of thing, but it would be loads helpful to me if there were some written documentation on what needed to get done (besides the small issues I've seen in GitHub). I want to help and be productive but am finding it hard to make any progress other than small CSS changes that need to happen!

On Thu, Oct 25, 2018 at 7:58 PM Brandon Paris brandonprs@gmail.com wrote:

Let me know if you want assistance setting things up, I've used a few different project management tools; they're all pretty straight forward so you'll be fine, let me know if you want help writing "stories."

On Thu, Oct 25, 2018, 19:31 Jack Burns notifications@github.com wrote:

No I have not but that is a great idea! I have been really slacking on documentation because I have been doing a lot of the code myself or directly with others but it is getting chaotic so that is my goal for tomorrow.

Best,

Jack Burns

On Thu, Oct 25, 2018 at 16:20 Brandon Paris notifications@github.com wrote:

Sounds good. If Simon is routinely committing / merging in master it shouldn't be an issue. Have you guys thought about using a story tracker like pivotal or jira? It'd be a good tool to use to track issues and features so that I don't start working on something that Simon is already working on.

B

On Thu, Oct 25, 2018, 19:07 Jack Burns notifications@github.com wrote:

Lemme look over these commits when I get home. I know that I have to chat with Simon, our other front-end guy and get you on the same page because he has been doing some work on the CSS as well. So I want to make sure that before I merge that none of your code or his code are conflicting/being written over.

best,

Jack Burns

On Thu, Oct 25, 2018 at 3:24 PM Brandon Paris < notifications@github.com> wrote:

Cleans up the header CSS and what displays a bit. We should discuss what else should go in the header for a washer/driver

You can view, comment on, or merge this pull request online at:

https://github.com/LoopieLLC/WasherPortal/pull/30 Commit Summary

  • Modifying look/feel of washer_session pagE
  • Updating footer of login portal
  • Modifications to driver/washer login pages
  • Conditionally link to either washer/driver sign-in depending on role
  • Check if user exists before rendering conditional user links
  • minor header changes
  • removing errant ruby tags
  • Merge branch 'master' into header-updates
  • Add elsif clause to login links
  • Merge branch 'master' into washer-login-css-updates
  • Resize logo
  • Merge branch 'washer-login-css-updates' into header-updates
  • Fix display of navbar submenu

File Changes

Patch Links:

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zFHdRRdsRoMcj9OtJRniA21Tg0WBks5uojo6gaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433234732 ,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipF0lGBmuJ0MFshAo0q_ZlLgbyWhn-ks5uokQvgaJpZM4X7N_z

.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub < https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433236985 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AJA3zFbIaiQ-AdJ4g-M3XEnvgO1bW7Sbks5uokchgaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433238987, or mute the thread https://github.com/notifications/unsubscribe-auth/AQipFx-_PlVNwalGxNihvF6ZmcHpCdETks5uoknIgaJpZM4X7N_z .

johncburns1 commented 5 years ago

Hi Brandon,

So as you have noticed, the project has gotten to a point in which organization is going to be essential for completing it. I am going to spend the next couple of days writing documentation, interviewing clients, and creating well defined user stories so that everybody can be on the same page and knows what we still need to do to get this thing finished.

Until recently, it has been mostly me but now that I have some more help, I need to take some time to get everybody on the same page. Let me get back to you either today or tomorrow with some more concrete planning and tasks.

Best,

Jack Burns

On Sat, Oct 27, 2018 at 7:22 AM Brandon Paris notifications@github.com wrote:

Hey Jack,

I'm having a hard time being productive when I sit down to do some work on the portal. I think I could crank out a lot of front-end work if I had a better notion of where the UI was headed and what kinds of tasks still needed to be done. I understand that might be an as-you-go type of thing, but it would be loads helpful to me if there were some written documentation on what needed to get done (besides the small issues I've seen in GitHub). I want to help and be productive but am finding it hard to make any progress other than small CSS changes that need to happen!

On Thu, Oct 25, 2018 at 7:58 PM Brandon Paris brandonprs@gmail.com wrote:

Let me know if you want assistance setting things up, I've used a few different project management tools; they're all pretty straight forward so you'll be fine, let me know if you want help writing "stories."

On Thu, Oct 25, 2018, 19:31 Jack Burns notifications@github.com wrote:

No I have not but that is a great idea! I have been really slacking on documentation because I have been doing a lot of the code myself or directly with others but it is getting chaotic so that is my goal for tomorrow.

Best,

Jack Burns

On Thu, Oct 25, 2018 at 16:20 Brandon Paris notifications@github.com wrote:

Sounds good. If Simon is routinely committing / merging in master it shouldn't be an issue. Have you guys thought about using a story tracker like pivotal or jira? It'd be a good tool to use to track issues and features so that I don't start working on something that Simon is already working on.

B

On Thu, Oct 25, 2018, 19:07 Jack Burns notifications@github.com wrote:

Lemme look over these commits when I get home. I know that I have to chat with Simon, our other front-end guy and get you on the same page because he has been doing some work on the CSS as well. So I want to make sure that before I merge that none of your code or his code are conflicting/being written over.

best,

Jack Burns

On Thu, Oct 25, 2018 at 3:24 PM Brandon Paris < notifications@github.com> wrote:

Cleans up the header CSS and what displays a bit. We should discuss what else should go in the header for a washer/driver

You can view, comment on, or merge this pull request online at:

https://github.com/LoopieLLC/WasherPortal/pull/30 Commit Summary

  • Modifying look/feel of washer_session pagE
  • Updating footer of login portal
  • Modifications to driver/washer login pages
  • Conditionally link to either washer/driver sign-in depending on role
  • Check if user exists before rendering conditional user links
  • minor header changes
  • removing errant ruby tags
  • Merge branch 'master' into header-updates
  • Add elsif clause to login links
  • Merge branch 'master' into washer-login-css-updates
  • Resize logo
  • Merge branch 'washer-login-css-updates' into header-updates
  • Fix display of navbar submenu

File Changes

Patch Links:

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zFHdRRdsRoMcj9OtJRniA21Tg0WBks5uojo6gaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433234732

,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipF0lGBmuJ0MFshAo0q_ZlLgbyWhn-ks5uokQvgaJpZM4X7N_z

.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433236985

, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zFbIaiQ-AdJ4g-M3XEnvgO1bW7Sbks5uokchgaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433238987>, or mute the thread < https://github.com/notifications/unsubscribe-auth/AQipFx-_PlVNwalGxNihvF6ZmcHpCdETks5uoknIgaJpZM4X7N_z

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433624862, or mute the thread https://github.com/notifications/unsubscribe-auth/AJA3zAq2Rwmj5FH2P_UsGH0HTCFyzl9eks5upGwVgaJpZM4X7N_z .

brandonparis commented 5 years ago

Solid, well let me know how I can help.

B

On Mon, Oct 29, 2018 at 1:58 PM Jack Burns notifications@github.com wrote:

Hi Brandon,

So as you have noticed, the project has gotten to a point in which organization is going to be essential for completing it. I am going to spend the next couple of days writing documentation, interviewing clients, and creating well defined user stories so that everybody can be on the same page and knows what we still need to do to get this thing finished.

Until recently, it has been mostly me but now that I have some more help, I need to take some time to get everybody on the same page. Let me get back to you either today or tomorrow with some more concrete planning and tasks.

Best,

Jack Burns

On Sat, Oct 27, 2018 at 7:22 AM Brandon Paris notifications@github.com wrote:

Hey Jack,

I'm having a hard time being productive when I sit down to do some work on the portal. I think I could crank out a lot of front-end work if I had a better notion of where the UI was headed and what kinds of tasks still needed to be done. I understand that might be an as-you-go type of thing, but it would be loads helpful to me if there were some written documentation on what needed to get done (besides the small issues I've seen in GitHub). I want to help and be productive but am finding it hard to make any progress other than small CSS changes that need to happen!

On Thu, Oct 25, 2018 at 7:58 PM Brandon Paris brandonprs@gmail.com wrote:

Let me know if you want assistance setting things up, I've used a few different project management tools; they're all pretty straight forward so you'll be fine, let me know if you want help writing "stories."

On Thu, Oct 25, 2018, 19:31 Jack Burns notifications@github.com wrote:

No I have not but that is a great idea! I have been really slacking on documentation because I have been doing a lot of the code myself or directly with others but it is getting chaotic so that is my goal for tomorrow.

Best,

Jack Burns

On Thu, Oct 25, 2018 at 16:20 Brandon Paris <notifications@github.com

wrote:

Sounds good. If Simon is routinely committing / merging in master it shouldn't be an issue. Have you guys thought about using a story tracker like pivotal or jira? It'd be a good tool to use to track issues and features so that I don't start working on something that Simon is already working on.

B

On Thu, Oct 25, 2018, 19:07 Jack Burns notifications@github.com wrote:

Lemme look over these commits when I get home. I know that I have to chat with Simon, our other front-end guy and get you on the same page because he has been doing some work on the CSS as well. So I want to make sure that before I merge that none of your code or his code are conflicting/being written over.

best,

Jack Burns

On Thu, Oct 25, 2018 at 3:24 PM Brandon Paris < notifications@github.com> wrote:

Cleans up the header CSS and what displays a bit. We should discuss what else should go in the header for a washer/driver

You can view, comment on, or merge this pull request online at:

https://github.com/LoopieLLC/WasherPortal/pull/30 Commit Summary

  • Modifying look/feel of washer_session pagE
  • Updating footer of login portal
  • Modifications to driver/washer login pages
  • Conditionally link to either washer/driver sign-in depending on role
  • Check if user exists before rendering conditional user links
  • minor header changes
  • removing errant ruby tags
  • Merge branch 'master' into header-updates
  • Add elsif clause to login links
  • Merge branch 'master' into washer-login-css-updates
  • Resize logo
  • Merge branch 'washer-login-css-updates' into header-updates
  • Fix display of navbar submenu

File Changes

(6)

(2)

(4)

(37)

(4)

(34)

(8)

(35)

(12)

Patch Links:

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zFHdRRdsRoMcj9OtJRniA21Tg0WBks5uojo6gaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433234732

,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipF0lGBmuJ0MFshAo0q_ZlLgbyWhn-ks5uokQvgaJpZM4X7N_z

.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433236985

, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zFbIaiQ-AdJ4g-M3XEnvgO1bW7Sbks5uokchgaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433238987 , or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipFx-_PlVNwalGxNihvF6ZmcHpCdETks5uoknIgaJpZM4X7N_z

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub < https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433624862>, or mute the thread < https://github.com/notifications/unsubscribe-auth/AJA3zAq2Rwmj5FH2P_UsGH0HTCFyzl9eks5upGwVgaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434012789, or mute the thread https://github.com/notifications/unsubscribe-auth/AQipF7cU95aoXwIISLz0T4DfurtKW1-6ks5up0GsgaJpZM4X7N_z .

johncburns1 commented 5 years ago

Brandon,

Just started a new pivotal tracker with Our current Epic and stories for this iteration, which will last for this week and maybe next week (I do not have a good gauge on how long iterations will be yet). Let me know what you think of them and I would love some feedback on what more I can explain and what information you might want to see on there. Could you send my your pivotal tracker account info so that I can invite you to the project?

Best,

Jack Burns

On Mon, Oct 29, 2018 at 11:04 AM Brandon Paris notifications@github.com wrote:

Solid, well let me know how I can help.

B

On Mon, Oct 29, 2018 at 1:58 PM Jack Burns notifications@github.com wrote:

Hi Brandon,

So as you have noticed, the project has gotten to a point in which organization is going to be essential for completing it. I am going to spend the next couple of days writing documentation, interviewing clients, and creating well defined user stories so that everybody can be on the same page and knows what we still need to do to get this thing finished.

Until recently, it has been mostly me but now that I have some more help, I need to take some time to get everybody on the same page. Let me get back to you either today or tomorrow with some more concrete planning and tasks.

Best,

Jack Burns

On Sat, Oct 27, 2018 at 7:22 AM Brandon Paris notifications@github.com wrote:

Hey Jack,

I'm having a hard time being productive when I sit down to do some work on the portal. I think I could crank out a lot of front-end work if I had a better notion of where the UI was headed and what kinds of tasks still needed to be done. I understand that might be an as-you-go type of thing, but it would be loads helpful to me if there were some written documentation on what needed to get done (besides the small issues I've seen in GitHub). I want to help and be productive but am finding it hard to make any progress other than small CSS changes that need to happen!

On Thu, Oct 25, 2018 at 7:58 PM Brandon Paris brandonprs@gmail.com wrote:

Let me know if you want assistance setting things up, I've used a few different project management tools; they're all pretty straight forward so you'll be fine, let me know if you want help writing "stories."

On Thu, Oct 25, 2018, 19:31 Jack Burns notifications@github.com wrote:

No I have not but that is a great idea! I have been really slacking on documentation because I have been doing a lot of the code myself or directly with others but it is getting chaotic so that is my goal for tomorrow.

Best,

Jack Burns

On Thu, Oct 25, 2018 at 16:20 Brandon Paris < notifications@github.com

wrote:

Sounds good. If Simon is routinely committing / merging in master it shouldn't be an issue. Have you guys thought about using a story tracker like pivotal or jira? It'd be a good tool to use to track issues and features so that I don't start working on something that Simon is already working on.

B

On Thu, Oct 25, 2018, 19:07 Jack Burns notifications@github.com wrote:

Lemme look over these commits when I get home. I know that I have to chat with Simon, our other front-end guy and get you on the same page because he has been doing some work on the CSS as well. So I want to make sure that before I merge that none of your code or his code are conflicting/being written over.

best,

Jack Burns

On Thu, Oct 25, 2018 at 3:24 PM Brandon Paris < notifications@github.com> wrote:

Cleans up the header CSS and what displays a bit. We should discuss what else should go in the header for a washer/driver

You can view, comment on, or merge this pull request online at:

https://github.com/LoopieLLC/WasherPortal/pull/30 Commit Summary

  • Modifying look/feel of washer_session pagE
  • Updating footer of login portal
  • Modifications to driver/washer login pages
  • Conditionally link to either washer/driver sign-in depending on role
  • Check if user exists before rendering conditional user links
  • minor header changes
  • removing errant ruby tags
  • Merge branch 'master' into header-updates
  • Add elsif clause to login links
  • Merge branch 'master' into washer-login-css-updates
  • Resize logo
  • Merge branch 'washer-login-css-updates' into header-updates
  • Fix display of navbar submenu

File Changes

(6)

(2)

(4)

(37)

(4)

(34)

(8)

(35)

(12)

Patch Links:

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zFHdRRdsRoMcj9OtJRniA21Tg0WBks5uojo6gaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433234732

,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipF0lGBmuJ0MFshAo0q_ZlLgbyWhn-ks5uokQvgaJpZM4X7N_z

.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433236985

, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zFbIaiQ-AdJ4g-M3XEnvgO1bW7Sbks5uokchgaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433238987 ,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipFx-_PlVNwalGxNihvF6ZmcHpCdETks5uoknIgaJpZM4X7N_z

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub < https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433624862 , or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zAq2Rwmj5FH2P_UsGH0HTCFyzl9eks5upGwVgaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434012789>, or mute the thread < https://github.com/notifications/unsubscribe-auth/AQipF7cU95aoXwIISLz0T4DfurtKW1-6ks5up0GsgaJpZM4X7N_z

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434015488, or mute the thread https://github.com/notifications/unsubscribe-auth/AJA3zJ-_96b8WoRNGUJ63ipeEO_Tg3GTks5up0NBgaJpZM4X7N_z .

brandonparis commented 5 years ago

Cool I'll take a look this evening.

Can you add brandonprs@gmail.com to the Pivotal account? If not, my username is brandonparis and I'm using my work email for my work Pivotal, so I'm assuming you should be able to use the same email for two different Pivotal accounts. That email is brandon@voxel51.com. I would prefer to use brandonprs@gmail.com if you can invite me there.

On Mon, Oct 29, 2018 at 3:35 PM Jack Burns notifications@github.com wrote:

Brandon,

Just started a new pivotal tracker with Our current Epic and stories for this iteration, which will last for this week and maybe next week (I do not have a good gauge on how long iterations will be yet). Let me know what you think of them and I would love some feedback on what more I can explain and what information you might want to see on there. Could you send my your pivotal tracker account info so that I can invite you to the project?

Best,

Jack Burns

On Mon, Oct 29, 2018 at 11:04 AM Brandon Paris notifications@github.com wrote:

Solid, well let me know how I can help.

B

On Mon, Oct 29, 2018 at 1:58 PM Jack Burns notifications@github.com wrote:

Hi Brandon,

So as you have noticed, the project has gotten to a point in which organization is going to be essential for completing it. I am going to spend the next couple of days writing documentation, interviewing clients, and creating well defined user stories so that everybody can be on the same page and knows what we still need to do to get this thing finished.

Until recently, it has been mostly me but now that I have some more help, I need to take some time to get everybody on the same page. Let me get back to you either today or tomorrow with some more concrete planning and tasks.

Best,

Jack Burns

On Sat, Oct 27, 2018 at 7:22 AM Brandon Paris < notifications@github.com> wrote:

Hey Jack,

I'm having a hard time being productive when I sit down to do some work on the portal. I think I could crank out a lot of front-end work if I had a better notion of where the UI was headed and what kinds of tasks still needed to be done. I understand that might be an as-you-go type of thing, but it would be loads helpful to me if there were some written documentation on what needed to get done (besides the small issues I've seen in GitHub). I want to help and be productive but am finding it hard to make any progress other than small CSS changes that need to happen!

On Thu, Oct 25, 2018 at 7:58 PM Brandon Paris brandonprs@gmail.com wrote:

Let me know if you want assistance setting things up, I've used a few different project management tools; they're all pretty straight forward so you'll be fine, let me know if you want help writing "stories."

On Thu, Oct 25, 2018, 19:31 Jack Burns notifications@github.com wrote:

No I have not but that is a great idea! I have been really slacking on documentation because I have been doing a lot of the code myself or directly with others but it is getting chaotic so that is my goal for tomorrow.

Best,

Jack Burns

On Thu, Oct 25, 2018 at 16:20 Brandon Paris < notifications@github.com

wrote:

Sounds good. If Simon is routinely committing / merging in master it shouldn't be an issue. Have you guys thought about using a story tracker like pivotal or jira? It'd be a good tool to use to track issues and features so that I don't start working on something that Simon is already working on.

B

On Thu, Oct 25, 2018, 19:07 Jack Burns < notifications@github.com> wrote:

Lemme look over these commits when I get home. I know that I have to chat with Simon, our other front-end guy and get you on the same page because he has been doing some work on the CSS as well. So I want to make sure that before I merge that none of your code or his code are conflicting/being written over.

best,

Jack Burns

On Thu, Oct 25, 2018 at 3:24 PM Brandon Paris < notifications@github.com> wrote:

Cleans up the header CSS and what displays a bit. We should discuss what else should go in the header for a washer/driver

You can view, comment on, or merge this pull request online at:

https://github.com/LoopieLLC/WasherPortal/pull/30 Commit Summary

  • Modifying look/feel of washer_session pagE
  • Updating footer of login portal
  • Modifications to driver/washer login pages
  • Conditionally link to either washer/driver sign-in depending on role
  • Check if user exists before rendering conditional user links
  • minor header changes
  • removing errant ruby tags
  • Merge branch 'master' into header-updates
  • Add elsif clause to login links
  • Merge branch 'master' into washer-login-css-updates
  • Resize logo
  • Merge branch 'washer-login-css-updates' into header-updates
  • Fix display of navbar submenu

File Changes

(6)

(2)

(4)

(37)

(4)

(34)

(8)

(35)

(12)

Patch Links:

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zFHdRRdsRoMcj9OtJRniA21Tg0WBks5uojo6gaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433234732

,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipF0lGBmuJ0MFshAo0q_ZlLgbyWhn-ks5uokQvgaJpZM4X7N_z

.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433236985

, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zFbIaiQ-AdJ4g-M3XEnvgO1bW7Sbks5uokchgaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433238987 ,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipFx-_PlVNwalGxNihvF6ZmcHpCdETks5uoknIgaJpZM4X7N_z

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433624862 ,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zAq2Rwmj5FH2P_UsGH0HTCFyzl9eks5upGwVgaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434012789 , or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipF7cU95aoXwIISLz0T4DfurtKW1-6ks5up0GsgaJpZM4X7N_z

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub < https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434015488>, or mute the thread < https://github.com/notifications/unsubscribe-auth/AJA3zJ-_96b8WoRNGUJ63ipeEO_Tg3GTks5up0NBgaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434049188, or mute the thread https://github.com/notifications/unsubscribe-auth/AQipF03ydfvRX2Hadp0XAnLBlEvD9blmks5up1h4gaJpZM4X7N_z .

johncburns1 commented 5 years ago

Brandon,

Just sent you the invite.

Best,

Jack Burns

On Mon, Oct 29, 2018 at 12:42 PM Brandon Paris notifications@github.com wrote:

Cool I'll take a look this evening.

Can you add brandonprs@gmail.com to the Pivotal account? If not, my username is brandonparis and I'm using my work email for my work Pivotal, so I'm assuming you should be able to use the same email for two different Pivotal accounts. That email is brandon@voxel51.com. I would prefer to use brandonprs@gmail.com if you can invite me there.

On Mon, Oct 29, 2018 at 3:35 PM Jack Burns notifications@github.com wrote:

Brandon,

Just started a new pivotal tracker with Our current Epic and stories for this iteration, which will last for this week and maybe next week (I do not have a good gauge on how long iterations will be yet). Let me know what you think of them and I would love some feedback on what more I can explain and what information you might want to see on there. Could you send my your pivotal tracker account info so that I can invite you to the project?

Best,

Jack Burns

On Mon, Oct 29, 2018 at 11:04 AM Brandon Paris <notifications@github.com

wrote:

Solid, well let me know how I can help.

B

On Mon, Oct 29, 2018 at 1:58 PM Jack Burns notifications@github.com wrote:

Hi Brandon,

So as you have noticed, the project has gotten to a point in which organization is going to be essential for completing it. I am going to spend the next couple of days writing documentation, interviewing clients, and creating well defined user stories so that everybody can be on the same page and knows what we still need to do to get this thing finished.

Until recently, it has been mostly me but now that I have some more help, I need to take some time to get everybody on the same page. Let me get back to you either today or tomorrow with some more concrete planning and tasks.

Best,

Jack Burns

On Sat, Oct 27, 2018 at 7:22 AM Brandon Paris < notifications@github.com> wrote:

Hey Jack,

I'm having a hard time being productive when I sit down to do some work on the portal. I think I could crank out a lot of front-end work if I had a better notion of where the UI was headed and what kinds of tasks still needed to be done. I understand that might be an as-you-go type of thing, but it would be loads helpful to me if there were some written documentation on what needed to get done (besides the small issues I've seen in GitHub). I want to help and be productive but am finding it hard to make any progress other than small CSS changes that need to happen!

On Thu, Oct 25, 2018 at 7:58 PM Brandon Paris < brandonprs@gmail.com> wrote:

Let me know if you want assistance setting things up, I've used a few different project management tools; they're all pretty straight forward so you'll be fine, let me know if you want help writing "stories."

On Thu, Oct 25, 2018, 19:31 Jack Burns <notifications@github.com

wrote:

No I have not but that is a great idea! I have been really slacking on documentation because I have been doing a lot of the code myself or directly with others but it is getting chaotic so that is my goal for tomorrow.

Best,

Jack Burns

On Thu, Oct 25, 2018 at 16:20 Brandon Paris < notifications@github.com

wrote:

Sounds good. If Simon is routinely committing / merging in master it shouldn't be an issue. Have you guys thought about using a story tracker like pivotal or jira? It'd be a good tool to use to track issues and features so that I don't start working on something that Simon is already working on.

B

On Thu, Oct 25, 2018, 19:07 Jack Burns < notifications@github.com> wrote:

Lemme look over these commits when I get home. I know that I have to chat with Simon, our other front-end guy and get you on the same page because he has been doing some work on the CSS as well. So I want to make sure that before I merge that none of your code or his code are conflicting/being written over.

best,

Jack Burns

On Thu, Oct 25, 2018 at 3:24 PM Brandon Paris < notifications@github.com> wrote:

Cleans up the header CSS and what displays a bit. We should discuss what else should go in the header for a washer/driver

You can view, comment on, or merge this pull request online at:

https://github.com/LoopieLLC/WasherPortal/pull/30 Commit Summary

  • Modifying look/feel of washer_session pagE
  • Updating footer of login portal
  • Modifications to driver/washer login pages
  • Conditionally link to either washer/driver sign-in depending on role
  • Check if user exists before rendering conditional user links
  • minor header changes
  • removing errant ruby tags
  • Merge branch 'master' into header-updates
  • Add elsif clause to login links
  • Merge branch 'master' into washer-login-css-updates
  • Resize logo
  • Merge branch 'washer-login-css-updates' into header-updates
  • Fix display of navbar submenu

File Changes

(6)

(2)

(4)

(37)

(4)

(34)

(8)

(35)

(12)

Patch Links:

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zFHdRRdsRoMcj9OtJRniA21Tg0WBks5uojo6gaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433234732

,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipF0lGBmuJ0MFshAo0q_ZlLgbyWhn-ks5uokQvgaJpZM4X7N_z

.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433236985

, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zFbIaiQ-AdJ4g-M3XEnvgO1bW7Sbks5uokchgaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433238987

,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipFx-_PlVNwalGxNihvF6ZmcHpCdETks5uoknIgaJpZM4X7N_z

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433624862 ,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zAq2Rwmj5FH2P_UsGH0HTCFyzl9eks5upGwVgaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434012789 ,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipF7cU95aoXwIISLz0T4DfurtKW1-6ks5up0GsgaJpZM4X7N_z

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub < https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434015488 , or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zJ-_96b8WoRNGUJ63ipeEO_Tg3GTks5up0NBgaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434049188>, or mute the thread < https://github.com/notifications/unsubscribe-auth/AQipF03ydfvRX2Hadp0XAnLBlEvD9blmks5up1h4gaJpZM4X7N_z

.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434051561, or mute the thread https://github.com/notifications/unsubscribe-auth/AJA3zBrj4SLNVxInanSbHrRTCCxlUBZwks5up1o5gaJpZM4X7N_z .

brandonparis commented 5 years ago

Great! Everything looks good, I appreciate the detail you put into each story.

Not that it really matters, but agile companies tend to use the fibonacci scale for story points. If you ever decide to stick to a sprint schedule (1-2 weeks), you might want to adopt the scale. 1 for trivial tasks 2 for trivial tasks that might take a few hours 3 for something that might take a day 5 for something that make take a few days or so 8 for something that could take a whole sprint 13 for something that needs to be broken up into smaller tasks :)

Obviously, interpret those points as you deem fit for the team. But that's the general gist. It's a good way to look at velocity over time, but don't concern yourself with that right now. That's for a project manager!

On Mon, Oct 29, 2018 at 3:44 PM Jack Burns notifications@github.com wrote:

Brandon,

Just sent you the invite.

Best,

Jack Burns

On Mon, Oct 29, 2018 at 12:42 PM Brandon Paris notifications@github.com wrote:

Cool I'll take a look this evening.

Can you add brandonprs@gmail.com to the Pivotal account? If not, my username is brandonparis and I'm using my work email for my work Pivotal, so I'm assuming you should be able to use the same email for two different Pivotal accounts. That email is brandon@voxel51.com. I would prefer to use brandonprs@gmail.com if you can invite me there.

On Mon, Oct 29, 2018 at 3:35 PM Jack Burns notifications@github.com wrote:

Brandon,

Just started a new pivotal tracker with Our current Epic and stories for this iteration, which will last for this week and maybe next week (I do not have a good gauge on how long iterations will be yet). Let me know what you think of them and I would love some feedback on what more I can explain and what information you might want to see on there. Could you send my your pivotal tracker account info so that I can invite you to the project?

Best,

Jack Burns

On Mon, Oct 29, 2018 at 11:04 AM Brandon Paris < notifications@github.com

wrote:

Solid, well let me know how I can help.

B

On Mon, Oct 29, 2018 at 1:58 PM Jack Burns <notifications@github.com

wrote:

Hi Brandon,

So as you have noticed, the project has gotten to a point in which organization is going to be essential for completing it. I am going to spend the next couple of days writing documentation, interviewing clients, and creating well defined user stories so that everybody can be on the same page and knows what we still need to do to get this thing finished.

Until recently, it has been mostly me but now that I have some more help, I need to take some time to get everybody on the same page. Let me get back to you either today or tomorrow with some more concrete planning and tasks.

Best,

Jack Burns

On Sat, Oct 27, 2018 at 7:22 AM Brandon Paris < notifications@github.com> wrote:

Hey Jack,

I'm having a hard time being productive when I sit down to do some work on the portal. I think I could crank out a lot of front-end work if I had a better notion of where the UI was headed and what kinds of tasks still needed to be done. I understand that might be an as-you-go type of thing, but it would be loads helpful to me if there were some written documentation on what needed to get done (besides the small issues I've seen in GitHub). I want to help and be productive but am finding it hard to make any progress other than small CSS changes that need to happen!

On Thu, Oct 25, 2018 at 7:58 PM Brandon Paris < brandonprs@gmail.com> wrote:

Let me know if you want assistance setting things up, I've used a few different project management tools; they're all pretty straight forward so you'll be fine, let me know if you want help writing "stories."

On Thu, Oct 25, 2018, 19:31 Jack Burns < notifications@github.com

wrote:

No I have not but that is a great idea! I have been really slacking on documentation because I have been doing a lot of the code myself or directly with others but it is getting chaotic so that is my goal for tomorrow.

Best,

Jack Burns

On Thu, Oct 25, 2018 at 16:20 Brandon Paris < notifications@github.com

wrote:

Sounds good. If Simon is routinely committing / merging in master it shouldn't be an issue. Have you guys thought about using a story tracker like pivotal or jira? It'd be a good tool to use to track issues and features so that I don't start working on something that Simon is already working on.

B

On Thu, Oct 25, 2018, 19:07 Jack Burns < notifications@github.com> wrote:

Lemme look over these commits when I get home. I know that I have to chat with Simon, our other front-end guy and get you on the same page because he has been doing some work on the CSS as well. So I want to make sure that before I merge that none of your code or his code are conflicting/being written over.

best,

Jack Burns

On Thu, Oct 25, 2018 at 3:24 PM Brandon Paris < notifications@github.com> wrote:

Cleans up the header CSS and what displays a bit. We should discuss what else should go in the header for a washer/driver

You can view, comment on, or merge this pull request online at:

https://github.com/LoopieLLC/WasherPortal/pull/30 Commit Summary

  • Modifying look/feel of washer_session pagE
  • Updating footer of login portal
  • Modifications to driver/washer login pages
  • Conditionally link to either washer/driver sign-in depending on role
  • Check if user exists before rendering conditional user links
  • minor header changes
  • removing errant ruby tags
  • Merge branch 'master' into header-updates
  • Add elsif clause to login links
  • Merge branch 'master' into washer-login-css-updates
  • Resize logo
  • Merge branch 'washer-login-css-updates' into header-updates
  • Fix display of navbar submenu

File Changes

(6)

(2)

(4)

(37)

(4)

(34)

(8)

(35)

(12)

Patch Links:

- https://github.com/LoopieLLC/WasherPortal/pull/30.patch

https://github.com/LoopieLLC/WasherPortal/pull/30.diff

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zFHdRRdsRoMcj9OtJRniA21Tg0WBks5uojo6gaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433234732

,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipF0lGBmuJ0MFshAo0q_ZlLgbyWhn-ks5uokQvgaJpZM4X7N_z

.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433236985

, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zFbIaiQ-AdJ4g-M3XEnvgO1bW7Sbks5uokchgaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433238987

,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipFx-_PlVNwalGxNihvF6ZmcHpCdETks5uoknIgaJpZM4X7N_z

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433624862

,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zAq2Rwmj5FH2P_UsGH0HTCFyzl9eks5upGwVgaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434012789 ,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipF7cU95aoXwIISLz0T4DfurtKW1-6ks5up0GsgaJpZM4X7N_z

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434015488 ,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zJ-_96b8WoRNGUJ63ipeEO_Tg3GTks5up0NBgaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434049188 , or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipF03ydfvRX2Hadp0XAnLBlEvD9blmks5up1h4gaJpZM4X7N_z

.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub < https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434051561>, or mute the thread < https://github.com/notifications/unsubscribe-auth/AJA3zBrj4SLNVxInanSbHrRTCCxlUBZwks5up1o5gaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434051951, or mute the thread https://github.com/notifications/unsubscribe-auth/AQipF9izQ0xPCkoYsI96JqTEBUwm5VQMks5up1qKgaJpZM4X7N_z .

johncburns1 commented 5 years ago

Brandon,

Love the feedback. I am reading some book on Agile right now so hopefully I can continue to apply some of those practices in the future and as the team grows. Please feel free to let me know how and where I can be doing better. I always greatly appreciate feedback. Do you have a more clear idea about what needs to be done during this sprint? Did you snag a story to work on?

Best,

Jack Burns

On Mon, Oct 29, 2018 at 2:51 PM Brandon Paris notifications@github.com wrote:

Great! Everything looks good, I appreciate the detail you put into each story.

Not that it really matters, but agile companies tend to use the fibonacci scale for story points. If you ever decide to stick to a sprint schedule (1-2 weeks), you might want to adopt the scale. 1 for trivial tasks 2 for trivial tasks that might take a few hours 3 for something that might take a day 5 for something that make take a few days or so 8 for something that could take a whole sprint 13 for something that needs to be broken up into smaller tasks :)

Obviously, interpret those points as you deem fit for the team. But that's the general gist. It's a good way to look at velocity over time, but don't concern yourself with that right now. That's for a project manager!

On Mon, Oct 29, 2018 at 3:44 PM Jack Burns notifications@github.com wrote:

Brandon,

Just sent you the invite.

Best,

Jack Burns

On Mon, Oct 29, 2018 at 12:42 PM Brandon Paris <notifications@github.com

wrote:

Cool I'll take a look this evening.

Can you add brandonprs@gmail.com to the Pivotal account? If not, my username is brandonparis and I'm using my work email for my work Pivotal, so I'm assuming you should be able to use the same email for two different Pivotal accounts. That email is brandon@voxel51.com. I would prefer to use brandonprs@gmail.com if you can invite me there.

On Mon, Oct 29, 2018 at 3:35 PM Jack Burns notifications@github.com wrote:

Brandon,

Just started a new pivotal tracker with Our current Epic and stories for this iteration, which will last for this week and maybe next week (I do not have a good gauge on how long iterations will be yet). Let me know what you think of them and I would love some feedback on what more I can explain and what information you might want to see on there. Could you send my your pivotal tracker account info so that I can invite you to the project?

Best,

Jack Burns

On Mon, Oct 29, 2018 at 11:04 AM Brandon Paris < notifications@github.com

wrote:

Solid, well let me know how I can help.

B

On Mon, Oct 29, 2018 at 1:58 PM Jack Burns < notifications@github.com

wrote:

Hi Brandon,

So as you have noticed, the project has gotten to a point in which organization is going to be essential for completing it. I am going to spend the next couple of days writing documentation, interviewing clients, and creating well defined user stories so that everybody can be on the same page and knows what we still need to do to get this thing finished.

Until recently, it has been mostly me but now that I have some more help, I need to take some time to get everybody on the same page. Let me get back to you either today or tomorrow with some more concrete planning and tasks.

Best,

Jack Burns

On Sat, Oct 27, 2018 at 7:22 AM Brandon Paris < notifications@github.com> wrote:

Hey Jack,

I'm having a hard time being productive when I sit down to do some work on the portal. I think I could crank out a lot of front-end work if I had a better notion of where the UI was headed and what kinds of tasks still needed to be done. I understand that might be an as-you-go type of thing, but it would be loads helpful to me if there were some written documentation on what needed to get done (besides the small issues I've seen in GitHub). I want to help and be productive but am finding it hard to make any progress other than small CSS changes that need to happen!

On Thu, Oct 25, 2018 at 7:58 PM Brandon Paris < brandonprs@gmail.com> wrote:

Let me know if you want assistance setting things up, I've used a few different project management tools; they're all pretty straight forward so you'll be fine, let me know if you want help writing "stories."

On Thu, Oct 25, 2018, 19:31 Jack Burns < notifications@github.com

wrote:

No I have not but that is a great idea! I have been really slacking on documentation because I have been doing a lot of the code myself or directly with others but it is getting chaotic so that is my goal for tomorrow.

Best,

Jack Burns

On Thu, Oct 25, 2018 at 16:20 Brandon Paris < notifications@github.com

wrote:

Sounds good. If Simon is routinely committing / merging in master it shouldn't be an issue. Have you guys thought about using a story tracker like pivotal or jira? It'd be a good tool to use to track issues and features so that I don't start working on something that Simon is already working on.

B

On Thu, Oct 25, 2018, 19:07 Jack Burns < notifications@github.com> wrote:

Lemme look over these commits when I get home. I know that I have to chat with Simon, our other front-end guy and get you on the same page because he has been doing some work on the CSS as well. So I want to make sure that before I merge that none of your code or his code are conflicting/being written over.

best,

Jack Burns

On Thu, Oct 25, 2018 at 3:24 PM Brandon Paris < notifications@github.com> wrote:

Cleans up the header CSS and what displays a bit. We should discuss what else should go in the header for a washer/driver

You can view, comment on, or merge this pull request online at:

https://github.com/LoopieLLC/WasherPortal/pull/30 Commit Summary

  • Modifying look/feel of washer_session pagE
  • Updating footer of login portal
  • Modifications to driver/washer login pages
  • Conditionally link to either washer/driver sign-in depending on role
  • Check if user exists before rendering conditional user links
  • minor header changes
  • removing errant ruby tags
  • Merge branch 'master' into header-updates
  • Add elsif clause to login links
  • Merge branch 'master' into washer-login-css-updates
  • Resize logo
  • Merge branch 'washer-login-css-updates' into header-updates
  • Fix display of navbar submenu

File Changes

(6)

(2)

(4)

(37)

(4)

(34)

(8)

(35)

(12)

Patch Links:

- https://github.com/LoopieLLC/WasherPortal/pull/30.patch

https://github.com/LoopieLLC/WasherPortal/pull/30.diff

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zFHdRRdsRoMcj9OtJRniA21Tg0WBks5uojo6gaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433234732

,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipF0lGBmuJ0MFshAo0q_ZlLgbyWhn-ks5uokQvgaJpZM4X7N_z

.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433236985

, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zFbIaiQ-AdJ4g-M3XEnvgO1bW7Sbks5uokchgaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433238987

,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipFx-_PlVNwalGxNihvF6ZmcHpCdETks5uoknIgaJpZM4X7N_z

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433624862

,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zAq2Rwmj5FH2P_UsGH0HTCFyzl9eks5upGwVgaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434012789

,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipF7cU95aoXwIISLz0T4DfurtKW1-6ks5up0GsgaJpZM4X7N_z

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434015488 ,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zJ-_96b8WoRNGUJ63ipeEO_Tg3GTks5up0NBgaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434049188 ,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipF03ydfvRX2Hadp0XAnLBlEvD9blmks5up1h4gaJpZM4X7N_z

.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub < https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434051561 , or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zBrj4SLNVxInanSbHrRTCCxlUBZwks5up1o5gaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434051951>, or mute the thread < https://github.com/notifications/unsubscribe-auth/AQipF9izQ0xPCkoYsI96JqTEBUwm5VQMks5up1qKgaJpZM4X7N_z

.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434094252, or mute the thread https://github.com/notifications/unsubscribe-auth/AJA3zEkfbQVXJHRy33y2Ou7eCeq0nDAJks5up3hMgaJpZM4X7N_z .

brandonparis commented 5 years ago

I just added a story that I've been working on, a general reworking of the site so that it more closely matches the screenshots in the Wiki. Let me know if there are more updated designs that I should be trying to match instead of the ones in the Wiki.

Also, everything I've suggested are just that: suggestions. They're not the only way of doing things, just the ways that I've seen in my career so far. So if you're ever not down with an idea, don't feel obliged to give it a try.

On Mon, Oct 29, 2018 at 9:24 PM Jack Burns notifications@github.com wrote:

Brandon,

Love the feedback. I am reading some book on Agile right now so hopefully I can continue to apply some of those practices in the future and as the team grows. Please feel free to let me know how and where I can be doing better. I always greatly appreciate feedback. Do you have a more clear idea about what needs to be done during this sprint? Did you snag a story to work on?

Best,

Jack Burns

On Mon, Oct 29, 2018 at 2:51 PM Brandon Paris notifications@github.com wrote:

Great! Everything looks good, I appreciate the detail you put into each story.

Not that it really matters, but agile companies tend to use the fibonacci scale for story points. If you ever decide to stick to a sprint schedule (1-2 weeks), you might want to adopt the scale. 1 for trivial tasks 2 for trivial tasks that might take a few hours 3 for something that might take a day 5 for something that make take a few days or so 8 for something that could take a whole sprint 13 for something that needs to be broken up into smaller tasks :)

Obviously, interpret those points as you deem fit for the team. But that's the general gist. It's a good way to look at velocity over time, but don't concern yourself with that right now. That's for a project manager!

On Mon, Oct 29, 2018 at 3:44 PM Jack Burns notifications@github.com wrote:

Brandon,

Just sent you the invite.

Best,

Jack Burns

On Mon, Oct 29, 2018 at 12:42 PM Brandon Paris < notifications@github.com

wrote:

Cool I'll take a look this evening.

Can you add brandonprs@gmail.com to the Pivotal account? If not, my username is brandonparis and I'm using my work email for my work Pivotal, so I'm assuming you should be able to use the same email for two different Pivotal accounts. That email is brandon@voxel51.com. I would prefer to use brandonprs@gmail.com if you can invite me there.

On Mon, Oct 29, 2018 at 3:35 PM Jack Burns <notifications@github.com

wrote:

Brandon,

Just started a new pivotal tracker with Our current Epic and stories for this iteration, which will last for this week and maybe next week (I do not have a good gauge on how long iterations will be yet). Let me know what you think of them and I would love some feedback on what more I can explain and what information you might want to see on there. Could you send my your pivotal tracker account info so that I can invite you to the project?

Best,

Jack Burns

On Mon, Oct 29, 2018 at 11:04 AM Brandon Paris < notifications@github.com

wrote:

Solid, well let me know how I can help.

B

On Mon, Oct 29, 2018 at 1:58 PM Jack Burns < notifications@github.com

wrote:

Hi Brandon,

So as you have noticed, the project has gotten to a point in which organization is going to be essential for completing it. I am going to spend the next couple of days writing documentation, interviewing clients, and creating well defined user stories so that everybody can be on the same page and knows what we still need to do to get this thing finished.

Until recently, it has been mostly me but now that I have some more help, I need to take some time to get everybody on the same page. Let me get back to you either today or tomorrow with some more concrete planning and tasks.

Best,

Jack Burns

On Sat, Oct 27, 2018 at 7:22 AM Brandon Paris < notifications@github.com> wrote:

Hey Jack,

I'm having a hard time being productive when I sit down to do some work on the portal. I think I could crank out a lot of front-end work if I had a better notion of where the UI was headed and what kinds of tasks still needed to be done. I understand that might be an as-you-go type of thing, but it would be loads helpful to me if there were some written documentation on what needed to get done (besides the small issues I've seen in GitHub). I want to help and be productive but am finding it hard to make any progress other than small CSS changes that need to happen!

On Thu, Oct 25, 2018 at 7:58 PM Brandon Paris < brandonprs@gmail.com> wrote:

Let me know if you want assistance setting things up, I've used a few different project management tools; they're all pretty straight forward so you'll be fine, let me know if you want help writing "stories."

On Thu, Oct 25, 2018, 19:31 Jack Burns < notifications@github.com

wrote:

No I have not but that is a great idea! I have been really slacking on documentation because I have been doing a lot of the code myself or directly with others but it is getting chaotic so that is my goal for tomorrow.

Best,

Jack Burns

On Thu, Oct 25, 2018 at 16:20 Brandon Paris < notifications@github.com

wrote:

Sounds good. If Simon is routinely committing / merging in master it shouldn't be an issue. Have you guys thought about using a story tracker like pivotal or jira? It'd be a good tool to use to track issues and features so that I don't start working on something that Simon is already working on.

B

On Thu, Oct 25, 2018, 19:07 Jack Burns < notifications@github.com> wrote:

Lemme look over these commits when I get home. I know that I have to chat with Simon, our other front-end guy and get you on the same page because he has been doing some work on the CSS as well. So I want to make sure that before I merge that none of your code or his code are conflicting/being written over.

best,

Jack Burns

On Thu, Oct 25, 2018 at 3:24 PM Brandon Paris < notifications@github.com> wrote:

Cleans up the header CSS and what displays a bit. We should discuss what else should go in the header for a washer/driver

You can view, comment on, or merge this pull request online at:

https://github.com/LoopieLLC/WasherPortal/pull/30 Commit Summary

  • Modifying look/feel of washer_session pagE
  • Updating footer of login portal
  • Modifications to driver/washer login pages
  • Conditionally link to either washer/driver sign-in depending on role
  • Check if user exists before rendering conditional user links
  • minor header changes
  • removing errant ruby tags
  • Merge branch 'master' into header-updates
  • Add elsif clause to login links
  • Merge branch 'master' into washer-login-css-updates
  • Resize logo
  • Merge branch 'washer-login-css-updates' into header-updates
  • Fix display of navbar submenu

File Changes

(6)

(2)

(4)

(37)

(4)

(34)

(8)

(35)

(12)

Patch Links:

- https://github.com/LoopieLLC/WasherPortal/pull/30.patch

https://github.com/LoopieLLC/WasherPortal/pull/30.diff

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <https://github.com/LoopieLLC/WasherPortal/pull/30 , or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zFHdRRdsRoMcj9OtJRniA21Tg0WBks5uojo6gaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433234732

,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipF0lGBmuJ0MFshAo0q_ZlLgbyWhn-ks5uokQvgaJpZM4X7N_z

.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433236985

, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zFbIaiQ-AdJ4g-M3XEnvgO1bW7Sbks5uokchgaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433238987

,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipFx-_PlVNwalGxNihvF6ZmcHpCdETks5uoknIgaJpZM4X7N_z

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-433624862

,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zAq2Rwmj5FH2P_UsGH0HTCFyzl9eks5upGwVgaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434012789

,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipF7cU95aoXwIISLz0T4DfurtKW1-6ks5up0GsgaJpZM4X7N_z

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434015488

,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zJ-_96b8WoRNGUJ63ipeEO_Tg3GTks5up0NBgaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434049188 ,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipF03ydfvRX2Hadp0XAnLBlEvD9blmks5up1h4gaJpZM4X7N_z

.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <

https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434051561 ,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/AJA3zBrj4SLNVxInanSbHrRTCCxlUBZwks5up1o5gaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434051951 , or mute the thread <

https://github.com/notifications/unsubscribe-auth/AQipF9izQ0xPCkoYsI96JqTEBUwm5VQMks5up1qKgaJpZM4X7N_z

.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub < https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434094252>, or mute the thread < https://github.com/notifications/unsubscribe-auth/AJA3zEkfbQVXJHRy33y2Ou7eCeq0nDAJks5up3hMgaJpZM4X7N_z

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/LoopieLLC/WasherPortal/pull/30#issuecomment-434138398, or mute the thread https://github.com/notifications/unsubscribe-auth/AQipF_7XROXMsdyPB32Lo9FQnDPdHa2aks5up6pWgaJpZM4X7N_z .