Now that we've mostly decided what our data should look like (see #8), it's time to decide how we will store it. The purpose of this task is to enumerate potential solutions and then create "spike" tasks to investigate.
You might want to reach out to @Zenahr to get his thoughts on his solution involving a CI/CD build step.
Collaborators
This will be owned by the data team: @esu2020 @pandevim @justonsky
Deliverable
For each solution (i.e. AirTable, Google Sheets, raw JSON), create a new GitHub issue for someone to "spike" the feasibility. Those tasks may involve building a prototype, asking mentors who have worked with these technologies in the past, and basically understanding what it would take for us to integration with a given solution.
The result from this will be a series of tasks that read "Spike AirTable as our data store", "Spike Google Sheets as our data store", etc. Each of these tasks should be timeboxed and be assigned to one of you.
Objective
Now that we've mostly decided what our data should look like (see #8), it's time to decide how we will store it. The purpose of this task is to enumerate potential solutions and then create "spike" tasks to investigate.
You might want to reach out to @Zenahr to get his thoughts on his solution involving a CI/CD build step.
Collaborators
This will be owned by the data team: @esu2020 @pandevim @justonsky
Deliverable
For each solution (i.e. AirTable, Google Sheets, raw JSON), create a new GitHub issue for someone to "spike" the feasibility. Those tasks may involve building a prototype, asking mentors who have worked with these technologies in the past, and basically understanding what it would take for us to integration with a given solution.
The result from this will be a series of tasks that read "Spike AirTable as our data store", "Spike Google Sheets as our data store", etc. Each of these tasks should be timeboxed and be assigned to one of you.