Team Charter - nateyb93/WeatherActive GitHub Wiki

Mission

We value code that not only performs its desired functionality, but is easy to read and consistant. Our code must adhere to the team's Coding Standards document. Coding standards used by the team include: ◦Function and variable names shall be named using camelCase.
- Function and instance variables declarations shall be commented using XML-style "/**" comments.
- Helper functions shall be used whenever possible to reduce cluttered code and increase project readability.
- Code shall never extend beyond the length of a computer screen. When possible, a single line of code shall be no more than 80 characters long.
- Functions and instance variable shall be declared in alphabetical order to increaase readability.
- At least two lines of whitespace shall be used between function declarations. For instance variable declarations, oen line of whitespace shall be used. *Braces shall always be used in concordance with loops and conditional statements, even if the nested code is only one line long.
We value visually pleasing project presentations, but not at the risk of losing clarity of the data being presented.

On texts and e-mails: "All team members shall reply to all text messages within an hour, unless the text recipient is in class or otherwise unavailable. E-mails will be reserved for larger messages. If a team member must contact a teammate immediately, text message, e-mail and Facebook may be used."
On meetings: "Team meetings shall be called when a subject cannot be adequately discussed over e-mail. The team member who called the meeting must send a meeting agenda to the remaining team members no later than the night before the meeting. If a team member must be late to a meeting or absent, he shall contact the remaining team members as soon as possible. The absent team member shall receive a copy of what was discussed at the meeting. Actions to be taken regarding habitual absenteeism will be discussed in The Intervention Protocol."
On grades: "All team members must work to achieve an A on all graded deliverables."
On version control: "All team members must use the team GitHub repository for editing their portion of the project."
On deadlines: "All team members must submit their portion of the project in a timely fashion, as early as possible. If a team member does not think their portion of the project can be completed on time, he shall contact the remaining team members as soon as possible for assistance."

Architect: Triton Pitassi will act as the team's primary project architect and ensure that the JavaScript functionality of the project is working properly.
Data Manager/Version Control Monitor: Nathan Brown will act as the team's primary database manager and will ensure the master branch of the team's GitHub repository only contains code that is ready for use.
Design Manager: Daniel Jones will act as the team's primary project interface designer and will be resposible to create the project's HTML and CSS.

If a team member is habitually late to/absent from team meetings, fails to submit work on time or submits sub-standard work, the teams shall:

Step one: A meeting shall be held between the affected team members. All team members shall use respectful language towards one another and attempt to understand why the problems are occuring. If able/needed, other team members shall assist the problematic team member to the best of their ability. If the problematic team member assures the others that the problem will be fixed, the situation shall be considered resolved. However, if the problem persists and the problematic team member will not accept help, the team shall proceed to:
Step two: The team shall request a meeting with Dr. Crenshaw to discuss the recurring problems and find a solution.