Fwd: [IMPORTANT] PMCs/pPMCs: Apache Project visibility and promotion (please read)

[vongosling <vo...@apache.org>]

Hi,

I'm glad we're not on this list. We've made the same mistake over the past
few years. Hopefully, all of us have learned from this and help the
community grow better and better. Forward this e-mail, and I hope we all
guys could read it carefully about neutrality, about brand violation
attitude about Apache Software Foundation.

Finally, it's important to remember that nothing happens if we could not
make a decision in the community(I don't remember the official words, but
if you remember, please remind us again:-)), you can not have any
misleading link or other infringing, non-neutral words and actions on the
website, no matter who you are.

Let's work together to build a better community around Apache Culture :-)

---------- Forwarded message ---------
发件人： Sally Khudairi <sk...@apache.org>
Date: 2021年8月26日周四 上午11:40
Subject: [IMPORTANT] PMCs/pPMCs: Apache Project visibility and promotion
(please read)
To: ASF Marketing & Publicity <pr...@apache.org>


Hello PMCs and pPMCs --I hope you are all well.

Whether you're an established TLP or currently being mentored in the
Incubator, the information below is how to maximize your Project/Podling's
visibility and work within the ASF's communication guidelines. All
PMCs/pPMCs are responsible for their respective code, community, and
communications. This email contains details on:

 I. Official project announcements
 I-a. Milestone announcements
 II. Project and Podling listings
 III. Social Media
 IV. Blogging and Feathercast
 V. Project Logos and "Powered By" assets
 V-a. Website branding compliance
     ***please see ALERT in this section***
 VI. Creative assistance available
 VII. "Personal" promotions


Those of you who are familiar with promotions options and wish to skip this
email, I understand, but implore you to read section V-a (you don't want me
coming after you). Other sections have updates and may be noteworthy.

OK --here we go!

I. Official project announcements. All official communications, including
release announcements and related community updates, take place on mailing
lists. In addition to your user@ and dev@ lists, we encourage PMCs to also
send select project updates to announce@apache.org, the ASF's official news
email list.

We have strict guidelines regarding posting to announce@apache.org, which
is a moderated list. Your message must:

1) be sent from your apache.org address;
2) be in PLAINTEXT (no HTML mail, no embedded links --any HTML messages
will not clear moderation);
2a) have no attachments;
3) contain [ANNOUNCE] or [ANN] before a clear subject line (eg: "[ANNOUNCE]
Apache PROJECTNAME v2.3 released");
4) include your project boilerplate ~10-60 words (DOAP = description of a
project; eg. https://projects.apache.org/project.html?bookkeeper )
5) include a link to the project homepage or download source(s)
6) include the incubating disclaimer, if applicable

announce@apache.org is used for one-way communications for code/release
updates, CVE notices, major community events (such as project conferences),
but NOT team updates ("welcome XYZ as a committer"); interactive Q&A ("ask
us here with any questions"); minor activities (new lists, MeetUps
scheduled, blog posts), etc. (those belong on your dev/user lists).

Examples: https://lists.apache.org/list.html?announce@apache.org

Highly Recommended: sending your news to announce@ helps amplify your
message to thousands of subscribers, and be included in official ASF
promotions, including the Weekly News Round-ups (published every Friday;
read by members of the media/analyst community --SD News publishes weekly
updates on Apache projects from the Round-ups). Check out
https://blogs.apache.org/foundation/date/20210813 .


I-a. Milestone announcements. Those projects with *milestone* announcements
(graduation from the Incubator, major release, highly-visible/important
deployment or use case, or serious security issue) are welcome to contact
us at press@ to see how we can help. These can take several forms:

1) ASF press release https://blogs.apache.org/foundation/date/20210802
2) Apache Project press release
https://blogs.apache.org/foundation/entry/the-apache-cassandra-project-releases
3) media alert https://blogs.apache.org/foundation/date/20210504
4) blog post/statement
https://blogs.apache.org/foundation/entry/apache-struts-statement-on-equifax
5) guest post blog on third party site
https://opensource.com/article/19/3/apache-projects


II. Project and Podling listings. Help the public, the press, and others
find your project more easily, so they can use it and tell others about it.
Please be sure that your projects are listed, linked, and updated:

 - TLPs, sub-projects, and incubating podlings https://projects.apache.org/
 - Incubating podlings http://incubator.apache.org/ AND
http://incubator.apache.org/projects/

We sometimes receive queries from journalists about a new Apache podling
that's not yet on our radar. What we usually do in such instances is look
the project up on projects.a.o as well as incubator.a.o --however,
sometimes we're unable to find it, and therefore are unable to make a
comment (because it pretty much "doesn't exist yet"). That's doesn't make
us look good. Please ensure your project is on the ASF's lists, so we can
help point others to you.


III. Social Media. The ASF's two primary channels for social media are

 - Twitter https://twitter.com/TheASF/
 - and LinkedIn
https://www.linkedin.com/company/the-apache-software-foundation

...we also have a showcase page for ApacheCon
https://www.linkedin.com/showcase/35584119/ .

We encourage each project to create and maintain your own Twitter account,
which is the fastest way to reach your growing communities. This is also an
excellent way to get stats and factoids published about your project
amplified on ASF channels thorugh our "Did you know?" campaign:

 - in the Weekly News Round-ups
https://blogs.apache.org/foundation/date/20210820
 - on Twitter https://twitter.com/TheASF/status/1428863174636359680?s=20
 - in LinkedIn
https://www.linkedin.com/feed/update/urn:li:activity:6832454193790406656

NOTE: the ASF does not maintain a Facebook page, but Apache Community
Development (ComDev) does https://www.facebook.com/ApacheSoftwareFoundation/
(as well as a Twitter account https://twitter.com/ApacheCommunity). Those
of you wishing to have a Facebook presence or other social media channels
are welcome to do so.


IV. Blogging and Feathercast. The ASF's blog service,
https://blogs.apache.org/ , is a great way to share regular updates on your
Project's progress, particularly technical information, deep-dive on a
release, user guides, and more. You may obtain publishing credentials, as
well as your own Project sub-directory (blogs.a.o/PROJECTNAME), by filing a
JIRA ticket with Infra https://issues.apache.org/jira/projects/INFRA/

Those who have promoted their project presentations and tracks at ApacheCon
may be familiar with Feathercast, the official voice of the ASF
https://feathercast.apache.org/ . Feathercast originated 15 years ago as a
personal podcast from ASF Members Rich Bowen and David Reid, and has since
expanded to include videos of project highlights as well as ApacheCon and
Apache Roadshow presentations. Whilst Feathercast does not yet publish on a
regular schedule, we may be able to accommodate any time-sensitive needs:
contact us at press@apache.org for assistance.


V. Project Logos and "Powered By" assets. Do you know if your project logo
is listed at http://apache.org/logos/ ? If not, follow the "How do I get my
project logo on this page?" instructions to add it. The logos on this page
are how we pull together the collective "NASCAR" graphics for the ASF's
banners at conferences and other promotions, such as our Annual Report
https://s.apache.org/FY2020AnnualReport . Be sure you're represented!

You can also create and use a customized "Powered By" badge to encourage
your users to promote your project on your Project Website, social media,
stickers and t-shirts for conferences, and more. "Powered By" badges are a
great way to get your brand in front of your user base and increase brand
recognition with enthusiasts. ASF Sponsors use them as well
https://aws.amazon.com/blogs/opensource/supporting-apache-software-foundation/
(this image is from the old template and feather logo). Templates, ASF
feathers, logos, brand guidelines and more are available at
http://apache.org/foundation/press/kit/


V-a. Website branding compliance

IMPORTANT: PMCs who list "powered by" companies on their Project sites
(organizations that are using your project --in their products/solutions or
otherwise) MUST NOT BE DOING SO ON THE PROJECT HOME PAGE.

WHY: the ASF is strictly vendor-neutral. Listing company names and/or logos
on a project's home page is disallowed as it can imply "ownership" or
preferred status or otherwise imbalanced relationship. Whether this is the
case or not, it is not acceptable. The policy is the same as "thanking"
companies for their support of a project
http://apache.org/foundation/marks/linking#projectthanks

WHAT WE'RE NOT SAYING: please don't misunderstand the "no third party logos
on your homepage" policy. We *love* projects promoting their users! Many of
you have commented that we always include user organizations in our press
releases --one of the first things that members of the media and analyst
community ask is, "who uses you?". We're proud of all our projects and your
collective efforts: we want to ensure that everyone is being fairly
represented and considered.

Some projects that are in violation are recent graduates from the Incubator
and may not have ever been aware of this policy. Others are long-standing
TLPs with refreshed Websites: perhaps there are new contributors who helped
with the redesign and weren't aware. We understand that this action has
likely been done in error, but needs to be rectified. Your "Powered By"
listings can be on any page within your Project site but NOT the home page.

There are different ways you can recognize organizations that are Powered
By Apache (YourProjectName) --here are some good examples:

1) Full logo -- Airflow -- http://airflow.apache.org/use-cases/
2) Shown with screenshots -- Flex --
http://flex.apache.org/community-showcase.html
3) Named list -- CloudStack -- http://cloudstack.apache.org/users.html

To that end ...now that you know...

ALERT: the following projects need to change their homepages --

 - APISIX http://apisix.apache.org/
 - Beam http://beam.apache.org/
 - Cassandra https://cassandra.apache.org/_/index.html
 - Cordova http://cordova.apache.org/
 - DolphinScheduler http://dolphinscheduler.apache.org/
 - Drill http://drill.apache.org/
 - Dubbo https://dubbo.apache.org/zh/
 - Flink http://flink.apache.org/
 - Griffin http://griffin.apache.org/
 - Hudi http://hudi.apache.org/
 - Ignite http://ignite.apache.org/
 - Isis http://isis.apache.org/
 - jClouds http://jclouds.apache.org/
 - Kylin http://kylin.apache.org/
 - Libcloud http://libcloud.apache.org/
 - Mynewt http://mynewt.apache.org/
 - OODT http://oodt.apache.org/
 - OpenWhisk http://openwhisk.apache.org/
 - Phoenix http://phoenix.apache.org/
 - Pinot http://pinot.apache.org/
 - Pulsar http://pulsar.apache.org/
 - Singa http://singa.apache.org/
 - Samza http://samza.apache.org/
 - Shiro http://shiro.apache.org/
 - SkyWalking http://skywalking.apache.org/
 - Solr http://solr.apache.org/
 - Storm http://storm.apache.org/
 - Submarine http://submarine.apache.org/
 - Superset http://superset.apache.org/
 - Wicket http://wicket.apache.org/


If your project is listed above, please contact us at press@ to let us know
when you will be able to update your Website's homepage. Ideally this will
be completed within the next 30 days, but understand that there are some
exceptions with PMC availability, etc. Please *do not* ignore this request.

Speaking of Project Websites ...two more requests:

1) if you have the old ASF logo or feather on your site (looks like this
https://apache.org/images/feathertm.gif and this
https://apache.org/images/asf_logo.gif ), please update it to the new
version (this https://apache.org/foundation/press/kit/#links --several
versions available-- released in 2015). Please let us know if you need
assistance.

2) update your copyright date(s). Some sites appear to not have been
updated in a while (still mention ASF's 10th Anniversary, for example --we
celebrated 22 years this March).


VI. Creative assistance available. ASF Marketing & Publicity oversees
Central Services, a very small team that can help with graphics production,
logo development, and other creative needs. Assistance is provided on a
first come, first served basis. To request help, complete the form at
https://www.apache.org/foundation/press/central-services-request


VII. Personal promotions. Did you know that you can share your personal
Apache experience with a Success at Apache blog post? Now in its 5th year,
"Success at Apache" is the blog series that focuses on the people and
processes behind why the ASF "just works". This is *not* a corporate piece
--it's your experience, in your voice (very little intervention or edits
unless required). Here are some examples
https://blogs.apache.org/foundation/feed/entries/atom?cat=SuccessAtApache

If you're a Committer, you can participate! If you're interested in sharing
your experience, drop me a note and we'll get you on the schedule. We aim
to publish monthly, and had some snags over the past year for various
reasons, so we're looking forward to starting up again.

Those who prefer to share their experience from the PMC angle may write a
"Project Perspectives" post --here's an example from Apache Weex
https://blogs.apache.org/foundation/entry/project-perspectives-apache-weex-incubating
Your experience and area(s) of interest may be different, and that's great.
We'd love to hear from you.


Thank you in advance for your attention and help where applicable. As
always, do let me know if you need assistance or further information. I
hope this helps :-)

Best,
Sally

- - -
Vice President Sponsor Relations
The Apache Software Foundation

Tel +1 617 921 8656 | sk@apache.org


-- 
Best Regards :-)