Re: [Proposal] Apache Local Community

[Austin Bennett]

Quite sensible:  I am based in San Francisco and could spearhead an effort
here.

Will look forward to contributing and helping this flourish.  In-Person
really does help build community -- even though (esp. for Apache) getting
things done async/virtual is super important.

On Tue, Jun 25, 2019 at 10:37 PM Swapnil M Mane 
wrote:

> Hello team,
>
> Recently, I got the opportunity to explore the possibility of having
> roadshow in India.
> During this process, I faced some challenges in contacting the local Apache
> people and committers,
> these challenges and my previous experiences (with other communities and
> student community)
> gives birth to the idea of forming the Apache Local Community (ALC).
>
> ALC will be similar to Google Developer Group [1], Facebook Developer
> Circles [2], Mozilla Reps [3],
> you can find the local GDG [4] and Developer Circles [5].
>
> *What is ALC*
> ALC is a local group of Apache (Open Source), enthusiast. Each local group
> will be called as ALC chapter.
>
> *Role of ALC*
> -- Spread the awareness on Apache in the local community.
> -- Host various events for local open source lovers (at least should have
> one monthly meetup).
> -- Share the details about ASF, The Apache Way, and various Apache's
> projects in local students, developers, and the business community.
> -- Bring together project users and developers
>
> *How ALC will be formed*
> Each town/city will strictly have single ALC chapter.
> If ALC chapter doesn't exist in the town, the interested volunteer can
> contact ALC committee via form or mail to form it.
> An ALC chapter will be led by a community manager.
>
> *Benefits of ALC*
> -- We have limited ApacheCon and Roadshow, the ALC will open the doors for
> having frequent and small events.
> -- It will be a platform for committers from different projects (living in
> the same town/city) to meet and exchange knowledge, thoughts, and ideas.
> Currently, it happens the committer of one apache project doesn't know much
> about the committer from another project (both belongs to the same town ;)
> -- Building community, as the Apache maxim "Community Over Code".
>
> These all are very initial ideas if we planned to proceed with this, as a
> community, we can work details of defining roles and responsibility of ALC,
> the process of forming ALC chapters, how the ALC chapters will function
> (community manager/lead of ALC chapters), etc.
>
> I am aware of Apache Mentoring Programme [6] and Local Mentors [7], but the
> ALC is different from this, it is about forming a designated local
> community.
>
> All the inputs and thoughts are highly appreciated.
>
> P.S. ALC is just first word came in my mind, if you think there can be a
> better name than ALC, please feel free to discuss.
>
> [1] https://developers.google.com/programs/community/gdg/
> [2] https://developers.facebook.com/developercircles/
> [3] https://reps.mozilla.org/about/
> [4] https://developers.google.com/programs/community/gdg/directory/
> [5] https://developers.facebook.com/developercircles/find
> [6] https://community.apache.org/mentoringprogramme.html
> [7] https://community.apache.org/localmentors.html
>
> Best Regards,
> Swapnil M Mane
>

Re: [Proposal] Apache Local Community

[Austin Bennett]

The company I do much work for has a large presence in Bangalore, and
regularly connect with those colleagues.  Happy to push those connections
to get involved locally (and potentially schedule myself to be out there)
should sufficient interest in that locale.



On Thu, Jun 27, 2019 at 6:07 AM Vijay Kedia  wrote:

> In Bangalore also, There are a lot of development groups on Meetup.com. I
> believe some of them are Apache committers too.
>
>
> On Thu, 27 Jun 2019 at 6:22 PM, Peter Hunsberger <
> peter.hunsber...@gmail.com>
> wrote:
>
> > Around here we get a lot of local development focused groups on
> > Meetup.com...
> >
> > On Thu, Jun 27, 2019 at 5:24 AM Claude Warren  wrote:
> >
> > > As a developer in a small city (Galway, IE) I can't think of another
> > Apache
> > > developer in the area.  I am certain there must be some and I know of
> OS
> > > developers that are not Apache devs.  Is there a mechanism where by
> > Apache
> > > committers may locate other committers in their area?  Without this
> > > capability I don't see how I could build an ALC team.  It would be nice
> > if
> > > I could reach out directly to local developers.
> > >
> > > However, I am very interested in this idea.
> > >
> > > Claude
> > >
> > >
> > > On Thu, Jun 27, 2019 at 8:03 AM Swapnil M Mane <
> swapnilmm...@apache.org>
> > > wrote:
> > >
> > > > Thanks very much Andrew for showing the interest.
> > > >
> > > > Glad to hear from you Pranay, thanks so much for your comments.
> > > >
> > > > @Team,
> > > > I will share more details on how to proceed further on this soon
> > (waiting
> > > > for getting some more inputs from the community).
> > > >
> > > >
> > > > - Best Regards,
> > > > Swapnil M Mane
> > > >
> > > >
> > > >
> > > > On Thu, Jun 27, 2019 at 12:04 PM Pranay Pandey <
> pandeypra...@gmail.com
> > >
> > > > wrote:
> > > >
> > > > > Hi Swapnil,
> > > > >
> > > > > This is a fantastic idea and need of the hour for sure. This
> concept
> > > will
> > > > > help to spread the word Apache across the world. I will be glad to
> > > > > participate and help.
> > > > >
> > > > > Best Regards,
> > > > > Pranay
> > > > > --
> > > > > Pranay Pandey
> > > > > Mobile : +919826035576
> > > > > Skype: pranay.pandey
> > > > > Linkedin: http://in.linkedin.com/in/pranaypandey
> > > > > Twitter: @pandeypranay
> > > > >
> > > > >
> > > > >
> > > > > On Wed, Jun 26, 2019 at 11:07 AM Swapnil M Mane <
> > > swapnilmm...@apache.org
> > > > >
> > > > > wrote:
> > > > >
> > > > >> Hello team,
> > > > >>
> > > > >> Recently, I got the opportunity to explore the possibility of
> having
> > > > >> roadshow in India.
> > > > >> During this process, I faced some challenges in contacting the
> local
> > > > >> Apache
> > > > >> people and committers,
> > > > >> these challenges and my previous experiences (with other
> communities
> > > and
> > > > >> student community)
> > > > >> gives birth to the idea of forming the Apache Local Community
> (ALC).
> > > > >>
> > > > >> ALC will be similar to Google Developer Group [1], Facebook
> > Developer
> > > > >> Circles [2], Mozilla Reps [3],
> > > > >> you can find the local GDG [4] and Developer Circles [5].
> > > > >>
> > > > >> *What is ALC*
> > > > >> ALC is a local group of Apache (Open Source), enthusiast. Each
> local
> > > > group
> > > > >> will be called as ALC chapter.
> > > > >>
> > > > >> *Role of ALC*
> > > > >> -- Spread the awareness on Apache in the local community.
> > > > >> -- Host various events for local open source lovers (at least
> should
> > > > have
> > > > >> one monthly meetup).
> > > > >> -- Share the details about ASF, The Apache Way, and various
> Apache's
> > > > >> projects in local students, developers, and the business
> community.
> > > > >> -- Bring together project users and developers
> > > > >>
> > > > >> *How ALC will be formed*
> > > > >> Each town/city will strictly have single ALC chapter.
> > > > >> If ALC chapter doesn't exist in the town, the interested volunteer
> > can
> > > > >> contact ALC committee via form or mail to form it.
> > > > >> An ALC chapter will be led by a community manager.
> > > > >>
> > > > >> *Benefits of ALC*
> > > > >> -- We have limited ApacheCon and Roadshow, the ALC will open the
> > doors
> > > > for
> > > > >> having frequent and small events.
> > > > >> -- It will be a platform for committers from different projects
> > > (living
> > > > in
> > > > >> the same town/city) to meet and exchange knowledge, thoughts, and
> > > ideas.
> > > > >> Currently, it happens the committer of one apache project doesn't
> > know
> > > > >> much
> > > > >> about the committer from another project (both belongs to the same
> > > town
> > > > ;)
> > > > >> -- Building community, as the Apache maxim "Community Over Code".
> > > > >>
> > > > >> These all are very initial ideas if we planned to proceed with
> this,
> > > as
> > > > a
> > > > >> community, we can work details of defining roles and
> responsibility
> > of
> > > > >> ALC,
> > > > 

Re: Volunteers wanted: Hackathon organization at ApacheCon Berlin 2019

[Austin Bennett]

Sensible thought, Steve,

I was imagining the sort of things that get setup and contributed to (by me
and others I collaborated with) for Vegas to be setup in such a way to
easily replicated in Berlin.


On Mon, Jul 8, 2019 at 8:35 AM Steve Blackmon  wrote:

> Hi Myrle,
>
> I expect the process and mechanics of hackathon planning and execution of
> the ACNA and ACEU hackathons will be more similar than different, cultural
> differences between a Las Vegas casino and Kulterbrauerei aside.
>
> It makes sense to set up a different accountable event leadership group,
> but we should try to coordinate our efforts closely.  To that end I invite
> everyone on this thread to dial into any ACNA hackathon weekly planning
> meeting (Sundays at 11AM CST) and contribute, and I will be happy to
> participate in the planning effort for Berlin as well.
>
> Event details, notes, and links regarding ACNA hackathon here:
>
> https://docs.google.com/spreadsheets/d/1QyOryFSFifORXrm_EgLuimH6t4t98FnvcKEctcdDg2Y
>
> sblack...@apache.org
> On Jun 26, 2019, 9:38 AM -0500, Myrle Krantz , wrote:
> > Hey everyone,
> >
> > Much like for Las Vegas, I'm hoping we can find a volunteer or two who is
> > interested in helping to make the hackathon in Berlin awesome.
> >
> > Is anyone interested in assisting here?
> >
> > To quote Rich:
> >
> > "I need 1 to 3 volunteers to own the Hackathon for ACNA.
> >
> > The Hackathon has long been a central part of ApacheCon. However, the
> > success of the hackathon waxes and wanes over the years, due largely to
> > whether someone steps up to drive it.
> >
> > The hackathon has multiple intertwined purposes:
> >
> > * Attract and mentor new committers
> > * Strengthen personal bonds within project community
> > * Foster cross-project cooperation
> > * Knock out difficult bugs/features/documentation projects
> >
> > For this to be successful, the following things need to happen
> >
> > * Projects need to know about it
> > * They need to prepare ahead of time. In particular, they need to think
> > about what they will be working on
> > * The plan (ie, what we'll be working on) must be promoted both within
> > the project (so that core project members show up prepared) and outside
> > (so that curious people show up and play along)
> > * There needs to be great signage on-site, and we need to mention it at
> > every plenary
> >
> > To this end, I need someone(s) to step up to own this. I do not have
> > time to be the point person on this.
> >
> > I need someone who cares about building project communities, is
> > enthusiastic about working directly with projects to build their
> > hackathon plans, and who plans to attend ACNA to do the on-site stuff
> > necessary to support the above. I need someone who is willing to take
> > the reins on this and drive it without much direction from me or anyone
> > else, and just report back periodically on progress.
> >
> > Please let me know if you are willing to lead this effort. Thank you."
> >
> > Thanks,
> > Myrle Krantz
> > Conference Chair, ApacheCon Berlin 2019
> > The Apache Software Foundation
>

Fwd: ACNA 2019 Hackathon

[Austin Bennett]

Hi,

We (some involved with Beam) have discussed contributing to both ACNA and
the European efforts.  Have (and still am) traveling and vacation in
China.  Intend to connect upon return.

We have discussed: hackathon, tools, contributing to, "office
hours"/user-and-or-dev-help, etc.

Looking forward to ApacheCon and contributing to the Hackathon as sensible.

Cheers,
Austin


-- Forwarded message -
From: Steve Blackmon 
Date: Mon, Jul 15, 2019 at 9:45 AM
Subject: ACNA 2019 Hackathon
To: planners 


Dear Apache Project PMC Members:

There will be space at ACNA 2019 dedicated to a hackathon.  The space
will be available throughout the conference, from the start of each
day’s schedule until 11:45 PM, with the possible exception of during
keynote and single-track / conference-wide events.

The ACNA Hackathon sub-committee wants this to be the most productive
hackathon in ApacheCon history.  Collaborative development on project
source code, improvements to project documentation, and development of
example apps or tools built upon one or more Apache projects are all
encouraged.

More details will be available leading up to the event, but here’s
generally what to expect:

- Dedicated space with chairs, power, wifi, snacks, and caffeine.
- Tables dedicated to specific participating projects
- ‘Getting Started’ discussions for new and aspiring committers
- Help setting up development environments or completing hackathon tasks
- Concierge Charging Station with supervised charging of phones/laptops.

With most logistical concerns now attended to, we are identifying
interested participants, promoters, and coordinators.  Are you an
Apache member or committer willing to do the following on behalf of
your project:

- Operate a dedicated hackathon table?
- Designate collaborative work for your project’s table to help hackers
focus?
- Encourage your community to hack at your project’s table?
- Report out during and following the event about what was attempted
and accomplished?

Interested? Reply to plann...@apachecon.com to reserve a table or two
for your project that we can advertise to your community.

We are currently working out a Hackathon schedule that will be posted,
letting attendees know when they should expect activities related to
their project and various open sessions to take place. If you will
take on the lead role for your project, we will work with you to plan,
prepare, and generate interest in the wider community.

If you aren’t interested in hacking yourself but want to help others,
we could also use persons who are willing to do one or more of the
following:

- Operate the primary information table in the hackathon space for several
hours
- Give a short introductory tools or skills presentation / answer questions
- Host ‘Office Hours’ and hold scheduled 1-on-1 discussions with other
attendees
- Help the projects who are hacking coordinate their meeting times via slack
- Man the concierge charging station.

Thanks!

sblack...@apache.org
ACNA Hackathon sub-committee chair

P.S. We invite anyone who has ideas to share with the planning
committee, or is considering participating in any way, to let us know
via dev@community.apache.org

Re: Fwd: Kafka Summit listing on ASF events site

[Austin Bennett]

Hi Melissa,

Is there a rate for Apache Members/Committers?

I recently saw Flink is offering that for their forthcoming EU Summit:
https://lists.apache.org/thread.html/%3CCAAdrtT2geJjp

Also, @sha...@apache.org  and @dev
 , that one (Flink EU conference) might be good
to get on the Apache Calendar?

Cheers,
Austin



On Wed, Jul 24, 2019 at 1:26 PM Sharan Foga  wrote:

> Hi Melissa
>
> I will add it.
>
> Thanks
> Sharan
>
> On 2019/06/20 20:39:05, Melissa Almgren  wrote:
> > Just circling back on this request, thank you!
> > Best,
> > Melissa
> >
> > -- Forwarded message -
> > From: Melissa Almgren 
> > Date: Thu, Jun 13, 2019 at 10:09 AM
> > Subject: Kafka Summit listing on ASF events site
> > To: 
> >
> >
> > Greetings!
> >
> > We would like to add Kafka Summit San Francisco to the events calendar
> here:
> > http://community.apache.org/calendars/index.html
> >
> > Here is the relevant info:
> >
> > https://kafka-summit.org/events/kafka-summit-san-francisco-2019/
> > *2019-09-30 to 2019-10-01*
> > Hilton San Francisco Union Square
> > 333 O’Farrell Street
> > San Francisco,
> > CA 94102
> > 415-771-1400
> >
> > Please let me know if you have any questions or need any further
> > information.
> > Best,
> > Melissa
> >
> > --
> > *Melissa Almgren*
> > Senior Manager, Events Marketing | Confluent
> > 415.378.7191
> > Follow us: Twitter  | blog
> >
> > 
> > [image: https://kafka-summit.org/events/kafka-summit-san-francisco-2019]
> > 
> >
> >
> >
> >
> > 
> >
> >
> >
> >
> > --
> > *Melissa Almgren*
> > Senior Manager, Events Marketing | Confluent
> > 415.378.7191
> > Follow us: Twitter  | blog
> >
> > 
> > [image: https://kafka-summit.org/events/kafka-summit-san-francisco-2019]
> > 
> >
> >
> >
> >
> > 
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Help Me In Contributing

[Austin Bennett]

Hi Priyank,

Checkout Apache Training (Though, I don't think that this contains what
you're seeking, yet):  https://training.apache.org

Perhaps this is useful though aimed at Beam (and exposes my ignorances in a
few areas):
https://www.youtube.com/watch?v=PtPslSdAPcM&list=PL4dEBWmGSIU_jJ82n0WK46agJy4ThegIQ&index=33&t=0s

Generally (if going with something Apache):
* Find a project that interests you
* Read/Follow lists, get a sense of community
* Pay attention to outstanding issues and offer something (new
perspectives, documentation, feedback, bug fixes, etc etc).
* Do more where needed.

Open source can be as simple as making the code publicly available.
Though, there can also be more when working to with the communities around
the code.

Good luck on your journey!

Cheers,
Austin


On Sat, Aug 3, 2019 at 12:12 PM Priyank Aggarwal 
wrote:

> Hey Everyone,
>
> I am new to open source and i want to start contributing , so can anybody
> help me out and guide me from where to start.
>
> Thank you
>

Re: ALC, and who can speak on behalf of Apache

[Austin Bennett]

The bits on mentorship make some sense, although I am confused.  If about
who is allowed/endorsed to speak on behalf of the ASF, then:

* Should only speakers at events be of a condoned status (how are they
vetted)?
or:
* Would a required minimum number of mentors (PMC/Foundation members) be
required in attendance, to be able to correct mis-messages?
or more extreme:
* Should every piece of content be recorded and reviewed, and if
insufficient then the group should be discredited (that is extreme and
unlikely, but I think you see the example).

^ The first two perhaps are things that should then also be included in the
report of an event.

Otherwise, it seems without the above invites much more bureaucracy without
actually doing much to solve/prevent the problem that seems to concern
people?






On Fri, Dec 6, 2019 at 8:37 AM Rich Bowen  wrote:

>
>
> On 12/4/19 5:56 PM, Issac Goldstand wrote:
> >
> > On Dec 4, 2019 22:15, Rich Bowen  wrote:
> >
> >
> > . But I've learned from Fedora user
> > groups that allowing any random stranger to start up a group, using
> our
> > Trademarks, to promote whatever message comes into their head, is
> > *going* to bite us in the butt, sooner rather than later.
> >
> > Are these from groups that are managed/overseen by RedHat? Can you share
> > more information about what you've learned the hard way? Because maybe
> > the way I suggest below is objectively wrong, and if so I'd rather
> > understand the faulty reasoning on my part sooner, rather than later...
>
> I'm reluctant to tell stories on a public list, particularly when almost
> all of the stories are third-hand. But the lesson learned is that when
> you give someone a title, there's a chance that they will take it as a
> fiefdom - a little kingdom where they rule, call the shots, and don't
> have to answer to anyone else.
>
> >
> > I've mentioned before that my standpoint is that it's impossible to
> > properly police every fan driven event out there, and I seem to recall
> > that use of a trademark by fans in a manner that isn't making profits is
> > generally considered acceptable use.  Is it not therefore a good-enoungh
> > way to start by allowing (CTR instead of RTC as it were)?
>
> Absolutely. We don't even *want* to police every fan event. And we want
> a LOT of fan events. The nuance is the moment we give our Official Seal
> Of Approval to a group/event/organization, then we are implicitly
> approving their message, and that's where we introduce audience confusion.
>
> >
> >
> > This is *NOT* about the Indore group and their recent event. Rather
> > it's
> > about the future. The groups currently out there are full of
> > experienced
> > Apache people. All well and good. The second wave will be full of
> > people
> > wanting to promote their business, or their personal brand, using our
> > name, and spreading misinformation about Apache under our official
> > banner.
> >
> > Once there is enough traction in the user groups that we can see a clear
> > difference between user (fan) groups that are promoting Apache vs groups
> > that are using the name to promote themselves, we could go with the
> > carrot and stick. The carrot is recognition and support by the ASF for
> > the good players, and the stick is trademark abuse complaints and
> > threats of legal action to those that don't.
> >
> > Or even just the stick.
> >
> > Because the carrot means having to make rules. And rules make life
> > harder for volunteers. Pulling off a successful meetup/event and
> > maintaining a successful community is hard enough without rules.
> > Sometimes rules are unavoidable, and so be it, but let's keep the
> > barrier of entry as low as possible for the amazing folks who are trying
> > to raise positive awareness of what we do here.
> >
> >
> > We *cannot* allow this to happen. To do so would be a dereliction of
> > our
> > duty as a PMC. We must plan for the bad actors, even while enabling
> the
> > good actors.
> >
> > Can we really expect to catch all the bad actors, long term? Especially
> > since anyone can go to meetup.com, register The Official Apache
> Software
> > Foundation Meetup of Somecity, Somecountry, tack on the feather logo,
> > and run with it with us none the wiser... Yes, we'd react swiftly and
> > forcefully once we *did* catch on, but we can't stop it from happening.
> > We can't monitor everything.
>
> No, we cannot expect to catch them all. But if, as I say above, give any
> group our Official Seal Of Approval, and give them space on OUR website,
> we are *explicitly* endorsing whatever they say. That's the line that
> cannot be crossed.
>
> >
> > We've gone 20 years without real traction in local small events that we
> > are happy with. Suddenly in the past week I'm seeing more interest than
> > we've had in years. Yes, we should have a plan for bad actors, but not
> > at the cost of stifling potentially good ones.
>
> +1
>
> > 

Re: Conference software

[Austin Bennett]

If that's licensed for many to use, great.

Beam had used https://sessionize.com -- which we were very happy with.
If not charging for the (Airflow) conference, sessionize comes at no
cost.  .


On Fri, Dec 27, 2019 at 3:16 AM Kevin A. McGrail  wrote:
>
> Yes, we just bought it for another year.  Cc'ing Rich Bowen to share info.
>
> On Fri, Dec 27, 2019, 04:25 Driesprong, Fokko  wrote:
>
> > Hi all,
> >
> > At the Apache Airflow project, we're looking at organizing two summits, one
> > in the US, and one in the EU. I've noticed that we're having some kind of
> > software for managing the sessions and the speakers:
> > https://aceu19.apachecon.com/schedule?day=2019-10-22
> >
> > My question is, does anyone know which software this is? And if this can be
> > used for any Apache related conferences like Airflow?
> >
> > Please let me know,
> >
> > Kind regards,
> > Fokko Driesprong
> >

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

Re: Update information on community.apache.org

[Austin Bennett]

Looks like would change the file
https://github.com/apache/comdev-site/blob/trunk/templates/standard.html

Still didn't read as to exactly the process for updating and getting the
site built, so I didn't put in a PR (to modify master and/or trunc).



On Sat, Feb 15, 2020 at 11:03 AM Tomasz Urbaszek 
wrote:

> Hi all,
>
> I've just spotted that footer on community page
> https://community.apache.org has "Copyright© 2018". I think this
> should be updated to avoid "this page is dead" feeling. Who should I
> contact to request the update?
>
> Best,
> Tomek Urbaszek
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Update information on community.apache.org

[Austin Bennett]

When looking at that code for the page, I had thought that perhaps would
not hard-code the year, but would use a javascript function to get the
date/year and include that when the site gets rendered -- but that makes
sense in my head, which easily doesn't translate to being
easy-to-impliment.

On Sun, Feb 16, 2020 at 1:39 PM Tomasz Urbaszek 
wrote:

> Thanks for the quick response! It seems that https://www.apache.org is
> also little bit out of date (2019 instead of 2020). Is there any
> possibility to use some auto-update?
>
> T.
>
>
> On Sun, Feb 16, 2020 at 3:51 PM Shane Curcuru 
> wrote:
> >
> > Roy Lenferink wrote on 2020-2-16 6:34AM EST:
> > > Following the WEBSITE-HOWTO [1] I just updated the year from 2018 to
> 2020.
> > > However, a comdev-er still needs to publish the site [2] as I was
> unable to.
> > > "svnmucc: E175013: Access to
> > >
> '/repos/infra/!svn/txr/1056611-mpm7/websites/production/community/content'
> > > forbidden"
> >
> > Done!  Excellent instructions, I had forgotten about the cms publish
> > links.  Thanks to Tomasz for reporting.
> >
> > > [1] https://github.com/apache/comdev-site/blob/trunk/WEBSITE-HOWTO.txt
> > > [2] https://cms.apache.org/community/publish?diff=1
> >
> > --
> >
> > - Shane
> >   Comdev PMC
> >   The Apache Software Foundation
> >
> > -
> > 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: [VOTE] Move community.a.o site from CMS/SVN to Hugo/Git

[Austin Bennett]

+1 (non-binding)

On Sat, Feb 22, 2020 at 4:48 AM Bertrand Delacretaz 
wrote:

> On Sat, Feb 22, 2020 at 12:11 PM Roy Lenferink 
> wrote:
> > [X ] +1 for moving over from the CMS/svn to Hugo/git...
>
> I'm not familiar with Hugo but it's well known and looking at
> https://github.com/apache/comdev-site/pull/5 it doesn't look hard to
> manage.
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

ASF Slack for community?

[Austin Bennett]

Hi Apache CommDev,

Unsure if this is the right place, but starting here...

Working on building Apache Beam's community, and have a forthcoming
https://beamsummit.org

The event is virtual, and we would like to invite attendees (potentially a
few hundred) to use some sort of messaging and likely slack to interact
with eachother/speakers/etc during the event.

We had thought ASF slack would be great, as we have many #beam channels,
and also with people signing up might get additional exposure to additional
projects and the foundation overall.  Is there any issues in us using
https://s.apache.org/slack-invite  for
this purpose (we'd then create some #beamsummit... channels, etc)?

Thanks,
Austin

Re: ASF Slack for community?

[Austin Bennett]

Hi Jarek,  Great to hear -- my hope would be that Beam intends to
use/grow/play well with the overall Apache Community.  We don't currently
have our own Slack community, though that is also a possibility to setup.
I am imagining it is better if those users are in ASF and therefore might
attend to and collaborate with/contribute to other projects as well.



On Mon, Jul 13, 2020 at 11:53 AM Jarek Potiuk  wrote:

> Just a comment from the Apache Airflow Summit that is half-way through.
>
> I think by not using Beam slack you are missing some opportunity to bring
> people in your slack :). I just got an email from Slack that we got 562 new
> members added last week :).
>
> J.
>
>
> On Mon, Jul 13, 2020 at 7:26 PM Rich Bowen  wrote:
>
> >
> >
> > On 7/13/20 1:03 PM, Austin Bennett wrote:
> > > Hi Apache CommDev,
> > >
> > > Unsure if this is the right place, but starting here...
> > >
> > > Working on building Apache Beam's community, and have a forthcoming
> > > https://beamsummit.org
> > >
> > > The event is virtual, and we would like to invite attendees
> (potentially
> > a
> > > few hundred) to use some sort of messaging and likely slack to interact
> > > with eachother/speakers/etc during the event.
> > >
> > > We had thought ASF slack would be great, as we have many #beam
> channels,
> > > and also with people signing up might get additional exposure to
> > additional
> > > projects and the foundation overall.  Is there any issues in us using
> > > https://s.apache.org/slack-invite <http://s.apache.org/slack-invite>
> for
> > > this purpose (we'd then create some #beamsummit... channels, etc)?
> >
> > the-asf.slack.com is the official Apache Slack instance, and is owned by
> > Infra. I *think* they'd be ok with this, but it might be best to ask
> them.
> >
> > I also have to make my obligatory remark that I really wish you would
> > have considered incorporating your content into ApacheCon again this
> year.
> >
> > --
> > Rich Bowen - rbo...@rcbowen.com
> > @rbowen
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
> >
>
> --
> +48 660 796 129
>

Re: ASF Slack for community?

[Austin Bennett]

Thanks, Julian,

Ultimately, my question comes down to: is it OK to point people interested
in events for specific (in this case Beam) events to the communication
platform used by the wider asf community.  I figure it is ideal to expand
the overall Apache tent/community.  Though there are certainly tradeoffs.

Unless needed, the question of which platform for the foundation to use
seems a separate discussion.

Cheers,
Austin




On Thu, Jul 16, 2020 at 9:03 AM Julian Foad  wrote:

> On behalf of FOSS fans everywhere: please seriously consider using
> [Matrix], the Open federated standard system.  It's perfect for this
> sort of community, with bridges to Slack and IRC and many other systems.
>   In the last two years Matrix has leapt ahead of other contenders like
> XMPP and is becoming the Open system of choice adopted by organisations
> from Mozilla to universities and governments.
>
> It's a great platform for integrating the chat side, and even the
> presentation side through Jitsi, of online events.  The matrix devs do
> it and wrote a blog post describing how:
> https://matrix.org/docs/guides/running-online-events
>
> Before any of us risks pushing another FOSS community into the
> proprietary silo trap, let's pause and consider how we all would in fact
> be paying for it if it's "free as in beer".  I've been watching this
> space since five years ago when the FOSS alternatives were weak, and now
> I'm really excited to see that, with the overwhelming global need for
> such a thing, Matrix has grown strong and is accelerating rapidly.
>
> I would strongly encourage the ASF membership to deploy their own Matrix
> server ASAP as it's the perfect fit for this sort of organization.  I
> run a personal Matrix server and benefit from modern multi-device
> single-app access to all my IRC messaging (via a public bridge), all my
> WhatsApp messaging (via a private bridge), some private notes like
> diaries, as well as federated native Matrix messaging.
>
> I can give more detailed advice and put you in touch with specific
> contacts.
>
> - Julian
>
>
> See:
>
> * https://matrix.org -- for an introduction to Matrix
>
> * https://matrix.org/docs/guides/running-online-events -- see above
>
> * https://element.io/blog/welcome-to-element/ -- for an introduction to
> the top company/brand of Matrix services and apps (a bit like how Redhat
> is to Linux)
>
> * https://sifted.eu/articles/element-germany-deal/ -- news about big
> government deployments of Matrix
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: ASF Slack for community?

[Austin Bennett]

 this part
> > of the ASF Slack with the goal of growing the Beam community there and
> > expose people to the ASF overall, over splintering the community over
> > different Slack channels - this with the assumption in mind that it is
> > ok from an infrastructure POV. As community events grow (and hopefully
> > budget with it), I'd even propose we try and share burden of cost in
> > that direction in the future.
> >
> > On Fri, 17 Jul 2020 at 15:49, Austin Bennett
> > mailto:whatwouldausti...@gmail.com>>
> wrote:
> >
> > Thanks, Julian,
> >
> > Ultimately, my question comes down to: is it OK to point people
> > interested
> > in events for specific (in this case Beam) events to the
> communication
> > platform used by the wider asf community.  I figure it is ideal to
> > expand
> > the overall Apache tent/community.  Though there are certainly
> > tradeoffs.
> >
> > Unless needed, the question of which platform for the foundation
> > to use
> > seems a separate discussion.
> >
> > Cheers,
> > Austin
> >
> >
> >
> >
> > On Thu, Jul 16, 2020 at 9:03 AM Julian Foad  > <mailto:julianf...@apache.org>> wrote:
> >
> > > On behalf of FOSS fans everywhere: please seriously consider using
> > > [Matrix], the Open federated standard system.  It's perfect for
> this
> > > sort of community, with bridges to Slack and IRC and many other
> > systems.
> > >   In the last two years Matrix has leapt ahead of other
> > contenders like
> > > XMPP and is becoming the Open system of choice adopted by
> > organisations
> > > from Mozilla to universities and governments.
> > >
> > > It's a great platform for integrating the chat side, and even the
> > > presentation side through Jitsi, of online events.  The matrix
> > devs do
> > > it and wrote a blog post describing how:
> > > https://matrix.org/docs/guides/running-online-events
> > >
> > > Before any of us risks pushing another FOSS community into the
> > > proprietary silo trap, let's pause and consider how we all would
> > in fact
> > > be paying for it if it's "free as in beer".  I've been watching
> this
> > > space since five years ago when the FOSS alternatives were weak,
> > and now
> > > I'm really excited to see that, with the overwhelming global
> > need for
> > > such a thing, Matrix has grown strong and is accelerating rapidly.
> > >
> > > I would strongly encourage the ASF membership to deploy their
> > own Matrix
> > > server ASAP as it's the perfect fit for this sort of
> > organization.  I
> > > run a personal Matrix server and benefit from modern multi-device
> > > single-app access to all my IRC messaging (via a public bridge),
> > all my
> > > WhatsApp messaging (via a private bridge), some private notes like
> > > diaries, as well as federated native Matrix messaging.
> > >
> > > I can give more detailed advice and put you in touch with specific
> > > contacts.
> > >
> > > - Julian
> > >
> > >
> > > See:
> > >
> > > * https://matrix.org -- for an introduction to Matrix
> > >
> > > * https://matrix.org/docs/guides/running-online-events -- see
> above
> > >
> > > * https://element.io/blog/welcome-to-element/ -- for an
> > introduction to
> > > the top company/brand of Matrix services and apps (a bit like
> > how Redhat
> > > is to Linux)
> > >
> > > * https://sifted.eu/articles/element-germany-deal/ -- news about
> big
> > > government deployments of Matrix
> > >
> > >
> > -
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > <mailto:dev-unsubscr...@community.apache.org>
> > > For additional commands, e-mail: dev-h...@community.apache.org
> > <mailto:dev-h...@community.apache.org>
> > >
> > >
> >
>
>

Re: ASF Slack for community?

[Austin Bennett]

Dear Infra:

Can you please confirm we would not be terrible community members by using
the slack for our stated and intended purpose?

Since this is an event to grow the community, we need to ensure the uptime
of s.apache.org/slack-invite throughout, so verifying we are playing nicely
to avoid issues (for pettier individuals or if viewed as not playing nice,
I would be very concerned about that uptime, because downtime during the
event would have negative consequences for growing the Beam [and by
relation, collaboration] the Apache community.  Also, ASF is also a
"community partner" for the event, for whatever that is worth.


Furthermore, letting this start a kickoff for discussion if useful to
establish up an additional link or method to track, ex:
s.apache.org/beam-summit-slack-invite - if we are worried about [desire
for] attributing signups.  I suspect that's overkill (and would rather
not), but am willing to code that up for the foundation, if that helps this
get done.

Thanks,
Austin




P.S.  Thanks, Roy.




On Mon, Jul 27, 2020 at 10:31 AM Roy Lenferink 
wrote:

> Also keep in mind that Slack uses a Fair Billing Policy [1]. You won't be
> billed for inactive members (inactive being if a member didn't use its
> Slack account in over 14 days).
> Having a certain number of users join during/after a conference they
> probably all have useful input for the Beam community (code, documentation,
> presentation or as a potential Beam user).
> In the first couple of weeks after the conference most of that input will
> probably be collected (the yay factor for new projects). And if not they
> will probably go inactive and you won't be billed for them.
>
> So I agree with Austin here, does the cost of adding the users outweigh
> the addition of potential new contributors.
>
> Also, if the cost of Slack is becoming too much for the ASF (don't know if
> we have a sponsored instance?), how about e.g. Mattermost [2][3] as a
> self-hosted alternative (or only for conferences) ? Just throwing some
> ideas out there..
>
> - Roy
>
> [1]
> https://slack.com/intl/en-nl/help/articles/218915077-Fair-Billing-Policy
> [2] https://github.com/mattermost/mattermost-server
> [3] https://mattermost.com/
>
> Op ma 27 jul. 2020 om 18:31 schreef Austin Bennett <
> whatwouldausti...@gmail.com>:
>
>> Hi All,
>>
>> My intent would be to use this ASF Resource for communication of
>> potential newcomers to the Beam community (and with the hope that they
>> become involved with the foundation overall), looking to state that
>> clearly.
>>
>> Cost is a reasonable argument -- but I need to question whether the
>> financial costs outweigh the potential benefits, and therefore looking to
>> make explicit the purpose of the Slack Community, if this is something we
>> are going to be told not to do.
>>
>>
>> As a thought exercise/perspective; please bear with the following -->
>>
>> * I have been in the ASF Slack long before I was a committer on the
>> project.
>> * There is lots of activity in the ASF Slack Beam channels from
>> non-committers (and a way to identify future committers, based on positive
>> interactions with the community).
>> * I lead workshops (in most cases personal free/volunteer time) on
>> getting involved with contributing to OpenSource/ASF/Beam, and I certainly
>> point all attendees to the training to ASF Slack channel (as well as
>> mailing lists) -- should I not be doing that?
>>
>> One potentially useful, but not great analogy would be traditional
>> funnels and conversion rates -- would like to build a funnel and community
>> for Beam (and serving ASF more generally), people that are
>> interested/curious, some of which will convert to maintaining activity ->
>> learning more -> chatting with others -> contributing
>> docs/use-case/bugs/code -> becoming committers -> etc...  In that light,
>> you can see how there are benefits for this to be the start of an
>> interaction and journey for people to get involved with the foundation?
>> That is at least my goal/motivation.
>>
>> How do we distinguish users in this case (say anyone I point to the Slack
>> channels as a way to start following a community and getting involved in
>> discussions), from a broader conference attendee (in the cases, such
>> workshops are often at conferences)?  Why would we exclude people/purpose?
>>
>> Do my aims make sense?  Is growing the ASF community in this manner not
>> supported by the infrastructure?  If Slack is not a useful common tool that
>> we can point anyone to, should we be using it?  Or, at least can someone
>> provide

Re: Microsoft Commerce + Ecosystems Pride Tech Talk Opportunity

[Austin Bennett]

+divers...@apache.org 

On Wed, Mar 23, 2022 at 9:03 AM Nina Reynolds
 wrote:

> Hello,
>
>
>
> My name is Nina Reynolds; I am a software engineer in Microsoft’s Commerce
> + Ecosystems division, and a Chapter Lead at the Commerce + Ecosystems
> GLEAM (Global LGBTQI+ Employees and Allies at Microsoft) ERG.
>
>
>
> In June, we are hosting a series of pride events, and I’m trying to see
> who I can assemble for a panel working-titled “Pride for Techies.”
>
>
>
> I’m contacting people within open source organizations important to the
> organization’s software stack to see if someone is interested in a paid
> speaking opportunity and is either:
>
>- A member of the LGBTQI+ community who wants to speak deeply about a
>technical topic in this space
>- A contributor who is willing to speak on their diversity, equity,
>and inclusion efforts in the open source community as it pertains to
>LGBQTI+ contributors
>
>
>
> Internally, we and our friends in Data are big fans of Apache Spark,
> Parquet, and Kafka, so a member of the Apache contributor or DEI community
> would be awesome!
>
>
>
> Thank you for your time,
>
>
>
>
>
> _
>
> 🌸🌺🌸
>
> _
>
> *Nina Reynolds*
>
> Software Engineer II
>
>
>

Re: Microsoft Commerce + Ecosystems Pride Tech Talk Opportunity

[Austin Bennett]

+d...@diversity.apache.org 

On Wed, Mar 23, 2022 at 9:03 AM Nina Reynolds
 wrote:

> Hello,
>
>
>
> My name is Nina Reynolds; I am a software engineer in Microsoft’s Commerce
> + Ecosystems division, and a Chapter Lead at the Commerce + Ecosystems
> GLEAM (Global LGBTQI+ Employees and Allies at Microsoft) ERG.
>
>
>
> In June, we are hosting a series of pride events, and I’m trying to see
> who I can assemble for a panel working-titled “Pride for Techies.”
>
>
>
> I’m contacting people within open source organizations important to the
> organization’s software stack to see if someone is interested in a paid
> speaking opportunity and is either:
>
>- A member of the LGBTQI+ community who wants to speak deeply about a
>technical topic in this space
>- A contributor who is willing to speak on their diversity, equity,
>and inclusion efforts in the open source community as it pertains to
>LGBQTI+ contributors
>
>
>
> Internally, we and our friends in Data are big fans of Apache Spark,
> Parquet, and Kafka, so a member of the Apache contributor or DEI community
> would be awesome!
>
>
>
> Thank you for your time,
>
>
>
>
>
> _
>
> 🌸🌺🌸
>
> _
>
> *Nina Reynolds*
>
> Software Engineer II
>
>
>

Re: First contribution campaign collab?

[Austin Bennett]

Happy to help.  Along with mentoring in Google Summer of Code, I've led
workshops in a number of capacities and conferences/venues/countries ( Beam
Summit, HOPE , etc ) on helping people get their first
code contribution into a[n apache :-) ] project, outlining general paths
for contributing, and community overall.  Though concretely getting a PR
created and merged is very straightforward, I also try to highlight the
many ways to contribute that are not code.  Interacting people right as
they are addressing could prove useful and yield interesting stories, and
there are ways to cast a net to find people that might want to opt into the
initiative for sharing about their first contribution that is much 'lower
touch'.


To the specifics of publicizing/amplifying what is already happening:  for
GitHub based projects, there are very low effort ways to let first-time-PR
contributors know to opt-in/contact marketing.  For example, see:
https://github.com/behaviorbot/first-pr-merge ...  and specifically: '
firstPRMergeComment'.  It would potentially be easy for any project to add
that, along with a message to contact
ComDev/P&M/specific-contact-information?  The thought is that would help
grow our communities?  Should we get a general recipe together for projects
can add this to their repos ( in that case, where to point
first-time-contributors, a specific email/other?) ?  Then, potentially just
a matter of getting potentially interested PMCs to add to their repos.


My only concern would be ensuring that this gets updated/removed from
repos, once no longer an initiative from p&m.  Said another way, if asking
new contributors to contact someone, we need those people to be responsive,
else it needs to be updated/removed.



On Tue, Sep 27, 2022 at 12:02 PM Jarek Potiuk  wrote:

> Great idea.
>
> Happy to help with publicising and with reaching out to our contributors. I
> can get some good examples from the past and current (we have a
> more-or-less constant stream of new contributors at Airflow (in the order
> of 10 new contributors a week I think).
> Also happy to brainstorm/discuss at ApacheCon - we have a talk with Ismael
> "Growing your contributor's base" which is pretty relevant.
>
> We also just started an initiative together with a few people from Apache
> Beam (something that I wanted to mention at the talk) that we want to start
> measuring the behaviours of contributors, discussions, etc and eventually
> turn it into a tool of sorts that will help commiters and PMC members and
> encourage/engage new contributors or prospective contributors to our
> projects to continue/grow/make their first serious contributions. We could
> likely connect those efforts somehow. There is a (rather little) chance we
> will have some very early dashboard prototype by the ApacheCon, but I think
> all involved people will be at the ApacheCon and maybe we will find time to
> talk about it :)?
>
> J.
>
>
> On Tue, Sep 27, 2022 at 6:47 PM Rich Bowen  wrote:
>
> > This is certainly something that we have talked about over the years,
> > but never got around to, so having M&P providing some steam behind
> > this is very welcome.
> >
> > One of the things that seems important is making sure that projects
> > are also engaged - or, more specifically, that we only promote first-
> > contrib for projects that are engaged. I say this because we had some
> > first contributor stuff around a recent Apachecon, and the target
> > project almost rejected the whole lot because it was "pizzas we didn't
> > order" and they hadn't been involved in the conversation. We managed
> > to get them to review and accept most of the contributions,
> > eventually, but it was an awkward situation.
> >
> > Anyways, count me in for mentoring and whatever, although time may be
> > limited.
> >
> > --Rich
> >
> > On Tue, 2022-09-27 at 11:23 -0400, Joe Brockmeier wrote:
> > > Hi all,
> > >
> > > We (M&P) would like to propose a collaboration with ComDev about
> > > encouraging new contributions to ASF projects.
> > >
> > > Melissa Logan and the Constantia team have drafted a set of
> > > messaging
> > > and plan for the campaign with an objective of reaching 50 or more
> > > people to share their first contribution to an ASF project on social
> > > media, etc.
> > >
> > > Much of this activity is happening *anyway* but we'd like to
> > > recognize
> > > and encourage it. I'd like to do that with ComDev to:
> > >
> > > 1) Amplify the effort: If folks in ComDev would like to participate
> > > in
> > > mentoring, boosting the signal on social media, and/or helping with
> > > the marketing side of things that would be awesome.
> > > 2) Get input: As I said, people are already making their first
> > > contributions and we could solicit contributors to speak up - but
> > > I'd
> > > like to make sure the campaign is aligned with ComDev!
> > > 3) Avoid unwelcome surprises! This is an area with a lot of overlap
> > > and we didn't want to spring it

Re: First contribution campaign collab?

[Austin Bennett]

If auto-messaging first time contributors on their first merge, is there a
specific message you'd like to 'advertise'/suggest that they reach out to
P&M ( including contact method )?

On Tue, Sep 27, 2022 at 2:41 PM Melissa Logan  wrote:

> Great input, please keep it coming. Others, let us know if you/your
> community would like to participate.
>
> One of the things that seems important is making sure that projects
> are also engaged - or, more specifically, that we only promote first-
> contrib for projects that are engaged.
> > Rich, great feedback and we will be using this approach. And thanks for
>
> Happy to help with publicising and with reaching out to our contributors. I
> can get some good examples from the past and current (we have a
> more-or-less constant stream of new contributors at Airflow (in the order
> of 10 new contributors a week I think).
> > Jarek, fantastic! We will be in touch.
>
> We also just started an initiative together with a few people from Apache
> Beam (something that I wanted to mention at the talk) that we want to start
> measuring the behaviours of contributors, discussions, etc and eventually
> turn it into a tool of sorts that will help commiters and PMC members and
> encourage/engage new contributors or prospective contributors to our
> projects to continue/grow/make their first serious contributions.
> > Jarek, please do keep us informed as this progresses. There are
> additional ways M&P could help promote.
>
> Though concretely getting a PR
> created and merged is very straightforward, I also try to highlight the
> many ways to contribute that are not code.  Interacting people right as
> they are addressing could prove useful and yield interesting stories, and
> there are ways to cast a net to find people that might want to opt into the
> initiative for sharing about their first contribution that is much 'lower
> touch'.
> > Austin, we agree completely. We would like to highlight all types of
> contributions.
>
> Should we get a general recipe together for projects
> can add this to their repos ( in that case, where to point
> first-time-contributors, a specific email/other?) ?
> > This is an interesting idea. Some projects may have a workflow/docs in
> place; let's find out! This campaign could serve the dual purpose of
> enabling us to aggregate best practices across communities for first-time
> contributors.
>
> On Tue, Sep 27, 2022 at 1:52 PM Austin Bennett
>  wrote:
> >
> > Happy to help.  Along with mentoring in Google Summer of Code, I've led
> > workshops in a number of capacities and conferences/venues/countries (
> Beam
> > Summit, HOPE <https://hope.net/>, etc ) on helping people get their
> first
> > code contribution into a[n apache :-) ] project, outlining general paths
> > for contributing, and community overall.  Though concretely getting a PR
> > created and merged is very straightforward, I also try to highlight the
> > many ways to contribute that are not code.  Interacting people right as
> > they are addressing could prove useful and yield interesting stories, and
> > there are ways to cast a net to find people that might want to opt into
> the
> > initiative for sharing about their first contribution that is much 'lower
> > touch'.
> >
> >
> > To the specifics of publicizing/amplifying what is already happening:
> for
> > GitHub based projects, there are very low effort ways to let
> first-time-PR
> > contributors know to opt-in/contact marketing.  For example, see:
> > https://github.com/behaviorbot/first-pr-merge ...  and specifically: '
> > firstPRMergeComment'.  It would potentially be easy for any project to
> add
> > that, along with a message to contact
> > ComDev/P&M/specific-contact-information?  The thought is that would help
> > grow our communities?  Should we get a general recipe together for
> projects
> > can add this to their repos ( in that case, where to point
> > first-time-contributors, a specific email/other?) ?  Then, potentially
> just
> > a matter of getting potentially interested PMCs to add to their repos.
> >
> >
> > My only concern would be ensuring that this gets updated/removed from
> > repos, once no longer an initiative from p&m.  Said another way, if
> asking
> > new contributors to contact someone, we need those people to be
> responsive,
> > else it needs to be updated/removed.
> >
> >
> >
> > On Tue, Sep 27, 2022 at 12:02 PM Jarek Potiuk  wrote:
> >
> > > Great idea.
> > >
> > > Happy to help with publicising and with 

Re: First contribution campaign collab?

[Austin Bennett]

Also, where should the ticket/issue get filed?  Is this comdev?  Is there
Jira/GH-issues for Comdev and/or P&M?  Naturally, also in relevant
projects' codebases if implemented.

This doesn't seem the right location, as it seems a collection of issues
related to many individual projects?
https://issues.apache.org/jira/projects/COMDEV/



On Tue, Sep 27, 2022 at 3:35 PM Austin Bennett 
wrote:

> If auto-messaging first time contributors on their first merge, is there a
> specific message you'd like to 'advertise'/suggest that they reach out to
> P&M ( including contact method )?
>
> On Tue, Sep 27, 2022 at 2:41 PM Melissa Logan 
> wrote:
>
>> Great input, please keep it coming. Others, let us know if you/your
>> community would like to participate.
>>
>> One of the things that seems important is making sure that projects
>> are also engaged - or, more specifically, that we only promote first-
>> contrib for projects that are engaged.
>> > Rich, great feedback and we will be using this approach. And thanks for
>>
>> Happy to help with publicising and with reaching out to our contributors.
>> I
>> can get some good examples from the past and current (we have a
>> more-or-less constant stream of new contributors at Airflow (in the order
>> of 10 new contributors a week I think).
>> > Jarek, fantastic! We will be in touch.
>>
>> We also just started an initiative together with a few people from Apache
>> Beam (something that I wanted to mention at the talk) that we want to
>> start
>> measuring the behaviours of contributors, discussions, etc and eventually
>> turn it into a tool of sorts that will help commiters and PMC members and
>> encourage/engage new contributors or prospective contributors to our
>> projects to continue/grow/make their first serious contributions.
>> > Jarek, please do keep us informed as this progresses. There are
>> additional ways M&P could help promote.
>>
>> Though concretely getting a PR
>> created and merged is very straightforward, I also try to highlight the
>> many ways to contribute that are not code.  Interacting people right as
>> they are addressing could prove useful and yield interesting stories, and
>> there are ways to cast a net to find people that might want to opt into
>> the
>> initiative for sharing about their first contribution that is much 'lower
>> touch'.
>> > Austin, we agree completely. We would like to highlight all types of
>> contributions.
>>
>> Should we get a general recipe together for projects
>> can add this to their repos ( in that case, where to point
>> first-time-contributors, a specific email/other?) ?
>> > This is an interesting idea. Some projects may have a workflow/docs in
>> place; let's find out! This campaign could serve the dual purpose of
>> enabling us to aggregate best practices across communities for first-time
>> contributors.
>>
>> On Tue, Sep 27, 2022 at 1:52 PM Austin Bennett
>>  wrote:
>> >
>> > Happy to help.  Along with mentoring in Google Summer of Code, I've led
>> > workshops in a number of capacities and conferences/venues/countries (
>> Beam
>> > Summit, HOPE <https://hope.net/>, etc ) on helping people get their
>> first
>> > code contribution into a[n apache :-) ] project, outlining general paths
>> > for contributing, and community overall.  Though concretely getting a PR
>> > created and merged is very straightforward, I also try to highlight the
>> > many ways to contribute that are not code.  Interacting people right as
>> > they are addressing could prove useful and yield interesting stories,
>> and
>> > there are ways to cast a net to find people that might want to opt into
>> the
>> > initiative for sharing about their first contribution that is much
>> 'lower
>> > touch'.
>> >
>> >
>> > To the specifics of publicizing/amplifying what is already happening:
>> for
>> > GitHub based projects, there are very low effort ways to let
>> first-time-PR
>> > contributors know to opt-in/contact marketing.  For example, see:
>> > https://github.com/behaviorbot/first-pr-merge ...  and specifically: '
>> > firstPRMergeComment'.  It would potentially be easy for any project to
>> add
>> > that, along with a message to contact
>> > ComDev/P&M/specific-contact-information?  The thought is that would help
>> > grow our communities?  Should we get a general recipe together for
>> projec

Re: Use GitLab, not GitHub

[Austin Bennett]

Not taking a stance on any migration; can't help but wondering:  What
prevents GitLab from getting to the point where GitHub is now and in the
future an equivalent push is to be suggested to move away from GitLab?



On Mon, Feb 18, 2019 at 9:23 AM Jorge Betancourt 
wrote:

> Hi,
>
> It is true that Github is, at the end of the day, a commercial entity, and
> that we're placing valuable metadata, regarding the changes that eventually
> will end up being maintained by the members of our projects. Like Rich said
> there is a great value on being reachable to outside contributors, and
> right now I would say that a lot of them find use through Github because at
> this point is a very logical assumption (from the user's point of view).
>
> I've seen that some projects (I've seen this on Nutch) mirror the
> interactions on Github into Jira, at least as long as the PR is linked to
> the appropriate issue in Jira, that way we still keep the conversation
> around the proposed changes in our control. The integration could be
> improved but I think this protects us partially. Perhaps this could be used
> by more/all projects? At least it could be included in the contributions
> guidelines of our repositories.
>
> Best Regards,
> Jorge
>
> On Mon, Feb 18, 2019 at 3:39 PM Rich Bowen  wrote:
>
> >
> >
> > On 2/18/19 9:30 AM, Julian Foad wrote:
> > > Thanks for your comments, Rich.
> > >
> > > Re. "owning our data": we do own our source code but what about all the
> > conversational metadata in GH? In the Subversion project we have a GH
> > mirror of the code but pull requests and code comments etc. in GH aren't
> > even copied to the Subversion PMC mailing lists, apart from the first
> > message in each PR which is; these are known limitations.
> >
> > Indeed. This is a very good point.
> >
> > >
> > > Re. "infra": infra is here to create and manage the infra to support
> the
> > projects' wants and needs; I am speaking here to the community to try to
> > influence their wants and needs.
> >
> > Yeah, I would also like to see us move away from GitHub. But the
> > argument that it's where people look first, is compelling. Perhaps we
> > can be influential in changing that? I don't know.
> >
> >
> >
> > --
> > Rich Bowen - rbo...@rcbowen.com
> > http://rcbowen.com/
> > @rbowen
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
> >
>

Diversity / Inclusion

[Austin Bennett]

Hi Apache Community,

This is related to recent discussions, but I'm looking for practical
suggestions for a concrete initiative, so not jumping in on those threads.

Working with the administration at a local community college - looking at
methods for training some English as a second language - and immigrant (to
the USA) - students to learn things coding/computing.  Computer Science is
an 'impacted' major, meaning students are not even able to gain access to
those classes, so there is motivation to figure out how to expand those
capabilities.

This has me exploring putting things together to train these students.
Outside of the technical skills, I am imagining teaching them about (and
encourage living by) the Apache Way, and thoughts around encouraging this
mentality from the outset ("meritocracy" as a quite loaded word, for
example).  It seems such awareness would be beneficial to people as they
are learning (and anyone); In addition this might serve as a pipeline for
the future for people that would contribute positively to Apache.

Anything else I should be looking at outside of the website:
https://community.apache.org ?

Thanks,
Austin

Re: Diversity / Inclusion

[Austin Bennett]

Thanks, Bertrand,

I had found it and subscribed when it was mentioned, and had seen the
thread circulating this morning.  It hadn't seemed like much was formalized
there (from what I had read in the archives), but I should just post a
similar message to that group and see what happens!  (thanks for the nudge)



On Mon, Apr 1, 2019 at 4:29 AM Bertrand Delacretaz 
wrote:

> On Sun, Mar 31, 2019 at 3:38 PM Roy Lenferink 
> wrote:
> > ...Since a month we have got a training podling as well
>
> FWIW that mailing list is at
> https://lists.apache.org/list.html?d...@training.apache.org
>
> -Bertrand
>

Re: ACNA Hackathon - Volunteer(s) needed

[Austin Bennett]

Great to hear this is coming together.  I'm happy to help getting movement
from the Beam Community.

Very interested to hear concrete plans for hackathon, it will inform the
rest of what content we offer in the Beam tracks.  At prior beam summits
(ex: beamsummit.org), we've had intro to contributing workshops, and
working with (hands-on) beam.  We think these things are good for people to
do, though it sounds like getting setup for contributing code would largely
be covered in a hackathon?  What about getting something working -- hacking
on a project (ex: getting a beam pipeline or something like a spark ml job
running).

Wanting to ensure that we don't unnecessarily have overlapping/competing
content.

@rob, @Kevin, @Steve -- maybe let me know as you start to get this worked
out.  Happy to attempt to listen in on history lesson, should you arrange
something with @rich.

On Mon, May 27, 2019 at 1:55 PM Rich Bowen  wrote:

> Awesome. It sounds like we have the three hackathon leads/volunteers -
> Rob Tompkins, Steve Blackmon, and Kevin McGrail - which seems like the
> ideal number for a leadership group. Do feel free to recruit more
> volunteers to help with the work. I'll reach out every month for updates
> for my board report.
>
> And, of course, I'm very willing to share history, expectations,
> insight, advice, and so on. And you, in turn, are very welcome to take
> the reins and drive it in a new direction if you have the inspiration to
> do so.
>
> Thanks!
>
> On 5/27/19 1:35 PM, Steve Blackmon wrote:
> > I am willing to lead (or to assist) hackathon coordination.  I have
> participated over the past several years and run similar local events, so I
> think I have a decent idea of what needs to happen on site, and believe I
> can do a decent job of motivating project participation.
> >
> > The more volunteers the better I suspect, as there will be a lot of
> threads to start and follow-up on.
> > On May 27, 2019, 9:37 AM -0500, Rob Tompkins ,
> wrote:
> >>
> >>
> >>> On May 27, 2019, at 7:50 AM, Rich Bowen  wrote:
> >>>
> >>>
> >>>
>  On 5/27/19 9:45 AM, Kevin A. McGrail wrote:
>  Is the hackathon run all the days of the event?
> >>>
> >>> Yes. All day, every day, in Laughlin 3. Round tables. Power and
> network. Nothing else provided.
> >>>
> >>
> >> Happy to help on this one. As I haven’t owned anything like this, I’ll
> need guidance.
> >>
> >> -Rob
> >>
>  --
>  Kevin A. McGrail
>  Member, Apache Software Foundation
>  Chair Emeritus Apache SpamAssassin Project
>  https://www.linkedin.com/in/kmcgrail - 703.798.0171
> > On Mon, May 27, 2019 at 9:44 AM Rich Bowen 
> wrote:
> > I need 1 to 3 volunteers to own the Hackathon for ACNA.
> >
> > The Hackathon has long been a central part of ApacheCon. However, the
> > success of the hackathon waxes and wanes over the years, due largely
> to
> > whether someone steps up to drive it.
> >
> > The hackathon has multiple intertwined purposes:
> >
> > * Attract and mentor new committers
> > * Strengthen personal bonds within project community
> > * Foster cross-project cooperation
> > * Knock out difficult bugs/features/documentation projects
> >
> > For this to be successful, the following things need to happen
> >
> > * Projects need to know about it
> > * They need to prepare ahead of time. In particular, they need to
> think
> > about what they will be working on
> > * The plan (ie, what we'll be working on) must be promoted both
> within
> > the project (so that core project members show up prepared) and
> outside
> > (so that curious people show up and play along)
> > * There needs to be great signage on-site, and we need to mention it
> at
> > every plenary
> >
> > To this end, I need someone(s) to step up to own this. I do not have
> > time to be the point person on this.
> >
> > I need someone who cares about building project communities, is
> > enthusiastic about working directly with projects to build their
> > hackathon plans, and who plans to attend ACNA to do the on-site stuff
> > necessary to support the above. I need someone who is willing to take
> > the reins on this and drive it without much direction from me or
> anyone
> > else, and just report back periodically on progress.
> >
> > Please let me know if you are willing to lead this effort. Thank you.
> >
> > (Note: If you're on the other side of the pond, I expect that Myrle
> will
> > also be looking for someone to do this for ACEU, too.)
> >
> > --
> > Rich Bowen - rbo...@rcbowen.com
> > http://rcbowen.com/
> > @rbowen
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
> >
> >>>
> >>> --
> >>> Rich Bowen 

Re: ACNA Hackathon - Volunteer(s) needed

[Austin Bennett]

Hi Rich,

Great; sounds like we'll plan on a hands-on developing things *in*/*using*
Beam.  What about contributing workshop?  It sounds like a Hackathon space
might help people understand things like: specifics of getting Jira
username, finding issues, ?signing ICLA?, knowing to subscribe to dev/user
lists, etc?  Many of us not having attended previous ApacheCon(s) are
unsure the audience, alternate tracks, etc etc.

Cheers,
Austin



On Tue, May 28, 2019 at 5:35 AM Rich Bowen  wrote:

>
>
> On 5/27/19 6:11 PM, Austin Bennett wrote:
> > Great to hear this is coming together.  I'm happy to help getting
> movement
> > from the Beam Community.
> >
> > Very interested to hear concrete plans for hackathon, it will inform the
> > rest of what content we offer in the Beam tracks.  At prior beam summits
> > (ex: beamsummit.org), we've had intro to contributing workshops, and
> > working with (hands-on) beam.  We think these things are good for people
> to
> > do, though it sounds like getting setup for contributing code would
> largely
> > be covered in a hackathon?  What about getting something working --
> hacking
> > on a project (ex: getting a beam pipeline or something like a spark ml
> job
> > running).
> >
> > Wanting to ensure that we don't unnecessarily have overlapping/competing
> > content.
> >
> > @rob, @Kevin, @Steve -- maybe let me know as you start to get this worked
> > out.  Happy to attempt to listen in on history lesson, should you arrange
> > something with @rich.
>
> The kind of session you're talking about - hands-on, mentored workshops
> - are awesome and encouraged, and do not, in my opinion, conflict with a
> more passive "come join us" central hackathon space. Indeed, they
> complement one another, and each should promote the other.
>
>
> >
> > On Mon, May 27, 2019 at 1:55 PM Rich Bowen  wrote:
> >
> >> Awesome. It sounds like we have the three hackathon leads/volunteers -
> >> Rob Tompkins, Steve Blackmon, and Kevin McGrail - which seems like the
> >> ideal number for a leadership group. Do feel free to recruit more
> >> volunteers to help with the work. I'll reach out every month for updates
> >> for my board report.
> >>
> >> And, of course, I'm very willing to share history, expectations,
> >> insight, advice, and so on. And you, in turn, are very welcome to take
> >> the reins and drive it in a new direction if you have the inspiration to
> >> do so.
> >>
> >> Thanks!
> >>
> >> On 5/27/19 1:35 PM, Steve Blackmon wrote:
> >>> I am willing to lead (or to assist) hackathon coordination.  I have
> >> participated over the past several years and run similar local events,
> so I
> >> think I have a decent idea of what needs to happen on site, and believe
> I
> >> can do a decent job of motivating project participation.
> >>>
> >>> The more volunteers the better I suspect, as there will be a lot of
> >> threads to start and follow-up on.
> >>> On May 27, 2019, 9:37 AM -0500, Rob Tompkins ,
> >> wrote:
> >>>>
> >>>>
> >>>>> On May 27, 2019, at 7:50 AM, Rich Bowen  wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>> On 5/27/19 9:45 AM, Kevin A. McGrail wrote:
> >>>>>> Is the hackathon run all the days of the event?
> >>>>>
> >>>>> Yes. All day, every day, in Laughlin 3. Round tables. Power and
> >> network. Nothing else provided.
> >>>>>
> >>>>
> >>>> Happy to help on this one. As I haven’t owned anything like this, I’ll
> >> need guidance.
> >>>>
> >>>> -Rob
> >>>>
> >>>>>> --
> >>>>>> Kevin A. McGrail
> >>>>>> Member, Apache Software Foundation
> >>>>>> Chair Emeritus Apache SpamAssassin Project
> >>>>>> https://www.linkedin.com/in/kmcgrail - 703.798.0171
> >>>>>>> On Mon, May 27, 2019 at 9:44 AM Rich Bowen 
> >> wrote:
> >>>>>>> I need 1 to 3 volunteers to own the Hackathon for ACNA.
> >>>>>>>
> >>>>>>> The Hackathon has long been a central part of ApacheCon. However,
> the
> >>>>>>> success of the hackathon waxes and wanes over the years, due
> largely
> >> to
> >>>>>>> whether someone steps up to drive it.

Re: ACNA Hackathon - Volunteer(s) needed

[Austin Bennett]

Yes, @Aizhamal I agree.

Though, It is largely unclear to me the things that are core Apache as part
of commons and those that might be project specific.  It is easy to take
the perspective of here's how a specific project works which is similar to
most others.  It is another to dig into all projects.  Perhaps incubator or
some other governance prescribes some bits?  I suspect, at a minimum, there
are differences between each/all projects.

Ex:
Differences???
* user@ is not required (anecdotally, since Airflow just got)
* Slack groups
* GitHub

Common???
* dev@
* JIRA



On Tue, May 28, 2019 at 3:38 PM Aizhamal Nurmamat kyzy 
wrote:

> Hi Rich,
>
> We are doing a contributor's workshop for Beam in the upcoming summit in
> Europe, but most of the content should be easily adjustable to any Apache
> projects. For example, instead of subscribing to dev@beam.a.o. we can
> teach them how to subscribe to dev@community.a.o. Introduction to ICLA,
> Jira, GitHub and other similar tools and processes should be the same
> across all projects. WDYT Austin?
>
>
> On Tue, May 28, 2019 at 3:28 PM Rich Bowen  wrote:
>
>> This sounds like a great thing to have as part of the hackathon. Perhaps
>> cover part of this at the start of each day? None of these things are
>> specific to Beam but apply to  all projects right?
>>
>> On Tue, May 28, 2019, 12:09 Austin Bennett 
>> wrote:
>>
>> > Hi Rich,
>> >
>> > Great; sounds like we'll plan on a hands-on developing things
>> *in*/*using*
>> > Beam.  What about contributing workshop?  It sounds like a Hackathon
>> space
>> > might help people understand things like: specifics of getting Jira
>> > username, finding issues, ?signing ICLA?, knowing to subscribe to
>> dev/user
>> > lists, etc?  Many of us not having attended previous ApacheCon(s) are
>> > unsure the audience, alternate tracks, etc etc.
>> >
>> > Cheers,
>> > Austin
>> >
>> >
>> >
>> > On Tue, May 28, 2019 at 5:35 AM Rich Bowen  wrote:
>> >
>> >>
>> >>
>> >> On 5/27/19 6:11 PM, Austin Bennett wrote:
>> >> > Great to hear this is coming together.  I'm happy to help getting
>> >> movement
>> >> > from the Beam Community.
>> >> >
>> >> > Very interested to hear concrete plans for hackathon, it will inform
>> the
>> >> > rest of what content we offer in the Beam tracks.  At prior beam
>> summits
>> >> > (ex: beamsummit.org), we've had intro to contributing workshops, and
>> >> > working with (hands-on) beam.  We think these things are good for
>> >> people to
>> >> > do, though it sounds like getting setup for contributing code would
>> >> largely
>> >> > be covered in a hackathon?  What about getting something working --
>> >> hacking
>> >> > on a project (ex: getting a beam pipeline or something like a spark
>> ml
>> >> job
>> >> > running).
>> >> >
>> >> > Wanting to ensure that we don't unnecessarily have
>> overlapping/competing
>> >> > content.
>> >> >
>> >> > @rob, @Kevin, @Steve -- maybe let me know as you start to get this
>> >> worked
>> >> > out.  Happy to attempt to listen in on history lesson, should you
>> >> arrange
>> >> > something with @rich.
>> >>
>> >> The kind of session you're talking about - hands-on, mentored workshops
>> >> - are awesome and encouraged, and do not, in my opinion, conflict with
>> a
>> >> more passive "come join us" central hackathon space. Indeed, they
>> >> complement one another, and each should promote the other.
>> >>
>> >>
>> >> >
>> >> > On Mon, May 27, 2019 at 1:55 PM Rich Bowen 
>> wrote:
>> >> >
>> >> >> Awesome. It sounds like we have the three hackathon
>> leads/volunteers -
>> >> >> Rob Tompkins, Steve Blackmon, and Kevin McGrail - which seems like
>> the
>> >> >> ideal number for a leadership group. Do feel free to recruit more
>> >> >> volunteers to help with the work. I'll reach out every month for
>> >> updates
>> >> >> for my board report.
>> >> >>
>> >> >> And, of course, I'm very willing to share history, expectations,
>> >> >> insight, advice, a