mik-laj commented on issue #10085: URL: https://github.com/apache/airflow/issues/10085#issuecomment-667625999
I agree that we can think about using the projects, but the umbrella ticket is still helpfull. This will allow new contributors to become more familiar with the plan. I would like this ticket to be the place a new contributor should start off if they want to work on Airflow 2.0. If we want to organize our project as a kanban, we will have several columns such as Blocked, TODO, WIP, Review in progress, Review approved, Done. This allows you to easily follow the progress as you can see the cards move to the right. However, these cards are chaotic for someone who is unfamiliar with the project. They don't know why something needs to be done and he doesn't know the full context. I would like to point out that even we use a similar document during our work in various projects at Polidea, but we have it in the form of a spreadsheet. We tried to use Github Issues, the Github project, but in the end the spreadsheet turns out to be the most helpful. We can move to the wiki, but I don't see any benefit over using the Github Issues. On the other hand, using Github Issue will allow you to reach a wider audience more easily. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
