This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-training.git
The following commit(s) were added to refs/heads/asf-site by this push:
new f12d880 Site checkin for project Training: Website
f12d880 is described below
commit f12d880b875523081e961b4667e107b68bf77787
Author: jenkins <[email protected]>
AuthorDate: Wed Sep 25 15:56:07 2024 +0000
Site checkin for project Training: Website
---
dependencies.html | 12 +-
.../WEB-INF/classes/images/cookie_cutter.jpg | Bin 0 -> 147455 bytes
.../WEB-INF/classes/images/eat-together.jpg | Bin 0 -> 247933 bytes
.../WEB-INF/classes/images/mentoring.jpg | Bin 0 -> 91396 bytes
.../WEB-INF/classes/images/orc_wg.png | Bin 0 -> 153400 bytes
.../WEB-INF/classes/images/party.jpg | Bin 0 -> 96154 bytes
.../comdev/working-groups/images/cookie_cutter.jpg | Bin 0 -> 147455 bytes
.../comdev/working-groups/images/eat-together.jpg | Bin 0 -> 247933 bytes
.../comdev/working-groups/images/mentoring.jpg | Bin 0 -> 91396 bytes
.../comdev/working-groups/images/orc_wg.png | Bin 0 -> 153400 bytes
.../comdev/working-groups/images/party.jpg | Bin 0 -> 96154 bytes
presentations/comdev/working-groups/index.html | 210 ++++++++++-----------
presentations/training/demo/index.html | 2 +-
13 files changed, 110 insertions(+), 114 deletions(-)
diff --git a/dependencies.html b/dependencies.html
index b81b44b..0e8f4d7 100644
--- a/dependencies.html
+++ b/dependencies.html
@@ -720,8 +720,8 @@
</tr>
<tr class="b">
<td
align="left">training-content-apache-comdev-working-groups-1.0.0-SNAPSHOT.war</td>
- <td align="right">19.6 MB</td>
- <td align="right">244</td>
+ <td align="right">21 MB</td>
+ <td align="right">254</td>
<td align="right">1</td>
<td align="right">1</td>
<td align="center">1.8</td>
@@ -882,8 +882,8 @@
</tr>
<tr class="b">
<td align="right">19</td>
- <td align="right">167 MB</td>
- <td align="right">4182</td>
+ <td align="right">168.4 MB</td>
+ <td align="right">4192</td>
<td align="right">7</td>
<td align="right">3</td>
<td align="center">1.8</td>
@@ -891,8 +891,8 @@
</tr>
<tr class="a">
<td align="right">compile: 19</td>
- <td align="right">compile: 167 MB</td>
- <td align="right">compile: 4182</td>
+ <td align="right">compile: 168.4 MB</td>
+ <td align="right">compile: 4192</td>
<td align="right">compile: 7</td>
<td align="right">compile: 3</td>
<td align="center">1.8</td>
diff --git
a/presentations/comdev/working-groups/WEB-INF/classes/images/cookie_cutter.jpg
b/presentations/comdev/working-groups/WEB-INF/classes/images/cookie_cutter.jpg
new file mode 100644
index 0000000..4d4268a
Binary files /dev/null and
b/presentations/comdev/working-groups/WEB-INF/classes/images/cookie_cutter.jpg
differ
diff --git
a/presentations/comdev/working-groups/WEB-INF/classes/images/eat-together.jpg
b/presentations/comdev/working-groups/WEB-INF/classes/images/eat-together.jpg
new file mode 100644
index 0000000..47a3738
Binary files /dev/null and
b/presentations/comdev/working-groups/WEB-INF/classes/images/eat-together.jpg
differ
diff --git
a/presentations/comdev/working-groups/WEB-INF/classes/images/mentoring.jpg
b/presentations/comdev/working-groups/WEB-INF/classes/images/mentoring.jpg
new file mode 100644
index 0000000..9bfd5e2
Binary files /dev/null and
b/presentations/comdev/working-groups/WEB-INF/classes/images/mentoring.jpg
differ
diff --git
a/presentations/comdev/working-groups/WEB-INF/classes/images/orc_wg.png
b/presentations/comdev/working-groups/WEB-INF/classes/images/orc_wg.png
new file mode 100644
index 0000000..d37744f
Binary files /dev/null and
b/presentations/comdev/working-groups/WEB-INF/classes/images/orc_wg.png differ
diff --git
a/presentations/comdev/working-groups/WEB-INF/classes/images/party.jpg
b/presentations/comdev/working-groups/WEB-INF/classes/images/party.jpg
new file mode 100644
index 0000000..427e735
Binary files /dev/null and
b/presentations/comdev/working-groups/WEB-INF/classes/images/party.jpg differ
diff --git a/presentations/comdev/working-groups/images/cookie_cutter.jpg
b/presentations/comdev/working-groups/images/cookie_cutter.jpg
new file mode 100644
index 0000000..4d4268a
Binary files /dev/null and
b/presentations/comdev/working-groups/images/cookie_cutter.jpg differ
diff --git a/presentations/comdev/working-groups/images/eat-together.jpg
b/presentations/comdev/working-groups/images/eat-together.jpg
new file mode 100644
index 0000000..47a3738
Binary files /dev/null and
b/presentations/comdev/working-groups/images/eat-together.jpg differ
diff --git a/presentations/comdev/working-groups/images/mentoring.jpg
b/presentations/comdev/working-groups/images/mentoring.jpg
new file mode 100644
index 0000000..9bfd5e2
Binary files /dev/null and
b/presentations/comdev/working-groups/images/mentoring.jpg differ
diff --git a/presentations/comdev/working-groups/images/orc_wg.png
b/presentations/comdev/working-groups/images/orc_wg.png
new file mode 100644
index 0000000..d37744f
Binary files /dev/null and
b/presentations/comdev/working-groups/images/orc_wg.png differ
diff --git a/presentations/comdev/working-groups/images/party.jpg
b/presentations/comdev/working-groups/images/party.jpg
new file mode 100644
index 0000000..427e735
Binary files /dev/null and
b/presentations/comdev/working-groups/images/party.jpg differ
diff --git a/presentations/comdev/working-groups/index.html
b/presentations/comdev/working-groups/index.html
index 5e007bf..b78978e 100644
--- a/presentations/comdev/working-groups/index.html
+++ b/presentations/comdev/working-groups/index.html
@@ -414,140 +414,136 @@ ul.byline li + li {
margin-top: 0.25em;
}
</style><link rel="stylesheet"
href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.1/css/all.min.css";
/><link rel="stylesheet"
href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.1/css/v4-shims.min.css";
/></head><body><div class="header"><div class="left"></div><div
class="right"></div></div><div class="reveal"><div class="slides"><section
id="comdev-working-groups"><h2>ComDev Working Groups</h2><div
class="slide-content"><div class="ulist"><ul><li class="fragment"> [...]
-<section><div class="slide-content"><div class="paragraph"><p>" ComDev is
…​ charged with coordinating community development
efforts."</p></div>
-<div class="imageblock"><img src="images/cat-herding.jpg" alt="cat
herding"></div>
-<aside class="notes"><div class="paragraph"><p>Picture: "Cat herders" -
signifying that coordinating community can be
-challenging.</p></div>
-<div class="ulist"><ul><li><p>ComDev exists to help projects build their
communties</p></li><li><p>Yes, projects should do this themselves, but having
common practices and tools lowers the barrier</p></li><li><p>ComDev is a PMC -
a peer to other PMCs. It does <strong>not</strong> have authority over other
PMCs.</p></li></ul></div></aside></div></section>
-<section><div class="slide-content"><div class="paragraph"><p>Key Point:
ComDev does not do this work <strong>for</strong> you. It’s a place
+<section id="a-bit-about-comdev"><h2>A bit about ComDev</h2><div
class="slide-content"><div class="paragraph"><p>" …​ charged with
coordinating community development efforts."</p></div>
+<aside class="notes"><div class="ulist"><ul><li><p>ComDev exists to help
projects build their communties</p></li><li><p>Yes, projects should do this
themselves, but having common practices and tools lowers the
barrier</p></li><li><p>ComDev is a PMC - a peer to other PMCs. It does
<strong>not</strong> have authority over other
PMCs.</p></li></ul></div></aside></div></section>
+<section id="we-are-all-comdev"><h2>We are all ComDev</h2><div
class="slide-content"><div class="imageblock"><img
src="images/barn-raising.jpg" alt="barn raising"></div>
+<small>CC by "Elgin County Archives" on Flickr</small>
+<aside class="notes"><div class="paragraph"><p>Key Point: ComDev does not do
this work <strong>for</strong> you. It’s a place
for everyone to <strong>collaborate on best practices</strong> and tools that
span all projects. Come join us.</p></div>
-<div class="imageblock"><img src="images/barn-raising.jpg" alt="barn
raising"></div>
-<small>CC by Historic Bremen Indiana on Flickr</small>
-<aside class="notes"><div class="paragraph"><p>Picture: A community building a
barn together.</p></div>
<div class="paragraph"><p>ComDev is the ideal place for people with so-called
"non-technical"
skills that they want to contribute to the ASF.</p></div>
<div class="paragraph"><p>However, there is a tendency for people to wait for
someone else to lead
before they get more deeply involved.</p></div></aside></div></section>
<section id="whats-a-working-group"><h2>What’s a working group?</h2><div
class="slide-content"><div class="ulist"><ul><li
class="fragment"><p>Like-minded people …​</p></li><li
class="fragment"><p>working towards a common goal …​</p></li><li
class="fragment"><p>collaboratively, in
public</p></li></ul></div></div></section>
-<section id="each-group-has"><h2>Each group has</h2><div
class="slide-content"><div class="ulist"><ul><li><p>Git repo - <a
href="https://github.com/apache/comdev-working-groups";
class="bare">https://github.com/apache/comdev-working-groups</a></p></li><li><p>A
narrowly-defined goal or mission</p></li></ul></div>
-<aside class="notes"><div class="paragraph"><p>Narrowly defined so that
there’s no ambiguity, room for scope creep, or
-potential to overlap/conflict with other
efforts.</p></div></aside></div></section>
-<section id="why"><h2>Why?</h2><div class="slide-content"><div
class="paragraph"><p>After all, everyone knows that they can just dive in and
start doing
-stuff, right?</p></div>
-<div class="imageblock"><img src="images/dive.jpg" alt="dive"></div>
-<small>CC by "Noirin Shirley" on Flickr</small>
-<aside class="notes"><div class="paragraph"><p>Picture: Someone "diving
in"</p></div>
-<div class="paragraph"><p>Yes, it’s open source and "everyone knows"
that they can come
-contribute. But it can still be intimidating. People don’t know where to
-start.</p></div>
-<div class="paragraph"><p>People like to be asked. They like to be invited.
They
-like to be welcomed.</p></div>
-<div class="paragraph"><p>We get email to the dev@community mailing list
almost every week that
-asks "where I can get involved" and invariably someone says "Find a
-place and just start!" which is both true, and incredibly unhelpful.
-Working groups give a more focused answer "pick one of
these."</p></div></aside></div></section>
-<section><div class="slide-content"><div class="paragraph"><p>And, let’s
be honest, sometimes we we aren’t the most welcoming place.</p></div>
-<div class="imageblock"><img src="images/shark.jpg" alt="shark"></div>
-<aside class="notes"><div class="paragraph"><p>Picture: Rich’s kid with
a shark (sometimes you don’t want to dive in
-with the sharks)</p></div>
-<div class="paragraph"><p>Having clearly defined places to do clearly defined
work can lower the
-anxiety of joining something new.</p></div></aside></div></section>
-<section><div class="slide-content"><div class="imageblock"><img
src="images/welcome.jpg" alt="welcome"></div>
+<section id="welcome"><h2>Welcome</h2><div class="slide-content"><div
class="imageblock"><img src="images/welcome.jpg" alt="welcome"></div>
<small>CC by "alborzshawn" on Flickr</small>
-<aside class="notes"><div class="paragraph"><p>Picture: A "welcome"
sign.</p></div>
-<div class="paragraph"><p>The working groups exist to give explicit welcome
and <strong>permission</strong> to
-anyone who wants to participate.</p></div></aside></div></section>
-<section><div class="slide-content"><div class="imageblock"><img
src="images/ask-me.jpg" alt="ask me"></div>
-<aside class="notes"><div class="paragraph"><p>Picture: An "Ask me" badge from
a long-ago ApacheCon</p></div>
-<div class="paragraph"><p>Having a "title" (I’m a member of the
-Advisors working group!) gives people a feeling that they are authorized
-to speak with that voice. It gives <strong>explicit permission</strong>. It
also
-encourages others to take them seriously ("oh, you’re part of the
-working group")</p></div>
-<div class="paragraph"><p>It also gives a structure within which to
participate, and a recommended
-way to get started.</p></div></aside></div></section>
-<section id="working-groups-so-far"><h2>Working groups so far</h2></section>
-<section id="wg-wg"><h2>wg-wg</h2><div class="slide-content"><div
class="ulist"><ul><li><p>For discussion of cross-working-group norms, process,
or tools</p></li><li><p>Purely advisory - WGs can do what they want - but wg-wg
proposes
-structure and processes.</p></li><li><p>Defines recommended way to start a new
WG</p></li></ul></div>
+<aside class="notes"><div class="paragraph"><p>Yes, it’s open source and
"everyone knows" that they can come
+contribute. But people like to be asked. They like to be invited. They
+like to be welcomed.</p></div>
+<div class="paragraph"><p>The working groups exist to give explicit welcome
and permission to
+anyone who wants to participate. Come join
us!</p></div></aside></div></section>
+<section id="wg-wg"><h2>wg-wg</h2><div class="slide-content"><div
class="ulist"><ul><li><p>For discussion of cross-working-group norms, process,
or tools</p></li></ul></div>
<aside class="notes"><div class="ulist"><ul><li><p>This is where we document
the ways that working groups should work.</p></li><li><p>It’s also where
we can collaborate on shared resources or processes
that benefit all WGs</p></li></ul></div></aside></div></section>
-<section id="wg-advisors"><h2>wg-advisors</h2><div class="slide-content"><div
class="ulist"><ul><li><p>Advising projects and PMCs on best
practice</p></li><li><p>Seasoned ASF members and community
managers</p></li><li><p>It’s important to respect a project’s
autonomy</p></li></ul></div>
+<section id="wg-wg-why"><h2>wg-wg: why?</h2><div class="slide-content"><div
class="imageblock"><img src="images/cookie_cutter.jpg" alt="cookie
cutter"></div>
+<aside class="notes"><div class="paragraph"><p>Standardization across working
groups makes it easier for people to join
+another WG once they’re familiar with how WGs work.</p></div>
+<div class="paragraph"><p>But flexibility is important too, when WGs have
different needs. So this
+group must work <strong>with</strong> all of the other groups to figure out
what can be
+shared, and what needs to be kept separate.</p></div>
+<div class="paragraph"><p>So far, it’s only decided on some vague advice
that WGs report up to the
+ComDev PMC about their progress.</p></div></aside></div></section>
+<section id="wg-advisors"><h2>wg-advisors</h2><div class="slide-content"><div
class="ulist"><ul><li><p>Advising projecdts and PMCs on best
practice</p></li><li><p>Seasoned ASF members and community
managers</p></li><li><p>It’s important to respect a project’s
autonomy</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>This is really no different
from going to the project and volunteering
your expertise, but having the working group emboldens pepole to do this
-work.</p></div>
-<div class="paragraph"><p>The primary goal is not so much to force people to
do things a
-particular way, but to streamline it for people who don’t know how to
-get started.</p></div>
+work. And it makes projects more willing to accept the advice, as it’s
+part of an "official program".</p></div>
<div class="paragraph"><p>Ask first. You will probably be welcome, but
don’t assume. Be clear that
you’re offering advice, but don’t have standing to vote or enforce
-anything. And once you’ve done this for a while, there’s a chance
that
-some projects will invite you to stick
around.</p></div></aside></div></section>
-<section id="wg-advisors-contd"><h2>wg-advisors, cont’d</h2><div
class="slide-content"><div class="ulist"><ul><li><p>Get involved if</p><div
class="ulist"><ul><li><p>You’ve been around the ASF a long
time</p></li><li><p>You’re a Community Manager or Developer Advocate in
your "real life"</p></li><li><p>You have skills like metrics, doc writing,
event planning or anything
-else that might be of value to an open source
project</p></li></ul></div></li></ul></div></div></section>
+anything.</p></div></aside></div></section>
+<section id="wg-advisors-2"><h2>wg-advisors</h2><div
class="slide-content"><div class="imageblock"><img src="images/mentoring.jpg"
alt="mentoring"></div>
+<small>CC by Open Knowledge Foundation Deutschland, on Flickr</small>
+<aside class="notes"><div class="paragraph"><p>Every generation of a project
is responsible for mentoring the next
+generation. Failure to do do inevitably results in the drying up of new
+ideas.</p></div>
+<div class="paragraph"><p>wg-advisors helps bridge that gap, and should
<strong>always</strong> focus on enabling
+the project community to do the work rather than doing it for
them.</p></div></aside></div></section>
+<section id="how"><h2>How?</h2><div class="slide-content"><div
class="ulist"><ul><li><p>Listen more than you speak</p></li><li><p>Get to know
key people, and corporate participants, engaged in the
+project</p></li><li><p>Read board reports. Identify and solve
problems</p></li><li><p>Mentor people attempting to become committers or PMC
members, who
+don’t appear to be getting much support</p></li><li><p>Just generally
…​ become a part of the
community</p></li></ul></div></div></section>
<section id="wg-badging"><h2>wg-badging</h2><div class="slide-content"><div
class="imageblock"><img src="images/fas-paranoid-panda.png" alt="fas paranoid
panda"></div>
<div class="ulist"><ul><li><p>"Badges" to celebrate
accomplishments</p></li><li><p>Still in idea phase - could use your
help</p></li></ul></div>
-<aside class="notes"><div class="paragraph"><p>Picture: An example badge from
badges.fedoraproject.org</p></div></aside></div></section>
-<section><div class="slide-content"><div class="imageblock"><img
src="images/fedora-badges.png" alt="fedora badges"></div>
-<aside class="notes"><div class="paragraph"><p>Picture: Screenshot of
badges.fedoraproject.org</p></div>
-<div class="paragraph"><p>Concept based on the Fedora badging system - <a
href="https://badges.fedoraproject.org/";
class="bare">https://badges.fedoraproject.org/</a></p></div>
-<div class="paragraph"><p>Badges could celebrate your first PR, your 100th
closed issue, or your
-1000th email message. Or they could be event-based ("Attended Community
-Over Code Denver 2024")</p></div></aside></div></section>
-<section><div class="slide-content"><div class="imageblock"><img
src="images/reddit-badges.png" alt="reddit badges"></div>
-<aside class="notes"><div class="paragraph"><p>Picture: screenshot of Reddit
badges</p></div>
-<div class="paragraph"><p>Worth noting that some people find this frivolous,
or that it
-trivializes what we do. Other people like earning achievements,
-celebrating milestones, and trying new things.</p></div>
-<div class="paragraph"><p>If you don’t like this idea, then accept that
it’s not for you, and move
-on. You’re not obliged to participate.</p></div></aside></div></section>
-<section id="challenges"><h2>Challenges</h2><div class="slide-content"><div
class="ulist"><ul><li><p>There used to be a variety of open source badging
options. Most of
-them have gone closed, or died out</p></li><li><p>Would probably want it
integrated to some degree with participants'
-ApacheID, which would require knowledge of how that
works</p></li></ul></div></div></section>
-<section id="wg-code-of-conduct"><h2>wg-code-of-conduct</h2><div
class="slide-content"><div class="ulist"><ul><li><p>Providing a recommended
template for project code of conduct</p><div class="ulist"><ul><li><p>(Based on
the Contributor Covenant)</p></li><li><p><a
href="https://www.contributor-covenant.org/";
class="bare">https://www.contributor-covenant.org/</a></p></li></ul></div></li><li><p><strong>NOT</strong>
an enforcing body, nor are we requiring any project to do anything</p></li>
[...]
-<section id="wg-social"><h2>wg-social</h2><div class="slide-content"><div
class="ulist"><ul><li><p>AKA Party Working Group</p></li><li><p>Orchestrating
local <strong>social</strong> gathering of Apache
enthusiasts</p></li><li><p>See also ALC - Apache Local Communities - <a
href="https://s.apache.org/alc";
class="bare">https://s.apache.org/alc</a></p></li><li><p>Still in idea/startup
stage</p></li></ul></div></div></section>
-<section id="wg-social-media"><h2>wg-social-media</h2><div
class="slide-content"><div class="ulist"><ul><li><p>Write and publish content
on all social media platforms</p></li><li><p>Amplify the messages of our
projects, and help them craft better content</p></li><li><p>Coordinate with
M&P for consistent messaging</p></li><li><p>Still in idea/startup
stage</p></li></ul></div></div></section>
-<section><div class="slide-content"><div class="paragraph"><p><span
class="image"><img src="images/facebook.png" alt="facebook"></span></p></div>
-<aside class="notes"><div class="paragraph"><p>The Facebook page gets a lot of
beginner questions, as well as a lot of
-spam. Having a rotation of people to handle this, be friendly,
-welcoming, and informative, as well as posting regular topical content,
-would be great.</p></div></aside></div></section>
-<section><div class="slide-content"><div class="imageblock"><img
src="images/twitter.png" alt="twitter"></div>
-<aside class="notes"><div class="paragraph"><p>The official Twitter is handled
by M&P, but there are several other
-Twitter handles (@apachecommunity, and many project handles) and there
-are other social media outlets where we do not have a presence, but
-probably should. You can help make that
happen.</p></div></aside></div></section>
-<section id="wg-website"><h2>wg-website</h2><div class="slide-content"><div
class="imageblock"><img src="images/website.png" alt="website"></div>
-<aside class="notes"><div class="paragraph"><p>Picture: Screenshot of
community.apache.org</p></div>
-<div class="paragraph"><p>Yes, our website is terrible. Please come help
us.</p></div>
-<div class="paragraph"><p>Needs:
-* Information architecture.
-* Design.
-* Navigation by audience.
-* Content creation.</p></div></aside></div></section>
+<aside class="notes"><div class="paragraph"><p>Concept based on the Fedora
badging sysem - <a href="https://badges.fedoraproject.org/";
class="bare">https://badges.fedoraproject.org/</a></p></div></aside></div></section>
+<section id="fedora-badges"><h2>Fedora badges</h2><div
class="slide-content"><div class="imageblock"><img
src="images/fedora-badges.png" alt="fedora badges"></div>
+<aside class="notes"><div class="paragraph"><p>Some people love it. Some
people say gamification trivializes hard work,
+and rewards the wrong behavior. Come join the conversation.</p></div>
+<div class="paragraph"><p>What will we celebrate?
+* First commit, 100th commit
+* Becoming a commiter! Becoming a PMC member! Becoming a PMC chair!
+* Attending events
+* Being a RM
+* Voted on a release</p></div></aside></div></section>
+<section id="why-this-is-hard"><h2>Why this is hard</h2><div
class="slide-content"><div class="imageblock"><img
src="images/reddit-badges.png" alt="reddit badges"></div>
+<aside class="notes"><div class="paragraph"><p>There used to be a bunch of
open source badging solutions. They have all
+either gone closed source, or simply dried up.</p></div>
+<div class="paragraph"><p>Also, we would need to integrate with ASF LDAP in
some way. And adhere
+to GDPR and CRA and who knows what else. Come
help.</p></div></aside></div></section>
+<section id="wg-code-of-conduct"><h2>wg-code-of-conduct</h2><div
class="slide-content"><div class="ulist"><ul><li><p>Providing a recommended
template for project code of conduct</p><div class="ulist"><ul><li><p>(Based on
the Contributor Covenant)</p></li><li><p><a
href="https://www.contributor-covenant.org/";
class="bare">https://www.contributor-covenant.org/</a></p></li></ul></div></li></ul></div></div></section>
+<section id="code-of-conduct-what-its-not"><h2>Code of conduct: What
it’s <strong>NOT</strong></h2><div class="slide-content"><div
class="ulist"><ul><li><p><strong>NOT</strong> an enforcing body, nor are we
requiring any project to do anything</p></li><li><p><strong>NOT</strong>
working on a Foundation-level global Code of
Conduct</p></li></ul></div></div></section>
+<section id="wg-social"><h2>wg-social</h2><div class="slide-content"><div
class="imageblock"><img src="images/party.jpg" alt="party"></div>
+<small>CC by Dr. Matthias Ripp, on Flickr</small>
+<aside class="notes"><div class="ulist"><ul><li><p>Orchestrating local
gathering of Apache enthusiasts</p></li><li><p>AKA Party Working
Group</p></li><li><p>Still in idea/startup
stage</p></li></ul></div></aside></div></section>
+<section id="what-wg-social-might-do"><h2>What wg-social might do</h2><div
class="slide-content"><div class="ulist"><ul><li><p>Identify places where
there’s a concentration of ASF people, and
+encourage people visiting there to meet for a meal</p></li><li><p>Revive the
map? (Needs to respect privacy laws!)</p></li><li><p>Gatherings at major tech
events (FOSDEM, OSSummit, and so on)</p></li><li><p>Geeky movie
night!</p></li></ul></div></div></section>
+<section><div class="slide-content"><div class="imageblock"><img
src="images/eat-together.jpg" alt="eat together"></div>
+<small>CC by Kristopher Traquair, photos.apachecon.com</small>
+<aside class="notes"><div class="paragraph"><p>Communities who eat together
end up working together better. Identifying
+your colleagues as human, and not just lines of code, tends to make
+dealing with conflict a lot easier.</p></div></aside></div></section>
+<section id="alc"><h2>ALC</h2><div class="slide-content"><div
class="paragraph"><p>See also ALC - Apache Local Communities - <a
href="https://s.apache.org/alc"; class="bare">https://s.apache.org/alc</a> -
+that’s something different.</p></div></div></section>
+<section id="wg-social-media"><h2>wg-social-media</h2><div
class="slide-content"><div class="imageblock"><img src="images/twitter.png"
alt="twitter"></div>
+<aside class="notes"><div class="ulist"><ul><li><p>Write and publish content
on all social media platforms</p></li><li><p>Amplify the messages of our
projects, and help them craft better content</p></li><li><p>Coordinate with
M&P for consistent messaging</p></li><li><p>Still in idea/startup
stage</p></li></ul></div></aside></div></section>
+<section id="questions-to-be-addressed"><h2>Questions to be addressed</h2><div
class="slide-content"><div class="ulist"><ul><li><p>Should we keep using
Twitter?</p></li><li><p>Should we engage more in some other
platform?</p></li><li><p>What kind of content do we want to
post?</p></li><li><p>And, as always, the focus should remain on building strong
ASF
+communities</p></li></ul></div></div></section>
+<section id="wg-website"><h2>wg-website</h2><div class="slide-content"><div
class="paragraph"><p><a href="https://community.apache.org/";
class="bare">https://community.apache.org/</a></p></div>
+<div class="imageblock"><img src="images/website.png" alt="website"></div>
+<aside class="notes"><div class="ulist"><ul><li><p>Yes, our website is
objectively terrible. We know. Come
help.</p></li></ul></div></aside></div></section>
<section id="wg-welcome"><h2>wg-welcome</h2><div class="slide-content"><div
class="ulist"><ul><li><p>Helping projects, and the ASF in general, be more
welcoming</p></li><li><p>e.g. …​</p><div
class="ulist"><ul><li><p>helping projects write better project
definitions</p></li><li><p>answering beginner questions on dev@community or
elsewhere</p></li></ul></div></li></ul></div></div></section>
-<section id="wg-welcome-sample-answers"><h2>wg-welcome - Sample
answers</h2><div class="slide-content"><div class="ulist"><ul><li><p>(See Git
repo)</p></li><li><p>Provides sample/boilerplate answers to common
questions</p></li></ul></div>
-<div class="imageblock"><img src="images/sample-answer.png" alt="sample
answer"></div>
-<aside class="notes"><div class="paragraph"><p>Picture: Screenshot of one of
the sample answers</p></div></aside></div></section>
-<section id="sample-answers"><h2>Sample Answers</h2><div
class="slide-content"><div class="ulist"><ul><li><p>Why do we need sample
answers?</p><div class="ulist"><ul><li><p>Consistent
messaging</p></li><li><p>Thorough, friendly answers with
links</p></li></ul></div></li></ul></div>
+<section id="wg-welcome-sample-answers"><h2>wg-welcome - Sample
answers</h2><div class="slide-content"><div class="imageblock"><img
src="images/sample-answer.png" alt="sample answer"></div>
+<aside class="notes"><div class="ulist"><ul><li><p>(See Git
repo)</p></li><li><p>Provides sample/boilerplate answers to common
questions</p></li></ul></div></aside></div></section>
+<section id="sample-answers"><h2>Sample answers</h2><div
class="slide-content"><div class="ulist"><ul><li><p>Why?</p><div
class="ulist"><ul><li><p>Consistent messaging</p></li><li><p>Thorough, friendly
answers with links</p></li></ul></div></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Using the recommended sample
answer ensures that canonical links are
-provided, and that we are giving people consistent answers.</p></div>
-<div class="paragraph"><p>Perhaps more importantly, it lets
<strong>anyone</strong> jump in with the right
-answer, and this gets more people engaged in community
support.</p></div></aside></div></section>
-<section id="wg-your-idea-here"><h2>wg-your-idea-here</h2><div
class="slide-content"><div class="ulist"><ul><li><p>Is there something
you’re passionate about and want to gather a group of like-minded people
to work on it?</p></li><li><p>Propose your WG on <a
href="mailto:[email protected]";>[email protected]</a></p></li></ul></div></div></section>
+provided, and that we are giving people consistent
answers.</p></div></aside></div></section>
+<section><div class="slide-content"><div class="imageblock"><img
src="images/dive.jpg" alt="dive"></div>
+<aside class="notes"><div class="paragraph"><p>Perhaps more importantly, it
lets <strong>anyone</strong> jump in with the right
+answer, and this gets more people engaged in community support. Over
+time, as they build their confidence, they can do more.</p></div></aside>
+<div class="paragraph"><p>==!</p></div>
+<div class="imageblock"><img src="images/shark.jpg" alt="shark"></div>
+<aside class="notes"><div class="paragraph"><p>And, let’s be honest, we
are not always the most welcoming of people.
+Questions like "how do I get involved" are <strong>often</strong> answered by
"go look
+at the projects lists and pick one and start doing stuff!" which is not
+anything more than they already knew. Crafting helpful, welcoming
+answers, and encouraging projects to do the same, will lead to more
+welcoming contributor onboarding.</p></div></aside></div></section>
+<section id="wg-your-idea-here"><h2>wg-your-idea-here</h2><div
class="slide-content"><div class="ulist"><ul><li><p>Is there something
you’re passionate about and want to gather a group of like-minded people
to work on it?</p></li><li><p>Propose your WG on <a
href="mailto:[email protected]";>[email protected]</a></p></li></ul></div>
+<aside class="notes"><div class="paragraph"><p>Useful when you really think
something should happen, but know that you
+can’t do it on your own. Come propose the
WG!</p></div></aside></div></section>
<section id="how-to-communicate"><h2>How to communicate</h2><div
class="slide-content"><div class="imageblock"><img src="images/wg-email.png"
alt="wg email"></div>
-<div class="ulist"><ul><li><p>Send email to <a
href="mailto:[email protected]";>[email protected]</a></p></li><li><p>Use
a Subject: line tag identifying the working group</p></li></ul></div>
-<aside class="notes"><div class="paragraph"><p>Picture: Email headers showing
how to communicate about working groups</p></div></aside></div></section>
+<div class="ulist"><ul><li><p>Send email to <a
href="mailto:[email protected]";>[email protected]</a></p></li><li><p>Use
a Subject: line tag identifying the working
group</p></li></ul></div></div></section>
<section id="getting-involved"><h2>Getting involved</h2><div
class="slide-content"><div class="ulist"><ul><li><p>Show
up</p></li><li><p>Introduce yourself</p></li><li><p>Say what you want to work
on</p></li><li><p>Then <strong>start doing it</strong>. You are
allowed.</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>The key point here is that
<strong>you</strong> are the owner of the working group.
You don’t have to get permission or approval for your idea, as long as
you are transparent/public about what you’re working on, and welcome
feedback and discussion.</p></div></aside></div></section>
+<section id="other-working-groups"><h2>Other working groups</h2><div
class="slide-content"><div class="paragraph"><p>Working groups outside of
ComDev</p></div></div></section>
+<section id="orc-wg"><h2>ORC WG</h2><div class="slide-content"><div
class="ulist"><ul><li><p>Open Regulatory Compliance working
group</p></li></ul></div>
+<div class="imageblock"><img src="images/orc_wg.png" alt="orc wg"></div>
+<aside class="notes"><div class="paragraph"><p>Collaboration between Eclipse,
Apache, and other open source
+non-profits.</p></div></aside></div></section>
+<section id="member-level-working-groups"><h2>Member-level working
groups</h2><div class="slide-content"><div class="ulist"><ul><li><p>Governance
committee</p></li><li><p>Communication platforms
WG</p></li></ul></div></div></section>
+<section id="not-a-working-group-but"><h2>Not a working group, but
…​</h2><div class="slide-content"><div
class="paragraph"><p>TRAINING.apache.org produces training materials for
projects, and about
+the ASF as a whole, for use in your presentations, meetups, and so on,
+all under the Apache License, so that you can grab one and use it as a
+starting point.</p></div></div></section>
<section id="more-info"><h2>More Info</h2><div class="slide-content"><div
class="paragraph"><p><a href="https://community.apache.org/workinggroups";
class="bare">https://community.apache.org/workinggroups</a></p></div></div></section>
<section id="questions"><h2>Questions?</h2><div class="slide-content"><div
class="paragraph"><p>This presentation is part of the Apache Training
(Incubating) project,
and under the AL2.0 license.</p></div>
<div class="paragraph"><p><a href="https://training.apache.org/";
class="bare">https://training.apache.org/</a></p></div>
-<div class="imageblock"><img src="images/training-logo.svg" alt="training
logo"></div></div></section></div></div><div class="footer"><div
class="left"></div><div class="right"></div></div><script
src="reveal.js-5.1.0/dist/reveal.js"></script><script>Array.prototype.slice.call(document.querySelectorAll('.slides
section')).forEach(function(slide) {
+<div class="imageblock"><img src="images/training-logo.svg" alt="training
logo"></div>
+<aside class="notes"><div class="paragraph"><p>Where not noted, photos are CC
by Rich Bowen</p></div></aside></div></section></div></div><div
class="footer"><div class="left"></div><div class="right"></div></div><script
src="reveal.js-5.1.0/dist/reveal.js"></script><script>Array.prototype.slice.call(document.querySelectorAll('.slides
section')).forEach(function(slide) {
if (slide.getAttribute('data-background-color')) return;
// user needs to explicitly say he wants CSS color to override otherwise we
might break custom css or theme (#226)
if (!(slide.classList.contains('canvas') ||
slide.classList.contains('background'))) return;
@@ -641,7 +637,7 @@ Reveal.initialize({
// present. If this is set to a nonzero value, the pacing
// timer will work out the time available for each slide,
// instead of using the defaultTiming value
- totalTime: 2100,
+ totalTime: 0,
// Specify the minimum amount of time you want to allot to
// each slide, if using the totalTime calculation method. If
// the automated time allocation causes slide pacing to fall
diff --git a/presentations/training/demo/index.html
b/presentations/training/demo/index.html
index 539a576..a4f6a08 100644
--- a/presentations/training/demo/index.html
+++ b/presentations/training/demo/index.html
@@ -414,7 +414,7 @@ ul.byline li + li {
margin-top: 0.25em;
}
</style><link rel="stylesheet"
href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.1/css/all.min.css";
/><link rel="stylesheet"
href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.1/css/v4-shims.min.css";
/></head><body><div class="header"><div class="left"></div><div
class="right"></div></div><div class="reveal"><div class="slides"><section
id="example-presentation"><h2>Example Presentation</h2><div
class="slide-content"><div class="paragraph"><p>Doc Writer <<a hr [...]
-2024-09-17
+2024-09-25
:revnumber: 1.0.0-SNAPSHOT
:example-caption!:</p></div></div></section>
<section id="introduction"><h2>Introduction</h2><div
class="slide-content"><div class="ulist"><ul><li class="fragment"><p>This is a
presentation for an example project.</p></li><li class="fragment"><p>This
project does something.</p></li><li class="fragment"><p>We just haven’t
decided what that is yet.</p></li></ul></div></div></section>
