Plan the project using milestones and issues

[akira25]

For the Wizard GSoC project, there are several subtasks that need to be done. Many of them, you already outlined in your application for the project.

Please transform your proposed timeline into Issues and Milestones:

Issues are a good way, for organising information on a certain feature or bug. They are mostly a valuable resource for tracking, how a topic evolved in the project and in which order something happend.

Milestones are a way to connect Issues with a due-date. Thus you can keep track of which tasks should be fulfilled until which point in time.

Assigned to @gabrielportas, once he accepted the invitation to the repo.

[Noki]

The way you used tags and issues is kind of odd. Tags are usually used to categorize task e.g. by component (frontend, backend, documentation) or type (bug, feature). Issues should be organized into projects and milestones where milestones represent the greater timeline and keep track of the progress of different phases of a project and the project itself gives a nice swimlane board to track the current todo, progress and review states for all issues of the project.

The issues you created so far are really sparse and not really issues at all, in my opinion they are mostly milestones and you should create them as those and in the order of how they depend on each other. You should have multiple milestones for the first and second half of GSoC, I suggest to create them like this:

• Create a Project planing
• Define UI Structure and Functionality
• Deploy UI and Backend Locally
• Conduct Extensive Testing
• ...
• Mid-term Evaluation
• ...
• Detailed Documentation
• ...

In addition please create a single project (e.g. named GSoC 2024) so we get swimlanes for tracking the actual issues.

Regarding the issues for the milestones you should create smaller issues to achieve the goal over time and probably also use checklists within the issues e.g.:

• Define UI Structure and Functionality:
  • Review existing mockups and create frontend tasks for next phase
  • Review existing mockups and create backend tasks for next phase
• Create Frontend and Backend
  • Create dummy wizard page
  • Add fields to wizard page
    • ...
    • ...
    • ...

You can have a look at https://github.com/freifunk-berlin/berlin.freifunk.net/milestones?direction=asc&sort=title&state=open to get an idea of how this could look like.

I suggest you familize yourself with how issues, projects and milestones are ment to work together at Github, there a plenty of good YouTube videos.

For me this planning task is not done and therefore I reopened it.

Best regards Tobias