Document the Development Process (gitHub)

[jjeroch]

Merve will lead the ticket; Julia and Evelyn to support

Summary
Documenting Team Methods for Handling Tickets and Ticket Labels; etc......
Reason: moved from Jira to GitHub and process have changed ++ open source needs a place to follow the process/toDos!

Description:
task is to document the team's methods for handling tickets and ticket labels. This documentation will serve as a reference for the team members as well as the open source community/new contributors and ensure consistency in the ticket management process. Please follow the guidelines below while creating the document:

1. Ticket Handling Methods:

   • Describe the process of creating, assigning, and closing tickets.
   • Explain how to prioritize and categorize tickets based on urgency and impact. (And who does what)
   • Outline the steps for updating ticket status and communicating progress.

2. Ticket Labels:

   • Define the different labels used for categorizing tickets (e.g., bug, feature, enhancement, technical debt).
   • Explain the purpose and usage of each label. (and where to find them)
   • Provide examples and guidelines for applying labels appropriately.

3. Ticket Management Best Practices:

   • Share best practices for effective ticket management, such as:
     • Clear and concise ticket descriptions.
     • Assigning tickets to the appropriate team members.
     • Regularly updating ticket status and progress.
     • Collaborating and communicating within the ticketing system.

4. Documentation Format: => lets align on the correct format

   • Create a well-structured document using markdown or any other suitable format.
   • Include relevant examples, screenshots, or diagrams to illustrate concepts if necessary.
   • Ensure the document is easily accessible and up-to-date for all stakeholders.

[msinamci]

You can find the docu under project details

As README for the project portal

I add also a short description for the project.