Few important points: We already have a very good source of "everything-airflow" : https://github.com/jghoman/awesome-apache-airflow - this is maintained by Jakob Homan - and it contains a list of a lot of resources of Airflow. They are a bit vetted by Jakob who is a member of the community, but it's not really moderated or not seen as the "official source of information" . We certainly do not want to replace it and provide links to 100s of blogs and presentations. We really want to be the "official" source of information for the users (mainly) - not even for community members. So this source should be fairly well moderated. Like we should definitely avoid having a hidden endorsement for anyone's company or product.
There is a reason why we do not have a section on "Airflow-as-a-service" in our official website. Also that's why I thin blogs to (including my own) Polidea blogs should be removed. Airflow official page is really something that should be community-controlled and all the links from there should be somewhat 'community-official'. Unless we designate a special section that will be for "non-community-controlled". If we decide to have it - all the links outside should have "no-follow" attribute set (https://en.wikipedia.org/wiki/Nofollow) and it should be clearly stated for the readers, that those are external sources and that the Apache Airflow Community has no control over and that the use of those external sources is "your own risk". This is very clearly responsibility (including legal responsibility!) on the PMC side (and this is one of the very few things where responsibility is clearly on the PMC members). This is really Brand responsibility: http://www.apache.org/foundation/marks/responsibility.html including Website Branding Responsibility http://www.apache.org/foundation/marks/pmcs.html . That's rather serious and important and this is something I think we will have to agree between PMCs - what external content should be allowed on ur official `airflow.apache.org` page to be sure that we are protecting Apache brand enough. We will keep everyone updated on what will be official approach to that once we come to a conclusion. J
