Skip to content
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.

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

ER: Wins randomizer content management #4282

Open
1 of 5 tasks
ExperimentsInHonesty opened this issue Mar 24, 2023 · 2 comments
Open
1 of 5 tasks

ER: Wins randomizer content management #4282

ExperimentsInHonesty opened this issue Mar 24, 2023 · 2 comments
Assignees
Labels
Added to dev/pm agenda Complexity: Large Dependency An issue is blocking the completion or starting of another issue ER Emergent Request P-Feature: About Us https://www.hackforla.org/about/ P-Feature: Home page https://www.hackforla.org/ role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 2pt Can be done in 7-12 hours
Milestone

Comments

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Mar 24, 2023

Dependency

Emergent Requirement - Problem

We need a way to

  • know when we need specific practice area wins cards for the randomizer
  • see at a glance which wins are in the randomizer (per practice area)
  • keep track of which wins have been in the randomizer (in the past)

Issue you discovered this emergent requirement in

Date discovered

2023-03-24

Did you have to do something temporarily

  • YES
  • NO

Who was involved

@ExperimentsInHonesty

What happens if this is not addressed

We are likely to end up with too many of one practice area in the randomizer or a super manual process for auditing that. And no plan for how to know what the past states were, etc.

Resources

[wins spreadsheet]

Recommended Action Items

  • Make a new issue
  • Discuss with team
  • Let a Team Lead know

Potential solutions [draft]

Categories

  • Community Management (we call it admin but we should move to calling it Community Management which is industry standard)
  • Content
  • Data
  • Design
  • Engineering
  • Dev Ops
  • PM (Project and Product)
  • Research
  • SEO/Marketing
  • Fundraising
@ExperimentsInHonesty ExperimentsInHonesty added role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers Complexity: Large P-Feature: About Us https://www.hackforla.org/about/ P-Feature: Home page https://www.hackforla.org/ size: 2pt Can be done in 7-12 hours labels Mar 24, 2023
@ExperimentsInHonesty ExperimentsInHonesty added this to the 05. Know HFLA milestone Mar 24, 2023
@ExperimentsInHonesty ExperimentsInHonesty added the Dependency An issue is blocking the completion or starting of another issue label Mar 24, 2023
@roslynwythe roslynwythe self-assigned this Apr 2, 2023
@github-actions

This comment was marked as outdated.

@kimberlytanyh kimberlytanyh added the ER Emergent Request label Sep 10, 2023
@roslynwythe
Copy link
Member

roslynwythe commented Dec 14, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Added to dev/pm agenda Complexity: Large Dependency An issue is blocking the completion or starting of another issue ER Emergent Request P-Feature: About Us https://www.hackforla.org/about/ P-Feature: Home page https://www.hackforla.org/ role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 2pt Can be done in 7-12 hours
Projects
Development

No branches or pull requests

3 participants