potiuk commented on issue #27476: URL: https://github.com/apache/airflow/issues/27476#issuecomment-1306078261
@alexakra - absolutely, feel free to add those docs. That would be great help for people like you in the future. This is a good idea - now that you got all the explanation, you are completely free to make a PR with such documentation improvements. Airlfow is created by more than 2200 contributors - mostly people like you who wanted to do something and got helped by maintainers and decided to contribute back what they learned in exchange for the free software they got for absolutely free and help they got absolutely for free. And will all the discussion and explanations you just got, you are likely the best person in the world to add such documentation - simply because it will be easy for you to write it in the way that will be easy to grasp by people like you - people like maintainers have far too many assumptions in their head to write such documentation in the way that will be good for the users. On the other hand you seem to know already what kind of documentation we miss on it. And it's rather easy to add a new documentation - it's almost as easy as writing comments or posting issues. Just go to the page where you want to add docs and click "suggest a change on this page" button - and you will get Pull request wher you will get the pge to edit and you can use GitHub UI to write the docs - literally the same UI you used for posting the issue and teh whole discussion above. I willl be super happy to review and guide you while doing such documentation. Regarding the plugins and failure - I also heartily welcome you to make PR for that - that is more involved, unlike the documentation it requires more experience and writing tests, but if you feel like editing the chart and adding new options - it is great opportunity that you test it in your local copy (charts can be very easily modifiable and once you get it working you can contributre the PR back. That would be very cool contribution. This is also the fastest way to get it implemented. Alternatively - you can create feature requests for those. I can mark them as "good first issue" - then there is a chance someone will pick it up and implement it. But there is very litle influence on that, someone must simply pick an interest and implementt it and we as maintainers are happy to help with reviewig and merging. Just wanted to let you know that this is how open-source works (just in case you are not aware). -- 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]
