community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roman Shaposhnik <...@apache.org>
Subject What's the ideal job title for somebody who is payed to help ASF communities grow?
Date Sun, 08 Mar 2015 21:09:17 GMT
Hi!

a recent thread with one of the PMCs pointed out an issue
that I've long wanted to solicit feedback for: what is the ideal
job title for somebody who is payed to help ASF communities
grow?

I have always thought that 'Technical/Community Evangelist, Apache FOO'
would be appropriate, just like 'Software Engineer, Apache FOO'
doesn't seem to be problematic.

However it was pointed out, that when we're talking community
as opposed engineering adding an Apache project name could
be misleading and give an impression that the person somehow
has a way to direct that community b/c of the job function.

Question #1: what's the general consensus on 'Technical/Community
Evangelist, Apache FOO' ?

If we'd rather discourage its use, what are the alternatives? One
that was suggested so far was to drop the 'Apache FOO'. This
could work but seems unfair to the person who may be as
bonafide a community evangelist as they come.

Another idea was to use commercial product names where appropriate
instead of Apache FOO. Thus instead of saying 'Technical/Community
Evangelist, Apache FOO' it would say 'Technical/Community Evangelist,
FOOPROD'. This could work for cases where project names != product
names, but what about things like Apache CloudStack?

Thanks,
Roman.

Mime
View raw message