I've seen it in other open source communities where someone tries to
maintain a somewhat detailed summary newsletter of what's going on with the
project, but weekly is a fairly brutal cadence, and it doesn't usually last
for long. In a past life (for the Meteor.js community), my team built a
tool where people could submit, discuss, and vote on content
newsletter-worthy content - and we automated emailing a summary of that
weekly, which crowdsourced the problem of collecting/sorting content.

Now if we would consider a monthly cadence, I have an idea... We (the
Airflow Summit organizers) are working on a plan to produce monthly online
meetups, and along with that, a high-quality monthly Airflow-related email
newsletter. We're currently working on a first draft plan for this, and
lining up resources to make this happen, including a budget for tools and
production.

We could merge your idea, Karolina, into this newsletter, by including a
section which could highlight the good work that is being done, as well as
highlight opportunities for community devs to plug in — which will increase
the value of this newsletter.

Thoughts?

-Ry


On Wed, Sep 9, 2020 at 8:07 AM Tomasz Urbaszek <[email protected]> wrote:

> I think it's a really good idea!
>
> Few points / ideas:
>
> 1. What tool can we use and if paid who will cover it? Is it possible
> to create new mailing list like `[email protected]` that can be
> used for a newsletter? EDIT: devlist don't support html right?
>
> 2. Who should be responsible for preparing it? We will at least need a
> nice template but how will care for the content? Can we automate
> something?
>
> 3. Let's have a "PR of the month" section :D
>
> Tomek
>
>
> On Wed, Sep 9, 2020 at 1:57 PM Jarek Potiuk <[email protected]>
> wrote:
> >
> > Strong +1.
> >
> > I reviewed and cleaned-up my inbox yesterday (and I woke up this morning
> to
> > 50+ new emails - surely some of them are for PRs and other things I am
> > engaged with, but I am working on Airflow pretty much full time (ir
> > sometimes I think 150% ;), but I only imagine how people must feel if
> this
> > is just side-job for them.
> >
> > And I think if it will be nicely formatted (similar to the Superset
> > newsletter for those who follow it) and "stand out", that might be rather
> > useful to catch up. And it should not be that difficult - to get the
> > content, I think this is just a matter of having a place where anyone
> from
> > the community will be able to add their "important events", a little bit
> of
> > nagging in slack and remind people to submit their "news" and someone who
> > can nicely arrange and redact this.
> >
> > And with 2.0 approaching and our work on it accelerating I think we
> > will have enough content for weekly newsletters.
> >
> > J
> >
> >
> > On Wed, Sep 9, 2020 at 12:26 AM Karolina Rosół <
> [email protected]>
> > wrote:
> >
> > > Hi guys,
> > >
> > > Past few days I was wondering if it's a good idea to have a sort of
> summary
> > > of the subjects that are being discussed among the community.
> > > It could be weekly/bi-weekly/monthly "release" but with the summary of
> the
> > > subjects that are hot within the Apache Airflow community atm.
> > >
> > > Why would the community need a summary like this?
> > >
> > >    1. Community is getting bigger and the number of the
> discussions/votings
> > >    & other things will grow;
> > >    2. Sometimes the number of emails is simply too big to handle on a
> daily
> > >    basis;
> > >    3. Not everyone who wants to contribute will follow the devlist so
> > >    often;
> > >    4. Also, it is a great way of learning on a high level what the
> > >    community is all about and maybe would help new contributors decide
> on
> > > what
> > >    matters to invest their time? Plus for people who are managers e.g.
> and
> > >    don't understand how devlist works, they can have a sort of cheat
> sheet
> > > and
> > >    be more supportive for open source initiatives within various
> companies'
> > >    teams.
> > >    5. There are a couple of categories in the email subjects currently.
> > >    However, I imagine such newsletter to be more precise yet in a
> "bullet
> > >    point" form i.e,
> > >       - Category: Operators
> > >          - Current discussions: KubernetesPodOperator [ERROR]
> > >       - Category: Announcements
> > >          - Apache Airflow version 1.10.12 has been released!
> > >
> > > To sum up, I'm not sure about the frequency of sending such a
> newsletter.
> > > In my opinion a weekly basis is the best to be able to go through all
> of
> > > the emails and then prepare a summary.
> > >
> > > Let me know what you guys think and if something like that sounds
> useful at
> > > all.
> > >
> > >
> > > Karolina Rosół
> > > Polidea <https://www.polidea.com/> | Project Manager
> > >
> > > M: +48 606 630 236 <+48606630236>
> > > E: [email protected]
> > > [image: Polidea] <https://www.polidea.com/>
> > >
> > > Check out our projects! <https://www.polidea.com/our-work>
> > > [image: Github] <https://github.com/Polidea> [image: Facebook]
> > > <https://www.facebook.com/Polidea.Software> [image: Twitter]
> > > <https://twitter.com/polidea> [image: Linkedin]
> > > <https://www.linkedin.com/company/polidea> [image: Instagram]
> > > <https://instagram.com/polidea> [image: Behance]
> > > <https://www.behance.net/polidea> [image: dribbble]
> > > <https://dribbble.com/polideadesign>
> > >
> >
> >
> > --
> >
> > Jarek Potiuk
> > Polidea <https://www.polidea.com/> | Principal Software Engineer
> >
> > M: +48 660 796 129 <+48660796129>
> > [image: Polidea] <https://www.polidea.com/>
>
>
>
> --
>
> Tomasz Urbaszek
> Polidea | Software Engineer
>
> M: +48 505 628 493
> E: [email protected]
>
> Unique Tech
> Check out our projects!
>

Reply via email to