Dev Processes

Where We Are

Our team has established:

• A working GitHub workflow (issues → branches → PR → dev → main)
• Documentation structure (README, docs/, Wiki, GitHub Pages)
• Early UI sketches and core feature list

• Our team is in the planning and setup stage, defining our product goals, roles, and collaboration methods before starting development.
  
• We aim to build a functional and well-documented Job Tracker App that helps users organize and track job applications efficiently, following an agile, sprint-based workflow.

Where We Are Going

Over the next sprints, our goals are:

• Finish core CRUD features (applications, statuses, dates, company info).
• Add authentication (JWT-based login + protected routes).
• Implement role-based authorization (user vs admin).
• Build the front-end SPA interface.
• Deploy to Render (staging) and Google Cloud (production).
• Extend infrastructure (email reminders using Nodemailer).
• Finalize API documentation and system design.

Team Rules and Collaboration

• Will meet minimum twice a week in current class time to work together and talk about project.
• We will communicate using text messaging and discord to work outside of class.
• Each member takes ownership of specific areas such as frontend, backend, database, and documentation, while all members contribute to testing and code reviews.

Conflict Resolution & Accountability

• We handle disagreements through open discussion and majority rule. All major decisions are documented in issues or meeting notes to keep the process transparent and accountable.

GitHub Settings

To maintain code quality and prevent accidental breakage:

✔️ Protected main Branch

• Direct pushes disabled
• PRs required
• Review required
  

✔️ Required Code Review

• All PRs must be reviewed before merging.
• No self-approvals.
• Encourages collaboration and shared knowledge.
  

✔️ Separation of Environments

• dev → staging app on Render
• main → production app on Google Cloud