You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@incubator.apache.org by ti...@apache.org on 2024/05/31 11:14:04 UTC
(incubator) branch master updated: Describe details about incubating status (#128)
This is an automated email from the ASF dual-hosted git repository.
tison pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator.git
The following commit(s) were added to refs/heads/master by this push:
new 30e58af62 Describe details about incubating status (#128)
30e58af62 is described below
commit 30e58af62e0ec97f23d6248aa1e459520342d331
Author: tison <wa...@gmail.com>
AuthorDate: Fri May 31 19:14:00 2024 +0800
Describe details about incubating status (#128)
Signed-off-by: tison <wa...@gmail.com>
---
pages/guides/branding.ad | 8 +++++---
pages/guides/publicity.ad | 9 ++++-----
2 files changed, 9 insertions(+), 8 deletions(-)
diff --git a/pages/guides/branding.ad b/pages/guides/branding.ad
index 86a95c946..c68133285 100644
--- a/pages/guides/branding.ad
+++ b/pages/guides/branding.ad
@@ -41,7 +41,7 @@ _Podling-Name_' (see link:#Naming[Naming] below).
A podling and affiliated persons can issue press releases that
reference the podling, but cannot issue press releases with the
specific intent of announcing the podling. The podling can conduct
-informal PR activities such as media outreach, blog publicity, etc.
+informal press release activities such as media outreach, blog publicity, etc.
The ASF will not issue any press releases for any podling at this
stage. The
link:http://www.apache.org/press/index.html#whoweare[Apache Press Team]
@@ -60,13 +60,15 @@ joint press release with any other affiliated organizations or groups.
After a podling has been approved, the lists are created, and the initial
code drop has commenced, you *MUST* refer to the podling as `Apache
_Podling-Name_` *AND* mention that the project is
- under Incubation. Suitable mentions include:
+ under Incubation. Suitable mentions include:
-- Inclusion of the `http://_podling-name_.incubator.apache.org/` URL
- `Apache _Podling-Name_ is currently undergoing Incubation at the Apache Software Foundation`.
+- Referring to the podling as `Apache _Podling-Name_ (Incubating)`.
The Incubator PMC (IPMC) must approve other references before you publish them. You only need to make these statements upon the first reference to the podling in a document.
+Specifically, you MUST include these statements in the README file of each repository belonging to the podling. You SHOULD add a link to the link:#Disclaimers[Disclaimers] in the README file. You CAN also refer the podling as `Apache _Podling-Name_ (Incubating)` in the GitHub repository description.
+
== Disclaimers
Podling web sites MUST include a clear disclaimer on their
diff --git a/pages/guides/publicity.ad b/pages/guides/publicity.ad
index 7b485fda6..b52c61015 100644
--- a/pages/guides/publicity.ad
+++ b/pages/guides/publicity.ad
@@ -29,7 +29,7 @@ Table of Contents
== 1) Prior to Entering the Apache Incubator
-Under no circumstances may any individuals or organizations seek publicity related to the proposed podling during this process. Per the https://incubator.apache.org/guides/branding.html[Incubator Branding Guidelines], you may not refer to a podling as "Apache _Podling Name_" until the Apache Incubator has officially accepted, its mailing lists are active, and podling participants have submtited code related to the podling into Apache repositories.
+Under no circumstances may any individuals or organizations seek publicity related to the proposed podling during this process. Per the https://incubator.apache.org/guides/branding.html[Incubator Branding Guidelines], you may not refer to a podling as "Apache _Podling-Name_" until the Apache Incubator has officially accepted, its mailing lists are active, and podling participants have submtited code related to the podling into Apache repositories.
No party can make announcements or statements 1) about their intention to submit a named project to the Apache Incubator or 2) that a specific project has been submitted to the Apache Incubator.
@@ -40,7 +40,7 @@ You may not disseminate formal press releases or announcements of any kind on an
We encourage Apache podlings and their communities to actively build awareness of their project through emails, blog posts, social media, and other means of outreach. Educational opportunities include online meetings, videos, podcasts, articles, and interactions at conferences and related community events.
-When speaking with members of the media and analyst community, you must refer to the podling as "Apache _Podling Name_" as per the Branding Guidelines, along with explaining the requisite podling disclaimer(s). Be prepared to answer "Who uses you?" As a podling’s known user base grows, PMCs (Project Management Committees) are welcome to promote their users on a "Powered By" page such as https://cwiki.apache.org/hadoop/PoweredBy[Apache Hadoop's Powered By page]. Create and promote podling [...]
+When speaking with members of the media and analyst community, you must refer to the podling as "Apache _Podling-Name_" as per the Branding Guidelines, along with explaining the requisite podling disclaimer(s). Be prepared to answer "Who uses you?" As a podling’s known user base grows, Podling Project Management Committees (PPMCs) are welcome to promote their users on a "Powered By" page such as https://cwiki.apache.org/hadoop/PoweredBy[Apache Hadoop's Powered By page]. Create and promot [...]
Podlings should prepare news announcements and hone their messaging _privately_ within their PMCs (keeping the content confidential to the PMC, and not on dev@, user@ or any other public list or forum) to ensure that the public or press don’t scoop your story before it’s out or publish inaccurate information. Messaging may change, features may not be available as soon as intended, testimonials may need adjusting, and so on, and it’s best to minimize the chances of your story getting out [...]
@@ -50,10 +50,9 @@ As all Apache PMCs (and Incubator PPMCs) are responsible for the "care and feedi
- Ensure your https://projects.apache.org/[project listing and DOAP (Description Of A Project) file] accurately reflects what the podling is about. Be succinct, particularly with the short description (note that the project may fall under one category): this helps those unfamiliar with your project find you. Use the longer project description as the official project boilerplate ("About Apache _Project Name_") and, for consistency, include it in official news announcements, media briefing [...]
- Upload a high-resolution version of your project’s logo at http://www.apache.org/logos/[apache.org/logos/].
-- Contact ASF Infrastructure to establish a https://blogs.apache.org/_PROJECTNAME_ project blog directory (and admin/publishing credentials).
- Request a project interview on https://feathercast.apache.org/[Feathercast, the voice of the ASF].
- Gain additional exposure by posting newsworthy podling updates and milestones to http://apache.org/foundation/mailinglists.html#foundation-announce[announce(at)apache(dot)org]. The Apache team adds these to the Apache Weekly News Round-Ups, which it also sends to members of the media and analyst community.
-- Establish a Twitter (and/or other social media) account(s) with a handle that includes "Apache" or "ASF" with the project name and description (example at https://twitter.com/ApacheAccumulo[https://twitter.com/ApacheAccumulo]). Share information often, and point to your podling Website and email list archives where possible.
+- Establish an X (formerly Twitter) (and/or other social media) account(s) with a handle that includes "Apache" or "ASF" with the project name and description (example at https://x.com/ApacheArrow[https://x.com/ApacheArrow]). Share information often, and point to your podling website and email list archives where possible. Credentials to these accounts must be shared among the PPMC. And the PPMC is responsible for the posts.
- Participate in Media & Analyst Training (held during ApacheCon; complimentary for Apache Committers and Members).
- Comply with guidelines for "founding" individuals, organizations, and communities of Apache podlings as applicable (details below).
@@ -63,7 +62,7 @@ Podling cannot disseminate formal press releases or announcements of any kind on
Podlings wishing to issue a press release announcing their graduation as an Apache Top-Level Project (TLP) must follow ASF Marketing & Publicity (ASF M&P) https://docs.google.com/document/d/1y3fZYn92LlnNadYxUsRiJEMwz0urKxnotBtDn0Cq_G0/edit[guidelines].
-Podling Project Management Committees (PPMCs) are responsible for writing the first draft of a formal ASF press release and sharing it with ASF M&P for approval. A press release is a great opportunity to solicit quotes/testimonials from the Podling’s community to demonstrate the project’s robustness and breadth of deployment. TLP announcements may include 1-2 quotes (including, but not limited to, VP of the project/PMC chair and community endorsements). A recent example of a TLP press re [...]
+PPMCs are responsible for writing the first draft of a formal ASF press release and sharing it with ASF M&P for approval. A press release is a great opportunity to solicit quotes/testimonials from the Podling’s community to demonstrate the project’s robustness and breadth of deployment. TLP announcements may include 1-2 quotes (including, but not limited to, VP of the project/PMC chair and community endorsements). A recent example of a TLP press release is: https://news.apache.org/founda [...]
Organizations supporting/using the Podling are welcome to issue their own, standalone "hurrah, Apache Podling Name!" press release (or blog post) to support the Podling’s graduation after the ASF has issued its announcement. All third parties need to coordinate messaging and timing with both the Podling PMC and ASF M&P. Third-party releases must not use the Apache boilerplate.
---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org