potiuk commented on issue #57356: URL: https://github.com/apache/airflow/issues/57356#issuecomment-4274065491
> [@potiuk](https://github.com/potiuk) perhaps in the future you can ask with more etiquette and follow your own code of conduct. As I already mentioned I'll be opening a new issue as you "recomment" Which particular point of our code of conduct you think I violated? I simply explained why commenting on a closed issue that was opened 5 months ago and has many loosely related examples will not likely lead to your problem being solved. I thought it was helpful comment that expleained how things work here - becasue if someone has expectation that commententig "still seing it" on a closed issue - then I would be happy to re-iterate that no - it's not going to help - for the reasons I explained. You can generally take it as advice and follow (so I am super glad you did). Also another comment so that you are also aware how open-source project work: the better, more precisely and more reproducibly you describe your issue, with little ambiguities and with avoiding "noise" - the bigger chance someone will actually look at it and solve it. Ideally if you could look and solve it yourself and propose a PR that would be better - we have more than 3700 users who contributed - many of them were users like you, who had problems, looked at the open source code, found it and submitted a fix - this is absolutely best for volunteer maintainer if a user does it. Second best if the user describes the issue and provide super clear minimally reproducible POC that the maintainer can run and fix, That significantly increases a chance that somoene will look at it and fix. This is the reality of open-source project. You get it for free, without any guarantees, there is no formal "support" team like you have in corporations where support team are paid. Here you have 3700+ people and the best chance for you to get it solved by one of those people deciding to spend their free time and help you - is to open good descriptive issue with POC or even submitting a PR (and then testing when release candidate is - out we usually tag people when we produce an RC and expect them to test what we propose). That's how things work here. There is no "anger" or bad will or "code of conduct" violation here - it's just a patient explanation how things work here, because often people come to open source project with terribly inflated expectations - so one part of my role which I (this part voluntarily mind you) took on is to explain it to people and set the right expectations. I know it is hard when someone tells you "no, it does not work the way you thought", but - my advise is that you learn from that and follo the way how many thousands people do here. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
