Re: ComDev Graphic Needed for ApacheCon @Home

[Skylar Deranick]

Hint.  Its a drink

On Mon, Jul 27, 2020, 12:07 PM Sharan Foga  wrote:

> Hi All
>
> We need an image or graphic that represents ComDev that will be used to
> promote the Community track at ApacheCon@Home. The graphic needs to be
> 1080 x 1080. We don't really have our own logo and have generally use the
> ASF feather. Does anyone have any ideas of anything else we could use?
>
> Thanks
> Sharan
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: ComDev Graphic Needed for ApacheCon @Home

[fpapon]

+1 for the signed feather!

regards;

François
fpa...@apache.org

Le 27/07/2020 à 21:19, Rich Bowen a écrit :
> I like the idea of using the signed feather in some way as part of
> this graphic.
>
> On 7/27/20 3:07 PM, Sharan Foga wrote:
>> Hi All
>>
>> We need an image or graphic that represents ComDev that will be used
>> to promote the Community track at ApacheCon@Home. The graphic needs
>> to be 1080 x 1080. We don't really have our own logo and have
>> generally use the ASF feather. Does anyone have any ideas of anything
>> else we could use?
>>
>> Thanks
>> Sharan
>>
>> -
>> 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

Update of bootstrap for ComDev site

[Maxim Solodovnik]

Hello All,

we currently have "Bootstrap v2.3.1" at ComDev site
Are there any objections if I update to version 4?

-- 
Best regards,
Maxim

Re: ComDev Graphic Needed for ApacheCon @Home

[Rich Bowen]

I like the idea of using the signed feather in some way as part of this 
graphic.


On 7/27/20 3:07 PM, Sharan Foga wrote:

Hi All

We need an image or graphic that represents ComDev that will be used to promote 
the Community track at ApacheCon@Home. The graphic needs to be 1080 x 1080. We 
don't really have our own logo and have generally use the ASF feather. Does 
anyone have any ideas of anything else we could use?

Thanks
Sharan

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



--
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

Re: ComDev Graphic Needed for ApacheCon @Home

[Tanmay Laud]

We could have a small contest and the community can vote for the entries.
What say?


-Tanmay

On Tue, 28 Jul, 2020, 12:37 am Sharan Foga,  wrote:

> Hi All
>
> We need an image or graphic that represents ComDev that will be used to
> promote the Community track at ApacheCon@Home. The graphic needs to be
> 1080 x 1080. We don't really have our own logo and have generally use the
> ASF feather. Does anyone have any ideas of anything else we could use?
>
> Thanks
> Sharan
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

ComDev Graphic Needed for ApacheCon @Home

[Sharan Foga]

Hi All

We need an image or graphic that represents ComDev that will be used to promote 
the Community track at ApacheCon@Home. The graphic needs to be 1080 x 1080. We 
don't really have our own logo and have generally use the ASF feather. Does 
anyone have any ideas of anything else we could use?

Thanks
Sharan

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

Re: ASF Slack for community?

[Roy Lenferink]

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 clear bounds on what is OK and not OK to be doing with it?
>
> Proposal: we use this slack channel for the BeamSummit, and learn how it
> goes.
> If concerned about persisting user accounts, perhaps can we configure an
> alternate link (if given permissions, I am willing) and we can track the
> signups through that link [ s.apache.org/
> temp-slack-invite ] - and
> auto-expire/delete their account after 30 days (or some interval) without
> some additional requirements to keep them as users.  It seems the fear is
> around accounts getting created that are not used and costing money.  I
> suspect (a) there are alot of inactive accounts, and (b) that we should be
> supporting the growing community in the same place.
>
> Thanks for bearing with this long message.
> Austin
>
> On Tue, Jul 21, 2020 at 12:15 PM Chris Thistlethwaite 
> wrote:
>
>> Infra discussed this at our last team meeting. Currently the way Slack
>> invites work via s.apache.org/slack-invite sends out an invite to become
>> a full member of the-asf.slack.com. You can read a bit more about this
>> at https://infra.apache.org/slack.html. The issue with that is members
>> (Slack Members NOT ASF Members) then cost money for the ASF, which will
>> be hard to track and forecast if every project starts using the-asf
>> workspace as a conference meet-up area. There's not an official way to
>> invite someone as a Single Channel Guest to Slack without their email
>> address. There's no URL they can visit to get an invite. There are
>> products out there that use a deprecated Slack API

Re: ASF Slack for community?

[Austin Bennett]

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 clear bounds on what is OK and not OK to be doing with it?

Proposal: we use this slack channel for the BeamSummit, and learn how it
goes.
If concerned about persisting user accounts, perhaps can we configure an
alternate link (if given permissions, I am willing) and we can track the
signups through that link [ s.apache.org/
temp-slack-invite
] - and auto-expire/delete their account after 30 days (or some interval)
without some additional requirements to keep them as users.  It seems the
fear is around accounts getting created that are not used and costing
money.  I suspect (a) there are alot of inactive accounts, and (b) that we
should be supporting the growing community in the same place.

Thanks for bearing with this long message.
Austin

On Tue, Jul 21, 2020 at 12:15 PM Chris Thistlethwaite 
wrote:

> Infra discussed this at our last team meeting. Currently the way Slack
> invites work via s.apache.org/slack-invite sends out an invite to become
> a full member of the-asf.slack.com. You can read a bit more about this
> at https://infra.apache.org/slack.html. The issue with that is members
> (Slack Members NOT ASF Members) then cost money for the ASF, which will
> be hard to track and forecast if every project starts using the-asf
> workspace as a conference meet-up area. There's not an official way to
> invite someone as a Single Channel Guest to Slack without their email
> address. There's no URL they can visit to get an invite. There are
> products out there that use a deprecated Slack API, but they aren't well
> maintained and Slack can turn off the API whenever they want. So as of
> this writing, we're recommending against using the-asf.slack.com for
> mass conference invites.
>
> We tried a workaround of sharing a channel with apachecon.slack.com,
> however you can't share a channel from a paid Slack instance to a free
> instance.
>
> I'm just throwing out ideas, but if you had a list of email addresses
> for attendees, you could bulk invite everyone as a Single Channel Guest
> (they'd just have access to #beam). Then they get the added bonus of
> being apart of the official Slack instance, can talk in the #beam
> channel as needed and if they become a committer to Beam then they could
> be "upgraded" to a full member account. Again, I'm just throwing it out
> there as no one has ever really talked about the process/workflow of a
> large group being dumped into Slack.
>
> -Chris T.
> #asfinfra
>
> On 7/18/20 8:01 AM, Matthias Baetens wrote:
> > Thanks for bringing this to the ComDev mailing list, Austin. As part
> > of the Beam Summit org team, I am in strong favour of making 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 cha

[presentation] Apache Camel 3 talk by Claus Ibsen and Andrea Cosentino

[Jonathan Vila Lopez]

Hi
I would like to share with all the Apache followers, that tomorrow
afternoon ( CEST ) we'll have a presentation about recently released Apache
Camel 3, the integration platform in the era of Kubernetes and Serverles..
It's a free and online event , in English, tomorrow Tuesday 28th at 19.00
CEST
https://www.meetup.com/es-ES/BarcelonaJUG/events/271746564/

Hope to see you there.

Happy coding.