You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Kaxil Naik <ka...@gmail.com> on 2020/01/03 14:36:43 UTC
[DISCUSS] Airflow Website Blog Guidelines
Hey all,
I wanted to raise a point regarding our Blog on the Airflow website.
There is an open PR: https://github.com/apache/airflow-site/pull/231 from
Chandu Kavar to add 2 blog posts based on his nicely written Airflow
testing material.
However, the blog post basically links back to the original content on
medium instead of providing the content on the website itself.
I replied saying we should have the entire content on the website for it to
be meaningful to serve any purpose.
And then I actually checked the currently published blog posts too and
found out that some posts are similar.
The blog post isn't that useful in that case.
So I would like to propose the following guidelines:
- The content should be on the Blog Post itself and not something like "To
Read more visit this website"
- Linking to own and other good blogs/article/docs are fine and encouraged
where it makes sense but not to intentionally drive traffic away from the
Blog Post
Let me know your thoughts.
Regards,
Kaxil
Re: [DISCUSS] Airflow Website Blog Guidelines
Posted by Jarek Potiuk <Ja...@polidea.com>.
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
Re: [DISCUSS] Airflow Website Blog Guidelines
Posted by Austin Bennett <wh...@gmail.com>.
Depends on your aims. @Kaxil "... for it to be meaningful to serve
any purpose." is quite loaded, and *any* seems a bit exaggerated.
There is value in being the go-to content aggregator, and therefore
initials stop, even if whole of content lives elsewhere.
That is different from trying to keep people onsite (or to be the
content source/owner/publisher), which is another valid aim.
Unclear of difference when it comes to search result rankings (not
sure that this would be considered a copy site, for instance) -- if
that is one thing trying to optimize for.
A more fundamental question would be what is trying to get
accomplished through the use of the blogs section. That would help
determine what practices/guidelines should be in place for it.
Ex:
* Drive traffic through search (therefore need to figure out optimizing that)
* Be the known go-to source (as a user I know that lots of
worthwhile/interesting things are linked to somewhere from the airflow
site and blog sections).
* Be sticky: keep people onsite longer.
* Etc
On Fri, Jan 3, 2020 at 7:26 PM Chandu Kavar <cc...@gmail.com> wrote:
>
> I like the idea of tagging for external blog posts. We can set some
> mandatory tags for external blogs, something like "external".
>
> On Sat, 4 Jan 2020, 7:57 am Kamil Breguła, <ka...@polidea.com>
> wrote:
>
> > Hello,
> >
> > Maybe we should allow teaser posts, but with a visible label? New
> > users, who do not know Airflow well, can see these teasers easily and
> > find these valuable content. A website without content will be of
> > little use and will have a low informational character. As a new
> > person, I would like to have easy access to these posts on other sites
> > also. They were more valuable to me than posts describing internal
> > project topics - GSOD, Airflow website launch. The website supports
> > tag mechanism, so it can be easily done.
> >
> > Best regards,
> > Kamil
> >
> > On Sat, Jan 4, 2020 at 12:09 AM Kaxil Naik <ka...@gmail.com> wrote:
> > >
> > > Agree with Jarek.
> > >
> > > On Fri, Jan 3, 2020 at 5:14 PM Jarek Potiuk <Ja...@polidea.com>
> > > wrote:
> > >
> > > > >
> > > > >
> > > > > Is it okay to copy the content from the original source to airflow
> > > > website?
> > > > >
> > > >
> > > > From what I know from our PR/Marketing people - think this practice is
> > > > discouraged and makes search engines demote ranks of the "copy" sites.
> > > > Google highly promotes original content and demotes sites that are
> > copying
> > > > it.
> > > >
> > > > J.
> > > >
> > > >
> > > > > On Fri, Jan 3, 2020 at 11:20 PM Jarek Potiuk <
> > Jarek.Potiuk@polidea.com>
> > > > > wrote:
> > > > >
> > > > > > BTW. I just looked at the blogs - I am also ok with removing the
> > two
> > > > > blogs
> > > > > > that we originally had - they were more to seed the "blogs" than
> > > > > intended
> > > > > > to drive traffic. It would make more sense to remove them so that
> > we
> > > > can
> > > > > > tell the contributors that we prefer original content.
> > > > > >
> > > > > > J
> > > > > >
> > > > > > On Fri, Jan 3, 2020 at 4:13 PM Jarek Potiuk <
> > Jarek.Potiuk@polidea.com>
> > > > > > wrote:
> > > > > >
> > > > > > > +1.
> > > > > > >
> > > > > > > On Fri, Jan 3, 2020 at 3:43 PM Tomasz Urbaszek <
> > turbaszek@apache.org
> > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > >> +1 for publishing whole blog posts on the Airflow website.
> > > > > > >>
> > > > > > >> T.
> > > > > > >>
> > > > > > >> On Fri, Jan 3, 2020 at 3:37 PM Kaxil Naik <ka...@gmail.com>
> > > > > wrote:
> > > > > > >>
> > > > > > >> > Hey all,
> > > > > > >> >
> > > > > > >> > I wanted to raise a point regarding our Blog on the Airflow
> > > > website.
> > > > > > >> >
> > > > > > >> > There is an open PR:
> > > > > https://github.com/apache/airflow-site/pull/231
> > > > > > >> from
> > > > > > >> > Chandu Kavar to add 2 blog posts based on his nicely written
> > > > Airflow
> > > > > > >> > testing material.
> > > > > > >> >
> > > > > > >> > However, the blog post basically links back to the original
> > > > content
> > > > > on
> > > > > > >> > medium instead of providing the content on the website itself.
> > > > > > >> >
> > > > > > >> > I replied saying we should have the entire content on the
> > website
> > > > > for
> > > > > > >> it to
> > > > > > >> > be meaningful to serve any purpose.
> > > > > > >> >
> > > > > > >> > And then I actually checked the currently published blog
> > posts too
> > > > > and
> > > > > > >> > found out that some posts are similar.
> > > > > > >> >
> > > > > > >> > The blog post isn't that useful in that case.
> > > > > > >> >
> > > > > > >> > So I would like to propose the following guidelines:
> > > > > > >> >
> > > > > > >> > - The content should be on the Blog Post itself and not
> > something
> > > > > like
> > > > > > >> "To
> > > > > > >> > Read more visit this website"
> > > > > > >> > - Linking to own and other good blogs/article/docs are fine
> > and
> > > > > > >> encouraged
> > > > > > >> > where it makes sense but not to intentionally drive traffic
> > away
> > > > > from
> > > > > > >> the
> > > > > > >> > Blog Post
> > > > > > >> >
> > > > > > >> > Let me know your thoughts.
> > > > > > >> >
> > > > > > >> > Regards,
> > > > > > >> > Kaxil
> > > > > > >> >
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > > Jarek Potiuk
> > > > > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > > > > > >
> > > > > > > M: +48 660 796 129 <+48660796129>
> > > > > > > [image: Polidea] <https://www.polidea.com/>
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > Jarek Potiuk
> > > > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > > > > >
> > > > > > M: +48 660 796 129 <+48660796129>
> > > > > > [image: Polidea] <https://www.polidea.com/>
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Jarek Potiuk
> > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > > >
> > > > M: +48 660 796 129 <+48660796129>
> > > > [image: Polidea] <https://www.polidea.com/>
> > > >
> >
Re: [DISCUSS] Airflow Website Blog Guidelines
Posted by Chandu Kavar <cc...@gmail.com>.
I like the idea of tagging for external blog posts. We can set some
mandatory tags for external blogs, something like "external".
On Sat, 4 Jan 2020, 7:57 am Kamil Breguła, <ka...@polidea.com>
wrote:
> Hello,
>
> Maybe we should allow teaser posts, but with a visible label? New
> users, who do not know Airflow well, can see these teasers easily and
> find these valuable content. A website without content will be of
> little use and will have a low informational character. As a new
> person, I would like to have easy access to these posts on other sites
> also. They were more valuable to me than posts describing internal
> project topics - GSOD, Airflow website launch. The website supports
> tag mechanism, so it can be easily done.
>
> Best regards,
> Kamil
>
> On Sat, Jan 4, 2020 at 12:09 AM Kaxil Naik <ka...@gmail.com> wrote:
> >
> > Agree with Jarek.
> >
> > On Fri, Jan 3, 2020 at 5:14 PM Jarek Potiuk <Ja...@polidea.com>
> > wrote:
> >
> > > >
> > > >
> > > > Is it okay to copy the content from the original source to airflow
> > > website?
> > > >
> > >
> > > From what I know from our PR/Marketing people - think this practice is
> > > discouraged and makes search engines demote ranks of the "copy" sites.
> > > Google highly promotes original content and demotes sites that are
> copying
> > > it.
> > >
> > > J.
> > >
> > >
> > > > On Fri, Jan 3, 2020 at 11:20 PM Jarek Potiuk <
> Jarek.Potiuk@polidea.com>
> > > > wrote:
> > > >
> > > > > BTW. I just looked at the blogs - I am also ok with removing the
> two
> > > > blogs
> > > > > that we originally had - they were more to seed the "blogs" than
> > > > intended
> > > > > to drive traffic. It would make more sense to remove them so that
> we
> > > can
> > > > > tell the contributors that we prefer original content.
> > > > >
> > > > > J
> > > > >
> > > > > On Fri, Jan 3, 2020 at 4:13 PM Jarek Potiuk <
> Jarek.Potiuk@polidea.com>
> > > > > wrote:
> > > > >
> > > > > > +1.
> > > > > >
> > > > > > On Fri, Jan 3, 2020 at 3:43 PM Tomasz Urbaszek <
> turbaszek@apache.org
> > > >
> > > > > > wrote:
> > > > > >
> > > > > >> +1 for publishing whole blog posts on the Airflow website.
> > > > > >>
> > > > > >> T.
> > > > > >>
> > > > > >> On Fri, Jan 3, 2020 at 3:37 PM Kaxil Naik <ka...@gmail.com>
> > > > wrote:
> > > > > >>
> > > > > >> > Hey all,
> > > > > >> >
> > > > > >> > I wanted to raise a point regarding our Blog on the Airflow
> > > website.
> > > > > >> >
> > > > > >> > There is an open PR:
> > > > https://github.com/apache/airflow-site/pull/231
> > > > > >> from
> > > > > >> > Chandu Kavar to add 2 blog posts based on his nicely written
> > > Airflow
> > > > > >> > testing material.
> > > > > >> >
> > > > > >> > However, the blog post basically links back to the original
> > > content
> > > > on
> > > > > >> > medium instead of providing the content on the website itself.
> > > > > >> >
> > > > > >> > I replied saying we should have the entire content on the
> website
> > > > for
> > > > > >> it to
> > > > > >> > be meaningful to serve any purpose.
> > > > > >> >
> > > > > >> > And then I actually checked the currently published blog
> posts too
> > > > and
> > > > > >> > found out that some posts are similar.
> > > > > >> >
> > > > > >> > The blog post isn't that useful in that case.
> > > > > >> >
> > > > > >> > So I would like to propose the following guidelines:
> > > > > >> >
> > > > > >> > - The content should be on the Blog Post itself and not
> something
> > > > like
> > > > > >> "To
> > > > > >> > Read more visit this website"
> > > > > >> > - Linking to own and other good blogs/article/docs are fine
> and
> > > > > >> encouraged
> > > > > >> > where it makes sense but not to intentionally drive traffic
> away
> > > > from
> > > > > >> the
> > > > > >> > Blog Post
> > > > > >> >
> > > > > >> > Let me know your thoughts.
> > > > > >> >
> > > > > >> > Regards,
> > > > > >> > Kaxil
> > > > > >> >
> > > > > >>
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > Jarek Potiuk
> > > > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > > > > >
> > > > > > M: +48 660 796 129 <+48660796129>
> > > > > > [image: Polidea] <https://www.polidea.com/>
> > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Jarek Potiuk
> > > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > > > >
> > > > > M: +48 660 796 129 <+48660796129>
> > > > > [image: Polidea] <https://www.polidea.com/>
> > > > >
> > > >
> > >
> > >
> > > --
> > >
> > > Jarek Potiuk
> > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > >
> > > M: +48 660 796 129 <+48660796129>
> > > [image: Polidea] <https://www.polidea.com/>
> > >
>
Re: [DISCUSS] Airflow Website Blog Guidelines
Posted by Kamil Breguła <ka...@polidea.com>.
Hello,
Maybe we should allow teaser posts, but with a visible label? New
users, who do not know Airflow well, can see these teasers easily and
find these valuable content. A website without content will be of
little use and will have a low informational character. As a new
person, I would like to have easy access to these posts on other sites
also. They were more valuable to me than posts describing internal
project topics - GSOD, Airflow website launch. The website supports
tag mechanism, so it can be easily done.
Best regards,
Kamil
On Sat, Jan 4, 2020 at 12:09 AM Kaxil Naik <ka...@gmail.com> wrote:
>
> Agree with Jarek.
>
> On Fri, Jan 3, 2020 at 5:14 PM Jarek Potiuk <Ja...@polidea.com>
> wrote:
>
> > >
> > >
> > > Is it okay to copy the content from the original source to airflow
> > website?
> > >
> >
> > From what I know from our PR/Marketing people - think this practice is
> > discouraged and makes search engines demote ranks of the "copy" sites.
> > Google highly promotes original content and demotes sites that are copying
> > it.
> >
> > J.
> >
> >
> > > On Fri, Jan 3, 2020 at 11:20 PM Jarek Potiuk <Ja...@polidea.com>
> > > wrote:
> > >
> > > > BTW. I just looked at the blogs - I am also ok with removing the two
> > > blogs
> > > > that we originally had - they were more to seed the "blogs" than
> > > intended
> > > > to drive traffic. It would make more sense to remove them so that we
> > can
> > > > tell the contributors that we prefer original content.
> > > >
> > > > J
> > > >
> > > > On Fri, Jan 3, 2020 at 4:13 PM Jarek Potiuk <Ja...@polidea.com>
> > > > wrote:
> > > >
> > > > > +1.
> > > > >
> > > > > On Fri, Jan 3, 2020 at 3:43 PM Tomasz Urbaszek <turbaszek@apache.org
> > >
> > > > > wrote:
> > > > >
> > > > >> +1 for publishing whole blog posts on the Airflow website.
> > > > >>
> > > > >> T.
> > > > >>
> > > > >> On Fri, Jan 3, 2020 at 3:37 PM Kaxil Naik <ka...@gmail.com>
> > > wrote:
> > > > >>
> > > > >> > Hey all,
> > > > >> >
> > > > >> > I wanted to raise a point regarding our Blog on the Airflow
> > website.
> > > > >> >
> > > > >> > There is an open PR:
> > > https://github.com/apache/airflow-site/pull/231
> > > > >> from
> > > > >> > Chandu Kavar to add 2 blog posts based on his nicely written
> > Airflow
> > > > >> > testing material.
> > > > >> >
> > > > >> > However, the blog post basically links back to the original
> > content
> > > on
> > > > >> > medium instead of providing the content on the website itself.
> > > > >> >
> > > > >> > I replied saying we should have the entire content on the website
> > > for
> > > > >> it to
> > > > >> > be meaningful to serve any purpose.
> > > > >> >
> > > > >> > And then I actually checked the currently published blog posts too
> > > and
> > > > >> > found out that some posts are similar.
> > > > >> >
> > > > >> > The blog post isn't that useful in that case.
> > > > >> >
> > > > >> > So I would like to propose the following guidelines:
> > > > >> >
> > > > >> > - The content should be on the Blog Post itself and not something
> > > like
> > > > >> "To
> > > > >> > Read more visit this website"
> > > > >> > - Linking to own and other good blogs/article/docs are fine and
> > > > >> encouraged
> > > > >> > where it makes sense but not to intentionally drive traffic away
> > > from
> > > > >> the
> > > > >> > Blog Post
> > > > >> >
> > > > >> > Let me know your thoughts.
> > > > >> >
> > > > >> > Regards,
> > > > >> > Kaxil
> > > > >> >
> > > > >>
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Jarek Potiuk
> > > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > > > >
> > > > > M: +48 660 796 129 <+48660796129>
> > > > > [image: Polidea] <https://www.polidea.com/>
> > > > >
> > > > >
> > > >
> > > > --
> > > >
> > > > Jarek Potiuk
> > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > > >
> > > > M: +48 660 796 129 <+48660796129>
> > > > [image: Polidea] <https://www.polidea.com/>
> > > >
> > >
> >
> >
> > --
> >
> > Jarek Potiuk
> > Polidea <https://www.polidea.com/> | Principal Software Engineer
> >
> > M: +48 660 796 129 <+48660796129>
> > [image: Polidea] <https://www.polidea.com/>
> >
Re: [DISCUSS] Airflow Website Blog Guidelines
Posted by Kaxil Naik <ka...@gmail.com>.
Agree with Jarek.
On Fri, Jan 3, 2020 at 5:14 PM Jarek Potiuk <Ja...@polidea.com>
wrote:
> >
> >
> > Is it okay to copy the content from the original source to airflow
> website?
> >
>
> From what I know from our PR/Marketing people - think this practice is
> discouraged and makes search engines demote ranks of the "copy" sites.
> Google highly promotes original content and demotes sites that are copying
> it.
>
> J.
>
>
> > On Fri, Jan 3, 2020 at 11:20 PM Jarek Potiuk <Ja...@polidea.com>
> > wrote:
> >
> > > BTW. I just looked at the blogs - I am also ok with removing the two
> > blogs
> > > that we originally had - they were more to seed the "blogs" than
> > intended
> > > to drive traffic. It would make more sense to remove them so that we
> can
> > > tell the contributors that we prefer original content.
> > >
> > > J
> > >
> > > On Fri, Jan 3, 2020 at 4:13 PM Jarek Potiuk <Ja...@polidea.com>
> > > wrote:
> > >
> > > > +1.
> > > >
> > > > On Fri, Jan 3, 2020 at 3:43 PM Tomasz Urbaszek <turbaszek@apache.org
> >
> > > > wrote:
> > > >
> > > >> +1 for publishing whole blog posts on the Airflow website.
> > > >>
> > > >> T.
> > > >>
> > > >> On Fri, Jan 3, 2020 at 3:37 PM Kaxil Naik <ka...@gmail.com>
> > wrote:
> > > >>
> > > >> > Hey all,
> > > >> >
> > > >> > I wanted to raise a point regarding our Blog on the Airflow
> website.
> > > >> >
> > > >> > There is an open PR:
> > https://github.com/apache/airflow-site/pull/231
> > > >> from
> > > >> > Chandu Kavar to add 2 blog posts based on his nicely written
> Airflow
> > > >> > testing material.
> > > >> >
> > > >> > However, the blog post basically links back to the original
> content
> > on
> > > >> > medium instead of providing the content on the website itself.
> > > >> >
> > > >> > I replied saying we should have the entire content on the website
> > for
> > > >> it to
> > > >> > be meaningful to serve any purpose.
> > > >> >
> > > >> > And then I actually checked the currently published blog posts too
> > and
> > > >> > found out that some posts are similar.
> > > >> >
> > > >> > The blog post isn't that useful in that case.
> > > >> >
> > > >> > So I would like to propose the following guidelines:
> > > >> >
> > > >> > - The content should be on the Blog Post itself and not something
> > like
> > > >> "To
> > > >> > Read more visit this website"
> > > >> > - Linking to own and other good blogs/article/docs are fine and
> > > >> encouraged
> > > >> > where it makes sense but not to intentionally drive traffic away
> > from
> > > >> the
> > > >> > Blog Post
> > > >> >
> > > >> > Let me know your thoughts.
> > > >> >
> > > >> > Regards,
> > > >> > Kaxil
> > > >> >
> > > >>
> > > >
> > > >
> > > > --
> > > >
> > > > Jarek Potiuk
> > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > > >
> > > > M: +48 660 796 129 <+48660796129>
> > > > [image: Polidea] <https://www.polidea.com/>
> > > >
> > > >
> > >
> > > --
> > >
> > > Jarek Potiuk
> > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > >
> > > M: +48 660 796 129 <+48660796129>
> > > [image: Polidea] <https://www.polidea.com/>
> > >
> >
>
>
> --
>
> Jarek Potiuk
> Polidea <https://www.polidea.com/> | Principal Software Engineer
>
> M: +48 660 796 129 <+48660796129>
> [image: Polidea] <https://www.polidea.com/>
>
Re: [DISCUSS] Airflow Website Blog Guidelines
Posted by Jarek Potiuk <Ja...@polidea.com>.
>
>
> Is it okay to copy the content from the original source to airflow website?
>
From what I know from our PR/Marketing people - think this practice is
discouraged and makes search engines demote ranks of the "copy" sites.
Google highly promotes original content and demotes sites that are copying
it.
J.
> On Fri, Jan 3, 2020 at 11:20 PM Jarek Potiuk <Ja...@polidea.com>
> wrote:
>
> > BTW. I just looked at the blogs - I am also ok with removing the two
> blogs
> > that we originally had - they were more to seed the "blogs" than
> intended
> > to drive traffic. It would make more sense to remove them so that we can
> > tell the contributors that we prefer original content.
> >
> > J
> >
> > On Fri, Jan 3, 2020 at 4:13 PM Jarek Potiuk <Ja...@polidea.com>
> > wrote:
> >
> > > +1.
> > >
> > > On Fri, Jan 3, 2020 at 3:43 PM Tomasz Urbaszek <tu...@apache.org>
> > > wrote:
> > >
> > >> +1 for publishing whole blog posts on the Airflow website.
> > >>
> > >> T.
> > >>
> > >> On Fri, Jan 3, 2020 at 3:37 PM Kaxil Naik <ka...@gmail.com>
> wrote:
> > >>
> > >> > Hey all,
> > >> >
> > >> > I wanted to raise a point regarding our Blog on the Airflow website.
> > >> >
> > >> > There is an open PR:
> https://github.com/apache/airflow-site/pull/231
> > >> from
> > >> > Chandu Kavar to add 2 blog posts based on his nicely written Airflow
> > >> > testing material.
> > >> >
> > >> > However, the blog post basically links back to the original content
> on
> > >> > medium instead of providing the content on the website itself.
> > >> >
> > >> > I replied saying we should have the entire content on the website
> for
> > >> it to
> > >> > be meaningful to serve any purpose.
> > >> >
> > >> > And then I actually checked the currently published blog posts too
> and
> > >> > found out that some posts are similar.
> > >> >
> > >> > The blog post isn't that useful in that case.
> > >> >
> > >> > So I would like to propose the following guidelines:
> > >> >
> > >> > - The content should be on the Blog Post itself and not something
> like
> > >> "To
> > >> > Read more visit this website"
> > >> > - Linking to own and other good blogs/article/docs are fine and
> > >> encouraged
> > >> > where it makes sense but not to intentionally drive traffic away
> from
> > >> the
> > >> > Blog Post
> > >> >
> > >> > Let me know your thoughts.
> > >> >
> > >> > Regards,
> > >> > Kaxil
> > >> >
> > >>
> > >
> > >
> > > --
> > >
> > > Jarek Potiuk
> > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > >
> > > M: +48 660 796 129 <+48660796129>
> > > [image: Polidea] <https://www.polidea.com/>
> > >
> > >
> >
> > --
> >
> > Jarek Potiuk
> > Polidea <https://www.polidea.com/> | Principal Software Engineer
> >
> > M: +48 660 796 129 <+48660796129>
> > [image: Polidea] <https://www.polidea.com/>
> >
>
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
[image: Polidea] <https://www.polidea.com/>
Re: [DISCUSS] Airflow Website Blog Guidelines
Posted by Chandu Kavar <cc...@gmail.com>.
+1.
Is it okay to copy the content from the original source to airflow website?
On Fri, Jan 3, 2020 at 11:20 PM Jarek Potiuk <Ja...@polidea.com>
wrote:
> BTW. I just looked at the blogs - I am also ok with removing the two blogs
> that we originally had - they were more to seed the "blogs" than intended
> to drive traffic. It would make more sense to remove them so that we can
> tell the contributors that we prefer original content.
>
> J
>
> On Fri, Jan 3, 2020 at 4:13 PM Jarek Potiuk <Ja...@polidea.com>
> wrote:
>
> > +1.
> >
> > On Fri, Jan 3, 2020 at 3:43 PM Tomasz Urbaszek <tu...@apache.org>
> > wrote:
> >
> >> +1 for publishing whole blog posts on the Airflow website.
> >>
> >> T.
> >>
> >> On Fri, Jan 3, 2020 at 3:37 PM Kaxil Naik <ka...@gmail.com> wrote:
> >>
> >> > Hey all,
> >> >
> >> > I wanted to raise a point regarding our Blog on the Airflow website.
> >> >
> >> > There is an open PR: https://github.com/apache/airflow-site/pull/231
> >> from
> >> > Chandu Kavar to add 2 blog posts based on his nicely written Airflow
> >> > testing material.
> >> >
> >> > However, the blog post basically links back to the original content on
> >> > medium instead of providing the content on the website itself.
> >> >
> >> > I replied saying we should have the entire content on the website for
> >> it to
> >> > be meaningful to serve any purpose.
> >> >
> >> > And then I actually checked the currently published blog posts too and
> >> > found out that some posts are similar.
> >> >
> >> > The blog post isn't that useful in that case.
> >> >
> >> > So I would like to propose the following guidelines:
> >> >
> >> > - The content should be on the Blog Post itself and not something like
> >> "To
> >> > Read more visit this website"
> >> > - Linking to own and other good blogs/article/docs are fine and
> >> encouraged
> >> > where it makes sense but not to intentionally drive traffic away from
> >> the
> >> > Blog Post
> >> >
> >> > Let me know your thoughts.
> >> >
> >> > Regards,
> >> > Kaxil
> >> >
> >>
> >
> >
> > --
> >
> > Jarek Potiuk
> > Polidea <https://www.polidea.com/> | Principal Software Engineer
> >
> > M: +48 660 796 129 <+48660796129>
> > [image: Polidea] <https://www.polidea.com/>
> >
> >
>
> --
>
> Jarek Potiuk
> Polidea <https://www.polidea.com/> | Principal Software Engineer
>
> M: +48 660 796 129 <+48660796129>
> [image: Polidea] <https://www.polidea.com/>
>
Re: [DISCUSS] Airflow Website Blog Guidelines
Posted by Jarek Potiuk <Ja...@polidea.com>.
BTW. I just looked at the blogs - I am also ok with removing the two blogs
that we originally had - they were more to seed the "blogs" than intended
to drive traffic. It would make more sense to remove them so that we can
tell the contributors that we prefer original content.
J
On Fri, Jan 3, 2020 at 4:13 PM Jarek Potiuk <Ja...@polidea.com>
wrote:
> +1.
>
> On Fri, Jan 3, 2020 at 3:43 PM Tomasz Urbaszek <tu...@apache.org>
> wrote:
>
>> +1 for publishing whole blog posts on the Airflow website.
>>
>> T.
>>
>> On Fri, Jan 3, 2020 at 3:37 PM Kaxil Naik <ka...@gmail.com> wrote:
>>
>> > Hey all,
>> >
>> > I wanted to raise a point regarding our Blog on the Airflow website.
>> >
>> > There is an open PR: https://github.com/apache/airflow-site/pull/231
>> from
>> > Chandu Kavar to add 2 blog posts based on his nicely written Airflow
>> > testing material.
>> >
>> > However, the blog post basically links back to the original content on
>> > medium instead of providing the content on the website itself.
>> >
>> > I replied saying we should have the entire content on the website for
>> it to
>> > be meaningful to serve any purpose.
>> >
>> > And then I actually checked the currently published blog posts too and
>> > found out that some posts are similar.
>> >
>> > The blog post isn't that useful in that case.
>> >
>> > So I would like to propose the following guidelines:
>> >
>> > - The content should be on the Blog Post itself and not something like
>> "To
>> > Read more visit this website"
>> > - Linking to own and other good blogs/article/docs are fine and
>> encouraged
>> > where it makes sense but not to intentionally drive traffic away from
>> the
>> > Blog Post
>> >
>> > Let me know your thoughts.
>> >
>> > Regards,
>> > Kaxil
>> >
>>
>
>
> --
>
> Jarek Potiuk
> Polidea <https://www.polidea.com/> | Principal Software Engineer
>
> M: +48 660 796 129 <+48660796129>
> [image: Polidea] <https://www.polidea.com/>
>
>
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
[image: Polidea] <https://www.polidea.com/>
Re: [DISCUSS] Airflow Website Blog Guidelines
Posted by Jarek Potiuk <Ja...@polidea.com>.
+1.
On Fri, Jan 3, 2020 at 3:43 PM Tomasz Urbaszek <tu...@apache.org> wrote:
> +1 for publishing whole blog posts on the Airflow website.
>
> T.
>
> On Fri, Jan 3, 2020 at 3:37 PM Kaxil Naik <ka...@gmail.com> wrote:
>
> > Hey all,
> >
> > I wanted to raise a point regarding our Blog on the Airflow website.
> >
> > There is an open PR: https://github.com/apache/airflow-site/pull/231
> from
> > Chandu Kavar to add 2 blog posts based on his nicely written Airflow
> > testing material.
> >
> > However, the blog post basically links back to the original content on
> > medium instead of providing the content on the website itself.
> >
> > I replied saying we should have the entire content on the website for it
> to
> > be meaningful to serve any purpose.
> >
> > And then I actually checked the currently published blog posts too and
> > found out that some posts are similar.
> >
> > The blog post isn't that useful in that case.
> >
> > So I would like to propose the following guidelines:
> >
> > - The content should be on the Blog Post itself and not something like
> "To
> > Read more visit this website"
> > - Linking to own and other good blogs/article/docs are fine and
> encouraged
> > where it makes sense but not to intentionally drive traffic away from the
> > Blog Post
> >
> > Let me know your thoughts.
> >
> > Regards,
> > Kaxil
> >
>
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
[image: Polidea] <https://www.polidea.com/>
Re: [DISCUSS] Airflow Website Blog Guidelines
Posted by Tomasz Urbaszek <tu...@apache.org>.
+1 for publishing whole blog posts on the Airflow website.
T.
On Fri, Jan 3, 2020 at 3:37 PM Kaxil Naik <ka...@gmail.com> wrote:
> Hey all,
>
> I wanted to raise a point regarding our Blog on the Airflow website.
>
> There is an open PR: https://github.com/apache/airflow-site/pull/231 from
> Chandu Kavar to add 2 blog posts based on his nicely written Airflow
> testing material.
>
> However, the blog post basically links back to the original content on
> medium instead of providing the content on the website itself.
>
> I replied saying we should have the entire content on the website for it to
> be meaningful to serve any purpose.
>
> And then I actually checked the currently published blog posts too and
> found out that some posts are similar.
>
> The blog post isn't that useful in that case.
>
> So I would like to propose the following guidelines:
>
> - The content should be on the Blog Post itself and not something like "To
> Read more visit this website"
> - Linking to own and other good blogs/article/docs are fine and encouraged
> where it makes sense but not to intentionally drive traffic away from the
> Blog Post
>
> Let me know your thoughts.
>
> Regards,
> Kaxil
>
Re: [DISCUSS] Airflow Website Blog Guidelines
Posted by Ry Walker <ry...@rywalker.com>.
Sure, I’d be happy to review it.
On Mon, Dec 7, 2020 at 1:24 PM Sounak Pradhan <so...@gmail.com> wrote:
> Hey everyone,
>
> I have written a blog about KubernetesPodOperator on Airflow and thought
> it would be nice to publish it on the Airflow official blogs site, is that
> possible? Should I just go ahead and create a PR?
>
> Regards,
> Sounak
>
> On 2020/01/03 14:36:43, Kaxil Naik <ka...@gmail.com> wrote:
> > Hey all,
> >
> > I wanted to raise a point regarding our Blog on the Airflow website.
> >
> > There is an open PR: https://github.com/apache/airflow-site/pull/231
> from
> > Chandu Kavar to add 2 blog posts based on his nicely written Airflow
> > testing material.
> >
> > However, the blog post basically links back to the original content on
> > medium instead of providing the content on the website itself.
> >
> > I replied saying we should have the entire content on the website for it
> to
> > be meaningful to serve any purpose.
> >
> > And then I actually checked the currently published blog posts too and
> > found out that some posts are similar.
> >
> > The blog post isn't that useful in that case.
> >
> > So I would like to propose the following guidelines:
> >
> > - The content should be on the Blog Post itself and not something like
> "To
> > Read more visit this website"
> > - Linking to own and other good blogs/article/docs are fine and
> encouraged
> > where it makes sense but not to intentionally drive traffic away from the
> > Blog Post
> >
> > Let me know your thoughts.
> >
> > Regards,
> > Kaxil
> >
>
--
Sent from Gmail Mobile
Re: [DISCUSS] Airflow Website Blog Guidelines
Posted by Sounak Pradhan <so...@gmail.com>.
Hey everyone,
I have written a blog about KubernetesPodOperator on Airflow and thought it would be nice to publish it on the Airflow official blogs site, is that possible? Should I just go ahead and create a PR?
Regards,
Sounak
On 2020/01/03 14:36:43, Kaxil Naik <ka...@gmail.com> wrote:
> Hey all,
>
> I wanted to raise a point regarding our Blog on the Airflow website.
>
> There is an open PR: https://github.com/apache/airflow-site/pull/231 from
> Chandu Kavar to add 2 blog posts based on his nicely written Airflow
> testing material.
>
> However, the blog post basically links back to the original content on
> medium instead of providing the content on the website itself.
>
> I replied saying we should have the entire content on the website for it to
> be meaningful to serve any purpose.
>
> And then I actually checked the currently published blog posts too and
> found out that some posts are similar.
>
> The blog post isn't that useful in that case.
>
> So I would like to propose the following guidelines:
>
> - The content should be on the Blog Post itself and not something like "To
> Read more visit this website"
> - Linking to own and other good blogs/article/docs are fine and encouraged
> where it makes sense but not to intentionally drive traffic away from the
> Blog Post
>
> Let me know your thoughts.
>
> Regards,
> Kaxil
>