-
Notifications
You must be signed in to change notification settings - Fork 0
Personnel Unit Groupings
These are the teams I think we might need.
The number in parentheses after the group name indicates an estimated group member count. This estimation is not hard and fast by any means.
The number in parentheses after a person's name indicates levels of preference for each job, with "1" being highly preferred.
If you think we need additional groups, add your ideas to the bottom of this page.
Responsible for receiving and storing ticker data.
- Bret Leduc (1)
- shaunwolff (1)
Standard Database Administration
- Nick Patterson (2)
- Martin DeWitt (1)
- Scott Williams (1)
- shaunwolff (3)
Responsible for page layouts, artwork, and user interface standards.
- brwhale (2)
- daveer (2)
- JAllred (1)
- TreaganP (1)
- dadolym (1)
- Tamarra Phillips phillipta (1)
- Jeff Karmy(4)
Manages user account creation, modification, and deletion, as well as user data storage.
- wernermichael (5)
Processes user commands, and performs trades. May involve coding a simple buy/sell scripting language for users to take advantage of.
- Jeff Karmy (1)
- Ryan Dempsey (2)
- Nick Patterson (3)
Sneaky ninjas that fix & write random stuff._
- brwhale (3)
- daveer (3)
In charge of developing a mobile app that tethers to the trade system.
- Sean Ewing (1)
- Nick Patterson (1)
- Cody Shilts (1)
- Jian Rossi (1)
Testing
- Ghenaj1 (1)
- jeremy-french (2)
- brwhale (1)
- daveer (1)
- carlsonjohn (2)
- blykins (1)
- dadolym (2)
- Jeff Karmy (2)
Manages the build process, assists with module compatibility.
- Bret Leduc (3)
- Ryan Dempsey (1)
Project Management
- jeremy-french (1)
- Martin DeWitt (1)
- Scott Williams (1)
- shaunwolff (2)
- Tamarra Phillips phillipta (2)
HTML code, page templates & layouts
- Cody Shilts (2)
- Sean Ewing (2)
- Jesse Allred (2)
- Bret Leduc (2)
- Melissa Dadoly (3)
##Security (4) Security
- Judy Weaver (1)
- blykins (1)
- carlsonjohn (1)
- Jeff Karmy (3)
New Group Suggestion: What about a documentation guy/gal? Yea, everybody should be writing documentation for their own section of the project, but still, seems we would benefit from having a single person in charge of combining and editing the documentation into a single uniform resource. This person would also be responsible for writing important documentation that does not specifically belong to any particular group. Thoughts?