Discussion -- GitHub Project Management

[BellJrDev]

https://docs.github.com/en/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects

· GitHub Projects Youtube Link

"Check tutorial on GitHub project management and the YouTube links regarding it in the Resources section above.

Analyze the following project board - https://github.com/apache/airflow/projects/9

Go through issues on the above board and check issues at different stages of completion. Go through their description and list 2 issues which are in Done state and follow the below conditions:
· An issue that has followed the right sequence to completion.
· An issue that has a difficulty

Explain why one of the above sequences looks good and one has a difficulty. Discuss below, the difficulty and how the sequence can be improved. "

IDK add your response to the directions in this issue thread. We will figure out how to submit these next week. Probably either (A) gradescope will let us copy-paste our responses individually. Or (B) I'll be able to just paste them all into the submission doc and indicate who said what.

[BellJrDev]

[Had a Difficulty] -- Build out custom Table components #15018
apache/airflow#15018
The problem with this issue is that it never had a helpful description that sufficiently conveyed its scope and purpose. Based on explanations from the assigned dev, this problem stemmed from a misuse of the project management features provided by GitHub; something that should have been a note was added as an active issue without context.
The associated task should have been documented elsewhere (possibly as note) until appropriate scoping was done, so that when it was time to create an issue, all of the necessary information would've been published and available to anyone looking to contribute.

[Proper Sequence] -- New Tree View #18675
apache/airflow#18675
The sequence that this issue followed to completion is more desirable. Right off the bat, detail was provided about the purpose and scope of the problem. Then as development continued, reviewers considered the progress and direction and made different fine tuning efforts to help the dev build the ideal solution. These efforts were communicated as comments on the original issue. The dev took in the feedback that was provided and made changes accordingly. Finally, the issue passed final reviews and was merged successfully.

[j-leidy]

[Had a Difficulty] -- Create a new gantt chart in React #19940
apache/airflow#19940
This issue does not follow the complete flow and it moves back and forth a lot.
This issue follows: To Do -> To Scope -> To Do -> To Scope -> To Do -> To Scope -> To Do -> In Progress -> Done
This to me shows that there may have been a scoping difficulty occurring with this issue. The team may have had trouble deciding on pointing or if it was low priority they failed to get to it in sprint-planning. Also the review state was skipped entirely.

[Proper Sequence ] -- Add routing + scaffolding of views #14802
apache/airflow#14802
This issue follows: Next Up -> Needs Scoping -> In Progress -> In Review -> Done
Since Next up and Needs Scoping (maybe now To Scope?) do not exist on this board I am inferring that this was the board order before reduction to the current board. If the ordering of the board back in 2021 was this, this issue follows the proper path. This to me does look like a good flow though however Next Up and Needs Scoping could be swapped. I’m unsure about that. If the flow is indeed in the order noted, it transitions between every state on the board in order making it a good flow.

[jp1779]

[Had a Difficulty] -- Add REST API auth flow for the new UI #15042
apache/airflow#15042

This issue had some difficulties which led to it not being completed (at least in this #). The sequence to completion was not necessarily incorrect since everything was constantly being updated and reviewed. However, there were difficulties with building and "failed jobs matching" which led to the issue going stale and being closed without being completed. Frequent incremental testing and a few more reviews might have helped locate bugs earlier/faster.

[Proper Sequence] -- Migrate DAG Code page to Grid Details #29858
apache/airflow#29858

This issue followed the right sequence to completion.

1. The author of the issue commented three tasks that would lead to the issue being rectified. He then added labels to the issue that helped specify it as a UI/UX issue for frontend developers.
2. The person who offered to solve the issue asked questions to make sure they are on the right track. Once the assigned person finished the tasks, they mentioned the issue so the author could review it.
3. The author then merged the results and marked the "in progress" issue as "done" a few days later.

The proper flow of this issue led to it being completed in a quick and efficient manner. It went from To do -> In progress -> Done. A review could have been performed before marking the issue as done, but that probably occurred in the few days following the "in progress".

[anbates]

[Had a Difficulty] – Improve JS Build File Sizes #29854
apache/airflow#29854
The problem with this issue is that it became stale and was eventually closed due to inactivity. Despite being identified as a bug and receiving a useful suggestion (using Webpack Bundle Analyzer), there was no follow-up or engagement from the team. This lack of activity led to GitHub automatically marking the issue as stale and closed.

The associated task should have been actively monitored and updated regularly. Assigning a team member to follow up on the issue and ensure continuous progress could have prevented it from becoming stale and ultimately unresolved.

[Proper Sequence] – Current User Permission Validation #14805
apache/airflow#14805
This issue followed the correct sequence to completion. Ryan Hamilton created it, and was linked to the AIP-38: Modern Web Application project. The issue was tagged appropriately with relevant labels such as API and UI.

Activity:

• Initial Comment: bbovenzi provided a clear plan on how the API should handle user permissions on login.

• Progress: The issue was actively discussed and suggestions were made to improve the implementation.

• Resolution: jscheffl reviewed the issue, and confirmed that it was either fixed or no longer relevant, leading to its closure.

The issue had a clear objective and was well-documented.
Contributors actively engaged in discussions and provided valuable input.
The issue was tracked and managed effectively, ensuring it followed the correct sequence from creation to closure.

[TimCarpenter4250]

[Had A Difficulty] - Improve mapped task instances auto-refresh #29855
apache/airflow#29855
This issue's problem is that no updates were ever provided. After w year of inactivity on the issue, github-bot stated that it would be closed automatically if no updates were provided. A month later, the issue was closed.
This issue should have been receiving updates as it was worked on. If it was decided not to work on this issue, then it should have been closed manually.

[Proper Sequence] - Current user permission validation #14805
apache/airflow#14805
This issue did a much better job of following the correct sequence. It was created, given labels, and was linked to AIP-38. A suggestion was given, progress updates were given, and once it was complete the issue was marked as closed. This issue had much more engagement than the other and was maintained properly.

[bkanter-purdue]

[Issue] - Current user permission validation
This one was opened and closed without any real work done on it. It was also opened without a description, and a description had to be added by another user. Another contributor mentioned the issue, then it was finally tagged with a "task" label before one of the contributors just closed it.

[Proper] - Show average dag run duration
This one was the opposite of the issue. It was properly implemented. There was discussion. tags, and there was even a "bonus" feature that can be discussed. It was also tagged at the time it was created, and included an actual description. Goes from discussion, to in progress, to testing, to implemented/closed in a nice order.

[BellJrDev]

Combined into a document for submission.