[Announce] Community Over Code Registration Now Open

[Brian Proffitt]

All:

The organizers of Community Over Code North America have announced today[1]
the opening of registration for the event. Formerly known as ApacheCon,
Community Over Code is the flagship event of the ASF, showcasing content
from many of the project communities at the ASF. Community Over Code North
America will be held at the Halifax Convention Centre in Halifax, Nova
Scotia October 7-10, 2023.

This year, Community Over Code will feature four days of sessions, with
tracks focusing on Search, Big Data, Cassandra, Community,  Financial Tech,
Geospatial, Internet of Things, Community, Geospatial, Cassandra, Financial
Tech, Search, and many other topics. Each evening will also feature Birds
of a Feather (BoF) sessions, where communities will have an opportunity for
freeform discussion and planning around our various projects.

Early bird registration is available from now until July 31, 2023 for
US$500 per attendee, a savings of US$250. After that, regular registration
for the event will be US$750 until September 21. Late registration begins
on September 22, at US$850.

Apache committers can register for US$250. If you want to take advantage of
this, please use the following steps:

   1. When starting the registration process, please use your apache.org email
   address with your personal information.
   2. Select the Committer category.
   3. Enter this code to apply a discount to get the price to US$250:
   *CCNACOMMIT23*

*Note*: *If you have applied to be a speaker, you should wait until
notification that your talk was accepted before registering. This way you
won't have to go through the refund process.*

Registered attendees can take advantage of discounted rooms at hotels near
the venue. To view all registration rates, deadlines, and room block
information, visit the event’s Registration page[2].

*Call for Proposals*
Speakers who can address content spanning ASF projects, open source
governance, community, or software development are encouraged to submit a
proposal. The call for presentations[3] is open now through July 13, 2023.

*Event Sponsorship*
For organizations interested in sponsoring Community Over Code, visit the
Community Over Code Sponsorship page[4].

*Travel Assistance*
The ASF Travel Assistance Committee (TAC) provides financial aid to members
of the open source community who are interested in attending a Community
Over Code event but face financial hardships that make attending difficult
or impossible. Applications for Community Over Code North America are being
accepted until July 22, 2023. For more information, please read the latest
blog[5]. To apply, visit https://tac-apply.apache.org/.

Thanks,
BKP

[1]
https://news.apache.org/foundation/entry/apache-software-foundation-opens-registration-for-community-over-code-north-america
[2] https://communityovercode.org/registration/
[3] https://communityovercode.org/call-for-presentations/
[4] https://communityovercode.org/sponsors/
[5]
https://news.apache.org/foundation/entry/how-to-apply-for-travel-assistance-for-community-over-code-2023-events

Brian Proffitt
VP, Marketing & Publicity
Co-organizer, Community Over Code
Member, Apache Software Foundation
Member, Apache Community Development & Incubator PMCs
Red Hat Open Source Program Office

Today's ASF News: Community Over Code Registration + CFP Open

[Whitney True]

Hello ASF Community,

Today the ASF announced

that registration for Community Over Code North America is now
open. The Call for Proposals is also open until *00:01 UTC July 13.*

Reminder that Community Over Code North America will be held at the Halifax
Convention Centre in Halifax, Nova Scotia October 7-10, 2023.

*To Register:* https://communityovercode.org/registration/
*Early bird registration is available until July 31, 2023 for US$500 per
attendee, a savings of US$250. Apache committers can register for US$250.
For more details on registration rates and room block discounts, please
click the link above. *

*To Submit a CFP:* https://communityovercode.org/call-for-presentations/

For Travel Assistance please read the latest blog
,
or to apply, visit https://tac-apply.apache.org/.

For organizations interested in sponsoring Community Over Code, you can
download a prospectus from the Community Over Code Sponsorship page
.

And last, for those on social media, the event hashtag is #CommunityOverCode

Many thanks!
Whitney
(On Behalf of ASF M)

Re: Anyone interested in initiating an ALC Frankfurt?

[Christian Grobmeier]

On Tue, Jul 11, 2023, at 14:56, Christofer Dutz wrote:
> Ok … so I guess there’s no real interest in such a thing.
>
> Probably creating an ALC Germany sort of sounds like a stupid idea … 
> one sort of contradicting the L in Local ;-)

Germany is very local for somebody living in a country like India :-)

Seriously, a ALC Germany, where the attendees of such conferences travel from 
city to city doesn't sound too bad for me. In cooperation with Java Usergroups 
this may work. I have done something similar with fellows for Apache Struts a 
few years back



>
> Chris
>
> Von: Richard Zowalla 
> Datum: Mittwoch, 14. Juni 2023 um 09:10
> An: dev@community.apache.org 
> Betreff: Re: Anyone interested in initiating an ALC Frankfurt?
> Hi Chris,
>
> for me, Frankfurt is (with a 2.5h train ride) a bit too far away but I
> might be able to occussionally lurk in ;-) - so I wouldn't be able to
> organize things, etc.
>
> Gruß from Heilbronn / Germany
> Richard
>
> Am Mittwoch, dem 14.06.2023 um 06:35 + schrieb Christofer Dutz:
>> Hi all,
>>
>> I just wanted to bring forward the idea of initiating an ALC chapter
>> in Germany/Frankfurt.
>>
>> I noticed that many meetups near Frankfurt have shifted away from
>> reporting about real project, toward more theoretical content.
>> However, have I heard quite a few people that are a bit unhappy with
>> that.
>>
>> Having an ALC Frankfurt (or whatever we’d call it) would allow us to
>> promote our awesome Apache projects a bit more.
>>
>> I would even already have a place where we could regularly have such
>> meetings, as my former employer codecentric would be happy to
>> accommodate us.
>>
>> What do you folks think?
>>
>> Chris
>>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

AW: Changing the defaults for GitHub generated email titles?

[Christofer Dutz]

I have absolutely no idea … just whenever you leave it away the system starts 
yelling at you, telling you that it’s required ;-)
If the computer says so … I gotta obey ;-)

Von: Kelly Oglesbee 
Datum: Dienstag, 11. Juli 2023 um 15:00
An: dev@community.apache.org 
Betreff: Re: Changing the defaults for GitHub generated email titles?
Why id this necessary?

On Tue, Jul 11, 2023, 8:56 AM Christofer Dutz 
wrote:

> Hi Phil,
>
> Well, you can somewhat reduce it to whatever you like … however there
> seems to be one limitation, which I can’t quite explain.
> For some reason you need to have the repository name as part of the
> subject line. That’s why I added it to the end as there it didn’t interrupt
> my speed-reading and didn’t show up on my phone.
>
> And yeah … I agree that I also prefer the super-minimal prefixes [PR] for
> Pull-Requests [I] for Issues and [D] for Discussions.
> I think it takes me something round half a second to know that it’s a PR,
> Issue or Discussion.
> Generally, I could even live without them all together as it doesn’t
> really matter, if a discussion is about a PR, Issue or just a
> general-purpose discussion.
> In an all-email workflow, we never had these prefixes before … everything
> was just a discussion.
> But if you ask me .. I’d keep the minimal prefixes, but be in favor of the
> smaller ones above [PULL-REQUEST], [ISSUE] and [DISCUSSION] …
> well … I guess that was why I chose these defaults for the projects I
> could change it ;-)
>
> Chris
>
>
> Von: Phil Steitz 
> Datum: Mittwoch, 5. Juli 2023 um 20:57
> An: dev@community.apache.org 
> Betreff: Re: Changing the defaults for GitHub generated email titles?
> +1 from another Commons contributor drowning in the flood of cruft on
> commons-dev.  Shorter subject lines would be great.  I don't know if the
> tooling would support or can be customized for Commons, but one thing that
> would help would be to uniformly drop the word "Commons", so we go back to
> what we did when we actually used the dev list for discussion [Commons-Foo]
> is just [Foo].  There is also no value in the [GitHub] prefix in the
> messages from there.  All PRs come from there.  Probably should talk about
> this on Commons-dev (maybe with some special decorations on the subject
> line so people will see it amidst all of the bot stuff :)
>
> Phil
>
> On Mon, Jul 3, 2023 at 5:48 AM Gary Gregory 
> wrote:
>
> > Thanks for sharing these links; what a great start :-)
> >
> > I'm pretty sure the Commons community will welcome these kinds of
> > changes where a complaint has been the "flood" of emails from GitHub,
> > so hopefully this will help.
> >
> > For my money though, I'd prefer much shorter subject prefixes, even to
> > the extreme, I'll just learn the codes, otherwise, it's impossible to
> > read on my phone, which would be counterproductive (for me).
> >
> > For example, [BUILD-FAILURE] -> [BUILD-FAIL] -> [BUILD-F] -> [B-F],
> > just something much shorter, again, think phone. B means Build, F
> > means Fail, that kinda mapping. I'm not sure where the mapping would
> > be best documented, perhaps on each project's mailing list page.
> >
> > Gary
> >
> > On Mon, Jul 3, 2023 at 8:12 AM Christofer Dutz
> >  wrote:
> > >
> > > Hi all,
> > >
> > > So here’s an example of one week’s email traffic on one project before
> > and after the config changes:
> > >
> > > (Sorry for putting the Spotlight on you streampipes folks, but this is
> > the best positive example I know)
> > >
> > > Before the change:
> > >
> >
> https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-1-9|dto=2023-1-15
> > > Here you can see, that:
> > > a) It’s hard to see what something is about as the prefix is very large
> > > b) The only grouping happening is the same person doing the same thing
> > on one issue (commenting on an issue for example)
> > >
> > > Also, one week on the same list, with updated settings:
> > >
> >
> https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-6-12|dto=2023-6-18
> > :
> > > Here you can see:
> > > a) Greatly reduced number of threads
> > > b) Threads are grouped together
> > > c) You can actually follow a thread
> > > (The reason so many threads start with “RE:” is that the initial post
> > seems to be outside of the date-range of that week and the reason for one
> > or two long discussion titles, was they changed the config on 16.06.2023)
> > >
> > > Hope this brings a bit more context for some.
> > >
> > > Chris
> > >
> > >
> > >
> > > Von: Shane Curcuru 
> > > Datum: Freitag, 30. Juni 2023 um 23:20
> > > An: dev@community.apache.org 
> > > Betreff: Re: Changing the defaults for GitHub generated email titles?
> > > Christofer Dutz wrote on 6/30/23 3:49 AM:
> > > ...snip...
> > > > So in general, I would like to change the defaults used by the GitHub
> > tooling to the ones I proposed in
> >
> https://community.apache.org/contributors/mailing-lists.html#configuring-the-subject-lines-of-the-emails-being-sent
> > . Quite a 

AW: Anyone interested in initiating an ALC Frankfurt?

[Christofer Dutz]

Ok … so I guess there’s no real interest in such a thing.

Probably creating an ALC Germany sort of sounds like a stupid idea … one sort 
of contradicting the L in Local ;-)

Chris

Von: Richard Zowalla 
Datum: Mittwoch, 14. Juni 2023 um 09:10
An: dev@community.apache.org 
Betreff: Re: Anyone interested in initiating an ALC Frankfurt?
Hi Chris,

for me, Frankfurt is (with a 2.5h train ride) a bit too far away but I
might be able to occussionally lurk in ;-) - so I wouldn't be able to
organize things, etc.

Gruß from Heilbronn / Germany
Richard

Am Mittwoch, dem 14.06.2023 um 06:35 + schrieb Christofer Dutz:
> Hi all,
>
> I just wanted to bring forward the idea of initiating an ALC chapter
> in Germany/Frankfurt.
>
> I noticed that many meetups near Frankfurt have shifted away from
> reporting about real project, toward more theoretical content.
> However, have I heard quite a few people that are a bit unhappy with
> that.
>
> Having an ALC Frankfurt (or whatever we’d call it) would allow us to
> promote our awesome Apache projects a bit more.
>
> I would even already have a place where we could regularly have such
> meetings, as my former employer codecentric would be happy to
> accommodate us.
>
> What do you folks think?
>
> Chris
>


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Simple question: Project blogs

[Arnout Engelen]

On Tue, Jul 11, 2023 at 2:20 PM Bertrand Delacretaz 
wrote:

> we used to have
> https://twitter.com/planetapache and http://planet.apache.org/ but not
> anymore.
>
> Maybe https://apache.org/blogs would be a good place, with a manually
> curated list of project blogs?
>
> Or list them at https://projects.apache.org/ adding metadata to the
> projects LDAP info
>
> What would be really useful IMO is an aggregated RSS feed to which our
> project blogs can be added, which I suppose planet.a.o was doing.
>

I think there are plans to set such a thing up at https://blogs.apache.org (
https://issues.apache.org/jira/browse/INFRA-24702) - I would love that!


Kind regards,

Arnout

Re: Simple question: Project blogs

[Jarek Potiuk]

One comment - some projects might have their own "blogs"
https://airflow.apache.org/blog/ , Yes, not being the best citizen
(sorry!), having our own blog link

But I saw recently,  there have been improvements / changes in the way how
blogs are published, so maybe - if we see some incentives why following
other's - we can migrate.
Not sure how important it is to have all the blogs under the common
"umbrella" - is it important? necessary? recommended?

J.

On Tue, Jul 11, 2023 at 2:29 PM Brian Proffitt  wrote:

> All:
>
> Thank you for the data, it is very helpful. I have my question answered
> now!
>
> BKP
>
>
> On Tue, Jul 11, 2023 at 8:25 AM Ayush Saxena  wrote:
>
> > Hi,
> > A bunch of the old ones can be found here:
> > https://blogsarchive.apache.org/
> >
> > Rest for some projects: .blog.apache.org, like Hive:
> > https://hive.blog.apache.org/ and for some it is
> > .apache.org/blogs like Iceberg:
> > https://iceberg.apache.org/blogs/ and Ranger
> > https://ranger.apache.org/blogs.html
> >
> > Most of the projects would have a link on their main website, so you
> > can explore there.
> >
> > -Ayush
> >
> > On Tue, 11 Jul 2023 at 17:50, Bertrand Delacretaz
> >  wrote:
> > >
> > > Hi,
> > >
> > > On Tue, Jul 11, 2023 at 12:13 AM Brian Proffitt 
> wrote:
> > > >
> > > > Simply put, if I want to direct people to Apache project's blogs, I
> > would
> > > > send them to... where?..
> > >
> > > Right now I don't think that we have an answer, we used to have
> > > https://twitter.com/planetapache and http://planet.apache.org/ but not
> > > anymore.
> > >
> > > Maybe https://apache.org/blogs would be a good place, with a manually
> > > curated list of project blogs?
> > >
> > > Or list them at https://projects.apache.org/ adding metadata to the
> > > projects LDAP info
> > >
> > > What would be really useful IMO is an aggregated RSS feed to which our
> > > project blogs can be added, which I suppose planet.a.o was doing.
> > >
> > > -Bertrand (who recently restarted using RSS feeds and super happy about
> > that)
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
> >
>

Re: Simple question: Project blogs

[Brian Proffitt]

All:

Thank you for the data, it is very helpful. I have my question answered now!

BKP


On Tue, Jul 11, 2023 at 8:25 AM Ayush Saxena  wrote:

> Hi,
> A bunch of the old ones can be found here:
> https://blogsarchive.apache.org/
>
> Rest for some projects: .blog.apache.org, like Hive:
> https://hive.blog.apache.org/ and for some it is
> .apache.org/blogs like Iceberg:
> https://iceberg.apache.org/blogs/ and Ranger
> https://ranger.apache.org/blogs.html
>
> Most of the projects would have a link on their main website, so you
> can explore there.
>
> -Ayush
>
> On Tue, 11 Jul 2023 at 17:50, Bertrand Delacretaz
>  wrote:
> >
> > Hi,
> >
> > On Tue, Jul 11, 2023 at 12:13 AM Brian Proffitt  wrote:
> > >
> > > Simply put, if I want to direct people to Apache project's blogs, I
> would
> > > send them to... where?..
> >
> > Right now I don't think that we have an answer, we used to have
> > https://twitter.com/planetapache and http://planet.apache.org/ but not
> > anymore.
> >
> > Maybe https://apache.org/blogs would be a good place, with a manually
> > curated list of project blogs?
> >
> > Or list them at https://projects.apache.org/ adding metadata to the
> > projects LDAP info
> >
> > What would be really useful IMO is an aggregated RSS feed to which our
> > project blogs can be added, which I suppose planet.a.o was doing.
> >
> > -Bertrand (who recently restarted using RSS feeds and super happy about
> that)
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Simple question: Project blogs

[Ayush Saxena]

Hi,
A bunch of the old ones can be found here:
https://blogsarchive.apache.org/

Rest for some projects: .blog.apache.org, like Hive:
https://hive.blog.apache.org/ and for some it is
.apache.org/blogs like Iceberg:
https://iceberg.apache.org/blogs/ and Ranger
https://ranger.apache.org/blogs.html

Most of the projects would have a link on their main website, so you
can explore there.

-Ayush

On Tue, 11 Jul 2023 at 17:50, Bertrand Delacretaz
 wrote:
>
> Hi,
>
> On Tue, Jul 11, 2023 at 12:13 AM Brian Proffitt  wrote:
> >
> > Simply put, if I want to direct people to Apache project's blogs, I would
> > send them to... where?..
>
> Right now I don't think that we have an answer, we used to have
> https://twitter.com/planetapache and http://planet.apache.org/ but not
> anymore.
>
> Maybe https://apache.org/blogs would be a good place, with a manually
> curated list of project blogs?
>
> Or list them at https://projects.apache.org/ adding metadata to the
> projects LDAP info
>
> What would be really useful IMO is an aggregated RSS feed to which our
> project blogs can be added, which I suppose planet.a.o was doing.
>
> -Bertrand (who recently restarted using RSS feeds and super happy about that)
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Simple question: Project blogs

[Brian Proffitt]

On Tue, Jul 11, 2023 at 7:19 AM Matthias Seidel 
wrote:

> Hi Brian,
>
> Am 11.07.23 um 00:13 schrieb Brian Proffitt:
> > Simply put, if I want to direct people to Apache project's blogs, I would
> > send them to... where?
> >
> > The answer should be a URL(s).
>
> I would expect something like
>
> .apache.org/blog
>
> or
>
> .apache.org/blogs
>
> Regards,
>
>Matthias
>

Matthias: thank you.

[snip]

Re: Simple question: Project blogs

[Brian Proffitt]

On Mon, Jul 10, 2023 at 7:18 PM B C  wrote:

> I wouldn't send them to the Apache projects.
> Infact I would tell them to run the other direction.
>

Oh, look, an opinion when I asked for a factual answer. Not helpful.

[snip]

Re: Simple question: Project blogs

[Matthias Seidel]

Hi Brian,

Am 11.07.23 um 00:13 schrieb Brian Proffitt:
> Simply put, if I want to direct people to Apache project's blogs, I would
> send them to... where?
>
> The answer should be a URL(s).

I would expect something like

.apache.org/blog

or

.apache.org/blogs

Regards,

   Matthias

>
> Thanks!
> BKP
>



smime.p7s
Description: S/MIME Cryptographic Signature