Hi all, Paola here from Astronomer. I've been working at Astro since our early days in both Customer and Product-centric roles and have of course been closely following all-things Airflow for a long time.
I happened to read this conversation around GH Issue management and figure I can step up to volunteer as someone familiar with the project + Product Ops principles, if that'd be helpful. I could always start by: - Cleaning up/commenting on duplicate issues (or close given the right permissions) - Commenting on stale issues and investigate whether they're still a problem or already addressed - Asking questions as needed if issues need clarification or additional scoping If this would be helpful, I'm more than happy to get involved and pick at these over time. It'll likely be a journey that never ends, but I think a compelling need to keep the community momentum going. Let me know - and great to meet you all. Cheers, Paola On 2020/09/10 11:56:22, Tomasz Urbaszek <[email protected]> wrote: > Hi all, > > Currently, we have about 582 open issues on Github. The oldest opened > in March. Do you think we should consider using stale bot as we do for > PRs? > > I don't think that issue that is open since March is "so important" to > keep it still open. This would also automate the process of verifying > the issue (the author will be notified and asked for an update). If > the issue is something that we want to keep open we should be able to > use the "pinned" label. > > Other projects use it and I don't see anything wrong with it. I would > say that 30d is a good period for keeping an issue open. > > What do you think? > > Bests, > Tomek >
