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

311-Data Dev: v3 and v4 Objectives #1864

Closed
Tracked by #1862
traycn opened this issue Nov 21, 2024 · 3 comments
Closed
Tracked by #1862

311-Data Dev: v3 and v4 Objectives #1864

traycn opened this issue Nov 21, 2024 · 3 comments
Labels
Complexity: Missing This ticket needs a complexity (good first issue, small, medium, or large) draft Feature: Documentation Improvements or additions to documentation Role: Backend Related to API or other server-side work Role: Data Science Data management, loading, or analysis Role: DevOps infrastructure, CI or related work Role: Frontend React front end work size: 8pt Can be done in 31-48 hours

Comments

@traycn
Copy link
Member

traycn commented Nov 21, 2024

Dependency:

Prioritizing pre-launch tasks before outlining objectives. See comment.

Overview

We need to define what are the purpose, features, and requirements for 311-Data v3 and 311-Data v4, defining the progressive iterations of the application.

Action Items

311-data.v3

  • TODO: List Pre-launch action items
    --

311-data.v4

  • TODO: __further discussion

Resources/Instructions

REPLACE THIS TEXT -If there is a website which has documentation that helps with this issue provide the link(s) here.

@traycn traycn self-assigned this Nov 21, 2024
@traycn traycn added size: 8pt Can be done in 31-48 hours Role: Frontend React front end work Role: Backend Related to API or other server-side work Role: Data Science Data management, loading, or analysis Role: DevOps infrastructure, CI or related work and removed size: Missing Role: Missing labels Nov 21, 2024
@github-project-automation github-project-automation bot moved this to New Issue Approval in P: 311: Project Board Nov 21, 2024
@traycn traycn added the draft label Nov 22, 2024
@traycn traycn changed the title 311-Data Dev: Quaterly Goals 2025 311-Data Dev: v3 and v4 Objectives Nov 23, 2024
@ryanfchase
Copy link
Member

@traycn Would this be a good ticket to outline plans for upgrade to Material UI? Can you drop some resources for me to look at and I can potentially create some dev-research tickets?

@ryanfchase ryanfchase added the ready for dev lead ready for developer lead to review the issue label Jan 22, 2025
@ryanfchase ryanfchase removed their assignment Jan 22, 2025
@traycn traycn added Feature: Documentation Improvements or additions to documentation and removed Feature: Missing Milestone: Missing draft labels Jan 27, 2025
@traycn traycn added this to the 03 - Project Management milestone Jan 27, 2025
@traycn traycn added the Dependency An issue that includes dependencies label Jan 27, 2025
@traycn traycn moved this from New Issue Approval to Icebox (on hold) in P: 311: Project Board Jan 27, 2025
@traycn traycn removed the Dependency An issue that includes dependencies label Jan 30, 2025
@ryanfchase
Copy link
Member

I'm going to kick this back to New Issue Approval. The dependency is prioritizing pre-launch tasks, but that is not specific enough to be considered a blocker. If you are needing input from the team to resolve this team, please add it to the general meeting agenda and/or the dev meeting agenda.

@ryanfchase ryanfchase moved this from Icebox (on hold) to New Issue Approval in P: 311: Project Board Feb 5, 2025
@ryanfchase ryanfchase added draft Complexity: Missing This ticket needs a complexity (good first issue, small, medium, or large) and removed ready for dev lead ready for developer lead to review the issue labels Feb 5, 2025
@ExperimentsInHonesty ExperimentsInHonesty added the ready for dev lead ready for developer lead to review the issue label Feb 7, 2025
@ryanfchase
Copy link
Member

Closing as not planned -- the roadmap is better outlined by our project milestones.

@ryanfchase ryanfchase closed this as not planned Won't fix, can't repro, duplicate, stale Feb 12, 2025
@github-project-automation github-project-automation bot moved this from New Issue Approval to Done (without merge) in P: 311: Project Board Feb 12, 2025
@ryanfchase ryanfchase removed the ready for dev lead ready for developer lead to review the issue label Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Missing This ticket needs a complexity (good first issue, small, medium, or large) draft Feature: Documentation Improvements or additions to documentation Role: Backend Related to API or other server-side work Role: Data Science Data management, loading, or analysis Role: DevOps infrastructure, CI or related work Role: Frontend React front end work size: 8pt Can be done in 31-48 hours
Projects
Status: Done (without merge)
Development

No branches or pull requests

4 participants