Thank you - I will make sure to add a bullet point to the next draft.
On Tue, May 3, 2022, at 12:38, Jarek Potiuk wrote:
> And re: Christian - privacy policy is important :). We can even say that
> some PMCs already converted to Matomo and we wait for others to catch up
> (peer-pressure :D).
> J.
Agree. Makes perfect sense Bertrand. The reason for members-notify@ is very
clearly stated in the minutes and it's not that :).
J.
On Wed, May 4, 2022 at 10:26 AM Bertrand Delacretaz
wrote:
> -Hi,
>
> Le mar. 3 mai 2022 à 19:31, Craig Russell a écrit :
> > I could not find where we decided wh
-Hi,
Le mar. 3 mai 2022 à 19:31, Craig Russell a écrit :
> I could not find where we decided whether to use members@ or
members-notify@ but I approved it.
> If anyone objects to the mail list, we can have that discussion for next
time
I do object to using members-notify@ for those news, as
On Tue, 2022-05-03 at 14:20 -0500, Josh Fischer wrote:
> Yes, I will take point for the June newsletter.
Please start a new thread for each month's newsletter. This one is
getting pretty unweildy to search through. :)
Thanks!
--Rich
>
> On Tue, May 3, 2022 at 2:08 PM Rich Bowen wrote:
>
>
Happy to take on July one (I have Airflow Summit last week of May so I
expect heavy down/recovery time right after).
On Tue, May 3, 2022 at 9:20 PM Josh Fischer wrote:
> Yes, I will take point for the June newsletter.
>
>
> On Tue, May 3, 2022 at 2:08 PM Rich Bowen wrote:
>
> > On Tue, 2022-05-
Yes, I will take point for the June newsletter.
On Tue, May 3, 2022 at 2:08 PM Rich Bowen wrote:
> On Tue, 2022-05-03 at 12:47 -0500, Josh Fischer wrote:
> > Yeah! Next month let’s work on making the email cleaner. Less is
> > more
> > :-). I saw what was sent, it was still a bit much to par
On Tue, 2022-05-03 at 12:47 -0500, Josh Fischer wrote:
> Yeah! Next month let’s work on making the email cleaner. Less is
> more
> :-). I saw what was sent, it was still a bit much to parse through
> and
> understand.
>
Thank you, Josh, for handling this. Are you willing to take point again
fo
+1
On Tue, May 3, 2022 at 7:47 PM Josh Fischer wrote:
> Yeah! Next month let’s work on making the email cleaner. Less is more
> :-). I saw what was sent, it was still a bit much to parse through and
> understand.
>
>
>
>
>
> On Tue, May 3, 2022 at 12:35 PM Sam Ruby wrote:
>
> > On Tue, May 3
Yeah! Next month let’s work on making the email cleaner. Less is more
:-). I saw what was sent, it was still a bit much to parse through and
understand.
On Tue, May 3, 2022 at 12:35 PM Sam Ruby wrote:
> On Tue, May 3, 2022 at 1:30 PM Craig Russell wrote:
> >
> > I could not find where we
On Tue, May 3, 2022 at 1:30 PM Craig Russell wrote:
>
> I could not find where we decided whether to use members@ or members-notify@
> but I approved it.
As did I. :-)
> If anyone objects to the mail list, we can have that discussion for next time.
>
> Craig
- Sam Ruby
> > On May 3, 2022, at
I could not find where we decided whether to use members@ or members-notify@
but I approved it.
If anyone objects to the mail list, we can have that discussion for next time.
Craig
> On May 3, 2022, at 10:16 AM, Josh Fischer wrote:
>
> sent.
>
> On Tue, May 3, 2022 at 12:05 PM Jarek Potiuk
sent.
On Tue, May 3, 2022 at 12:05 PM Jarek Potiuk wrote:
> Good idea Rich. Converted all subjects to plain text, compressed them so
> that they fit in three short bullet points (not too long paragraph, still
> comprehensible) and added the link from Rich :)
>
>
> On Tue, May 3, 2022 at 6:12 PM
Good idea Rich. Converted all subjects to plain text, compressed them so
that they fit in three short bullet points (not too long paragraph, still
comprehensible) and added the link from Rich :)
On Tue, May 3, 2022 at 6:12 PM Rich Bowen wrote:
> On Tue, 2022-05-03 at 10:56 -0500, Josh Fischer w
On Tue, 2022-05-03 at 10:56 -0500, Josh Fischer wrote:
> Sam Ruby, suggested a plain text version for this round of the email.
> I
> **think** markdown was sent out last time and it didn't look good,
> making
> it harder to read/ understand .
>
> If we can find a way to make all the links easy to
Sam Ruby, suggested a plain text version for this round of the email. I
**think** markdown was sent out last time and it didn't look good, making
it harder to read/ understand .
If we can find a way to make all the links easy to read, let's do it. If
not, we might want to move them to an additiona
You mean the links to text ? We can do it of course but I have a feeling
that that defeats the purpose a bit because it allows the readers to jump
straight to the discussion :).
I updated it now to have bullet-points instead - and as long as it is not
too long, that might be better visually.
But if
Any way we can convert your addition to text? I feel it may be a lot to
sift through visually.
On Tue, May 3, 2022 at 8:32 AM Jarek Potiuk wrote:
> Updated. I think it's cool.
> I limited it to only discussions started in April.
>
> Seems we have a small enough number of discussions starting ev
Updated. I think it's cool.
I limited it to only discussions started in April.
Seems we have a small enough number of discussions starting every month, to
fit one small paragraph easily - and seeing just subjects of the
discussions with links directly to the discussions might be a nice
reminder/re
> One option is to put that digest on a separate page, and just provide a
link to it?
Or maybe simply put it in one paragraph/long line with links to relevant
discussions :). I will try to do it and we can decide if it makes sense.
Let me try.
On Tue, May 3, 2022 at 2:44 PM Josh Fischer wrote:
I plan on sending the newsletter in a few hours. If someone wants to add
anymore details please add them asap.
On Tue, May 3, 2022 at 7:39 AM Rich Bowen wrote:
> On Tue, 2022-05-03 at 12:35 +0200, Jarek Potiuk wrote:
> > I looked through it - I have one other comment/proposal: should we
> > may
On Tue, 2022-05-03 at 12:35 +0200, Jarek Potiuk wrote:
> I looked through it - I have one other comment/proposal: should we
> maybe
> add a digest of discussions running on members@a.o ? I think a lot
> of
> people does not follow up those and while it is easy to look at the
> list in
> archives,
And re: Christian - privacy policy is important :). We can even say that
some PMCs already converted to Matomo and we wait for others to catch up
(peer-pressure :D).
J.
On Tue, May 3, 2022 at 12:35 PM Jarek Potiuk wrote:
> I looked through it - I have one other comment/proposal: should we maybe
I looked through it - I have one other comment/proposal: should we maybe
add a digest of discussions running on members@a.o ? I think a lot of
people does not follow up those and while it is easy to look at the list in
archives, maybe listing the discussions with one-line summary would be good
?
Hi,
Le mar. 3 mai 2022 à 08:22, Christian Grobmeier a écrit :
> Is the move to the new privacy policy interesting enough to be added to the
> bullet points?
> It’s a boring topic topic too many but maybe worth to mention due to its
> impact on websites..
Definitely worth mentioning IMO.
-Bert
Hi
Is the move to the new privacy policy interesting enough to be added to the
bullet points? It’s a boring topic topic too many but maybe worth to mention
due to its impact on websites
Cheers
--
The Apache Software Foundation
V.P., Data Privacy
On Mon, May 2, 2022, at 17:03, Josh Fischer wrote
I just added the CFP information about ApacheCon Asia 2022.
Hope I can catch up with the train this month.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Mon, May 2, 2022 at 11:03 PM Josh Fischer wrote:
>
> Gotcha. I’ll send it out tomorrow!
>
> On Mon, May 2, 2022 at 9:49 AM Sam Ruby w
Gotcha. I’ll send it out tomorrow!
On Mon, May 2, 2022 at 9:49 AM Sam Ruby wrote:
> On Mon, May 2, 2022 at 10:39 AM Josh Fischer wrote:
> >
> > I remember us agreeing to send it out on May 5. Since I'm not a member,
> > I'll leave that up to either Rich or Sam to send out.
>
> I had sent the
On Mon, May 2, 2022 at 10:39 AM Josh Fischer wrote:
>
> I remember us agreeing to send it out on May 5. Since I'm not a member,
> I'll leave that up to either Rich or Sam to send out.
I had sent the last one out on the first Tuesday of the month, which
happened to be the 5th last month. I'd rec
I remember us agreeing to send it out on May 5. Since I'm not a member,
I'll leave that up to either Rich or Sam to send out.
Thank ya
On Mon, May 2, 2022 at 9:21 AM Rich Bowen wrote:
> The last one we sent, Sam sent directly to the members-notify list -
> which does, indeed, need to be done b
The last one we sent, Sam sent directly to the members-notify list -
which does, indeed, need to be done by a member.
I've added one more (member-specific) item to the highlights. I feel
like we're missing something important, but I cannot remember what it
is.
What is our send date?
On Mon, 2022
On Mon, May 2, 2022 at 9:57 AM Josh Fischer wrote:
>
> The newsletter has been updated and just about ready for sending out.. Not
> sure of the whos or hows of getting this across the foundation. Is there
> a preferred way that I can get this distributed? Is this something only
> a member can/sh
The newsletter has been updated and just about ready for sending out.. Not
sure of the whos or hows of getting this across the foundation. Is there
a preferred way that I can get this distributed? Is this something only
a member can/should do?
On Wed, Apr 20, 2022 at 4:20 PM Josh Fischer wrote:
We have room for another bullet point or two if anyone wants to add
anything to the critical committer communications letter. We have about
two weeks before it will be sent out. Link below.
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=210078929
- Josh
On Tue, Apr 5, 2022 at
On Tue, Apr 5, 2022 at 10:30 AM Josh Fischer wrote:
>
> Created a starter with a few fun facts here:
> https://cwiki.apache.org/confluence/x/0YyFD
>
> Feel free to add or take away as you see fit.
THANK YOU!
> - Josh
- Sam Ruby
> On Tue, Apr 5, 2022 at 8:40 AM Sam Ruby wrote:
>
> > Message ha
Created a starter with a few fun facts here:
https://cwiki.apache.org/confluence/x/0YyFD
Feel free to add or take away as you see fit.
- Josh
On Tue, Apr 5, 2022 at 8:40 AM Sam Ruby wrote:
> Message has been posted. Next time it probably should be a pure plain
> text version.
>
> Anybody want
Message has been posted. Next time it probably should be a pure plain
text version.
Anybody want to get started on May? Create the wiki page, put some
content there, and then send it out the first week in May after others
have been given the opportunity to contribute.
- Sam Ruby
On Thu, Mar 10
Hi,
Le mar. 5 avr. 2022 à 15:21, Rich Bowen a écrit :
> ...AFAIK, while there are a few things in the current draft
> that are not open to the public (ie, board meeting for example) there's
> no harm in informing the public - they just cannot participate...
I agree in principle, but we should cl
On Tue, 2022-04-05 at 08:44 +0200, Bertrand Delacretaz wrote:
> Le lun. 4 avr. 2022 à 19:16, Priya Sharma
> a écrit :
> >
> > I am also not able to view those pages (perhaps only ASF members
> > have
> > access)...
>
> That's correct, the ASFP wiki space is restricted to ASF members.
>
> It's
Le lun. 4 avr. 2022 à 19:16, Priya Sharma
a écrit :
>
> I am also not able to view those pages (perhaps only ASF members have
> access)...
That's correct, the ASFP wiki space is restricted to ASF members.
It's not fantastic that we're discussing here and not letting people
see that draft - OTOH
On Wed, 2022-03-30 at 16:07 -0400, Sam Ruby wrote:
>
> I'm a big fan of Cunninham's law:
> https://meta.wikimedia.org/wiki/Cunningham%27s_Law
>
> Accordingly, I've taken the sample newsletter and posted it here:
> https://cwiki.apache.org/confluence/display/ASFP/Member+Moment+-+April+2022
>
> I'
I am also not able to view those pages (perhaps only ASF members have
access).
On Mon, 4 Apr 2022 at 19:47, Josh Fischer wrote:
> I've tried to access both of the links that Betrand sent and I get a "Page
> not found" message in confluence.
>
> On Thu, Mar 31, 2022 at 3:15 AM Bertrand Delacretaz
I've tried to access both of the links that Betrand sent and I get a "Page
not found" message in confluence.
On Thu, Mar 31, 2022 at 3:15 AM Bertrand Delacretaz
wrote:
> Hi,
>
> Sam Ruby wrote:
>
> >... Accordingly, I've taken the sample newsletter and posted it here:
> >
> https://cwiki.apache.
On Thu, Mar 31, 2022 at 4:15 AM Bertrand Delacretaz
wrote:
>
> Hi,
>
> Sam Ruby wrote:
>
> >... Accordingly, I've taken the sample newsletter and posted it here:
> > https://cwiki.apache.org/confluence/display/ASFP/Member+Moment+-+April+2022
> > ...
>
> I've changed the structure slightly, with
>
Hi,
Sam Ruby wrote:
>... Accordingly, I've taken the sample newsletter and posted it here:
> https://cwiki.apache.org/confluence/display/ASFP/Member+Moment+-+April+2022
> ...
I've changed the structure slightly, with
https://cwiki.apache.org/confluence/display/ASFP/Member+Moments being
the home
big +1 to host the new letter draft to the wiki so every member can
add some news on that.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Thu, Mar 31, 2022 at 4:08 AM Sam Ruby wrote:
>
> On Tue, Mar 22, 2022 at 12:46 PM Rich Bowen wrote:
> >
> > Ok, looks like we have three volunteers -
On Tue, Mar 22, 2022 at 12:46 PM Rich Bowen wrote:
>
> Ok, looks like we have three volunteers - Josh Fisher, Dave Fisher, and
> Andrew Wetmore. So I don't feel like I'm doing this alone, which is
> good.
>
> What we need to do still is:
>
> 1) Pitch this to the membership to determine whether thi
My thoughts too (and BTW. I think this is great to start discussion
before we do it).
I think asking people is one thing which is important, but often you
might get answers from people who are outspoken, loud, and have a lot
of time - which I think is not the crowd we want to engage.
As one of th
On Tue, 2022-03-29 at 15:51 -0500, Josh Fischer wrote:
> Hey All,
>
> Some random thoughts/questions:
>
> I'm looking at the content on the newsletter page and my first few
> thoughts
> are "I don't know what to include" and probably more important "what
> do
> people want to read?". Would it be
Hey All,
Some random thoughts/questions:
I'm looking at the content on the newsletter page and my first few thoughts
are "I don't know what to include" and probably more important "what do
people want to read?". Would it be helpful to ask readers what they want to
hear about in the newsletter? I
FYI, as some of you are aware, I started a new job earlier this month,
and that is consuming *all* of my brain-cycles. If someone else wanted
to step up and start organizing the April newsletter, that would be
great - although we're alreay behind schedule for that. Failing that,
it seems more likel
Once a year member meetings are a bit long for us.
The regular newsletter can help us to create a rhythm for the community.
Please count me in, I really like the idea and want to make it happen.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Wed, Mar 23, 2022 at 12:46 AM Rich Bowen wrote
I am also happy to help. We need more positivity in members@ :D
On Tue, Mar 22, 2022 at 6:40 PM Priya Sharma
wrote:
>
> Hey team,
> Please count me in. I will help make it happen.
>
> On Tue, 22 Mar 2022 at 22:43, Rich Bowen wrote:
>
> > On Tue, 2022-03-22 at 17:54 +0100, Bertrand Delacretaz wro
Hey team,
Please count me in. I will help make it happen.
On Tue, 22 Mar 2022 at 22:43, Rich Bowen wrote:
> On Tue, 2022-03-22 at 17:54 +0100, Bertrand Delacretaz wrote:
> > Hi,
> >
> > Le mar. 22 mars 2022 à 17:46, Rich Bowen a écrit
> > :
> > > ...1) Pitch this to the membership to determine
On Tue, 2022-03-22 at 17:54 +0100, Bertrand Delacretaz wrote:
> Hi,
>
> Le mar. 22 mars 2022 à 17:46, Rich Bowen a écrit
> :
> > ...1) Pitch this to the membership to determine whether this should
> > land
> > on members@ or members-notify@..
>
> I think it's clearly members@ - the other list is
Hi,
Le mar. 22 mars 2022 à 17:46, Rich Bowen a écrit :
> ...1) Pitch this to the membership to determine whether this should land
> on members@ or members-notify@..
I think it's clearly members@ - the other list is meant for "formal
notifications" [1], with minimal traffic.
With a suitable subj
Ok, looks like we have three volunteers - Josh Fisher, Dave Fisher, and
Andrew Wetmore. So I don't feel like I'm doing this alone, which is
good.
What we need to do still is:
1) Pitch this to the membership to determine whether this should land
on members@ or members-notify@
2) Write sample newsl
Rich,
I will help make it happen.
- Josh
On Thu, Mar 10, 2022 at 9:01 AM Rich Bowen wrote:
> Problem: Members (and, more generally, committers) are less engaged with
> the larger Foundation than at any point in our history. Meanwhile, the
> mechanisms for getting more engaged (eg, the members
Problem: Members (and, more generally, committers) are less engaged with
the larger Foundation than at any point in our history. Meanwhile, the
mechanisms for getting more engaged (eg, the members mailing list) are a
firehose of unrelated content that is very frustrating to the casual
participa
58 matches
Mail list logo
