Team 5 Policies - rsanchez-wsu/jfiles GitHub Wiki

Team 5 Policies

Policy On the Use of the "Side Issue" Label

The "Side Issue" label was added to indicate that an issue is not associated with any milestone. For most issues, this is because they are not considered critical for that moment or would take too much time for one milestone and should be worked on off-and-on in free time.

In some cases, however, it is because the issue is not supposed to be directly worked on, rather it is built on through sub-issues. This is how Team 5 handles large, cumbersome issues that will take multiple weeks to complete. An example of this would be any issue that grows with the project, such as any issues about keeping code clean. Another example would be an issue that is created to unite similar issues together. Since issues can only be under one milestone, this can be done to break up one issue into smaller pieces that can be reasonably put on a weekly milestone. In this way, the team can work on broader issues (such as collaborating with other teams) while still keeping their milestones manageable.

See issue #66 as an example of how the one issue is used as a master to multiple sub-issues. In this way, the issues that are a part of this issue all have a hub to be linked to and there is a common place to communicate needs/wants to Team 5. There is also a channel in Slack, but these channels are not suited for long-term records. This is why having a communication hub in GitHub is beneficial; future classes/teams can review the conversations had at this location.

Team 5 Collaboration Policy

Team 5 shall make weekly milestones based on what issues exist at the time the milestone is made so that will know that they will have work to do for that milestone, that the work will be reasonable in amount, and what that work will even be. This is to say, they will build their current milestone for the week based on what issues they know of and will focus on those issues primarily. They will, however, build issues that are brought to them into the next milestone, so that they can know what they have to work on.

This means that if your team has an issue that they need done, you can expect Team 5 to take on your issue only after they finish the issues for their current milestone or build it into the next milestone. Keep this in mind when the end of the week is coming around and please plan ahead for anything you would like done. This shall be done so that Team 5 can know at the start of week all that they have to do for the week and can make milestones and plan around this information.

Please plan in advance around this and think of what you will need for the next week if possible. We acknowledge that this is not always possible, so please review the notice below on how to get help if it is urgent. We also may take an issue and break it up into sub-sub-issues if the issue is complex or large, so the more advanced notice we are given, the better it will be for all people.

Please communicate any and all collaboration requests through issue #66 so that the request can be recorded and processed efficiently. You may send a request through the "file_api_integration" channel in Slack, but be aware that we will take the request and post it in issue #66.

Team 5 Urgent Help Policy

If you need something and it is urgent, post it in issue #66 with @ mentions to me (@Dorkatron199), Brand(@BrandAllred), and Sergio(@srodriguez4) and send a post on the "file_api_integration" channel with @ mentions for each of our team members and a link to this page. Make sure to give the request the header "URGENT HELP REQUEST". One of our team members shall give notice that they've seen it as soon as they can and will notify the rest of the team. If there is a genuine need, we may set aside our milestone to help you.

Policy Disclaimer

All policies above pending long-term testing. These policies may be modified if deemed too restrictive to the project as a whole, are considered of poor temperament, or have some other problems. These policies are designed to help organize the workflow for Team 5, not drag down the project. Team 5 reserves the right to modify this policy as necessary. If any need to be changed, a notice will be put on the general channel of the change.