Weekly Data Engineering Newsletter

The data engineering weekly newsletter started with a mission of reflecting views on the latest developments in the data engineering world. Every week we publish selected blog posts in the newsletters and share thoughts on them. Data Engineering Weekly currently accepts contributions in two forms.

1. Founder story. See the announcement for the founder story.
2. Article contribution.

The founder's story will be published every Wednesday as a separate edition.

1. Write your story with a title and one-pager or add a link to the blog post you already published your story. The markdown format is a preferred format.

2. Add the file under the founder_story folder, and open a PR.

3. You could also point to a blog post you already published, given that the data engineering weekly can republish the content.

It is simple, open a pull request with the article title under the weekly folder. Please read the contributing guidelines before submitting the request.

article:
  author:
    linkedin: "<linkedin URL>"
    name: "<mention company name if it is published in a engineering blog else the author name>"
    twitter: "<twitter handle>"
  link: "<URL to the article>"
  review: "<Optional: Your review about the article>. It is okay if you can just share the links to the articles."
  reviewer:
    linkedin: "<optional: your LinkedIn handle>"
    name: "<optional> if you would like to add your name as a reviewer in the data engineering weekly newsletter"
    twitter: "<optional: your twitter handle>"
  tags: "<comma separate tags about the theme of the article>"

Once the article submitted, the content will be either accepted or rejected for the publication.

On average, we read about 15+ articles every week before selecting a few articles to publish in every edition. We focus more on the quality of the content rather than the quantity of the content. A few guidelines to follow for submitting the articles.

1. No vendor promotional articles. We want to keep the data engineering weekly vendor neutral, genuinely reflecting the exciting development in data engineering.
2. Practice empathy when writing the review snapshot. The author of the article spends tremendous time and effort to write the article. Positive feedback is welcome, but no negative comments/ criticism, please.
3. Data Engineering Weekly can accept or reject any article submission request without any further explanation.
4. The contribution is purely voluntary with no monetary benefit from data engineering weekly publishers.

I'm starting this as an experiment. The contributing guide may not be perfect. We will iterate and improve the contributing guideline as we move along.

Please tag your suggestion @data_weekly on Twitter.