Establish Project Management

[AksonovSergei]

Goals:

1. Keep Track of Project State and Progress
2. Make Teamwork Clear and Smooth
3. Keep Documentation Useful and Up to Date

Ideas for tasks:

• Consider using a single repository for all tasks. What are the advantages and disadvantages?
• Define common GitHub project/organization attributes. Minimal list: GitHub Community Profile
• Define the process for joining the project.
• Define the communication process (e.g., regular meetings, discussions, etc.).
• Define the issue workflow and issue types.
• Define the branch strategy.
• Define rules for commits and pull requests (PRs).
• Define rules for code style and static code analysis.
• Define rules for testing and coverage.

[AksonovSergei]

Hi @ktryna,
Let's use this task as entry point.

[AksonovSergei]

Hi @ktryna
How's it going?
Did you have a chance to get overview of this project?
If you already have some ideas or have questions - let's discuss in this task.

[ktryna]

Hello @AksonovSergei
Currently, I am working on the Work Breakdown Structure. I am preparing two options: a shorter one and a more detailed one. I think that these documents might help participants understand the flow better.
Additionally, I have been thinking about the GitHub Project. I came up with some ideas, but I am not sure whether they are good ones.
I propose having five columns. Also, as we have different repos, I created a workflow that helps to pull all open issues and PRs into our backlog. Now, I am considering adding labels or custom fields. I suggest adding a label with the department name, as it will make orientation easier. I want to automate this process, but, for now, I do not know how to do it.

[AksonovSergei]

Would it be possible to have a short demo during this Wednesday's meeting?

[ktryna]

I suppose so.

Also, I would like to create a register of team members with their contact information, positions, and departments. I can create a template for Wednesday.