Skip to content

Feature/how we platform #41

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
SpBills wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Feature/how we platform #41

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b1bc26b
How we do work
SpBills Oct 9, 2023
2387a95
More platforms
SpBills Oct 9, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
52 changes: 12 additions & 40 deletions Processes/work/HowWeWork.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,8 +45,7 @@ Tenant 3: **Speak of the bad before the good**
Now that we know what was good for the team, we can begin planning the next sprint. This is a fairly in-the-weeds process.

1. Assign each story to 2 people
2. Score the stories (Note: this MUST be anonymous and between the two assignees. You can accomplish this by making them hold their hands up with 1-5 for the difficulty of the stories)
3. Make sure everyone knows why they are doing their work
2. Make sure everyone knows why they are doing their work

Tenant 4: **Nothing good happens without at least 2 people**

Expand All @@ -66,8 +65,16 @@ Basecamp contains a lot of the way that execs do work.

The todo list contains two things:

1. The operational board (things that are one-off tasks that do not produce an artifact)
2. The booper board (booper setups!)
1. The operational list (things that are one-off tasks that do not produce an artifact)
2. The booper list (booper setups!)

#### The Icebox

This is where all the unshaped/shaped work goes that we are not ready to do yet.

Sometimes, your project won't be one of the lists in here. In that case, create a new list inside of here for your project.

Otherwise, just add the todo in a *story format*.

#### The Project Board

Expand Down Expand Up @@ -139,39 +146,4 @@ This is timeboxed to a *15 minute* meeting.

Once this is finished, it may be dragged into *done*!

Make sure that you make stories in [Unshaped Work](#unshaped-work) after this meeting that defines the changes that the customer wants.

### GitHub

Github has two purposes.

1. Store the code
2. Provide documentation for developers

The code storage is provided through repositories. That is not important for this document.

#### Documentation for Developers

Documentation for developers is provided using the [Kanban Board](https://github.com/orgs/CreativeSolutionsGroup/projects/9). This is where the [Developer Backlog](https://scrumguides.org/scrum-guide.html#sprint-backlog) exists.

This is a traditional kanban board that goes through all the steps of work for developers. It is *not* a story board. It is a *task* board. It is much lower level than stories. If there is a "director" position on CSG currently, they will likely only work with the [Project Board](#the-project-board) and not this board.

##### Todo

These are tasks that are in the sprint but have yet to be started.

##### In Progress

These are tasks that are currently being worked on by developers.

##### Punt

These are tasks that need to be sent to the next sprint. It is very similar to the [Punt](#punt) of the Project Board.

##### In Review

This is where the technical execs are able to review the work of the developers. Technically, everyone should be able to do reviews, but currently it is relegated to technical execs.

##### Done

These are *closed* issues that are complete.
Make sure that you make stories in [Unshaped Work](#unshaped-work) after this meeting that defines the changes that the customer wants.
41 changes: 41 additions & 0 deletions Processes/work/Platforms.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
# Platforms

Here we document the various platforms that we use. It will be split into two sections. Alongside this split, it will also not be explaining the full extent of the technology. It will link to the documents that do talk about it.

## But first, a note.

Do not *ever* add a personal phone number as 2FA. Please add a FTT member's phone number. If you need to use 2FA for logging into an account, make sure that the FTT member is able to access it primarily. Then, most platforms will allow your personal or Cedarville email to be a tenant of that.

## Basecamp

Basecamp contains everything that we do at CSG from a meta perspective. It contains our work backlog and booper setup backlog. Please check out [this link](/Dev-Tools/basecamp/tool.md).

### HOW TO ACCESS?

To access this, you will be invited by the previous year's execs and receive an email.

## AWS

AWS contains all of the hosting for our many applications. To understand more about specific parts of AWS, please check out [this link](/Dev-Tools/aws/tool.md).

### HOW TO ACCESS?

Ask your exec for access. You usually should not have access to this unless
1. You are designated to be able to manage the deployments
2. You are an exec.

## Cloudflare

Cloudflare contains all of our hosting for serverless workers.

### HOW TO ACCESS?

Ask your exec for access. It is also contained under the Creative Solutions email so you should be able to just log into Cloudflare under that.

## Github

Github *only* hosts our code. We do not do project management in it anymore. We also do pull requests in it. For more information, please check out [this link](/Dev-Tools/github/tool.md).

### HOW TO ACCESS?

Your execs will add you to the GitHub organization. If you are not on, please ask your exec ASAP.