You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@community.apache.org by gi...@apache.org on 2023/03/30 13:42:37 UTC
[comdev-site] branch asf-site updated: Updated asf-site from master at b9492637bfd5622ba2a17d40a309dd5e67b3373a using https://ci-builds.apache.org/job/Community%20Development/job/site/job/master/231/
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/comdev-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new df9519d Updated asf-site from master at b9492637bfd5622ba2a17d40a309dd5e67b3373a using https://ci-builds.apache.org/job/Community%20Development/job/site/job/master/231/
df9519d is described below
commit df9519d1bacd0083eb294a9d4605176d24bcc69b
Author: jenkins <bu...@apache.org>
AuthorDate: Thu Mar 30 13:42:34 2023 +0000
Updated asf-site from master at b9492637bfd5622ba2a17d40a309dd5e67b3373a using https://ci-builds.apache.org/job/Community%20Development/job/site/job/master/231/
---
content/_pagefind/fragment/en_11eb579.pf_fragment | Bin 0 -> 1329 bytes
content/_pagefind/fragment/en_1c71581.pf_fragment | Bin 0 -> 2292 bytes
content/_pagefind/fragment/en_1f584a2.pf_fragment | Bin 0 -> 748 bytes
content/_pagefind/fragment/en_218bbc7.pf_fragment | Bin 0 -> 4694 bytes
content/_pagefind/fragment/en_22632fe.pf_fragment | Bin 0 -> 1580 bytes
content/_pagefind/fragment/en_32a72eb.pf_fragment | Bin 0 -> 3212 bytes
content/_pagefind/fragment/en_4189226.pf_fragment | Bin 0 -> 1473 bytes
content/_pagefind/fragment/en_42e388d.pf_fragment | Bin 0 -> 4298 bytes
content/_pagefind/fragment/en_491b982.pf_fragment | Bin 0 -> 886 bytes
content/_pagefind/fragment/en_4dc7388.pf_fragment | Bin 0 -> 817 bytes
content/_pagefind/fragment/en_54f4a2a.pf_fragment | Bin 0 -> 866 bytes
content/_pagefind/fragment/en_5f79579.pf_fragment | Bin 0 -> 2397 bytes
content/_pagefind/fragment/en_71144ab.pf_fragment | Bin 0 -> 652 bytes
content/_pagefind/fragment/en_7351c8b.pf_fragment | Bin 0 -> 1457 bytes
content/_pagefind/fragment/en_79ce9ac.pf_fragment | Bin 0 -> 2024 bytes
content/_pagefind/fragment/en_7ec04d7.pf_fragment | Bin 0 -> 1019 bytes
content/_pagefind/fragment/en_7fa8531.pf_fragment | Bin 0 -> 1412 bytes
content/_pagefind/fragment/en_7fdb7e7.pf_fragment | Bin 0 -> 1222 bytes
content/_pagefind/fragment/en_83b6ba1.pf_fragment | Bin 0 -> 648 bytes
content/_pagefind/fragment/en_84d2a09.pf_fragment | Bin 0 -> 937 bytes
content/_pagefind/fragment/en_8966534.pf_fragment | Bin 0 -> 964 bytes
content/_pagefind/fragment/en_8cc9acf.pf_fragment | Bin 0 -> 2814 bytes
content/_pagefind/fragment/en_8ce0667.pf_fragment | Bin 0 -> 652 bytes
content/_pagefind/fragment/en_92956ef.pf_fragment | Bin 0 -> 652 bytes
content/_pagefind/fragment/en_93fd2a2.pf_fragment | Bin 0 -> 1831 bytes
content/_pagefind/fragment/en_9dbf935.pf_fragment | Bin 0 -> 653 bytes
content/_pagefind/fragment/en_9dc95c7.pf_fragment | Bin 0 -> 830 bytes
content/_pagefind/fragment/en_9de1c5a.pf_fragment | Bin 0 -> 2580 bytes
content/_pagefind/fragment/en_9f1316a.pf_fragment | Bin 0 -> 2447 bytes
content/_pagefind/fragment/en_9fb5a1d.pf_fragment | Bin 0 -> 989 bytes
content/_pagefind/fragment/en_a6833eb.pf_fragment | Bin 0 -> 4130 bytes
content/_pagefind/fragment/en_a8325ac.pf_fragment | Bin 0 -> 1199 bytes
content/_pagefind/fragment/en_a9365ce.pf_fragment | Bin 0 -> 987 bytes
content/_pagefind/fragment/en_b9e55bf.pf_fragment | Bin 0 -> 2063 bytes
content/_pagefind/fragment/en_bb2ae1e.pf_fragment | Bin 0 -> 1347 bytes
content/_pagefind/fragment/en_c47a599.pf_fragment | Bin 0 -> 5650 bytes
content/_pagefind/fragment/en_cd9ae1d.pf_fragment | Bin 0 -> 2076 bytes
content/_pagefind/fragment/en_cff12d9.pf_fragment | Bin 0 -> 2785 bytes
content/_pagefind/fragment/en_d0c851f.pf_fragment | Bin 0 -> 1271 bytes
content/_pagefind/fragment/en_d35dd0f.pf_fragment | Bin 0 -> 788 bytes
content/_pagefind/fragment/en_d365f4b.pf_fragment | Bin 0 -> 1697 bytes
content/_pagefind/fragment/en_d7ca3be.pf_fragment | Bin 0 -> 10016 bytes
content/_pagefind/fragment/en_e0db249.pf_fragment | Bin 0 -> 1280 bytes
content/_pagefind/fragment/en_e5411f9.pf_fragment | Bin 0 -> 3373 bytes
content/_pagefind/fragment/en_e8302c8.pf_fragment | Bin 0 -> 3584 bytes
content/_pagefind/fragment/en_ea3879a.pf_fragment | Bin 0 -> 1314 bytes
content/_pagefind/fragment/en_ec5d61f.pf_fragment | Bin 0 -> 1231 bytes
content/_pagefind/fragment/en_f323563.pf_fragment | Bin 0 -> 1678 bytes
content/_pagefind/fragment/en_f3a482f.pf_fragment | Bin 0 -> 990 bytes
content/_pagefind/fragment/en_f5be8dc.pf_fragment | Bin 0 -> 4420 bytes
content/_pagefind/fragment/en_f9a9b48.pf_fragment | Bin 0 -> 1902 bytes
content/_pagefind/index/en_2d1c491.pf_index | Bin 0 -> 41854 bytes
content/_pagefind/index/en_515c41b.pf_index | Bin 0 -> 40337 bytes
content/_pagefind/index/en_cd35e47.pf_index | Bin 0 -> 14175 bytes
content/_pagefind/pagefind-entry.json | 1 +
content/_pagefind/pagefind-modular-ui.css | 214 ++++++++++++++
content/_pagefind/pagefind-modular-ui.js | 7 +
content/_pagefind/pagefind-ui.css | 1 +
content/_pagefind/pagefind-ui.js | 1 +
content/_pagefind/pagefind.en_33d979aeb8.pf_meta | Bin 0 -> 509 bytes
content/_pagefind/pagefind.js | 1 +
content/_pagefind/wasm.en.pagefind | Bin 0 -> 56984 bytes
content/_pagefind/wasm.unknown.pagefind | Bin 0 -> 52157 bytes
content/about/index.html | 91 ++++--
content/about/index.xml | 11 +-
content/apache-way.html | 16 +-
.../apache-way/apache-project-maturity-model.html | 221 +++++++++++----
content/apache-way/index.xml | 12 +-
content/boardreport.html | 19 +-
content/calendars/conferences.html | 35 ++-
content/calendars/index.html | 33 ++-
content/calendars/index.xml | 15 +-
content/comdevboardreports.html | 19 +-
content/committers/consensusBuilding.html | 42 ++-
content/committers/decisionMaking.html | 37 ++-
content/committers/funding-disclaimer.html | 50 +++-
content/committers/index.html | 67 ++++-
content/committers/index.xml | 15 +-
content/committers/lazyConsensus.html | 38 ++-
content/committers/voting.html | 38 ++-
content/contactpoints.html | 67 ++++-
content/contributors/becomingacommitter.html | 100 +++++--
content/contributors/etiquette.html | 90 +++---
content/contributors/index.html | 52 +++-
content/contributors/index.xml | 15 +-
content/events.html | 16 +-
content/events/index.xml | 12 +-
content/events/small-events.html | 37 ++-
.../{gettingstarted.html => gettingStarted.html} | 18 +-
content/gettingStarted/101.html | 50 +++-
content/gettingStarted/index.xml | 24 ++
content/gettingstarted/index.xml | 20 --
content/gsoc/experiences.html | 73 +++--
content/gsoc/gsoc-admin-tasks.html | 101 +++----
content/gsoc/guide-to-being-a-mentor.html | 90 ++++--
content/gsoc/index.html | 130 +++++++--
content/gsoc/index.xml | 38 +--
content/gsoc/mentee-ranking-process.html | 179 ++++++++----
...e-comdev-gsoc-issue-tracker-for-gsoc-tasks.html | 25 +-
content/history.html | 16 +-
content/history/boardresolution.html | 31 +-
content/history/index.xml | 14 +-
.../history/mentoringprogramme-icfoss-pilot.html | 116 +++++---
content/index.html | 169 ++++++++---
content/index.xml | 158 ++++++-----
content/links.html | 47 +++-
content/lists.html | 43 ++-
content/mentor-request-mail.html | 99 ++++---
content/mentoring/committer.html | 32 ++-
content/mentoring/firstpatch.html | 34 ++-
content/mentoring/index.html | 24 +-
content/mentoring/index.xml | 45 +--
content/mentoring/mentor.html | 29 +-
content/mentoring/pmc.html | 30 +-
content/newbiefaq.html | 124 ++++++--
content/newcomers/index.html | 29 +-
content/newcomers/index.xml | 11 +-
content/newcommitter.html | 207 ++++++++++----
content/newsletter/2017-04.html | 80 ++++--
content/newsletter/2017-05.html | 23 +-
content/newsletter/index.html | 22 +-
content/newsletter/index.xml | 13 +-
content/projectIndependence.html | 54 +++-
content/proposals.html | 16 +-
content/proposals/ZestProposal.html | 312 +++++++++++++--------
content/proposals/index.xml | 14 +-
content/sitemap.xml | 241 +++++++++++-----
content/speakers/index.html | 36 ++-
content/speakers/index.xml | 15 +-
content/speakers/slides.html | 105 +++++--
content/speakers/speakers.html | 72 +++--
131 files changed, 3281 insertions(+), 1101 deletions(-)
diff --git a/content/_pagefind/fragment/en_11eb579.pf_fragment b/content/_pagefind/fragment/en_11eb579.pf_fragment
new file mode 100644
index 0000000..c60c06a
Binary files /dev/null and b/content/_pagefind/fragment/en_11eb579.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_1c71581.pf_fragment b/content/_pagefind/fragment/en_1c71581.pf_fragment
new file mode 100644
index 0000000..2718bb2
Binary files /dev/null and b/content/_pagefind/fragment/en_1c71581.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_1f584a2.pf_fragment b/content/_pagefind/fragment/en_1f584a2.pf_fragment
new file mode 100644
index 0000000..03d51c1
Binary files /dev/null and b/content/_pagefind/fragment/en_1f584a2.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_218bbc7.pf_fragment b/content/_pagefind/fragment/en_218bbc7.pf_fragment
new file mode 100644
index 0000000..1fc3005
Binary files /dev/null and b/content/_pagefind/fragment/en_218bbc7.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_22632fe.pf_fragment b/content/_pagefind/fragment/en_22632fe.pf_fragment
new file mode 100644
index 0000000..b45b30d
Binary files /dev/null and b/content/_pagefind/fragment/en_22632fe.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_32a72eb.pf_fragment b/content/_pagefind/fragment/en_32a72eb.pf_fragment
new file mode 100644
index 0000000..94aedb8
Binary files /dev/null and b/content/_pagefind/fragment/en_32a72eb.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_4189226.pf_fragment b/content/_pagefind/fragment/en_4189226.pf_fragment
new file mode 100644
index 0000000..eb4ae14
Binary files /dev/null and b/content/_pagefind/fragment/en_4189226.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_42e388d.pf_fragment b/content/_pagefind/fragment/en_42e388d.pf_fragment
new file mode 100644
index 0000000..ec94ca6
Binary files /dev/null and b/content/_pagefind/fragment/en_42e388d.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_491b982.pf_fragment b/content/_pagefind/fragment/en_491b982.pf_fragment
new file mode 100644
index 0000000..f67022b
Binary files /dev/null and b/content/_pagefind/fragment/en_491b982.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_4dc7388.pf_fragment b/content/_pagefind/fragment/en_4dc7388.pf_fragment
new file mode 100644
index 0000000..e490479
Binary files /dev/null and b/content/_pagefind/fragment/en_4dc7388.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_54f4a2a.pf_fragment b/content/_pagefind/fragment/en_54f4a2a.pf_fragment
new file mode 100644
index 0000000..b2b17bd
Binary files /dev/null and b/content/_pagefind/fragment/en_54f4a2a.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_5f79579.pf_fragment b/content/_pagefind/fragment/en_5f79579.pf_fragment
new file mode 100644
index 0000000..4824cf6
Binary files /dev/null and b/content/_pagefind/fragment/en_5f79579.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_71144ab.pf_fragment b/content/_pagefind/fragment/en_71144ab.pf_fragment
new file mode 100644
index 0000000..e85639d
Binary files /dev/null and b/content/_pagefind/fragment/en_71144ab.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_7351c8b.pf_fragment b/content/_pagefind/fragment/en_7351c8b.pf_fragment
new file mode 100644
index 0000000..ad05175
Binary files /dev/null and b/content/_pagefind/fragment/en_7351c8b.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_79ce9ac.pf_fragment b/content/_pagefind/fragment/en_79ce9ac.pf_fragment
new file mode 100644
index 0000000..7726284
Binary files /dev/null and b/content/_pagefind/fragment/en_79ce9ac.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_7ec04d7.pf_fragment b/content/_pagefind/fragment/en_7ec04d7.pf_fragment
new file mode 100644
index 0000000..62bd74f
Binary files /dev/null and b/content/_pagefind/fragment/en_7ec04d7.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_7fa8531.pf_fragment b/content/_pagefind/fragment/en_7fa8531.pf_fragment
new file mode 100644
index 0000000..39b8727
Binary files /dev/null and b/content/_pagefind/fragment/en_7fa8531.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_7fdb7e7.pf_fragment b/content/_pagefind/fragment/en_7fdb7e7.pf_fragment
new file mode 100644
index 0000000..5466375
Binary files /dev/null and b/content/_pagefind/fragment/en_7fdb7e7.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_83b6ba1.pf_fragment b/content/_pagefind/fragment/en_83b6ba1.pf_fragment
new file mode 100644
index 0000000..ac453ef
Binary files /dev/null and b/content/_pagefind/fragment/en_83b6ba1.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_84d2a09.pf_fragment b/content/_pagefind/fragment/en_84d2a09.pf_fragment
new file mode 100644
index 0000000..18fd32e
Binary files /dev/null and b/content/_pagefind/fragment/en_84d2a09.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_8966534.pf_fragment b/content/_pagefind/fragment/en_8966534.pf_fragment
new file mode 100644
index 0000000..1f054ba
Binary files /dev/null and b/content/_pagefind/fragment/en_8966534.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_8cc9acf.pf_fragment b/content/_pagefind/fragment/en_8cc9acf.pf_fragment
new file mode 100644
index 0000000..b9a86d1
Binary files /dev/null and b/content/_pagefind/fragment/en_8cc9acf.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_8ce0667.pf_fragment b/content/_pagefind/fragment/en_8ce0667.pf_fragment
new file mode 100644
index 0000000..3645457
Binary files /dev/null and b/content/_pagefind/fragment/en_8ce0667.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_92956ef.pf_fragment b/content/_pagefind/fragment/en_92956ef.pf_fragment
new file mode 100644
index 0000000..da1efed
Binary files /dev/null and b/content/_pagefind/fragment/en_92956ef.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_93fd2a2.pf_fragment b/content/_pagefind/fragment/en_93fd2a2.pf_fragment
new file mode 100644
index 0000000..9ad9c45
Binary files /dev/null and b/content/_pagefind/fragment/en_93fd2a2.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_9dbf935.pf_fragment b/content/_pagefind/fragment/en_9dbf935.pf_fragment
new file mode 100644
index 0000000..7720c5c
Binary files /dev/null and b/content/_pagefind/fragment/en_9dbf935.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_9dc95c7.pf_fragment b/content/_pagefind/fragment/en_9dc95c7.pf_fragment
new file mode 100644
index 0000000..49baef3
Binary files /dev/null and b/content/_pagefind/fragment/en_9dc95c7.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_9de1c5a.pf_fragment b/content/_pagefind/fragment/en_9de1c5a.pf_fragment
new file mode 100644
index 0000000..a35e8eb
Binary files /dev/null and b/content/_pagefind/fragment/en_9de1c5a.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_9f1316a.pf_fragment b/content/_pagefind/fragment/en_9f1316a.pf_fragment
new file mode 100644
index 0000000..33bc22c
Binary files /dev/null and b/content/_pagefind/fragment/en_9f1316a.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_9fb5a1d.pf_fragment b/content/_pagefind/fragment/en_9fb5a1d.pf_fragment
new file mode 100644
index 0000000..ed2cac9
Binary files /dev/null and b/content/_pagefind/fragment/en_9fb5a1d.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_a6833eb.pf_fragment b/content/_pagefind/fragment/en_a6833eb.pf_fragment
new file mode 100644
index 0000000..7638b04
Binary files /dev/null and b/content/_pagefind/fragment/en_a6833eb.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_a8325ac.pf_fragment b/content/_pagefind/fragment/en_a8325ac.pf_fragment
new file mode 100644
index 0000000..5ec8f99
Binary files /dev/null and b/content/_pagefind/fragment/en_a8325ac.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_a9365ce.pf_fragment b/content/_pagefind/fragment/en_a9365ce.pf_fragment
new file mode 100644
index 0000000..ecad904
Binary files /dev/null and b/content/_pagefind/fragment/en_a9365ce.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_b9e55bf.pf_fragment b/content/_pagefind/fragment/en_b9e55bf.pf_fragment
new file mode 100644
index 0000000..30c0632
Binary files /dev/null and b/content/_pagefind/fragment/en_b9e55bf.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_bb2ae1e.pf_fragment b/content/_pagefind/fragment/en_bb2ae1e.pf_fragment
new file mode 100644
index 0000000..024fcc4
Binary files /dev/null and b/content/_pagefind/fragment/en_bb2ae1e.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_c47a599.pf_fragment b/content/_pagefind/fragment/en_c47a599.pf_fragment
new file mode 100644
index 0000000..d9e6df8
Binary files /dev/null and b/content/_pagefind/fragment/en_c47a599.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_cd9ae1d.pf_fragment b/content/_pagefind/fragment/en_cd9ae1d.pf_fragment
new file mode 100644
index 0000000..0bb50af
Binary files /dev/null and b/content/_pagefind/fragment/en_cd9ae1d.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_cff12d9.pf_fragment b/content/_pagefind/fragment/en_cff12d9.pf_fragment
new file mode 100644
index 0000000..bc9682a
Binary files /dev/null and b/content/_pagefind/fragment/en_cff12d9.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_d0c851f.pf_fragment b/content/_pagefind/fragment/en_d0c851f.pf_fragment
new file mode 100644
index 0000000..37b26a2
Binary files /dev/null and b/content/_pagefind/fragment/en_d0c851f.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_d35dd0f.pf_fragment b/content/_pagefind/fragment/en_d35dd0f.pf_fragment
new file mode 100644
index 0000000..93d1d3e
Binary files /dev/null and b/content/_pagefind/fragment/en_d35dd0f.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_d365f4b.pf_fragment b/content/_pagefind/fragment/en_d365f4b.pf_fragment
new file mode 100644
index 0000000..1e6821f
Binary files /dev/null and b/content/_pagefind/fragment/en_d365f4b.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_d7ca3be.pf_fragment b/content/_pagefind/fragment/en_d7ca3be.pf_fragment
new file mode 100644
index 0000000..6bdbfb6
Binary files /dev/null and b/content/_pagefind/fragment/en_d7ca3be.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_e0db249.pf_fragment b/content/_pagefind/fragment/en_e0db249.pf_fragment
new file mode 100644
index 0000000..c403556
Binary files /dev/null and b/content/_pagefind/fragment/en_e0db249.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_e5411f9.pf_fragment b/content/_pagefind/fragment/en_e5411f9.pf_fragment
new file mode 100644
index 0000000..4e5a37c
Binary files /dev/null and b/content/_pagefind/fragment/en_e5411f9.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_e8302c8.pf_fragment b/content/_pagefind/fragment/en_e8302c8.pf_fragment
new file mode 100644
index 0000000..8b1c771
Binary files /dev/null and b/content/_pagefind/fragment/en_e8302c8.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_ea3879a.pf_fragment b/content/_pagefind/fragment/en_ea3879a.pf_fragment
new file mode 100644
index 0000000..609cbeb
Binary files /dev/null and b/content/_pagefind/fragment/en_ea3879a.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_ec5d61f.pf_fragment b/content/_pagefind/fragment/en_ec5d61f.pf_fragment
new file mode 100644
index 0000000..c81a74c
Binary files /dev/null and b/content/_pagefind/fragment/en_ec5d61f.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_f323563.pf_fragment b/content/_pagefind/fragment/en_f323563.pf_fragment
new file mode 100644
index 0000000..962aac7
Binary files /dev/null and b/content/_pagefind/fragment/en_f323563.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_f3a482f.pf_fragment b/content/_pagefind/fragment/en_f3a482f.pf_fragment
new file mode 100644
index 0000000..c9523a8
Binary files /dev/null and b/content/_pagefind/fragment/en_f3a482f.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_f5be8dc.pf_fragment b/content/_pagefind/fragment/en_f5be8dc.pf_fragment
new file mode 100644
index 0000000..604b0dc
Binary files /dev/null and b/content/_pagefind/fragment/en_f5be8dc.pf_fragment differ
diff --git a/content/_pagefind/fragment/en_f9a9b48.pf_fragment b/content/_pagefind/fragment/en_f9a9b48.pf_fragment
new file mode 100644
index 0000000..4987240
Binary files /dev/null and b/content/_pagefind/fragment/en_f9a9b48.pf_fragment differ
diff --git a/content/_pagefind/index/en_2d1c491.pf_index b/content/_pagefind/index/en_2d1c491.pf_index
new file mode 100644
index 0000000..000c68a
Binary files /dev/null and b/content/_pagefind/index/en_2d1c491.pf_index differ
diff --git a/content/_pagefind/index/en_515c41b.pf_index b/content/_pagefind/index/en_515c41b.pf_index
new file mode 100644
index 0000000..1f28ba1
Binary files /dev/null and b/content/_pagefind/index/en_515c41b.pf_index differ
diff --git a/content/_pagefind/index/en_cd35e47.pf_index b/content/_pagefind/index/en_cd35e47.pf_index
new file mode 100644
index 0000000..971c45d
Binary files /dev/null and b/content/_pagefind/index/en_cd35e47.pf_index differ
diff --git a/content/_pagefind/pagefind-entry.json b/content/_pagefind/pagefind-entry.json
new file mode 100644
index 0000000..7e54bca
--- /dev/null
+++ b/content/_pagefind/pagefind-entry.json
@@ -0,0 +1 @@
+{"version":"0.12.0","languages":{"en":{"hash":"en_33d979aeb8","wasm":"en","page_count":51}}}
\ No newline at end of file
diff --git a/content/_pagefind/pagefind-modular-ui.css b/content/_pagefind/pagefind-modular-ui.css
new file mode 100644
index 0000000..9c6793e
--- /dev/null
+++ b/content/_pagefind/pagefind-modular-ui.css
@@ -0,0 +1,214 @@
+:root {
+ --pagefind-ui-scale: 0.8;
+ --pagefind-ui-primary: #034AD8;
+ --pagefind-ui-fade: #707070;
+ --pagefind-ui-text: #393939;
+ --pagefind-ui-background: #ffffff;
+ --pagefind-ui-border: #eeeeee;
+ --pagefind-ui-tag: #eeeeee;
+ --pagefind-ui-border-width: 2px;
+ --pagefind-ui-border-radius: 8px;
+ --pagefind-ui-image-border-radius: 8px;
+ --pagefind-ui-image-box-ratio: 3 / 2;
+ --pagefind-ui-font: system, -apple-system, ".SFNSText-Regular",
+ "San Francisco", "Roboto", "Segoe UI", "Helvetica Neue",
+ "Lucida Grande", sans-serif;
+}
+
+[data-pfmod-hidden] {
+ display: none !important;
+}
+
+[data-pfmod-suppressed] {
+ opacity: 0 !important;
+ pointer-events: none !important;
+}
+
+[data-pfmod-sr-hidden] {
+ -webkit-clip: rect(0 0 0 0) !important;
+ clip: rect(0 0 0 0) !important;
+ -webkit-clip-path: inset(100%) !important;
+ clip-path: inset(100%) !important;
+ height: 1px !important;
+ overflow: hidden !important;
+ overflow: clip !important;
+ position: absolute !important;
+ white-space: nowrap !important;
+ width: 1px !important;
+}
+
+[data-pfmod-loading] {
+ color: var(--pagefind-ui-text);
+ background-color: var(--pagefind-ui-text);
+ border-radius: var(--pagefind-ui-border-radius);
+ opacity: 0.1;
+ pointer-events: none;
+}
+
+/* Input */
+
+.pagefind-modular-input-wrapper {
+ position: relative;
+}
+
+.pagefind-modular-input-wrapper::before {
+ background-color: var(--pagefind-ui-text);
+ width: calc(18px * var(--pagefind-ui-scale));
+ height: calc(18px * var(--pagefind-ui-scale));
+ top: calc(23px * var(--pagefind-ui-scale));
+ left: calc(20px * var(--pagefind-ui-scale));
+ content: "";
+ position: absolute;
+ display: block;
+ opacity: 0.7;
+ -webkit-mask-image: url("data:image/svg+xml,%3Csvg width='18' height='18' viewBox='0 0 18 18' fill='none' xmlns='http://www.w3.org/2000/svg'%3E%3Cpath d='M12.7549 11.255H11.9649L11.6849 10.985C12.6649 9.845 13.2549 8.365 13.2549 6.755C13.2549 3.165 10.3449 0.255005 6.75488 0.255005C3.16488 0.255005 0.254883 3.165 0.254883 6.755C0.254883 10.345 3.16488 13.255 6.75488 13.255C8.36488 13.255 9.84488 12.665 10.9849 11.685L11.2549 11.965V12.755L16.2549 17.745L17.7449 16.255L12.7549 11.255Z [...]
+ mask-image: url("data:image/svg+xml,%3Csvg width='18' height='18' viewBox='0 0 18 18' fill='none' xmlns='http://www.w3.org/2000/svg'%3E%3Cpath d='M12.7549 11.255H11.9649L11.6849 10.985C12.6649 9.845 13.2549 8.365 13.2549 6.755C13.2549 3.165 10.3449 0.255005 6.75488 0.255005C3.16488 0.255005 0.254883 3.165 0.254883 6.755C0.254883 10.345 3.16488 13.255 6.75488 13.255C8.36488 13.255 9.84488 12.665 10.9849 11.685L11.2549 11.965V12.755L16.2549 17.745L17.7449 16.255L12.7549 11.255ZM6.75488 [...]
+ -webkit-mask-size: 100%;
+ mask-size: 100%;
+ z-index: 9;
+ pointer-events: none;
+}
+
+.pagefind-modular-input {
+ height: calc(64px * var(--pagefind-ui-scale));
+ padding: 0 calc(70px * var(--pagefind-ui-scale)) 0 calc(54px * var(--pagefind-ui-scale));
+ background-color: var(--pagefind-ui-background);
+ border: var(--pagefind-ui-border-width) solid var(--pagefind-ui-border);
+ border-radius: var(--pagefind-ui-border-radius);
+ font-size: calc(21px * var(--pagefind-ui-scale));
+ position: relative;
+ appearance: none;
+ -webkit-appearance: none;
+ display: flex;
+ width: 100%;
+ box-sizing: border-box;
+ font-weight: 700;
+}
+
+.pagefind-modular-input::placeholder {
+ opacity: 0.2;
+}
+
+.pagefind-modular-input-clear {
+ position: absolute;
+ top: calc(2px * var(--pagefind-ui-scale));
+ right: calc(2px * var(--pagefind-ui-scale));
+ height: calc(60px * var(--pagefind-ui-scale));
+ border-radius: var(--pagefind-ui-border-radius);
+ padding: 0 calc(15px * var(--pagefind-ui-scale)) 0 calc(2px * var(--pagefind-ui-scale));
+ color: var(--pagefind-ui-text);
+ font-size: calc(14px * var(--pagefind-ui-scale));
+ cursor: pointer;
+ background-color: var(--pagefind-ui-background);
+ border: none;
+ appearance: none;
+}
+
+/* ResultList */
+
+.pagefind-modular-list-result {
+ list-style-type: none;
+ display: flex;
+ align-items: flex-start;
+ gap: min(calc(40px * var(--pagefind-ui-scale)), 3%);
+ padding: calc(30px * var(--pagefind-ui-scale)) 0 calc(40px * var(--pagefind-ui-scale));
+ border-top: solid var(--pagefind-ui-border-width) var(--pagefind-ui-border);
+}
+
+.pagefind-modular-list-result:last-of-type {
+ border-bottom: solid var(--pagefind-ui-border-width) var(--pagefind-ui-border);
+}
+
+.pagefind-modular-list-thumb {
+ width: min(30%,
+ calc((30% - (100px * var(--pagefind-ui-scale))) * 100000));
+ max-width: calc(120px * var(--pagefind-ui-scale));
+ margin-top: calc(10px * var(--pagefind-ui-scale));
+ aspect-ratio: var(--pagefind-ui-image-box-ratio);
+ position: relative;
+}
+
+.pagefind-modular-list-image {
+ display: block;
+ position: absolute;
+ left: 50%;
+ transform: translateX(-50%);
+ font-size: 0;
+ width: auto;
+ height: auto;
+ max-width: 100%;
+ max-height: 100%;
+ border-radius: var(--pagefind-ui-image-border-radius);
+}
+
+.pagefind-modular-list-inner {
+ flex: 1;
+ display: flex;
+ flex-direction: column;
+ align-items: flex-start;
+ margin-top: calc(10px * var(--pagefind-ui-scale));
+}
+
+.pagefind-modular-list-title {
+ display: inline-block;
+ font-weight: 700;
+ font-size: calc(21px * var(--pagefind-ui-scale));
+ margin-top: 0;
+ margin-bottom: 0;
+}
+
+.pagefind-modular-list-link {
+ color: var(--pagefind-ui-text);
+ text-decoration: none;
+}
+
+.pagefind-modular-list-link:hover {
+ text-decoration: underline;
+}
+
+.pagefind-modular-list-excerpt {
+ display: inline-block;
+ font-weight: 400;
+ font-size: calc(16px * var(--pagefind-ui-scale));
+ margin-top: calc(4px * var(--pagefind-ui-scale));
+ margin-bottom: 0;
+ min-width: calc(250px * var(--pagefind-ui-scale));
+}
+
+/* FilterPills */
+
+.pagefind-modular-filter-pills-wrapper {
+ overflow-x: scroll;
+ padding: 15px 0;
+}
+
+.pagefind-modular-filter-pills {
+ display: flex;
+ gap: 6px;
+}
+
+.pagefind-modular-filter-pill {
+ display: flex;
+ justify-content: center;
+ align-items: center;
+ border: none;
+ appearance: none;
+ padding: 0 calc(24px * var(--pagefind-ui-scale));
+ background-color: var(--pagefind-ui-background);
+ color: var(--pagefind-ui-fade);
+ border: var(--pagefind-ui-border-width) solid var(--pagefind-ui-border);
+ border-radius: calc(25px * var(--pagefind-ui-scale));
+ font-size: calc(18px * var(--pagefind-ui-scale));
+ height: calc(50px * var(--pagefind-ui-scale));
+ cursor: pointer;
+ white-space: nowrap;
+}
+
+.pagefind-modular-filter-pill:hover {
+ border-color: var(--pagefind-ui-primary);
+}
+
+.pagefind-modular-filter-pill[aria-pressed="true"] {
+ border-color: var(--pagefind-ui-primary);
+ color: var(--pagefind-ui-primary);
+}
\ No newline at end of file
diff --git a/content/_pagefind/pagefind-modular-ui.js b/content/_pagefind/pagefind-modular-ui.js
new file mode 100644
index 0000000..2e1d27d
--- /dev/null
+++ b/content/_pagefind/pagefind-modular-ui.js
@@ -0,0 +1,7 @@
+(()=>{var b=Object.defineProperty;var w=(i,e)=>{for(var t in e)b(i,t,{get:e[t],enumerable:!0})};var f={};w(f,{FilterPills:()=>h,Input:()=>l,Instance:()=>p,ResultList:()=>a,Summary:()=>o});var r=class{constructor(e){this.element=document.createElement(e)}id(e){return this.element.id=e,this}class(e){return this.element.classList.add(e),this}attrs(e){for(let[t,s]of Object.entries(e))this.element.setAttribute(t,s);return this}text(e){return this.element.innerText=e,this}html(e){return this.e [...]
+ <div class="pagefind-modular-list-thumb" data-pfmod-loading></div>
+ <div class="pagefind-modular-list-inner">
+ <p class="pagefind-modular-list-title" data-pfmod-loading>${i(30)}</p>
+ <p class="pagefind-modular-list-excerpt" data-pfmod-loading>${i(40)}</p>
+ </div>
+</li>`},y=i=>{let e=new r("li").class("pagefind-modular-list-result"),t=new r("div").class("pagefind-modular-list-thumb").addTo(e);i?.meta?.image&&new r("img").class("pagefind-modular-list-image").attrs({src:i.meta.image,alt:i.meta.image_alt||i.meta.title}).addTo(t);let s=new r("div").class("pagefind-modular-list-inner").addTo(e),n=new r("p").class("pagefind-modular-list-title").addTo(s);return new r("a").class("pagefind-modular-list-link").text(i.meta?.title).attrs({href:i.meta?.url||i. [...]
diff --git a/content/_pagefind/pagefind-ui.css b/content/_pagefind/pagefind-ui.css
new file mode 100644
index 0000000..303ae74
--- /dev/null
+++ b/content/_pagefind/pagefind-ui.css
@@ -0,0 +1 @@
+.pagefind-ui__result.svelte-j9e30.svelte-j9e30{list-style-type:none;display:flex;align-items:flex-start;gap:min(calc(40px * var(--pagefind-ui-scale)),3%);padding:calc(30px * var(--pagefind-ui-scale)) 0 calc(40px * var(--pagefind-ui-scale));border-top:solid var(--pagefind-ui-border-width) var(--pagefind-ui-border)}.pagefind-ui__result.svelte-j9e30.svelte-j9e30:last-of-type{border-bottom:solid var(--pagefind-ui-border-width) var(--pagefind-ui-border)}.pagefind-ui__result-thumb.svelte-j9e30 [...]
diff --git a/content/_pagefind/pagefind-ui.js b/content/_pagefind/pagefind-ui.js
new file mode 100644
index 0000000..ca987e1
--- /dev/null
+++ b/content/_pagefind/pagefind-ui.js
@@ -0,0 +1 @@
+(()=>{var dn=Object.defineProperty;var S=(t,e)=>{for(var n in e)dn(t,n,{get:e[n],enumerable:!0})};function M(){}function Le(t){return t()}function gt(){return Object.create(null)}function V(t){t.forEach(Le)}function He(t){return typeof t=="function"}function X(t,e){return t!=t?e==e:t!==e||t&&typeof t=="object"||typeof t=="function"}var Ae;function Be(t,e){return Ae||(Ae=document.createElement("a")),Ae.href=e,t===Ae.href}function bt(t){return Object.keys(t).length===0}var Et=!1;function h [...]
diff --git a/content/_pagefind/pagefind.en_33d979aeb8.pf_meta b/content/_pagefind/pagefind.en_33d979aeb8.pf_meta
new file mode 100644
index 0000000..ae3fdfb
Binary files /dev/null and b/content/_pagefind/pagefind.en_33d979aeb8.pf_meta differ
diff --git a/content/_pagefind/pagefind.js b/content/_pagefind/pagefind.js
new file mode 100644
index 0000000..4d2dd16
--- /dev/null
+++ b/content/_pagefind/pagefind.js
@@ -0,0 +1 @@
+const pagefind_version="0.12.0";let wasm_bindgen;(function(){const __exports={};let script_src;if(typeof document==='undefined'){script_src=location.href}else{script_src=new URL("UNHANDLED",location.href).toString()}let wasm;let cachedUint8Memory0=null;function getUint8Memory0(){if(cachedUint8Memory0===null||cachedUint8Memory0.byteLength===0){cachedUint8Memory0=new Uint8Array(wasm.memory.buffer)}return cachedUint8Memory0}let WASM_VECTOR_LEN=0;function passArray8ToWasm0(arg,malloc){const [...]
\ No newline at end of file
diff --git a/content/_pagefind/wasm.en.pagefind b/content/_pagefind/wasm.en.pagefind
new file mode 100644
index 0000000..a20a266
Binary files /dev/null and b/content/_pagefind/wasm.en.pagefind differ
diff --git a/content/_pagefind/wasm.unknown.pagefind b/content/_pagefind/wasm.unknown.pagefind
new file mode 100644
index 0000000..bcd3f4b
Binary files /dev/null and b/content/_pagefind/wasm.unknown.pagefind differ
diff --git a/content/about/index.html b/content/about/index.html
index 866c378..edecf8a 100644
--- a/content/about/index.html
+++ b/content/about/index.html
@@ -9,7 +9,21 @@
<meta property="og:title" content="Community Development: What we do" />
<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/about/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+<meta property="og:url" content="https://community.apache.org/about/" />
+
+
+
+<meta property="og:updated_time" content="2023-03-29T11:49:44+02:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
<title>Apache Community Development - Community Development: What we do</title>
@@ -182,38 +196,50 @@
<hr>
- <h2 id="community-development-what-we-do">Community Development: What We Do <a class="headerlink" title="Permalink" href="#community-development-what-we-do">¶</a></h2>
+
+
+<h2 id="community-development-what-we-do">Community Development: What We Do</h2>
+
<p>The Community Development (ComDev) project
provides a wide array of information, <a href="/newbiefaq.html">FAQs</a>, and help to newcomers and existing committers, and maintains a number of <a href="#getcode">helpful tools</a>.</p>
+
<nav id="TableOfContents">
- <ul>
- <li><a href="#community-development-what-we-do">Community Development: What We Do</a>
- <ul>
- <li><a href="#mentoring-for-individuals-and-help-getting-around">Mentoring for Individuals and Help Getting Around</a></li>
- <li><a href="#mentoring-for-projects">Mentoring for Projects</a></li>
- <li><a href="#education--outreach">Education + Outreach</a></li>
- <li><a href="#diversity">Diversity</a></li>
- <li><a href="#conference-travel-assistance">Conference Travel Assistance</a></li>
- <li><a href="#getcode">Tools and Code we Maintain</a></li>
- <li><a href="#physical-artifacts">Physical artifacts</a></li>
- </ul>
- </li>
- <li><a href="#about-this-website">About This Website</a></li>
- </ul>
+<ul>
+<li>
+<ul>
+<li><a href="#community-development-what-we-do">Community Development: What We Do</a>
+<ul>
+<li><a href="#mentoring-for-individuals-and-help-getting-around">Mentoring for Individuals and Help Getting Around</a></li>
+<li><a href="#mentoring-for-projects">Mentoring for Projects</a></li>
+<li><a href="#education-outreach">Education + Outreach</a></li>
+<li><a href="#diversity">Diversity</a></li>
+<li><a href="#conference-travel-assistance">Conference Travel Assistance</a></li>
+<li><a href="#getcode">Tools and Code we Maintain</a></li>
+<li><a href="#physical-artifacts">Physical artifacts</a></li>
+</ul></li>
+<li><a href="#about-this-website">About This Website</a></li>
+</ul></li>
+</ul>
</nav>
-<h3 id="mentoring-for-individuals-and-help-getting-around">Mentoring for Individuals and Help Getting Around <a class="headerlink" title="Permalink" href="#mentoring-for-individuals-and-help-getting-around">¶</a></h3>
+
+<h3 id="mentoring-for-individuals-and-help-getting-around">Mentoring for Individuals and Help Getting Around</h3>
+
<ul>
<li><a href="/gsoc/">GSoC</a></li>
<li><a href="/newcomers/">Contributors Guide</a></li>
<li><a href="/committers">Committers Guide</a></li>
<li>Project Management Committees</li>
</ul>
-<h3 id="mentoring-for-projects">Mentoring for Projects <a class="headerlink" title="Permalink" href="#mentoring-for-projects">¶</a></h3>
+
+<h3 id="mentoring-for-projects">Mentoring for Projects</h3>
+
<ul>
<li><a href="https://incubator.apache.org/guides/mentor.html">Incubator Mentors</a> - Many folks here are IPMC members or mentors, too</li>
<li>Get community advice on dev@community</li>
</ul>
-<h3 id="education--outreach">Education + Outreach <a class="headerlink" title="Permalink" href="#education--outreach">¶</a></h3>
+
+<h3 id="education-outreach">Education + Outreach</h3>
+
<ul>
<li><a href="https://apachecon.com/">ApacheCon</a></li>
<li>Partnered Industry Events (FOSDEM etc.)</li>
@@ -221,35 +247,50 @@ provides a wide array of information, <a href="/newbiefaq.html">FAQs</a>, and he
<li>Event Representatives (booth coverage, etc.)</li>
<li><a href="/speakers/slides.html">Sample Presentations</a></li>
</ul>
-<h3 id="diversity">Diversity <a class="headerlink" title="Permalink" href="#diversity">¶</a></h3>
+
+<h3 id="diversity">Diversity</h3>
+
<ul>
<li><a href="https://www.apache.org/foundation/policies/conduct.html">Code of Conduct</a></li>
<li>Surveys</li>
</ul>
-<h3 id="conference-travel-assistance">Conference Travel Assistance <a class="headerlink" title="Permalink" href="#conference-travel-assistance">¶</a></h3>
+
+<h3 id="conference-travel-assistance">Conference Travel Assistance</h3>
+
<ul>
<li><a href="https://www.apache.org/travel">TAC - Travel Assistance Committee</a></li>
</ul>
-<h3 id="getcode">Tools and Code we Maintain <a class="headerlink" title="Permalink" href="#getcode">¶</a></h3>
+
+<h3 id="getcode">Tools and Code we Maintain</h3>
+
<p>ComDev manages a number of helpful tools for finding your way around.</p>
+
<ul>
<li>The <a href="https://projects.apache.org/">Apache Projects Directory</a> lists all our software projects. <a href="https://projects.apache.org/about.html">See the Project Directory <strong>code</strong></a> and the JSON data feeds available.</li>
<li><a href="https://home.apache.org/">Apache Committers Phone Book</a> lists all individual Apache committers. <a href="https://home.apache.org/phonebook-about.html">See the Phonebook <strong>code</strong></a>.</li>
<li>The <a href="https://reporter.apache.org/">Project Reporting Tool</a> (requires login) helps Apache PMCs create quarterly board reports. <a href="https://svn.apache.org/repos/asf/comdev/projects.apache.org/">See the Reporter <strong>code</strong></a>.</li>
<li>The <a href="https://cwiki.apache.org/confluence/display/COMDEV/ComDev+Wiki">ComDev Wiki</a> is also available for scratch or experimental work, although most permanent content should be here in the website.</li>
</ul>
+
<p>The ComDev PMC maintains these tools, so bring questions to our <a href="https://lists.apache.org/list.html?dev@community.apache.org">dev@</a> list.</p>
-<h3 id="physical-artifacts">Physical artifacts <a class="headerlink" title="Permalink" href="#physical-artifacts">¶</a></h3>
+
+<h3 id="physical-artifacts">Physical artifacts</h3>
+
<ul>
<li>Stickers: Request project stickers for your event, depending on geography</li>
<li>Assistance with producing <a href="https://www.redbubble.com/people/comdev/shop">swag for your project</a></li>
</ul>
-<h2 id="about-this-website">About This Website <a class="headerlink" title="Permalink" href="#about-this-website">¶</a></h2>
+
+<h2 id="about-this-website">About This Website</h2>
+
<p>The <a href="/">Apache Community Development PMC</a> maintains this <code>community.apache.org</code> website and works through the
-<a href="mailto:dev@community.apache.org">dev@community.apache.org</a> <a href="/lists.html">archived mailing list</a>.</p>
+dev@community.apache.org <a href="/lists.html">archived mailing list</a>.</p>
+
<p>See our <a href="/newbiefaq.html#websitecms">Newcomer FAQ</a> for how to suggest changes to this website.</p>
+
<p>The content is written in Markdown and published automatically via a Jenkins job.
Source code is hosted in a <a href="https://github.com/apache/comdev-site">Git repository</a>.</p>
+
<p>See the <a href="https://github.com/apache/comdev-site/blob/master/README.md">README.md</a> for more info.</p>
diff --git a/content/about/index.xml b/content/about/index.xml
index 9667aaa..a52f35f 100644
--- a/content/about/index.xml
+++ b/content/about/index.xml
@@ -1,10 +1,15 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Community Development: What we do on Apache Comdev</title>
<link>https://community.apache.org/about/</link>
<description>Recent content in Community Development: What we do on Apache Comdev</description>
<generator>Hugo -- gohugo.io</generator>
- <language>en</language><atom:link href="https://community.apache.org/about/index.xml" rel="self" type="application/rss+xml" />
+ <language>en</language>
+ <lastBuildDate>Wed, 29 Mar 2023 11:49:44 +0200</lastBuildDate>
+
+ <atom:link href="https://community.apache.org/about/index.xml" rel="self" type="application/rss+xml" />
+
+
</channel>
-</rss>
+</rss>
\ No newline at end of file
diff --git a/content/apache-way.html b/content/apache-way.html
index a14f376..02c33ff 100644
--- a/content/apache-way.html
+++ b/content/apache-way.html
@@ -9,7 +9,21 @@
<meta property="og:title" content="Apache-ways" />
<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/apache-way.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+<meta property="og:url" content="https://community.apache.org/apache-way.html" />
+
+
+
+
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
<title>Apache Community Development - Apache-ways</title>
diff --git a/content/apache-way/apache-project-maturity-model.html b/content/apache-way/apache-project-maturity-model.html
index 9715f90..149cce9 100644
--- a/content/apache-way/apache-project-maturity-model.html
+++ b/content/apache-way/apache-project-maturity-model.html
@@ -8,11 +8,25 @@
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="A Maturity Model for Apache Projects" />
<meta property="og:description" content="The Apache Project Maturity Model provides a suggested framework for evaluating the overall maturity of an Apache project community and the codebase that it maintains. While this model is specific to projects of the Apache Software Foundation (ASF), many of these factors apply to any open source project.
-Overview ¶ The goals of this maturity model are to describe how Apache projects operate in a concise and high-level way, and to provide a basic framework that projects may choose to use to evaluate themselves." />
+Overview The goals of this maturity model are to describe how Apache projects operate in a concise and high-level way, and to provide a basic framework that projects may choose to use to evaluate themselves." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/apache-way/apache-project-maturity-model.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="apache-way" />
+<meta property="og:url" content="https://community.apache.org/apache-way/apache-project-maturity-model.html" />
+
+
+
+
+<meta property="article:modified_time" content="2021-06-21T10:25:49+02:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2021-06-21T10:25:49+02:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - A Maturity Model for Apache Projects</title>
@@ -188,213 +202,285 @@ Overview ¶ The goals of this maturity model are to describe how Apache proj
<hr>
- <p>The <strong>Apache Project Maturity Model</strong> provides a suggested framework for evaluating the overall maturity of an Apache project community and the codebase that it maintains. While this model is specific to projects of the Apache Software Foundation (ASF), many of these factors apply to any open source project.</p>
-<h1 id="overview">Overview <a class="headerlink" title="Permalink" href="#overview">¶</a></h1>
+
+
+<p>The <strong>Apache Project Maturity Model</strong> provides a suggested framework for evaluating the overall maturity of an Apache project community and the codebase that it maintains. While this model is specific to projects of the Apache Software Foundation (ASF), many of these factors apply to any open source project.</p>
+
+<h1 id="overview">Overview</h1>
+
<p>The goals of this maturity model are to describe how Apache projects operate in a concise and high-level way, and to provide a basic framework that projects may choose to use to evaluate themselves.</p>
+
<p>It is usable outside of the ASF as well, for projects that might want to adopt some or all of these principles. Projects that envision moving to the ASF at some point might start working towards this to prepare for their move.</p>
+
<p>It does not describe all the details of how our projects operate, but aims to capture the invariants of Apache projects and point to additional information where needed. To be as concise as possible we use footnotes for anything that’s not part of the core model.</p>
+
<p>Contrary to other maturity models, we do not define staged partial compliance levels. A mature Apache project complies with all the elements of this model, and other projects are welcome to adopt the elements that suit their goals.</p>
+
<p>Note that we try to avoid using the word “must” below. The model describes the state of a mature project, as opposed to a set of rules.</p>
+
<p>Projects which incubate at the ASF might not fit into all the parts of this model; however a major goal of incubation is to bring the project’s community closer to it.</p>
+
<p>We welcome questions and feedback about this model on the <a href="https://lists.apache.org/list.html?dev@community.apache.org" target="_blank">comdev mailing list</a>.</p>
-<h1 id="the-apache-project-maturity-model">The Apache Project Maturity Model <a class="headerlink" title="Permalink" href="#the-apache-project-maturity-model">¶</a></h1>
+
+<h1 id="the-apache-project-maturity-model">The Apache Project Maturity Model</h1>
+
<p>Each item in the model has a unique ID to allow it to be easily referenced elsewhere.</p>
-<h2 id="code">Code <a class="headerlink" title="Permalink" href="#code">¶</a></h2>
+
+<h2 id="code">Code</h2>
+
<dl>
<dt id="CD10">CD10</dt>
<dd>
The project produces Open Source software for distribution to the public, at no charge.
<sup><a href="#fnref-a2e0cd066fd8f45af4e87bcdbf8d9abd3ad40872" id="fndef-a2e0cd066fd8f45af4e87bcdbf8d9abd3ad40872-0">1</a></sup>
</dd>
+
<dt id="CD20">CD20</dt>
<dd>
Anyone can easily discover and access the project's code.
</dd>
+
<dt id="CD30">CD30</dt>
<dd>
Anyone using standard, widely-available tools, can build the code in a reproducible way.
</dd>
+
<dt id="CD40">CD40</dt>
<dd>
The full history of the project's code is available via a source code
control system, in a way that allows anyone to recreate any released version.
</dd>
+
<dt id="CD50">CD50</dt>
<dd>
The source code control system establishes the provenance of each line of code in a reliable way, based on strong authentication of the
committer. When third parties contribute code, commit messages provide reliable information about the code provenance.
<sup><a href="#fnref-1a581282a720702d3a9e11f81f8c9eeddbee55a9" id="fndef-1a581282a720702d3a9e11f81f8c9eeddbee55a9-1">2</a></sup>
</dd>
+
</dl>
-<h2 id="licenses-and-copyright">Licenses and Copyright <a class="headerlink" title="Permalink" href="#licenses-and-copyright">¶</a></h2>
+
+<h2 id="licenses-and-copyright">Licenses and Copyright</h2>
+
<dl>
<dt id="LC10">LC10</dt>
<dd>The Apache License, version 2.0, covers the released code.
</dd>
+
<dt id="LC20">LC20</dt>
<dd>
Libraries that are mandatory dependencies of the project's code do not create more restrictions than the Apache License does.
<sup><a href="#fnref-76d333d056757395d9b6eb1d62e91a57dad757fa" id="fndef-76d333d056757395d9b6eb1d62e91a57dad757fa-2">3</a></sup>
<sup><a href="#fnref-3e4d977daeeb59a808fb0c40477b2cd50e913f2e" id="fndef-3e4d977daeeb59a808fb0c40477b2cd50e913f2e-3">4</a></sup>
</dd>
+
<dt id="LC30">LC30</dt>
<dd>
The libraries mentioned in LC20 are available as Open Source software.
</dd>
+
<dt id="LC40">LC40</dt>
<dd>Committers are bound by an Individual Contributor Agreement (the <a href="https://www.apache.org/licenses/icla.txt">"Apache iCLA"</a>) that
defines which code they may commit and how they need to
identify code that is not their own.
</dd>
+
<dt id="LC50">LC50</dt>
<dd>
The project clearly defines and documents the copyright ownership of everything that the project produces.
<sup><a href="#fnref-258df7a61c975c67bbef17d3cf7851bafd40b8fb" id="fndef-258df7a61c975c67bbef17d3cf7851bafd40b8fb-4">5</a></sup>
</dd>
+
</dl>
-<h2 id="releases">Releases <a class="headerlink" title="Permalink" href="#releases">¶</a></h2>
+
+<h2 id="releases">Releases</h2>
+
<dl>
+
<dt id="RE10">RE10</dt>
<dd>Releases consist of source code, distributed using standard and open archive
formats that are expected to stay readable in the long term.
<sup><a href="#fnref-d2389850862fcc9bddabb3c2e23b13922d68e3fc" id="fndef-d2389850862fcc9bddabb3c2e23b13922d68e3fc-5">6</a></sup>
</dd>
+
<dt id="RE20">RE20</dt>
<dd>
The project's PMC (Project Management Committee, see CS10) approves each software release in order to make the release an act of the Foundation.
</dd>
+
<dt id="RE30">RE30</dt>
<dd>
Releases are signed and/or distributed along with digests that anyone can reliably use to validate the downloaded archives.
</dd>
+
<dt id="RE40">RE40</dt>
<dd>The project can distribute convenience binaries alongside source code, but they are not Apache Releases, they are provided with no guarantee.
</dd>
+
<dt id="RE50">RE50</dt>
<dd>The project documents a repeatable release process so that
someone new to the project can independently generate the complete
set of artifacts required for a release.
</dd>
+
</dl>
-<h2 id="quality">Quality <a class="headerlink" title="Permalink" href="#quality">¶</a></h2>
+
+<h2 id="quality">Quality</h2>
+
<dl>
+
<dt id="QU10">QU10</dt>
<dd>The
project is open and honest about the quality of its code. Various levels
of quality and maturity for various modules are natural and acceptable
as long as they are clearly communicated.
</dd>
+
<dt id="QU20">QU20</dt>
<dd>
The project puts a very high priority on producing secure software.
<sup><a href="#fnref-89a5257606b929cc5ced2bee207c80b43541d488" id="fndef-89a5257606b929cc5ced2bee207c80b43541d488-6">7</a></sup>
</dd>
+
<dt id="QU30">QU30</dt>
<dd>
The project provides a well-documented, secure and private channel to report security issues, along with a documented way of responding to them.
<sup><a href="#fnref-7c23a24b04dcf9b4b10423685fbd37f69b2b3783" id="fndef-7c23a24b04dcf9b4b10423685fbd37f69b2b3783-7">8</a></sup>
</dd>
+
<dt id="QU40">QU40</dt>
<dd>The project puts a high priority on backwards compatibility and aims to document any incompatible changes and provide tools and documentation to help users transition to new features.
</dd>
+
<dt id="QU50">QU50</dt>
<dd>
The project strives to respond to documented bug reports in a timely manner.
</dd>
</dl>
-<h2 id="community">Community <a class="headerlink" title="Permalink" href="#community">¶</a></h2>
+
+<h2 id="community">Community</h2>
+
<dl>
+
<dt id="CO10">CO10</dt>
<dd>
The project has a well-known homepage that points to all the information required to operate according to this maturity model.
</dd>
+
<dt id="CO20">CO20</dt>
<dd>
The community welcomes contributions from anyone who acts in good faith and
in a respectful manner, and who adds value to the project.
</dd>
+
<dt id="CO30">CO30</dt>
<dd>
Contributions include source code, documentation, constructive bug
reports, constructive discussions, marketing and generally anything that adds value to the project.
</dd>
+
<dt id="CO40">CO40</dt>
<dd>
The community strives to be meritocratic and gives more rights and
responsibilities to contributors who, over time, add value to the project.
</dd>
+
<dt id="CO50">CO50</dt>
<dd>
The project documents how contributors can earn more rights such as commit
access or decision power, and applies these principles consistently.
</dd>
+
<dt id="CO60">CO60</dt>
<dd>
The community operates based on consensus of its members (see CS10) who
have decision power. Dictators, benevolent or not, are not welcome in
Apache projects.
</dd>
+
<dt id="CO70">CO70</dt>
<dd>
The project strives to answer user questions in a timely manner.
</dd>
+
</dl>
-<h2 id="consensus-building">Consensus Building <a class="headerlink" title="Permalink" href="#consensus-building">¶</a></h2>
-<dt id="CS10">CS10</dt>
-<dd>The
-project maintains a public list of its contributors who have decision
-power. The project's PMC (Project Management Committee) consists of
-those contributors.
-</dd>
-<dt id="CS20">CS20</dt>
+
+<h2 id="consensus-building">Consensus Building</h2>
+
+<p><dt id="CS10">CS10</dt>
+<dd>The
+project maintains a public list of its contributors who have decision
+power. The project’s PMC (Project Management Committee) consists of
+those contributors.
+</dd></p>
+
+<p><dt id="CS20">CS20</dt>
<dd>
Decisions require a consensus among PMC members
<sup><a href="#fnref-08fda1a3461c11086b8542178f35e0c27a4a46c3" id="fndef-08fda1a3461c11086b8542178f35e0c27a4a46c3-8">9</a></sup>
- and are documented on the project's main communications channel.
+ and are documented on the project’s main communications channel.
The PMC takes community opinions into account, but the PMC has the final word.
- </dd>
- <dt id="CS30">CS30</dt>
+ </dd></p>
+
+<p><dt id="CS30">CS30</dt>
<dd>
The project uses documented voting rules to build consensus when discussion is not sufficient.
- <sup><a href="#fnref-9b0cf71f04bcd81dddbf6199f1c771e27566611e" id="fndef-9b0cf71f04bcd81dddbf6199f1c771e27566611e-9">10</a></sup>
- </dd>
- <dt id="CS40">CS40</dt>
+ <sup><a href="#fnref-9b0cf71f04bcd81dddbf6199f1c771e27566611e" id="fndef-9b0cf71f04bcd81dddbf6199f1c771e27566611e-9">10</a></sup>
+ </dd></p>
+
+<p><dt id="CS40">CS40</dt>
<dd>In Apache projects, vetoes are only valid for code commits. The person exercising the veto must justify it with a technical explanation, as per the Apache voting rules
-defined in CS30.
-</dd>
-<dt id="CS50">CS50</dt>
+defined in CS30.
+</dd></p>
+
+<p><dt id="CS50">CS50</dt>
<dd>
-All "important" discussions happen asynchronously in written form on the
-project's main communications channel. Offline, face-to-face or private discussions
-<sup><a href="#fnref-d9e7a517f046358463f038f3830fef171e69f78b" id="fndef-d9e7a517f046358463f038f3830fef171e69f78b-10">11</a></sup>
-that affect the project are also documented on that channel.
-</dd>
-</dl>
-<h2 id="independence">Independence <a class="headerlink" title="Permalink" href="#independence">¶</a></h2>
+All “important” discussions happen asynchronously in written form on the
+project’s main communications channel. Offline, face-to-face or private discussions
+<sup><a href="#fnref-d9e7a517f046358463f038f3830fef171e69f78b" id="fndef-d9e7a517f046358463f038f3830fef171e69f78b-10">11</a></sup>
+that affect the project are also documented on that channel.
+</dd></p>
+
+<p></dl></p>
+
+<h2 id="independence">Independence</h2>
+
<dl>
+
<dt id="IN10">IN10</dt>
<dd>
The project is independent from any corporate or organizational influence.
<sup><a href="#fnref-764b2c2fd32deb4ff73ea01efa67c8556303c359" id="fndef-764b2c2fd32deb4ff73ea01efa67c8556303c359-11">12</a></sup>
</dd>
+
<dt id="IN20">IN20</dt>
<dd>Contributors act as themselves, not as representatives of a corporation or organization.
</dd>
+
</dl>
-<h1 id="how-to-use-the-apache-project-maturity-model">How To Use The Apache Project Maturity Model <a class="headerlink" title="Permalink" href="#how-to-use-the-apache-project-maturity-model">¶</a></h1>
+
+<h1 id="how-to-use-the-apache-project-maturity-model">How To Use The Apache Project Maturity Model</h1>
+
<p><strong>Remember:</strong> This model is a guide; it is not a requirements document. The model shows what generally good behaviors in an Apache project look like.</p>
+
<p>So far, inside the ASF, podlings preparing their graduation
from the <a href="https://incubator.apache.org">Apache Incubator</a> have used this model, mostly for self-assessment.</p>
+
<p>It might be useful for top-level ASF projects to regularly assess their maturity based on this model, but this is not a requirement at this time.</p>
+
<p>Here are a few self-assessment examples:</p>
+
<ul>
<li><a href="https://github.com/apache/groovy/blob/576b3c5d6a7022ac4a8df1ef118666456ce627fb/MATURITY.adoc">Apache Groovy podling self-assessment, 2015</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/TAVERNADEV/2016-03+Taverna+Graduation+Maturity+Assessment">Apache Taverna Graduation Maturity Assessment, 2016</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/CARBONDATA/Apache+Maturity+Model+Assessment+for+CarbonData">Apache CarbonData Podling Maturity Assessment, 2017</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/SERVICECOMB/Apache+Maturity+Model+Assessment+for+ServiceComb">Apache ServiceComb Maturity Model Assessment, 2018</a></li>
</ul>
-<h2 id="other-open-source-project-models">Other Open Source Project Models <a class="headerlink" title="Permalink" href="#other-open-source-project-models">¶</a></h2>
+
+<h2 id="other-open-source-project-models">Other Open Source Project Models</h2>
+
<p>See <a href="https://s.apache.org/apache_maturity_model">https://s.apache.org/apache_maturity_model</a> for the discussions that led to this document. Thanks to the many people who provided input! The links below are both inspirations for our model, and are some of the other ways that FOSS project participants have tried to quantify ways to measure open source projects.</p>
+
<ul>
<li><a href="http://oss-watch.ac.uk/resources/ssmm">http://oss-watch.ac.uk/resources/ssmm</a></li>
<li><a href="https://osswatch.jiscinvolve.org/wp/2014/12/11/open-or-fauxpen-use-the-oss-watch-openness-rating-tool-to-find-out/">https://osswatch.jiscinvolve.org/wp/2014/12/11/open-or-fauxpen-use-the-oss-watch-openness-rating-tool-to-find-out/</a></li>
@@ -404,83 +490,116 @@ from the <a href="https://incubator.apache.org">Apache Incubator</a> have used t
<li><a href="https://en.wikipedia.org/wiki/Capability_Maturity_Model_Integration">https://en.wikipedia.org/wiki/Capability_Maturity_Model_Integration</a></li>
<li><a href="https://www.apache.org/dev/project-requirements">https://www.apache.org/dev/project-requirements</a></li>
</ul>
-<h2 id="status--document-version">Status / Document Version <a class="headerlink" title="Permalink" href="#status--document-version">¶</a></h2>
+
+<h2 id="status-document-version">Status / Document Version</h2>
+
<p>v 1.0, February 2015, defined by consensus by Apache Community Development project.</p>
+
<p>v 1.1, October 2016 added RE50.</p>
+
<p>v 1.2, February 2018, reworked the “how to use” section with more links to self-assessments.</p>
+
<p>v 1.3, June 2021, improve readability and simplify the language where possible.</p>
+
<p>See the <a href="https://svn.apache.org/viewvc/comdev/site/trunk/content/apache-way/apache-project-maturity-model.mdtext?view=log" target="_blank">svn revision history</a> (for older
versions) and <a href="https://github.com/apache/comdev-site/commits/master/source/apache-way/apache-project-maturity-model.md">GitHub history</a> (since March 2020) of this document for more details and other minor changes.</p>
-<h3 id="footnotes">Footnotes <a class="headerlink" title="Permalink" href="#footnotes">¶</a></h3>
+
+<h3 id="footnotes">Footnotes</h3>
+
<ol>
+
<li>
<a id="fnref-a2e0cd066fd8f45af4e87bcdbf8d9abd3ad40872"></a>
"For distribution to the public at no charge" is straight from the from the ASF Bylaws at <a class="http" href="https://apache.org/foundation/bylaws.html" target="_blank">https://apache.org/foundation/bylaws.html</a>.
-<p>(<a href="#fndef-a2e0cd066fd8f45af4e87bcdbf8d9abd3ad40872-0">1</a>)</p>
+
+(<a href="#fndef-a2e0cd066fd8f45af4e87bcdbf8d9abd3ad40872-0">1</a>)
</li>
+
<li>
<a id="fndef-1a581282a720702d3a9e11f81f8c9eeddbee55a9-1"></a>
See also LC40.
-<p>(<a href="#fndef-1a581282a720702d3a9e11f81f8c9eeddbee55a9-1">2</a>)</p>
+
+(<a href="#fndef-1a581282a720702d3a9e11f81f8c9eeddbee55a9-1">2</a>)
</li>
+
<li>
<a id="fnref-76d333d056757395d9b6eb1d62e91a57dad757fa"></a>
It's ok for platforms (like a runtime used to execute our code) to have different licenses as long as they don't impose reciprocal licensing on
what we are distributing.
-<p>(<a href="#fndef-76d333d056757395d9b6eb1d62e91a57dad757fa-2">3</a>)</p>
+
+(<a href="#fndef-76d333d056757395d9b6eb1d62e91a57dad757fa-2">3</a>)
</li>
+
<li>
<a id="fnref-3e4d977daeeb59a808fb0c40477b2cd50e913f2e"></a>
<a class="http" href="https://apache.org/legal/resolved.html">https://apache.org/legal/resolved.html</a> has information about acceptable licenses for third-party dependencies.
-<p>(<a href="#fndef-3e4d977daeeb59a808fb0c40477b2cd50e913f2e-3">4</a>)</p>
+
+(<a href="#fndef-3e4d977daeeb59a808fb0c40477b2cd50e913f2e-3">4</a>)
</li>
+
<li>
<a id="fnref-258df7a61c975c67bbef17d3cf7851bafd40b8fb"></a>
In Apache projects, the ASF owns the copyright for the collective work,
i.e. the project's releases. Contributors retain copyright on their
contributions but grant the ASF a perpetual copyright license for them.
-<p>(<a href="#fndef-258df7a61c975c67bbef17d3cf7851bafd40b8fb-4">5</a>)</p>
+
+(<a href="#fndef-258df7a61c975c67bbef17d3cf7851bafd40b8fb-4">5</a>)
</li>
+
<li>
<a id="fnref-d2389850862fcc9bddabb3c2e23b13922d68e3fc"></a>
See <a class="http" href="https://www.apache.org/legal/release-policy.html">https://www.apache.org/legal/release-policy.html</a> for more info on Apache releases.
-<p>(<a href="#fndef-d2389850862fcc9bddabb3c2e23b13922d68e3fc-5">6</a>)</p>
+
+ (<a href="#fndef-d2389850862fcc9bddabb3c2e23b13922d68e3fc-5">6</a>)
</li>
+
<li>
<a id="fnref-89a5257606b929cc5ced2bee207c80b43541d488"></a>
The required level of security depends on the software's intended uses, of course. Projects should clearly document security expectations.
-<p>(<a href="#fndef-89a5257606b929cc5ced2bee207c80b43541d488-6">7</a>)</p>
+
+ (<a href="#fndef-89a5257606b929cc5ced2bee207c80b43541d488-6">7</a>)
</li>
+
<li>
<a id="fnref-7c23a24b04dcf9b4b10423685fbd37f69b2b3783"></a>
Apache projects can just point to <a class="http" href="https://www.apache.org/security/">https://www.apache.org/security/</a> or use their own security contacts page, which should also point to that.
-<p>(<a href="#fndef-7c23a24b04dcf9b4b10423685fbd37f69b2b3783-7">8</a>)</p>
+
+ (<a href="#fndef-7c23a24b04dcf9b4b10423685fbd37f69b2b3783-7">8</a>)
</li>
+
<li>
<a id="fnref-08fda1a3461c11086b8542178f35e0c27a4a46c3"></a>
In Apache projects, "consensus" means <em>widespread agreement among people who have decision power</em>. It does not necessarily mean "unanimity".
-<p>(<a href="#fndef-08fda1a3461c11086b8542178f35e0c27a4a46c3-8">9</a>)</p>
+
+ (<a href="#fndef-08fda1a3461c11086b8542178f35e0c27a4a46c3-8">9</a>)
</li>
+
<li>
<a id="fnref-9b0cf71f04bcd81dddbf6199f1c771e27566611e"></a>
For Apache projects, <a class="http" href="https://www.apache.org/foundation/voting.html" target="_blank">https://www.apache.org/foundation/voting.html</a> defines the voting rules.
-<p>(<a href="#fndef-9b0cf71f04bcd81dddbf6199f1c771e27566611e-9">10</a>)</p>
+
+ (<a href="#fndef-9b0cf71f04bcd81dddbf6199f1c771e27566611e-9">10</a>)
</li>
+
<li>
<a id="fnref-d9e7a517f046358463f038f3830fef171e69f78b"></a>
Each Apache project has a private mailing list that its PMC is expected to use
only when really needed. The private list is typically used for
discussions about people, for example to discuss and to vote on PMC
and committer candidates.
-<p>(<a href="#fndef-d9e7a517f046358463f038f3830fef171e69f78b-10">11</a>)</p>
+
+(<a href="#fndef-d9e7a517f046358463f038f3830fef171e69f78b-10">11</a>)
</li>
+
<li>
<a id="fnref-764b2c2fd32deb4ff73ea01efa67c8556303c359"></a>
Independence can be understood as basing the project's decisions on the open
discussions that happen on the project's main communications channel,
with no hidden agendas.
-<p>(<a href="#fndef-764b2c2fd32deb4ff73ea01efa67c8556303c359-11">12</a>)</p>
+
+(<a href="#fndef-764b2c2fd32deb4ff73ea01efa67c8556303c359-11">12</a>)
</li>
+
</ol>
diff --git a/content/apache-way/index.xml b/content/apache-way/index.xml
index 4a3c711..8f179e2 100644
--- a/content/apache-way/index.xml
+++ b/content/apache-way/index.xml
@@ -1,11 +1,15 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Apache-ways on Apache Comdev</title>
<link>https://community.apache.org/apache-way.html</link>
<description>Recent content in Apache-ways on Apache Comdev</description>
<generator>Hugo -- gohugo.io</generator>
- <language>en</language><atom:link href="https://community.apache.org/apache-way/index.xml" rel="self" type="application/rss+xml" />
+ <language>en</language>
+
+ <atom:link href="https://community.apache.org/apache-way/index.xml" rel="self" type="application/rss+xml" />
+
+
<item>
<title>A Maturity Model for Apache Projects</title>
<link>https://community.apache.org/apache-way/apache-project-maturity-model.html</link>
@@ -13,8 +17,8 @@
<guid>https://community.apache.org/apache-way/apache-project-maturity-model.html</guid>
<description>The Apache Project Maturity Model provides a suggested framework for evaluating the overall maturity of an Apache project community and the codebase that it maintains. While this model is specific to projects of the Apache Software Foundation (ASF), many of these factors apply to any open source project.
-Overview &para; The goals of this maturity model are to describe how Apache projects operate in a concise and high-level way, and to provide a basic framework that projects may choose to use to evaluate themselves.</description>
+Overview The goals of this maturity model are to describe how Apache projects operate in a concise and high-level way, and to provide a basic framework that projects may choose to use to evaluate themselves.</description>
</item>
</channel>
-</rss>
+</rss>
\ No newline at end of file
diff --git a/content/boardreport.html b/content/boardreport.html
index d9d8851..ae33d4c 100644
--- a/content/boardreport.html
+++ b/content/boardreport.html
@@ -10,9 +10,23 @@
<meta property="og:description" content="For complete details about what should be in ASF project board reports, including instructions on using the handy Reporter tool, please see:
https://apache.org/foundation/board/reporting" />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/boardreport.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="" />
+<meta property="og:url" content="https://community.apache.org/boardreport.html" />
+
+
+
+
+<meta property="article:modified_time" content="2023-03-21T14:07:43-04:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2023-03-21T14:07:43-04:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - BoardReport</title>
@@ -183,6 +197,7 @@ https://apache.org/foundation/board/reporting" />
<hr>
<p>For complete details about what should be in ASF project board reports, including instructions on using the handy Reporter tool, please see:</p>
+
<p><a href="https://apache.org/foundation/board/reporting">https://apache.org/foundation/board/reporting</a></p>
diff --git a/content/calendars/conferences.html b/content/calendars/conferences.html
index 49bf55f..ba8ff28 100644
--- a/content/calendars/conferences.html
+++ b/content/calendars/conferences.html
@@ -7,13 +7,27 @@
<meta name="keywords" content="apache, apache community, community development, opensource"/>
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="Apache Conferences Calendar" />
-<meta property="og:description" content="Deprecated - See New Calendar instead ¶ This calendar is no longer maintained; please see this page instead.
+<meta property="og:description" content="Deprecated - See New Calendar instead This calendar is no longer maintained; please see this page instead.
This Calendar is maintained by the Apache Community Development Committee (ComDev), to have your event listed considered for addition please mail dev@community.apache.org. Note that to be listed in this calendar events must conform to the Third Party Event Branding Policy.
-Upcoming events ¶ List loading This Calendar is also available as an iCal feed" />
+Upcoming events List loading This Calendar is also available as an iCal feed" />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/calendars/conferences.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="calendars" />
+<meta property="og:url" content="https://community.apache.org/calendars/conferences.html" />
+
+
+
+
+<meta property="article:modified_time" content="2020-07-20T20:22:04+02:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2020-07-20T20:22:04+02:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Apache Conferences Calendar</title>
@@ -189,18 +203,27 @@ Upcoming events ¶ List loading This Calendar is also available as an iCal f
<hr>
- <h2 id="deprecated---see-new-calendar-instead">Deprecated - See New Calendar instead <a class="headerlink" title="Permalink" href="#deprecated---see-new-calendar-instead">¶</a></h2>
+
+
+<h2 id="deprecated-see-new-calendar-instead">Deprecated - See New Calendar instead</h2>
+
<p>This calendar is no longer maintained; please see <a href="/calendars/">this page</a> instead.</p>
+
<p>This Calendar is maintained by the Apache Community Development Committee (ComDev),
to have your event listed considered for addition please mail <a href="mailto:dev@community.apache.org">dev@community.apache.org</a>.
Note that to be listed in this calendar events must conform to the <a href="https://www.apache.org/foundation/marks/events.html">Third Party Event Branding Policy</a>.</p>
-<h2 id="upcoming-events">Upcoming events <a class="headerlink" title="Permalink" href="#upcoming-events">¶</a></h2>
+
+<h2 id="upcoming-events">Upcoming events</h2>
+
<ul>
<li><em>List loading</em></li>
</ul>
+
<iframe src="https://www.google.com/calendar/embed?src=nerseigospses068jd57bk5ar8%40group.calendar.google.com&ctz=America/New_York"
style="border: 0" width="800" height="600" frameborder="0" scrolling="no"></iframe>
+
<p>This Calendar is also available as an <a href="https://www.google.com/calendar/ical/nerseigospses068jd57bk5ar8%40group.calendar.google.com/public/basic.ics">iCal feed</a></p>
+
<script type="text/javascript">
function handleContents(li, text) {
if(text == undefined || text.length == 0) {
diff --git a/content/calendars/index.html b/content/calendars/index.html
index 890e60e..df88733 100644
--- a/content/calendars/index.html
+++ b/content/calendars/index.html
@@ -9,7 +9,21 @@
<meta property="og:title" content="Apache Related Event Calendars" />
<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/calendars/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+<meta property="og:url" content="https://community.apache.org/calendars/" />
+
+
+
+<meta property="og:updated_time" content="2023-03-29T11:49:44+02:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
<title>Apache Community Development - Apache Related Event Calendars</title>
@@ -182,29 +196,40 @@
<hr>
- <p>This calendar lists major events relating to The Apache Software Foundation
+
+
+<p>This calendar lists major events relating to The Apache Software Foundation
and our many Apache projects. We also have an automated
<a href="https://www.apache.org/events/meetups.html">listing of upcoming Apache-related Meetups</a> (smaller events) available.</p>
+
<p>This Calendar is maintained by Apache Community Development volunteers (ComDev);
to have your event listed considered for addition please mail <a href="mailto:dev@community.apache.org">dev@community.apache.org</a>.
Note that to be listed in this calendar events must <b>already</b> conform
to the <a href="https://www.apache.org/foundation/marks/events.html">Third Party Event Branding Policy</a> and have been approved by
either the relevant Apache PMC or the Branding Committee.</p>
-<h2 id="upcoming-events">Upcoming Events <a class="headerlink" title="Permalink" href="#upcoming-events">¶</a></h2>
+
+<h2 id="upcoming-events">Upcoming Events</h2>
+
<ul id="events">
<li><i>List loading</i></li>
</ul>
+
<p><em>Disclaimer: Events called ‘ApacheCon’ or ‘Apache Roadshow’ are
official Apache Software Foundation events. Other listed events are put
on by projects, or third-party producers, and are listed here to support
our community, but are not official Foundation events.</em></p>
+
<iframe src="https://www.google.com/calendar/embed?src=nerseigospses068jd57bk5ar8%40group.calendar.google.com&ctz=America/New_York"
style="border: 0" width="800" height="600" frameborder="0" scrolling="no"></iframe>
+
<p>This Calendar is also available as an <a href="https://www.google.com/calendar/ical/nerseigospses068jd57bk5ar8%40group.calendar.google.com/public/basic.ics">iCal feed</a></p>
+
<script src="/js/jquery-1.9.1.min.js"></script>
<script src="https://events.apache.org/js/events-calendar.js"></script>
<script src="https://apis.google.com/js/client.js"></script>
-<h2 id="other-related-events">Other Related Events <a class="headerlink" title="Permalink" href="#other-related-events">¶</a></h2>
+
+<h2 id="other-related-events">Other Related Events</h2>
+
<p>In addition to major conferences that have applied for approval with us, there are a wide range of other
events which feature Apache projects and technologies. A list of upcoming
<a href="https://www.apache.org/events/meetups.html">Apache related Meetups is available</a>, powered in part by <a href="https://svn.apache.org/repos/asf/comdev/tools/get_meetups">this script</a>
diff --git a/content/calendars/index.xml b/content/calendars/index.xml
index bf92e62..66b59f4 100644
--- a/content/calendars/index.xml
+++ b/content/calendars/index.xml
@@ -1,21 +1,26 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Apache Related Event Calendars on Apache Comdev</title>
<link>https://community.apache.org/calendars/</link>
<description>Recent content in Apache Related Event Calendars on Apache Comdev</description>
<generator>Hugo -- gohugo.io</generator>
- <language>en</language><atom:link href="https://community.apache.org/calendars/index.xml" rel="self" type="application/rss+xml" />
+ <language>en</language>
+ <lastBuildDate>Wed, 29 Mar 2023 11:49:44 +0200</lastBuildDate>
+
+ <atom:link href="https://community.apache.org/calendars/index.xml" rel="self" type="application/rss+xml" />
+
+
<item>
<title>Apache Conferences Calendar</title>
<link>https://community.apache.org/calendars/conferences.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/calendars/conferences.html</guid>
- <description>Deprecated - See New Calendar instead &para; This calendar is no longer maintained; please see this page instead.
+ <description>Deprecated - See New Calendar instead This calendar is no longer maintained; please see this page instead.
This Calendar is maintained by the Apache Community Development Committee (ComDev), to have your event listed considered for addition please mail dev@community.apache.org. Note that to be listed in this calendar events must conform to the Third Party Event Branding Policy.
-Upcoming events &para; List loading This Calendar is also available as an iCal feed</description>
+Upcoming events List loading This Calendar is also available as an iCal feed</description>
</item>
</channel>
-</rss>
+</rss>
\ No newline at end of file
diff --git a/content/comdevboardreports.html b/content/comdevboardreports.html
index 88eb765..321e670 100644
--- a/content/comdevboardreports.html
+++ b/content/comdevboardreports.html
@@ -10,9 +10,23 @@
<meta property="og:description" content="Like every other ASF project, the ComDev PMC sends a quarterly report to the board. These reports are read by the board, and sometimes directors will ask the PMC for clarification or to make suggestions for the project.
You can read the complete list of Apache Community Development board reports. A chronological view of all minutes from ASF Board meetings is also public." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/comdevboardreports.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="" />
+<meta property="og:url" content="https://community.apache.org/comdevboardreports.html" />
+
+
+
+
+<meta property="article:modified_time" content="2023-03-21T13:34:10-04:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2023-03-21T13:34:10-04:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - ComDevBoardReports</title>
@@ -183,6 +197,7 @@ You can read the complete list of Apache Community Development board reports. A
<hr>
<p>Like every other ASF project, the ComDev PMC sends a <a href="https://www.apache.org/foundation/board/reporting">quarterly report to the board</a>. These reports are read by the board, and sometimes directors will ask the PMC for clarification or to make suggestions for the project.</p>
+
<p>You can read the complete list of <a href="https://whimsy.apache.org/board/minutes/Community_Development.html">Apache Community Development board reports</a>. A <a href="https://www.apache.org/foundation/board/calendar.html#board-meeting-minutes">chronological view of all minutes from ASF Board meetings</a> is also public.</p>
diff --git a/content/committers/consensusBuilding.html b/content/committers/consensusBuilding.html
index 0e8dc3d..d5a8cc1 100644
--- a/content/committers/consensusBuilding.html
+++ b/content/committers/consensusBuilding.html
@@ -8,11 +8,25 @@
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="Consensus Building" />
<meta property="og:description" content="In some cases there is no obvious path to take, or you might be a new community, or a new member of an existing community. In these cases people often need to build consensus by making proposals and eliciting responses.
-Constructive discussion is the lifeblood of a successful project. However, we want to avoid unnecessary discussion and significant amounts of unnecessary mail that everyone in the community needs to read. so many ASF projects adopt a shorthand notation for showing support, or otherwise, for a proposal." />
+Constructive discussion is the lifeblood of a successful project. However, we want to avoid unnecessary discussion and significant amounts of unnecessary mail that everyone in the community needs to read." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/committers/consensusBuilding.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="committers" />
+<meta property="og:url" content="https://community.apache.org/committers/consensusBuilding.html" />
+
+
+
+
+<meta property="article:modified_time" content="2020-12-02T09:52:19-04:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2020-12-02T09:52:19-04:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Consensus Building</title>
@@ -188,19 +202,27 @@ Constructive discussion is the lifeblood of a successful project. However, we wa
<hr>
- <p>In some cases there is no obvious path to take, or you might be a new community,
+
+
+<p>In some cases there is no obvious path to take, or you might be a new community,
or a new member of an existing community. In these cases people often
need to build consensus by making proposals and eliciting responses.</p>
+
<p>Constructive discussion is the lifeblood of a successful project. However, we want to avoid unnecessary discussion and significant
amounts of unnecessary mail that everyone in the community needs to read. so many ASF projects adopt a
shorthand notation for showing support, or otherwise, for a proposal.</p>
-<h2 id="expressing-support-or-otherwise">Expressing support (or otherwise) <a class="headerlink" title="Permalink" href="#expressing-support-or-otherwise">¶</a></h2>
+
+<h2 id="expressing-support-or-otherwise">Expressing support (or otherwise)</h2>
+
<p>It is important to understand that everyone is invited to express
their opinion of any given action or proposal. Apache projects are community
projects in which no single individual has more power than any other single
individual (except in a very few procedural situations).</p>
+
<p>The notation used is “+1”, “-1” and “0”. It’s also common to see “+0” and “-0”.</p>
+
<p>So, what do these notations mean?</p>
+
<ul>
<li>+1 means “I agree with this and will help make it happen”</li>
<li>+0 means “I agree with this but probably won’t make it happen, so my
@@ -210,20 +232,26 @@ my opinion is not that important”</li>
<li>-1 means “I don’t agree and I am offering an alternative that I am able
to help implement”</li>
</ul>
+
<p>Many people use fractions to indicate the strength of their feelings,
-e.g. “+0.5”. Some will even indicate their opinion that the proposal is a “no brainer” with something
+ e.g. “+0.5”. Some will even indicate their opinion that the proposal is a “no brainer” with something
like “+1000”.</p>
+
<p>This notation is not an exact science. It’s just a shorthand
way of communicating strength of feeling.</p>
-<h2 id="consensus-building-is-not-voting">Consensus building is not voting <a class="headerlink" title="Permalink" href="#consensus-building-is-not-voting">¶</a></h2>
+
+<h2 id="consensus-building-is-not-voting">Consensus building is not voting</h2>
+
<p>A confusing thing about this notation is that it is the same notation
used in a formal vote. Knowing when something is a vote and when it is a
preference is important. It’s easy to tell, though: if the subject line of the email thread does not have
“[Vote]” at the start then it’s just an opinion. We try not to call votes;
consensus building is much more inclusive.</p>
+
<p>The reasons for this notation being common is that when someone wants to
summarise a discussion thread they can mentally
add up the strength of feeling of the community and decide whether there is consensus.</p>
+
<p>If there is clear consensus in favor of a proposal, members of the community can proceed with
the work under the <a href="/committers/lazyConsensus.html">lazy consensus</a> model.</p>
diff --git a/content/committers/decisionMaking.html b/content/committers/decisionMaking.html
index 64ec9cd..59f101a 100644
--- a/content/committers/decisionMaking.html
+++ b/content/committers/decisionMaking.html
@@ -10,9 +10,23 @@
<meta property="og:description" content="The most important thing about engaging with any Apache project is that everyone is equal. All project participants with an opinion can express that opinion and, where appropriate, have the community consider it.
To some, the idea of having to establish consensus in a large and distributed team sounds inefficient and frustrating. Don’t despair, though: The Apache Way has a set of simple processes to ensure things proceed at a good pace." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/committers/decisionMaking.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="committers" />
+<meta property="og:url" content="https://community.apache.org/committers/decisionMaking.html" />
+
+
+
+
+<meta property="article:modified_time" content="2021-01-15T09:22:16-04:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2021-01-15T09:22:16-04:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Decision-Making</title>
@@ -188,27 +202,38 @@ To some, the idea of having to establish consensus in a large and distributed te
<hr>
- <p>The most important thing about engaging with any Apache project is that everyone
+
+
+<p>The most important thing about engaging with any Apache project is that everyone
is equal. All project participants with an opinion can express that opinion and, where
appropriate, have the community consider it.</p>
+
<p>To some, the idea of having to establish consensus in a large and distributed team
sounds inefficient and frustrating. Don’t despair, though: The Apache Way has a
set of simple processes to ensure things proceed at a good pace.</p>
+
<p>In ASF projects we don’t like to vote. We reserve that for the few things that need
official approval for legal or process reasons (e.g. approving a release or adding a new committer).
Most of the time we work with the consensus-building techniques documented below.</p>
-<h2 id="lazy-consensus">Lazy Consensus <a class="headerlink" title="Permalink" href="#lazy-consensus">¶</a></h2>
+
+<h2 id="lazy-consensus">Lazy Consensus</h2>
+
<p><a href="/committers/lazyConsensus.html">Lazy consensus</a> is the first, and possibly the most important, consensus-building
tool we have. Essentially lazy consensus means that you don’t need to get explicit
approval to proceed, but you need to be prepared to listen if someone objects.</p>
-<h2 id="consensus-building">Consensus Building <a class="headerlink" title="Permalink" href="#consensus-building">¶</a></h2>
+
+<h2 id="consensus-building">Consensus Building</h2>
+
<p>Sometimes lazy consensus is not appropriate. In such cases it is necessary to
make a proposal to the email list and discuss options. There are mechanisms
for quickly showing your support or otherwise for a proposal and
<a href="/committers/consensusBuilding.html">building consensus</a> within the community.</p>
+
<p>Once there is consensus to approve a proposal, people can proceed with the work under the <a href="/committers/lazyConsensus.html">lazy
consensus</a> model.</p>
-<h2 id="voting">Voting <a class="headerlink" title="Permalink" href="#voting">¶</a></h2>
+
+<h2 id="voting">Voting</h2>
+
<p>Occasionally a “feel” for consensus is not enough. Sometimes we need to
have a measurable consensus, for example, when <a href="/committers/voting.html">voting</a> to add committers or
to approve a release.</p>
diff --git a/content/committers/funding-disclaimer.html b/content/committers/funding-disclaimer.html
index 24767d4..cb6c9e4 100644
--- a/content/committers/funding-disclaimer.html
+++ b/content/committers/funding-disclaimer.html
@@ -12,9 +12,23 @@ This is ok in principle, but you have to make it clear that the campaign is your
This page gives a few examples of how to do that.
If you have any question about this, feel free to ask on our dev@community." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/committers/funding-disclaimer.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="committers" />
+<meta property="og:url" content="https://community.apache.org/committers/funding-disclaimer.html" />
+
+
+
+
+<meta property="article:modified_time" content="2021-07-06T11:05:05-04:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2021-07-06T11:05:05-04:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Funding campaign disclaimer</title>
@@ -190,26 +204,36 @@ If you have any question about this, feel free to ask on our dev@community." />
<hr>
- <p>Some Apache committers have successfully run funding campaigns to support their work on their favorite Apache projects.</p>
+
+
+<p>Some Apache committers have successfully run funding campaigns to support their work on their favorite Apache projects.</p>
+
<p>This is ok in principle, but you have to make it clear that the campaign is your own thing, and avoid any confusion about the role of the
ASF and how its projects work.</p>
+
<p>This page gives a few examples of how to do that.</p>
+
<p>If you have any question about this, feel free to ask on our
<a href="https://lists.apache.org/list.html?dev@community.apache.org">dev@community.apache.org</a> mailing list.</p>
-<h2 id="example-disclaimer-for-a-personal-crowdfunding-campaign">Example disclaimer for a personal crowdfunding campaign <a class="headerlink" title="Permalink" href="#example-disclaimer-for-a-personal-crowdfunding-campaign">¶</a></h2>
+
+<h2 id="example-disclaimer-for-a-personal-crowdfunding-campaign">Example disclaimer for a personal crowdfunding campaign</h2>
+
<p>Here’s a nice example, based on a disclaimer one committer has used:</p>
-<div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-text" data-lang="text"><span style="display:flex;"><span> Disclaimers: This campaign is done by me, FOO, as an independent individual, not
-</span></span><span style="display:flex;"><span> by the Apache Software Foundation nor the Apache BAR project. I'm not representing
-</span></span><span style="display:flex;"><span> the Foundation in any way in this campaign, nor does Apache endorse it. The
-</span></span><span style="display:flex;"><span> Foundation has a policy of not paying for development work. All its members are
-</span></span><span style="display:flex;"><span> voluntary, me included. Any code I'll write or change will have to pass the usual BAR
-</span></span><span style="display:flex;"><span> team approval process. If this campaign isn't funded, I'll continue participating
-</span></span><span style="display:flex;"><span> in the BAR project in the same way as before.
-</span></span></code></pre></div><p>See also the <a href="https://mail-archives.apache.org/mod_mbox/community-dev/201310.mbox/%3Cop.w4fwv6ewovlrp5%40arsmachina%3E">discussion thread</a> about this
+<div class="highlight"><pre style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-text" data-lang="text"> Disclaimers: This campaign is done by me, FOO, as an independent individual, not
+ by the Apache Software Foundation nor the Apache BAR project. I'm not representing
+ the Foundation in any way in this campaign, nor does Apache endorse it. The
+ Foundation has a policy of not paying for development work. All its members are
+ voluntary, me included. Any code I'll write or change will have to pass the usual BAR
+ team approval process. If this campaign isn't funded, I'll continue participating
+ in the BAR project in the same way as before.</code></pre></div>
+<p>See also the <a href="https://mail-archives.apache.org/mod_mbox/community-dev/201310.mbox/%3Cop.w4fwv6ewovlrp5%40arsmachina%3E">discussion thread</a> about this
campaign.</p>
-<h2 id="friends-of-apache-groovy">Friends of Apache Groovy <a class="headerlink" title="Permalink" href="#friends-of-apache-groovy">¶</a></h2>
+
+<h2 id="friends-of-apache-groovy">Friends of Apache Groovy</h2>
+
<p><a href="https://opencollective.com/friends-of-groovy">Friends of Apache Groovy</a> has another good example which supports activities
in the Apache Groovy community.</p>
+
<p>The <a href="https://opencollective.com/friends-of-groovy#section-about">explanation in their ‘about’ section</a> makes it clear that the
initiative is <em>not</em> affiliated with or driven by the ASF, and also that any contributions, funded or not, have to go
through the usual Apache Groovy acceptance process.</p>
diff --git a/content/committers/index.html b/content/committers/index.html
index 4bb5336..76a0de8 100644
--- a/content/committers/index.html
+++ b/content/committers/index.html
@@ -9,7 +9,21 @@
<meta property="og:title" content="Committer resources" />
<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/committers/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+<meta property="og:url" content="https://community.apache.org/committers/" />
+
+
+
+<meta property="og:updated_time" content="2023-03-29T11:49:44+02:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
<title>Apache Community Development - Committer resources</title>
@@ -182,82 +196,107 @@
<hr>
- <p>There are a number of useful Apache tools and services available for Apache projects
-and committers. This is a brief set of pointers or signposts to that information.</p>
-<h2 id="apache-infrastructure-information">Apache Infrastructure Information <a class="headerlink" title="Permalink" href="#apache-infrastructure-information">¶</a></h2>
+
+
+<p>There are a number of useful Apache tools and services available for Apache projects
+ and committers. This is a brief set of pointers or signposts to that information.</p>
+
+<h2 id="apache-infrastructure-information">Apache Infrastructure Information</h2>
+
<p>The primary portals for Apache Infra questions - how Subversion/Git/Websites, etc. work at the ASF - are pages at <a href="https://www.apache.org/dev/" target="_blank">apache.org/dev</a> and <a href="https://www.infra.apache.org" target="_blank">infra.apache.org</a>.</p>
+
<p>If you’re a committer, you can <a href="/newbiefaq.html#websitecms">patch this very website yourself</a>!</p>
-<h2 id="decision-making">Decision making <a class="headerlink" title="Permalink" href="#decision-making">¶</a></h2>
+
+<h2 id="decision-making">Decision making</h2>
+
<p>Decisions in Apache projects result from:</p>
+
<ul>
<li>action</li>
<li>consensus in the community</li>
<li>(if needed) votes within the community</li>
</ul>
+
<p>We have, over the years, developed a very simple and effective approach to
consensus building and decision making. Projects, and the ASF generally, make the vast majority of decisions
using <a href="/committers/lazyConsensus.html">lazy consensus</a>. If the “lazy” approach to consensus building seems
unsuitable for a particular decision, we seek to <a href="/committers/consensusBuilding.html">build consensus</a> within
the community. Very occasionally, usually for formal reasons relating to legal
responsibilities, it is necessary to call a <a href="/committes/voting.html">vote</a>.</p>
+
<p>Full descriptions of each of these approaches are available on various foundation
and project sites. However, we’ve provided an initial introduction to <a href="/committers/decisionMaking.html">decision
making</a> here on the community development site.</p>
-<h2 id="project-independence">Project independence <a class="headerlink" title="Permalink" href="#project-independence">¶</a></h2>
+
+<h2 id="project-independence">Project independence</h2>
+
<p>While not all ASF projects practice all aspects of the Apache Way in the same way, there are a number of rules that Apache
projects must follow – things like complying with PMC
<a href="https://www.apache.org/legal/release-policy.html">release voting</a>, <a href="https://www.apache.org/legal/">legal policy</a>, <a href="https://www.apache.org/foundation/marks/">brand policy</a>,
using <a href="https://www.apache.org/dev/#mail">mailing lists</a>, etc., which <a href="https://blogs.apache.org/comdev/entry/what_makes_apache_projects_different">various sites document</a>.</p>
+
<p>One of these invariant rules is that PMCs manage projects
independently of any commercial interests. The goal is to create an
environment in which all participants are equal and thus have an equal
opportunity to contribute to and benefit from our software, regardless
of motivation or financial objectives. There is more discussion of this principle
in our document <a href="/projectIndependence.html">Project Independence</a>.</p>
+
<p><a name="Index-Assistingwithprojectmanagement"></a></p>
-<h2 id="development-processes">Development processes <a class="headerlink" title="Permalink" href="#development-processes">¶</a></h2>
+
+<h2 id="development-processes">Development processes</h2>
+
<p>Each project in Apache is free to define its own development processes as
long as it respects our decision-making, legal and independence requirements.
However, over the many years that the ASF has existed, our projects have evolved and documented many best practices. In this section we
bring together some of the most popular of these practices. Most Apache projects
operate in ways that are largely similar to these processes.</p>
+
<ul>
<li><a href="https://subversion.apache.org/docs/community-guide/conventions.html#crediting">Crediting contributors</a> is a critical part of community building</li>
<li><a href="https://www.apache.org/legal/resolved.html">ASF Licensing Policy</a></li>
<li>Releases
+
<ul>
<li><a href="https://www.apache.org/legal/release-policy.html">Releases FAQ</a></li>
<li>Release audit is a process each release candidate must go through to ensure it is managing intellectual property (IP) correctly
+
<ul>
<li><a href="https://incubator.apache.org/rat/">RAT/Creadur</a> is a tool to assist this process</li>
-</ul>
-</li>
+</ul></li>
<li><a href="https://sling.apache.org/site/release-management.html">Release management</a> is how the project prepares and publishes its releases</li>
<li><a href="https://infra.apache.org/crypto.html">Handling cryptography</a> in an Apache Release</li>
<li><a href="https://www.apache.org/legal/src-headers.html">Source Headers and NOTICE</a> Files</li>
<li><a href="https://incubator.apache.org/guides/releasemanagement.html#distribution-best-practice">Distribution best practices</a></li>
-</ul>
-</li>
+</ul></li>
<li><a href="https://www.apache.org/dev/">ASF Developer section sitemap</a></li>
</ul>
-<h2 id="assisting-with-project-management-and-marketing">Assisting with project management and marketing <a class="headerlink" title="Permalink" href="#assisting-with-project-management-and-marketing">¶</a></h2>
+
+<h2 id="assisting-with-project-management-and-marketing">Assisting with project management and marketing</h2>
+
<p>There are many visible contributions of value in an Apache projects
(documentation, testing, coding user support, design etc.), but there are
also plenty of “back office” tasks that are necessary to maintain a healthy
project. This section describes some of the activities that you can help
with. In most cases you will need to be a committer to carry out these
activities, although non-committers can often act in supporting roles.</p>
+
<ul>
<li>Write informational <a href="https://infra.apache.org/project-blogs">blogs</a></li>
<li><a href="/newcommitter.html">Assessing and approving new committers</a></li>
<li><a href="/boardreport.html">Board Reports</a></li>
<li><a href="https://www.apache.org/foundation/marks/resources">Apache Project Branding/Trademark Resources</a></li>
</ul>
-<h2 id="speaking-about-apache-projects-at-events">Speaking about Apache projects at events <a class="headerlink" title="Permalink" href="#speaking-about-apache-projects-at-events">¶</a></h2>
+
+<h2 id="speaking-about-apache-projects-at-events">Speaking about Apache projects at events</h2>
+
<p>We encourage all of our committers to speak about Apache projects and
technologies, and generally to help to grow and enhance our community.</p>
-<h2 id="other-resources">Other Resources <a class="headerlink" title="Permalink" href="#other-resources">¶</a></h2>
+
+<h2 id="other-resources">Other Resources</h2>
+
<p>There is no shortage of useful resources for committers at Apache. Here are a few you might want to take a look at:</p>
+
<ul>
<li><a href="https://www.apache.org/foundation/how-it-works.html">How the ASF works</a></li>
<li><a href="https://infra.apache.org/new-committers-guide.html">Guide for New Committers</a></li>
diff --git a/content/committers/index.xml b/content/committers/index.xml
index 978260e..70190e5 100644
--- a/content/committers/index.xml
+++ b/content/committers/index.xml
@@ -1,11 +1,16 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Committer resources on Apache Comdev</title>
<link>https://community.apache.org/committers/</link>
<description>Recent content in Committer resources on Apache Comdev</description>
<generator>Hugo -- gohugo.io</generator>
- <language>en</language><atom:link href="https://community.apache.org/committers/index.xml" rel="self" type="application/rss+xml" />
+ <language>en</language>
+ <lastBuildDate>Wed, 29 Mar 2023 11:49:44 +0200</lastBuildDate>
+
+ <atom:link href="https://community.apache.org/committers/index.xml" rel="self" type="application/rss+xml" />
+
+
<item>
<title>Consensus Building</title>
<link>https://community.apache.org/committers/consensusBuilding.html</link>
@@ -13,7 +18,7 @@
<guid>https://community.apache.org/committers/consensusBuilding.html</guid>
<description>In some cases there is no obvious path to take, or you might be a new community, or a new member of an existing community. In these cases people often need to build consensus by making proposals and eliciting responses.
-Constructive discussion is the lifeblood of a successful project. However, we want to avoid unnecessary discussion and significant amounts of unnecessary mail that everyone in the community needs to read. so many ASF projects adopt a shorthand notation for showing support, or otherwise, for a proposal.</description>
+Constructive discussion is the lifeblood of a successful project. However, we want to avoid unnecessary discussion and significant amounts of unnecessary mail that everyone in the community needs to read.</description>
</item>
<item>
@@ -54,8 +59,8 @@ If you have any question about this, feel free to ask on our dev@community.</des
<guid>https://community.apache.org/committers/voting.html</guid>
<description>Occasionally a &ldquo;feel&rdquo; for consensus is not enough. Sometimes we need to have a measurable consensus, for example, when voting to invite new committers or to approve a release.
-Preparing for a Vote &para; It is important to ensure that the community has time to discuss the issue before voting. To do this, post an email to the list indicating the intention to call a vote and the options available. By the time a vote takes place there usually is consensus in the community on what path to take.</description>
+Preparing for a Vote It is important to ensure that the community has time to discuss the issue before voting. To do this, post an email to the list indicating the intention to call a vote and the options available. By the time a vote takes place there usually is consensus in the community on what path to take.</description>
</item>
</channel>
-</rss>
+</rss>
\ No newline at end of file
diff --git a/content/committers/lazyConsensus.html b/content/committers/lazyConsensus.html
index ee5b4a8..cd6b64c 100644
--- a/content/committers/lazyConsensus.html
+++ b/content/committers/lazyConsensus.html
@@ -9,9 +9,23 @@
<meta property="og:title" content="Lazy Consensus" />
<meta property="og:description" content="The concept of “lazy consensus” is very important in your project. Lazy consensus means that when you are convinced that you know what the community would like to see happen, you can assume that you have consensus in favor of the proposed work and can get on with it. You don’t have to insist people discuss and/or approve your plan, and you certainly don’t need to call a vote to get approval." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/committers/lazyConsensus.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="committers" />
+<meta property="og:url" content="https://community.apache.org/committers/lazyConsensus.html" />
+
+
+
+
+<meta property="article:modified_time" content="2022-02-20T11:10:20-04:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2022-02-20T11:10:20-04:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Lazy Consensus</title>
@@ -187,40 +201,52 @@
<hr>
- <p>The concept of “lazy consensus” is very important in your project. Lazy
+
+
+<p>The concept of “lazy consensus” is very important in your project. Lazy
consensus means that when you are convinced that you know what the community
would like to see happen, you can assume that you have consensus in favor of the proposed work and
can get on with it. You don’t have to insist people discuss and/or
approve your plan, and you certainly don’t need to call a vote to get approval.
You just assume you have the community’s support unless someone says otherwise.</p>
+
<p>We have a time machine (Subversion or Git). As long as you commit
(or submit patches) early and often, the community has plenty of opportunity
to indicate disapproval or point out issues. If you believe the community will support your action
you can operate on lazy consensus as long as you are prepared to roll back
any work should someone raise a valid objection.</p>
-<h2 id="avoiding-unnecessary-discussion">Avoiding unnecessary discussion <a class="headerlink" title="Permalink" href="#avoiding-unnecessary-discussion">¶</a></h2>
+
+<h2 id="avoiding-unnecessary-discussion">Avoiding unnecessary discussion</h2>
+
<p>The key thing about lazy consensus is that it’s easier for people to agree
by doing nothing, than it is to object, which requires them to propose an alternative. This has two effects: first, people are less
likely to object for the sake of objecting and, second, it cuts down on the amount
of unnecessary email traffic and discussion.</p>
+
<p>Lazy consensus lets us avoid having to wait for a community-based decision
before proceeding. However, it does require everyone who cares about the health
of the project to watch what is happening, as it is happening. Objecting too
far down the road will cause upset, while objecting (or asking for clarification
of intent) early is likely to be greeted with relief that someone is watching
and cares.</p>
-<h2 id="stating-lazy-consensus">Stating lazy consensus <a class="headerlink" title="Permalink" href="#stating-lazy-consensus">¶</a></h2>
+
+<h2 id="stating-lazy-consensus">Stating lazy consensus</h2>
+
<p>Sometimes a member of the community will believe a specific action is the correct
one for the project but is not sure that there will be consensus. They may not wish to proceed with the work without giving the
community an opportunity to provide feedback. In these circumstances they can make the
proposal and state that lazy consensus is in operation, like this:</p>
+
<ul>
<li>In an email to <code>dev@PROJECT</code>, they state their proposal, with sufficient supporting material for someone familiar with the project to understand it.</li>
<li>In the email they indicate that they will start
implementing the proposal in 72 hours unless someone objects. The time period takes into account that project members are a) busy and b) in time zones around the world.</li>
</ul>
+
<p>In this approach the the proposer does not insist that the developer community discuss or explicitly support the proposal. However, it allows space and time to <a href="/committers/consensusBuilding.html">express support or objections</a> or propose corrections to the proposal before work begins.</p>
-<h2 id="silence-is-consent">Silence is consent <a class="headerlink" title="Permalink" href="#silence-is-consent">¶</a></h2>
+
+<h2 id="silence-is-consent">Silence is consent</h2>
+
<p>People may choose to indicate their support for the proposal with a +1
mail - quick and easy to read and reassuring for the implementer. However,
remember, in a lazy consensus world silence is equivalent to support.</p>
diff --git a/content/committers/voting.html b/content/committers/voting.html
index a490021..c60de00 100644
--- a/content/committers/voting.html
+++ b/content/committers/voting.html
@@ -8,11 +8,25 @@
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="Voting" />
<meta property="og:description" content="Occasionally a “feel” for consensus is not enough. Sometimes we need to have a measurable consensus, for example, when voting to invite new committers or to approve a release.
-Preparing for a Vote ¶ It is important to ensure that the community has time to discuss the issue before voting. To do this, post an email to the list indicating the intention to call a vote and the options available. By the time a vote takes place there usually is consensus in the community on what path to take." />
+Preparing for a Vote It is important to ensure that the community has time to discuss the issue before voting. To do this, post an email to the list indicating the intention to call a vote and the options available. By the time a vote takes place there usually is consensus in the community on what path to take." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/committers/voting.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="committers" />
+<meta property="og:url" content="https://community.apache.org/committers/voting.html" />
+
+
+
+
+<meta property="article:modified_time" content="2022-02-20T11:05:53-04:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2022-02-20T11:05:53-04:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Voting</title>
@@ -188,27 +202,37 @@ Preparing for a Vote ¶ It is important to ensure that the community has tim
<hr>
- <p>Occasionally a “feel” for consensus is not enough. Sometimes we need to
+
+
+<p>Occasionally a “feel” for consensus is not enough. Sometimes we need to
have a measurable consensus, for example, when voting to invite new committers or
to approve a release.</p>
-<h2 id="preparing-for-a-vote">Preparing for a Vote <a class="headerlink" title="Permalink" href="#preparing-for-a-vote">¶</a></h2>
+
+<h2 id="preparing-for-a-vote">Preparing for a Vote</h2>
+
<p>It is important to ensure that the community has time to
discuss the issue before voting. To do this, post an email to the list
indicating the intention to call a vote and the options available. By the time
a vote takes place there usually is <a href="/committers/consensusBuilding.html">consensus in the community</a> on what path to take. The vote
itself is, normally, a formality; however, it is important as part of the record of the decisions of the PMC and the development of the project.</p>
-<h2 id="calling-a-vote">Calling a Vote <a class="headerlink" title="Permalink" href="#calling-a-vote">¶</a></h2>
+
+<h2 id="calling-a-vote">Calling a Vote</h2>
+
<p>Once it is time to call the vote, the proposer or a member of the PMC posts an email with the subject line starting
with <strong>[VOTE]</strong>. This helps community members not miss
an important vote thread. It also indicates that this is not a consensus-building conversation
but a formal vote.</p>
-<h3 id="casting-your-vote">Casting Your Vote <a class="headerlink" title="Permalink" href="#casting-your-vote">¶</a></h3>
+
+<h3 id="casting-your-vote">Casting Your Vote</h3>
+
<p>The notation used in voting is:</p>
+
<ul>
<li>+1 Yes, I agree</li>
<li>0 I have no strong opinion</li>
<li>-1 I object on the following grounds</li>
</ul>
+
<p>If you object you <strong>must</strong> support your objection and provide an alternative course
of action that you are willing and able to implement (where appropriate).</p>
diff --git a/content/contactpoints.html b/content/contactpoints.html
index c1671cc..f53c9d0 100644
--- a/content/contactpoints.html
+++ b/content/contactpoints.html
@@ -9,12 +9,26 @@
<meta property="og:title" content="ContactPoints" />
<meta property="og:description" content="If you have a question about anything Apache, the ComDev project is here to help.
To help us help you, try to direct your question to the right mailing list - our volunteer committers do all their work on mailing lists.
-Community Questions ¶ Email questions about community or issues across multiple Apache projects to dev@community.apache.org - or see our detailed Mailing List How To page.
-Technical Questions ¶ If you have a technical question about this website, or one of the tools that the ComDev project builds, email us at dev@community." />
+Community Questions Email questions about community or issues across multiple Apache projects to dev@community.apache.org - or see our detailed Mailing List How To page.
+Technical Questions If you have a technical question about this website, or one of the tools that the ComDev project builds, email us at dev@community." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/contactpoints.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="" />
+<meta property="og:url" content="https://community.apache.org/contactpoints.html" />
+
+
+
+
+<meta property="article:modified_time" content="2020-12-10T09:12:00-04:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2020-12-10T09:12:00-04:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - ContactPoints</title>
@@ -184,43 +198,68 @@ Technical Questions ¶ If you have a technical question about this website,
<hr>
- <p>If you have a question about anything Apache, the ComDev project is here to help.<br>
+
+
+<p>If you have a question about anything Apache, the ComDev project is here to help.<br />
To help us help you, try to direct your question to the right mailing list - our
volunteer committers do all their work on mailing lists.</p>
-<h1 id="community-questions">Community Questions <a class="headerlink" title="Permalink" href="#community-questions">¶</a></h1>
+
+<h1 id="community-questions">Community Questions</h1>
+
<p>Email questions about community or issues across multiple Apache projects to <a href="mailto:dev@community.apache.org?subject=New-Contact-Question">dev@community.apache.org</a> - or see our detailed <a href="//community.apache.org/lists.html">Mailing List How To</a> page.</p>
-<h1 id="technical-questions">Technical Questions <a class="headerlink" title="Permalink" href="#technical-questions">¶</a></h1>
+
+<h1 id="technical-questions">Technical Questions</h1>
+
<p>If you have a <em>technical</em> question about <em>this</em> website, or one of the tools that
the ComDev project builds, email us at <code>dev@community</code>.</p>
+
<p>If you <em>technical</em> question about <em>any other</em> Apache project, email
the <a href="/lists.html">appropriate user@<em>projectname</em>.apache.org</a> list, or the <code>dev@</code> list for
the project.</p>
-<h1 id="non-technical-questions">Non-Technical Questions <a class="headerlink" title="Permalink" href="#non-technical-questions">¶</a></h1>
+
+<h1 id="non-technical-questions">Non-Technical Questions</h1>
+
<p>Each of Apache’s email lists is privately archived: you can mail to them, and
we’ll answer, but you won’t be able to read the archives.</p>
+
<p><a name="ContactPoints-Trademarks"></a></p>
-<h2 id="trademarks">Trademarks <a class="headerlink" title="Permalink" href="#trademarks">¶</a></h2>
+
+<h2 id="trademarks">Trademarks</h2>
+
<p>Issues regarding trademarks, specific project names, or branding of the
ASF and any projects: see our <a href="//www.apache.org/foundation/marks/resources">Trademark Site Map</a>,
or send email to <a href="mailto:trademarks@apache.org">trademarks@apache.org</a>.</p>
+
<p><a name="ContactPoints-PublicityandMarketing"></a></p>
-<h2 id="publicity-and-marketing">Publicity and Marketing <a class="headerlink" title="Permalink" href="#publicity-and-marketing">¶</a></h2>
+
+<h2 id="publicity-and-marketing">Publicity and Marketing</h2>
+
<p>Issues dealing with publicity, marketing, or any inquires from the
press or analysts: see our <a href="https://www.apache.org/press/">Press Team Page</a>,
-or email to <a href="mailto:press@apache.org">press@apache.org</a>.</p>
+ or email to <a href="mailto:press@apache.org">press@apache.org</a>.</p>
+
<p><a name="ContactPoints-FundraisingandSponsorship"></a></p>
-<h2 id="fundraising-and-sponsorship">Fundraising and Sponsorship <a class="headerlink" title="Permalink" href="#fundraising-and-sponsorship">¶</a></h2>
+
+<h2 id="fundraising-and-sponsorship">Fundraising and Sponsorship</h2>
+
<p>Questions about fundraising, sponsorships, donations, or related
finances: see our <a href="//www.apache.org/foundation/contributing.html">Donations Information</a>,
or email to <a href="mailto:fundraising@apache.org">fundraising@apache.org</a>.</p>
+
<p><a name="ContactPoints-Legal"></a></p>
-<h3 id="legal">Legal <a class="headerlink" title="Permalink" href="#legal">¶</a></h3>
+
+<h3 id="legal">Legal</h3>
+
<p>Send specific legal questions that may need to be private, and require a
response from the ASF’s legal counsel to
<a href="mailto:legal-internal@apache.org">legal-internal@apache.org</a>.</p>
+
<p>Please read our <a href="https://www.apache.org/legal/#user-links">Legal FAQs</a> first.</p>
+
<p><a name="ContactPoints-Other"></a></p>
-<h3 id="other">Other <a class="headerlink" title="Permalink" href="#other">¶</a></h3>
+
+<h3 id="other">Other</h3>
+
<p>For more information on these and other foundation lists, see the <a href="https://www.apache.org/foundation/mailinglists.html">Mailing Lists</a> page.</p>
diff --git a/content/contributors/becomingacommitter.html b/content/contributors/becomingacommitter.html
index bbf2463..5ed77a0 100644
--- a/content/contributors/becomingacommitter.html
+++ b/content/contributors/becomingacommitter.html
@@ -7,12 +7,26 @@
<meta name="keywords" content="apache, apache community, community development, opensource"/>
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="Becoming a committer" />
-<meta property="og:description" content="Disclaimer ¶ Nothing in this post should be construed as a guarantee. You can do everything listed here, for years, and still not become a committer. This is because the decision is made by individuals on the project PMC, who do things for their own reasons.
+<meta property="og:description" content="Disclaimer Nothing in this post should be construed as a guarantee. You can do everything listed here, for years, and still not become a committer. This is because the decision is made by individuals on the project PMC, who do things for their own reasons.
On the contrary, this document discusses how things should work, and sometimes do work, in some Apache Software Foundation (ASF) projects, but might not on the one you’re interested in." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/contributors/becomingacommitter.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="contributors" />
+<meta property="og:url" content="https://community.apache.org/contributors/becomingacommitter.html" />
+
+
+
+
+<meta property="article:modified_time" content="2023-03-21T17:21:46-04:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2023-03-21T17:21:46-04:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Becoming a committer</title>
@@ -188,66 +202,120 @@ On the contrary, this document discusses how things should work, and sometimes d
<hr>
- <h1 id="disclaimer">Disclaimer <a class="headerlink" title="Permalink" href="#disclaimer">¶</a></h1>
+
+
+<h1 id="disclaimer">Disclaimer</h1>
+
<p>Nothing in this post should be construed as a guarantee. You can do everything listed here, for years, and still not become a committer. This is because the decision is made by individuals on the project PMC, who do things for their own reasons.</p>
+
<p>On the contrary, this document discusses how things should work, and sometimes do work, in some Apache Software Foundation (ASF) projects, but might not on the one you’re interested in.</p>
+
<p>Beneath each of these recommendations is the assumption that you are acting in good faith, for the benefit of the project. Simply attempting to check these boxes to game the system will reflect badly on you, and probably on your employer, too.</p>
-<h1 id="becoming-a-committer">Becoming a Committer <a class="headerlink" title="Permalink" href="#becoming-a-committer">¶</a></h1>
+
+<h1 id="becoming-a-committer">Becoming a Committer</h1>
+
<p>It’s important to remember that becoming a committer is not a reward, or a recognition, so much as that it is the project expressing self-interest. That is, people are added as a committer to a project because it benefits the project, not because it’s some kind of pat on the back for the individual in question. As such, every behavior suggested here is about advancing the interests of the project. It is critical that you think, first and foremost, about being a project owner, and work [...]
+
<p>These, therefore, are the behaviors that you should exhibit if you want to become a committer, and then a PMC member, on an ASF project. (These are not unique to ASF projects, of course, but process will differ greatly from one project to another, and are largely similar among ASF projects.)</p>
-<h1 id="read-the-mailing-list">Read the mailing list <a class="headerlink" title="Permalink" href="#read-the-mailing-list">¶</a></h1>
+
+<h1 id="read-the-mailing-list">Read the mailing list</h1>
+
<p>ASF projects communicate on the mailing list. If you want to be involved in the community, you must set aside time every week (preferably every day) to keep current on the community discussion.</p>
+
<p>When first participating in an ASF project, you can (and should) look back several months (or as far as you have time for) to see what has been discussed recently. You can do this at <a href="http://lists.apache.org/">lists.apache.org</a>.</p>
+
<p>A growing number of projects also have a presence on Slack, Discord, or somewhere else. Find where that is, and become a regular. A shrinking number of projects have a presence on Libera IRC – mostly the much older projects. This is where you’ll connect with the older members of the projects and learn more of the ancient project lore.</p>
-<h1 id="contribute-code-and-other-things">Contribute code (and other things) <a class="headerlink" title="Permalink" href="#contribute-code-and-other-things">¶</a></h1>
+
+<h1 id="contribute-code-and-other-things">Contribute code (and other things)</h1>
+
<p>If you want to become a committer, you should make significant contributions to the project. The most obvious thing to contribute to a software project is code. Code contributions should be diverse in terms of size and significance. That is, you should work on small issues and large. You should collaborate with others on features and fixes, and you should propose significant changes yourself. You should dig up old tickets, and work towards resolving them.</p>
+
<p>In particular, you should work on code that is of benefit to all users, rather than focusing solely on features that benefit only yourself, or your employer. As a project owner, you should care about the entire health and sustainability of the project.</p>
+
<p>Code contributions are not the only type of contribution that counts towards becoming a committer, it’s just the most common. Design, documentation, marketing, event management, and many other ways of contributing to the success of a project are also often considered in making someone a committer. While the term “committer” implies committing code, it can also be interpreted as someone who is committed to the project.</p>
-<h1 id="end-user-support">End user support <a class="headerlink" title="Permalink" href="#end-user-support">¶</a></h1>
+
+<h1 id="end-user-support">End user support</h1>
+
<p>Answering end user questions has many benefits. It’s the best way to establish expertise in aspects of the software that effect actual users, and, thus, the best way to stay in touch with user concerns. It’s also the way to establish and maintain visibility in the project community, because your name is always visible on the mailing list.</p>
+
<p>Caution: Do not just jump in and answer every question with visibility as a primary goal. Ensure that your answers are actually useful, and contribute something to the conversation. Simply posting to every conversation, particularly when someone else has already offered a good answer, can be perceived as attempting to game the metrics.</p>
-<h1 id="documentation">Documentation <a class="headerlink" title="Permalink" href="#documentation">¶</a></h1>
+
+<h1 id="documentation">Documentation</h1>
+
<p>Improving the documentation is one of the most effective things that one can do to improve the user experience. If you notice many people asking similar questions, this is usually an indication that the documentation is weak on that point. Fix it. When the question is asked again, point to the improved documentation, and ask for feedback as to how it could be further improved.</p>
+
<p>Take criticism of the documentation as a challenge, rather than a personal criticism.</p>
+
<p>As you learn about the project, consider yourself a tester of the documentation. If anything is unclear, propose a patch.</p>
-<h1 id="review-prs-and-tickets">Review PRs and tickets <a class="headerlink" title="Permalink" href="#review-prs-and-tickets">¶</a></h1>
+
+<h1 id="review-prs-and-tickets">Review PRs and tickets</h1>
+
<p>Dig into unmerged PRs and outstanding tickets. Figure out how to navigate the process to get an old ticket resolved, or a PR merged.</p>
+
<p>This is an investment in the project in two ways.</p>
+
<p>The obvious improvement is getting an issue fixed or a PR merged, thus enhancing the project. The less obvious way is that ancient tickets, and unmerged PRs, communicate that the project is not actively maintained, and that user issues are being ignored. This undermines project trust. Thus, addressing these things builds community trust, and increases your personal value to the project.</p>
-<h1 id="be-visible">Be visible <a class="headerlink" title="Permalink" href="#be-visible">¶</a></h1>
+
+<h1 id="be-visible">Be visible</h1>
+
<p>Participate meaningfully in discussions on the developer mailing list. Drive discussions through to action. Advocate for changes that help yourself and your employer, but also for those that improve the project as a whole.</p>
+
<p>Get to know the important characters on the project, and what their priorities are. Help them achieve those priorities in whatever way you can. Figure out who you can best collaborate with to advance your own personal interests in the project, but also the overall health of the project and community.</p>
+
<p>Start conversations around topics you’re passionate about, and volunteer to be the one to address them.</p>
+
<p>Do not, however, just talk to be seen. Nobody is fooled by that.</p>
-<h1 id="test-and-vote-on-releases-non-binding">Test, and vote on releases (non-binding) <a class="headerlink" title="Permalink" href="#test-and-vote-on-releases-non-binding">¶</a></h1>
+
+<h1 id="test-and-vote-on-releases-non-binding">Test, and vote on releases (non-binding)</h1>
+
<p>Testing releases, and then reporting problems or suggesting
improvements, is one of the most important functions of users, and is an
important way to contribute to a project. It also familiarizes you with
the function of the software, which will lead you to be a better
contributor.</p>
+
<p>Many projects use CI to continuously test proposed patches and PRs. Each
platform needs to be individually set up for testing, and often the
projects do not have enough people familiar with the specific
environments that might benefit from testing. You can propose additional
platforms to test on.</p>
+
<p>Vote on release candidates and releases (non-binding).</p>
+
<p>Note that a vote should always mean that you’ve actually tested, so testing releases is implied here, too. Indicate what platform(s) you’ve tested on, and what was the nature of the tests that you performed. Testing releases on a variety of platforms and configurations is a very valuable piece of information for projects with limited testing infrastructure.</p>
+
<p>While these votes don’t “count” towards making a release official, it’s both hugely beneficial for the project, and increases your visibility.</p>
-<h1 id="give-talks">Give talks <a class="headerlink" title="Permalink" href="#give-talks">¶</a></h1>
+
+<h1 id="give-talks">Give talks</h1>
+
<p>Propose talks to conferences about the project, and about how your employer’s customers are using it.</p>
+
<p>Proposing “Introduction to Apache Woobly” talks has many benefits. It is a great way to get the word out about the project. It’s good for establishing yourself as an expert in the field. It educates users (and potential customers) about operating the software. And it will help you identify what’s actually important about the software, how people use it, and what kinds of questions real users are asking about the software.</p>
+
<p>Community Over Code (formerly called ApacheCon) is the obvious place to give these talks, but also look for conferences about the general technology space around the project you’re contributing to.</p>
-<h1 id="once-youre-a-committer-">Once you’re a committer … <a class="headerlink" title="Permalink" href="#once-youre-a-committer-">¶</a></h1>
+
+<h1 id="once-you-re-a-committer">Once you’re a committer …</h1>
+
<p>If and when you achieve your goal of becoming a committer, don’t consider your journey done.</p>
+
<p>Becoming a PMC member is a continuation of the same path. Continue to do all of the above things, focusing more on the health of the project as a whole, rather than just your personal interests, or those of your employer or manager.</p>
+
<p>Also, take an active interest in other contributors – both those on your team, and those with other employers. Mentor them in following the same path that you followed. Encourage them. Celebrate them, and mention them to other contributors. This is an investment in the future of the project, so that, some day, when you move on to something else, the project will live on.</p>
+
<p>Interest across multiple projects, and at the Foundation-wide level, is the start of the path to becoming a Foundation Member, if that is something that interests you.</p>
-<h1 id="summary">Summary <a class="headerlink" title="Permalink" href="#summary">¶</a></h1>
+
+<h1 id="summary">Summary</h1>
+
<p>Finally, a reminder – there’s no way to guarantee promotion to committer or the PMC. However, if you make your goal the improvement of the project, rather than just about personal promotion, and approach these recommendations as a path to project ownership, in good faith, these are your best path towards that goal.</p>
-<h1 id="resources">Resources <a class="headerlink" title="Permalink" href="#resources">¶</a></h1>
+
+<h1 id="resources">Resources</h1>
+
<p>Find your project’s <a href="https://projects.apache.org/">committer and PMC membership lists</a></p>
+
<p>Read <a href="https://lists.apache.org/">mailing list archives</a></p>
+
<p>Find your contribution count to date on Github, for example: <a href="https://github.com/apache/hadoop/graphs/contributors">Apache hadoop contributors</a> (You can drag a date range to narrow it down to recent contributions.)</p>
+
<p>View <a href="https://www.apache.org/foundation/board/calendar.html">past board reports from your project</a>. This is a good way to judge the rate at which a given project adds committers and PMC members. It’s also a way to compare how long other individuals took to attain committer status.</p>
diff --git a/content/contributors/etiquette.html b/content/contributors/etiquette.html
index d6229f0..d4485c8 100644
--- a/content/contributors/etiquette.html
+++ b/content/contributors/etiquette.html
@@ -8,11 +8,25 @@
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="ASF Community Etiquette Guidelines" />
<meta property="og:description" content="The ASF and our many projects welcome all participants. Before you begin, it is important to review and respect our community guidelines. We have a few ASF-specific tips below.
-Code of Conduct ¶ The ASF has adopted a Code of Conduct which covers interactions in all the online spaces that ASF projects use - email, issue trackers, wikis, websites, IRC, and the like. ASF projects are made up of volunteers, and we work to ensure that all productive contributions are welcomed." />
+Code of Conduct The ASF has adopted a Code of Conduct which covers interactions in all the online spaces that ASF projects use - email, issue trackers, wikis, websites, IRC, and the like. ASF projects are made up of volunteers, and we work to ensure that all productive contributions are welcomed." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/contributors/etiquette.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="contributors" />
+<meta property="og:url" content="https://community.apache.org/contributors/etiquette.html" />
+
+
+
+
+<meta property="article:modified_time" content="2023-03-17T12:29:24-05:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2023-03-17T12:29:24-05:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - ASF Community Etiquette Guidelines</title>
@@ -188,67 +202,71 @@ Code of Conduct ¶ The ASF has adopted a Code of Conduct which covers intera
<hr>
- <p>The ASF and our many projects welcome all
+
+
+<p>The ASF and our many projects welcome all
participants. Before you begin, it is important to review and respect our community guidelines. We have a few
ASF-specific tips below.</p>
-<h1 id="coc">Code of Conduct <a class="headerlink" title="Permalink" href="#coc">¶</a></h1>
+
+<h1 id="coc">Code of Conduct</h1>
+
<p>The ASF has adopted a <a href="https://www.apache.org/foundation/policies/conduct.html">Code of Conduct</a> which covers interactions in
all the online spaces that ASF projects use - email, issue trackers, wikis,
websites, IRC, and the like. ASF projects are made up of volunteers, and
we work to ensure that all productive contributions are welcomed. Every PMC is expected to ensure their project’s lists show
proper behavior.</p>
-<h1 id="member">Guidelines for Conduct and Etiquette <a class="headerlink" title="Permalink" href="#member">¶</a></h1>
+
+<h1 id="member">Guidelines for Conduct and Etiquette</h1>
+
<p>The ASF as a corporation is run by several hundred members, who have deep and lasting experience
in helping to build and run long-term, successful open source projects. Below are some guidelines to help you communicate with other volunteers, and get the most out of your communication experience.</p>
+
<p><strong>General Communication Guidelines</strong></p>
+
<ul>
-<li>
-<p>Use a thoughtful, respectful tone to communicate your thoughts. Remember, text is difficult to interpret. There are no body language or voice tones to help interpret the messenger’s intent. Remember that the person on the other side of your communication is also a human deserving of understanding and
-respect.</p>
-</li>
-<li>
-<p>If you agree with someone, let them know. If you disagree, let them know as well. Positive and negative feedback are both necessary. Positive
+<li><p>Use a thoughtful, respectful tone to communicate your thoughts. Remember, text is difficult to interpret. There are no body language or voice tones to help interpret the messenger’s intent. Remember that the person on the other side of your communication is also a human deserving of understanding and
+respect.</p></li>
+
+<li><p>If you agree with someone, let them know. If you disagree, let them know as well. Positive and negative feedback are both necessary. Positive
feedback will help others feel more confident in their ideas, as well as ensure they know they’re on the right track. Negative feedback, given in a
-respectable tone, will help to guide the messenger toward a more productive solution.</p>
-</li>
-<li>
-<p>Avoid idiomatic and metaphoric language. At the ASF, we have thousands of volunteers that speak different languages. To avoid miscommunication, it
-is best to avoid this type of language in favor of clear, direct statements.</p>
-</li>
-<li>
-<p>Be patient when waiting for responses. Because the ASF is an international community, there may be some delays in response time. We call these
+respectable tone, will help to guide the messenger toward a more productive solution.</p></li>
+
+<li><p>Avoid idiomatic and metaphoric language. At the ASF, we have thousands of volunteers that speak different languages. To avoid miscommunication, it
+is best to avoid this type of language in favor of clear, direct statements.</p></li>
+
+<li><p>Be patient when waiting for responses. Because the ASF is an international community, there may be some delays in response time. We call these
“asynchronous responders.” We understand that it can be difficult and frustrating to wait, but please give these asynchronous responders time to read
-and address your message. The ASF strives to respond to all messages (email, slack, etc.) in a timely manner.</p>
-</li>
-<li>
-<p>Dealing with conflict and miscommunication: Here at the ASF, we strive to make everyone feel welcome and wanted in their roles. With that said, we
+and address your message. The ASF strives to respond to all messages (email, slack, etc.) in a timely manner.</p></li>
+
+<li><p>Dealing with conflict and miscommunication: Here at the ASF, we strive to make everyone feel welcome and wanted in their roles. With that said, we
also understand that miscommunications happen, especially in text. If you are sent a message that you don’t understand, or feel uncomfortable with, a
good first step would be to ask for clarification. Don’t be afraid to ask specific questions. Chances are, the person you’re communicating with has been
-in your position before, and will understand.</p>
-</li>
-<li>
-<p>Be forgiving and accept different priorities: Everyone that works on ASF projects is passsionate about their work, and we love and welcome that
+in your position before, and will understand.</p></li>
+
+<li><p>Be forgiving and accept different priorities: Everyone that works on ASF projects is passsionate about their work, and we love and welcome that
passion and hope you will bring your own passion to your projects. Please remember, the ASF currently has over 300 projects, each with their own project
priorities. If your priorities seem at odds with others, remember that compromise is essential to progress. Work with the other person to come up with a
-compromise that takes all project priorities into account.</p>
-</li>
-<li>
-<p>Note: Foul, derogatory, or divisive language in any form, up to and including threats, harassment, and discriminatory language, is strongly
-prohibited.</p>
-</li>
+compromise that takes all project priorities into account.</p></li>
+
+<li><p>Note: Foul, derogatory, or divisive language in any form, up to and including threats, harassment, and discriminatory language, is strongly
+prohibited.</p></li>
</ul>
+
<p><strong>Face-to-Face</strong> is excellent way to eliminate disagreements, but that is often
not practical. Consider a conversation via Skype, Google Hangouts or a Slack channel, just for the social aspect
of being part of this community. It does not need to be a formal meeting. Once we have a face to add to the words, and a general
idea how that person is socially, we are much more capable to interact via text.</p>
-<p><strong>Project decisions must always be made on mailing lists</strong>.<br>
+
+<p><strong>Project decisions must always be made on mailing lists</strong>.<br />
It’s great to have a synchronous online chat to work through some questions, but
be sure to bring the results of the chat (and any proposals for the
project community to consider) back to the mailing list. People who
weren’t able to attend the chat or call might also have ideas on the topic.
Be sure to allow at least 72 hours for others to read the proposals and
comment before closing out the issue.</p>
-<h1 id="other">Other Etiquette Guidelines <a class="headerlink" title="Permalink" href="#other">¶</a></h1>
+
+<h1 id="other">Other Etiquette Guidelines</h1>
+
<ul>
<li><a href="https://www.apache.org/foundation/policies/conduct.html">Official Apache-wide Code of Conduct</a></li>
<li><a href="https://www.apache.org/dev/contrib-email-tips">Email Etiquette Guidelines - writing good emails</a></li>
diff --git a/content/contributors/index.html b/content/contributors/index.html
index 7a25a29..29020ba 100644
--- a/content/contributors/index.html
+++ b/content/contributors/index.html
@@ -9,7 +9,21 @@
<meta property="og:title" content="Contributing to the Apache Software Foundation" />
<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/contributors/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+<meta property="og:url" content="https://community.apache.org/contributors/" />
+
+
+
+<meta property="og:updated_time" content="2023-03-29T11:49:44+02:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
<title>Apache Community Development - Contributing to the Apache Software Foundation</title>
@@ -182,68 +196,90 @@
<hr>
- <p>This page is for people who are reasonably
+
+
+<p>This page is for people who are reasonably
comfortable with open source development models but need a helping hand finding
their way around the Apache Software Foundation and our way of developing software
(commonly called “The Apache Way”). For those wishing to start from
the very beginning, we have a <a href="/newcomers/index.html">newcomers page</a>.</p>
-<h1 id="project-independence-and-policies">Project Independence And Policies <a class="headerlink" title="Permalink" href="#project-independence-and-policies">¶</a></h1>
+
+<h1 id="project-independence-and-policies">Project Independence And Policies</h1>
+
<p>While not all ASF projects practice all aspects of the Apache Way in the same way, there are a number of rules that Apache
projects must follow – things like complying with PMC
<a href="https://www.apache.org/legal/release-policy.html">release voting</a>, <a href="https://www.apache.org/legal/">legal policy</a>, <a href="https://www.apache.org/foundation/marks/">brand policy</a>,
using <a href="https://www.apache.org/dev/#mail">mailing lists</a>, etc., which are <a href="https://blogs.apache.org/comdev/entry/what_makes_apache_projects_different">documented in various places</a>.</p>
+
<p>One of these invariant rules is that projects are managed
independently of any commercial interests. The goal is to create an
environment in which all participants are equal and thus have an equal
opportunity to contribute to and benefit from our software, regardless
of motivation or financial objectives. This is discussed in more detail
in our document <a href="/projectIndependence.html">Project Independence</a>.</p>
-<h1 id="moving-from-contributor-to-committer">Moving From Contributor to Committer <a class="headerlink" title="Permalink" href="#moving-from-contributor-to-committer">¶</a></h1>
+
+<h1 id="moving-from-contributor-to-committer">Moving From Contributor to Committer</h1>
+
<p>Anyone can be a contributor to an Apache project. Being a contributor simply means
that you take an interest in the project and contribute in some way, ranging from asking
sensible questions (which document the project and provide feedback to developers)
through to providing new features as code patches.</p>
+
<p>If you become a valuable contributor to the project, the Project Management Committee (PMC) may invite you to become
a <em>committer</em>. At the ASF, a committer is someone who is
committed to a particular project. It brings with it the privilege of write access to
the project repository and resources. In many projects, committers may also be invited
to be part of the core group within the project that ensures the project’s vitality, the PMC.
In a few projects only a subset of committers who have earned even more merit are invited to be a part of the PMC.</p>
+
<p>One thing that is sometimes hard to understand, when you are new to the open
development process used at the ASF, is that we value the community more than
the code. A strong and healthy community will be respectful and be a fun and
rewarding place. More importantly, a diverse and healthy community can
continue to support the code over the longer term, even as individual
contributors come and go from the field.</p>
+
<p>In particular, we have some <a href="/contributors/etiquette">etiquette and behavior expectations</a> when
you work with Apache communities.</p>
+
<p>See also this <a href="/contributors/becomingacommitter.html">detailed advice for how to become a committer</a></p>
-<h2 id="contributing-a-project---copdoc">Contributing A Project - CoPDoC <a class="headerlink" title="Permalink" href="#contributing-a-project---copdoc">¶</a></h2>
+
+<h2 id="contributing-a-project-copdoc">Contributing A Project - CoPDoC</h2>
+
<p>The foundations of an Apache project and how the community contributes to it are
sometimes referred to by the acronym CoPDoC:</p>
+
<ul>
<li>(Co)mmunity - one must interact with others, and share vision and knowledge</li>
<li>(P)roject - a clear vision and consensus are needed</li>
<li>(Do)cumentation - without it, the stuff remains only in the minds of the authors</li>
-<li>(C)ode - discussion goes nowhere without code</li>
+<li>©ode - discussion goes nowhere without code</li>
</ul>
-<h2 id="anyone-can-become-a-committer">Anyone Can Become A Committer <a class="headerlink" title="Permalink" href="#anyone-can-become-a-committer">¶</a></h2>
+
+<h2 id="anyone-can-become-a-committer">Anyone Can Become A Committer</h2>
+
<p>There is nothing at the Apache Software Foundation that says you must write code
in order to be a committer. Anyone who is supportive of the community and works
in any of the CoPDoC areas is a likely candidate for committership.</p>
+
<p>Apache strives to be meritocratic. That is, once someone has contributed sufficiently to
any area of CoPDoC they can be voted in as a committer. Being a committer does
not necessarily mean you commit code; it means you are committed to the project
and are productively contributing to its success.</p>
+
<p>One of the key contributions people can make to the community is through the
support of a wide user base by assisting users on the user list, writing user-oriented docs and ensuring the developers understand the user viewpoint.
A main idea behind being a committer is the ability to be a mentor and to work
cooperatively with your peers.</p>
+
<p>Some users of a project’s software become committers in their own right. Some will test code,
some will write documentation, some will do bug triage and some will write code.</p>
+
<p>For more details see “<a href="https://www.apache.org/foundation/how-it-works.html">How it works</a>”. You can also make
<a href="/newbiefaq.html#websitecms">suggestions for how to update this website</a> you’re reading right now!</p>
-<h2 id="questions-and-feedback">Questions and Feedback <a class="headerlink" title="Permalink" href="#questions-and-feedback">¶</a></h2>
+
+<h2 id="questions-and-feedback">Questions and Feedback</h2>
+
<p>You can provide feedback and ask questions by subscribing to our mailing
list: send an email to
<a href="mailto:dev-subscribe@community.apache.org">dev-subscribe@community.apache.org</a>. Once subscribed, you can send your mail to
diff --git a/content/contributors/index.xml b/content/contributors/index.xml
index 71b4df0..327cd4d 100644
--- a/content/contributors/index.xml
+++ b/content/contributors/index.xml
@@ -1,11 +1,16 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Contributing to the Apache Software Foundation on Apache Comdev</title>
<link>https://community.apache.org/contributors/</link>
<description>Recent content in Contributing to the Apache Software Foundation on Apache Comdev</description>
<generator>Hugo -- gohugo.io</generator>
- <language>en</language><atom:link href="https://community.apache.org/contributors/index.xml" rel="self" type="application/rss+xml" />
+ <language>en</language>
+ <lastBuildDate>Wed, 29 Mar 2023 11:49:44 +0200</lastBuildDate>
+
+ <atom:link href="https://community.apache.org/contributors/index.xml" rel="self" type="application/rss+xml" />
+
+
<item>
<title>ASF Community Etiquette Guidelines</title>
<link>https://community.apache.org/contributors/etiquette.html</link>
@@ -13,7 +18,7 @@
<guid>https://community.apache.org/contributors/etiquette.html</guid>
<description>The ASF and our many projects welcome all participants. Before you begin, it is important to review and respect our community guidelines. We have a few ASF-specific tips below.
-Code of Conduct &para; The ASF has adopted a Code of Conduct which covers interactions in all the online spaces that ASF projects use - email, issue trackers, wikis, websites, IRC, and the like. ASF projects are made up of volunteers, and we work to ensure that all productive contributions are welcomed.</description>
+Code of Conduct The ASF has adopted a Code of Conduct which covers interactions in all the online spaces that ASF projects use - email, issue trackers, wikis, websites, IRC, and the like. ASF projects are made up of volunteers, and we work to ensure that all productive contributions are welcomed.</description>
</item>
<item>
@@ -22,9 +27,9 @@ Code of Conduct &para; The ASF has adopted a Code of Conduct which covers in
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/contributors/becomingacommitter.html</guid>
- <description>Disclaimer &para; Nothing in this post should be construed as a guarantee. You can do everything listed here, for years, and still not become a committer. This is because the decision is made by individuals on the project PMC, who do things for their own reasons.
+ <description>Disclaimer Nothing in this post should be construed as a guarantee. You can do everything listed here, for years, and still not become a committer. This is because the decision is made by individuals on the project PMC, who do things for their own reasons.
On the contrary, this document discusses how things should work, and sometimes do work, in some Apache Software Foundation (ASF) projects, but might not on the one you’re interested in.</description>
</item>
</channel>
-</rss>
+</rss>
\ No newline at end of file
diff --git a/content/events.html b/content/events.html
index 8b2c8de..1db34e6 100644
--- a/content/events.html
+++ b/content/events.html
@@ -9,7 +9,21 @@
<meta property="og:title" content="Events" />
<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/events.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+<meta property="og:url" content="https://community.apache.org/events.html" />
+
+
+
+
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
<title>Apache Community Development - Events</title>
diff --git a/content/events/index.xml b/content/events/index.xml
index e70a733..44f0a6d 100644
--- a/content/events/index.xml
+++ b/content/events/index.xml
@@ -1,18 +1,22 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Events on Apache Comdev</title>
<link>https://community.apache.org/events.html</link>
<description>Recent content in Events on Apache Comdev</description>
<generator>Hugo -- gohugo.io</generator>
- <language>en</language><atom:link href="https://community.apache.org/events/index.xml" rel="self" type="application/rss+xml" />
+ <language>en</language>
+
+ <atom:link href="https://community.apache.org/events/index.xml" rel="self" type="application/rss+xml" />
+
+
<item>
<title>Requirements for organizers of small Apache-related events</title>
<link>https://community.apache.org/events/small-events.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/events/small-events.html</guid>
- <description>Approval of small Apache-related events &para; The Community Development PMC is responsible for assisting with the organisation and promotion of all Apache events.
+ <description>Approval of small Apache-related events The Community Development PMC is responsible for assisting with the organisation and promotion of all Apache events.
Organizers of Apache-related events need approval for using the Apache trademarks in their event brandings.
The main steps are:
a) Get approval from the PMCs of the projects that your event is about.
@@ -21,4 +25,4 @@ c) Once brand use is approved by the respective PMCs, inform the community devel
</item>
</channel>
-</rss>
+</rss>
\ No newline at end of file
diff --git a/content/events/small-events.html b/content/events/small-events.html
index b4c4c38..306a4ee 100644
--- a/content/events/small-events.html
+++ b/content/events/small-events.html
@@ -7,16 +7,30 @@
<meta name="keywords" content="apache, apache community, community development, opensource"/>
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="Requirements for organizers of small Apache-related events" />
-<meta property="og:description" content="Approval of small Apache-related events ¶ The Community Development PMC is responsible for assisting with the organisation and promotion of all Apache events.
+<meta property="og:description" content="Approval of small Apache-related events The Community Development PMC is responsible for assisting with the organisation and promotion of all Apache events.
Organizers of Apache-related events need approval for using the Apache trademarks in their event brandings.
The main steps are:
a) Get approval from the PMCs of the projects that your event is about.
b) Abide by the Apache branding rules.
c) Once brand use is approved by the respective PMCs, inform the community development PMC of your event, including references to PMCs approval." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/events/small-events.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="events" />
+<meta property="og:url" content="https://community.apache.org/events/small-events.html" />
+
+
+
+
+<meta property="article:modified_time" content="2020-07-20T20:22:04+02:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2020-07-20T20:22:04+02:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Requirements for organizers of small Apache-related events</title>
@@ -192,21 +206,30 @@ c) Once brand use is approved by the respective PMCs, inform the community devel
<hr>
- <h1 id="approval-of-small-apache-related-events">Approval of small Apache-related events <a class="headerlink" title="Permalink" href="#approval-of-small-apache-related-events">¶</a></h1>
+
+
+<h1 id="approval-of-small-apache-related-events">Approval of small Apache-related events</h1>
+
<p>The Community Development PMC is responsible for assisting with the
organisation and promotion of all Apache events.</p>
+
<p>Organizers of Apache-related events need approval for using the
Apache trademarks in their event brandings.</p>
+
<p>The main steps are:</p>
+
<p>a) Get approval from the PMCs of the projects that your event is about.</p>
+
<p>b) Abide by the <a href="https://www.apache.org/foundation/marks/events.html">Apache branding rules</a>.</p>
+
<p>c) Once brand use is approved by the respective PMCs, inform the community
development PMC of your event, including references to PMCs approval.
-Ideally on our public (<a href="mailto:dev@community.apache.org">dev@community.apache.org</a>) mailing list,
-but at least in private (<a href="mailto:private@community.apache.org">private@community.apache.org</a>).</p>
+Ideally on our public (dev@community.apache.org) mailing list,
+but at least in private (private@community.apache.org).</p>
+
<p>d) Wait at least 72 hours for comments from the community development PMC
and then send an announcement of your event to
-<a href="mailto:dev@community.apache.org">dev@community.apache.org</a> so that it can be included in our
+dev@community.apache.org so that it can be included in our
<a href="../calendars/">events calendar</a>.</p>
diff --git a/content/gettingstarted.html b/content/gettingStarted.html
similarity index 97%
rename from content/gettingstarted.html
rename to content/gettingStarted.html
index 360751e..b8ed436 100644
--- a/content/gettingstarted.html
+++ b/content/gettingStarted.html
@@ -9,7 +9,21 @@
<meta property="og:title" content="GettingStarteds" />
<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/gettingstarted.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+<meta property="og:url" content="https://community.apache.org/gettingStarted.html" />
+
+
+
+
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
<title>Apache Community Development - GettingStarteds</title>
@@ -169,7 +183,7 @@
- <li class="breadcrumb-item"><a href='/gettingstarted.html'>Gettingstarted</a></li>
+ <li class="breadcrumb-item"><a href='/gettingStarted.html'>Getting started</a></li>
diff --git a/content/gettingStarted/101.html b/content/gettingStarted/101.html
index 2cba70c..3fe69e4 100644
--- a/content/gettingStarted/101.html
+++ b/content/gettingStarted/101.html
@@ -7,12 +7,26 @@
<meta name="keywords" content="apache, apache community, community development, opensource"/>
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="Getting started" />
-<meta property="og:description" content="Where do I start? ¶ If you have no idea where to start your engagement with an Apache project, this is the page for you.
-Finding the right project ¶ The key to working on projects at Apache (and on any open source project, for that matter) is to have a personal reason for being involved. You might be trying to solve a day job issue or learn a new technology, or simply want to do something fun in your free time." />
+<meta property="og:description" content="Where do I start? If you have no idea where to start your engagement with an Apache project, this is the page for you.
+Finding the right project The key to working on projects at Apache (and on any open source project, for that matter) is to have a personal reason for being involved. You might be trying to solve a day job issue or learn a new technology, or simply want to do something fun in your free time." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/gettingStarted/101.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="gettingStarted" />
+<meta property="og:url" content="https://community.apache.org/gettingStarted/101.html" />
+
+
+
+
+<meta property="article:modified_time" content="2023-03-29T19:28:51+01:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2023-03-29T19:28:51+01:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Getting started</title>
@@ -188,51 +202,69 @@ Finding the right project ¶ The key to working on projects at Apache (and o
<hr>
- <h1 id="where-do-i-start">Where do I start? <a class="headerlink" title="Permalink" href="#where-do-i-start">¶</a></h1>
+
+
+<h1 id="where-do-i-start">Where do I start?</h1>
+
<p>If you have no idea where to start your engagement with an Apache project,
this is the page for you.</p>
-<h3 id="finding-the-right-project">Finding the right project <a class="headerlink" title="Permalink" href="#finding-the-right-project">¶</a></h3>
+
+<h3 id="finding-the-right-project">Finding the right project</h3>
+
<p>The key to working on projects at Apache (and on any open source project, for that matter)
is to have a personal reason for being involved. You might be trying to solve
a day job issue or learn a new technology, or
simply want to do something fun in your free time. We don’t care what your
motivation is; we just care about you wanting to get involved.</p>
+
<p>If you don’t have a specific technical issue to solve you might be willing to
work on any project. Our <a href="https://projects.apache.org/">projects page</a> provides a useful index which
allows you to view projects alphabetically, by category or by coding language. When you view a project’s detail page in this list you will find information about their
mailing lists, issue tracker and other resources.</p>
+
<p>You might also like to view our
<a href="https://incubator.apache.org/">Incubating projects</a>. These projects work in exactly the same way as our “top
level projects” but are still developing their initial community.</p>
+
<p>Once you’ve found some interesting-looking projects, join their mailing lists and
start “lurking”. Read the mails that come through the list. Initially you will not
understand what people are talking about, but over time you will start to
pick up the language, objectives, strategies, concerns and working patterns of the community.</p>
-<h4 id="finding-an-issue-to-work-on">Finding an issue to work on <a class="headerlink" title="Permalink" href="#finding-an-issue-to-work-on">¶</a></h4>
+
+<h4 id="finding-an-issue-to-work-on">Finding an issue to work on</h4>
+
<p>If you are trying to satisfy a specific technical problem, you already know
what you want to work on; but if you are looking for something useful to do in
order to participate in an ASF project, the project’s issue/bug tracker is your
friend. You can find a link to it from the project’s home page or from its entry on the
projects page linked above.</p>
+
<p>In the project’s issue tracker you will find details of bugs that have been reported and feature
requests the project is considering. This should give you some
inspiration about how you might be able to help the project community. If
you are looking for a beginner-level issue, try searching Jira for issues
with the label “GSoC” or “mentor”; these are issues the community feels are
manageable for someone new to the ASF and their project.</p>
-<h2 id="joining-the-community">Joining the community <a class="headerlink" title="Permalink" href="#joining-the-community">¶</a></h2>
+
+<h2 id="joining-the-community">Joining the community</h2>
+
<p>Once you have identified an issue you would like to tackle, it’s time to join the
project’s mailing list (if you haven’t already) and get started.</p>
+
<p>Remember, community members are usually happy to help you, but they have to get something
in return. The community needs to believe that you intend to contribute positively
to their work. There is a limit to how much “hand-holding” you will get, so be ready
to do some work if you expect to continue to be helped in your first foray into
open source.</p>
+
<p>Alternatively you can dive straight in and work with the community. Since you’ve
been lurking on the lists for a while, you
should have a feel for how to get involved, so go for it.</p>
+
<p>A very good first step would be to introduce yourself in an email to the list. Explain your interest in the project and anything relevant in your background or skills, and identify the bug or feature request you would like to work on.</p>
-<h1 id="further-reading">Further Reading <a class="headerlink" title="Permalink" href="#further-reading">¶</a></h1>
+
+<h1 id="further-reading">Further Reading</h1>
+
<ul>
<li>Answers to some common questions are in our <a href="/newbiefaq.html">FAQ</a></li>
<li>To learn more about “The Apache Way” of developing software, see the
diff --git a/content/gettingStarted/index.xml b/content/gettingStarted/index.xml
new file mode 100644
index 0000000..d15c829
--- /dev/null
+++ b/content/gettingStarted/index.xml
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
+<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
+ <channel>
+ <title>GettingStarteds on Apache Comdev</title>
+ <link>https://community.apache.org/gettingStarted.html</link>
+ <description>Recent content in GettingStarteds on Apache Comdev</description>
+ <generator>Hugo -- gohugo.io</generator>
+ <language>en</language>
+
+ <atom:link href="https://community.apache.org/gettingStarted/index.xml" rel="self" type="application/rss+xml" />
+
+
+ <item>
+ <title>Getting started</title>
+ <link>https://community.apache.org/gettingStarted/101.html</link>
+ <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+
+ <guid>https://community.apache.org/gettingStarted/101.html</guid>
+ <description>Where do I start? If you have no idea where to start your engagement with an Apache project, this is the page for you.
+Finding the right project The key to working on projects at Apache (and on any open source project, for that matter) is to have a personal reason for being involved. You might be trying to solve a day job issue or learn a new technology, or simply want to do something fun in your free time.</description>
+ </item>
+
+ </channel>
+</rss>
\ No newline at end of file
diff --git a/content/gettingstarted/index.xml b/content/gettingstarted/index.xml
deleted file mode 100644
index 8231ee7..0000000
--- a/content/gettingstarted/index.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?>
-<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
- <channel>
- <title>GettingStarteds on Apache Comdev</title>
- <link>https://community.apache.org/gettingstarted.html</link>
- <description>Recent content in GettingStarteds on Apache Comdev</description>
- <generator>Hugo -- gohugo.io</generator>
- <language>en</language><atom:link href="https://community.apache.org/gettingstarted/index.xml" rel="self" type="application/rss+xml" />
- <item>
- <title>Getting started</title>
- <link>https://community.apache.org/gettingStarted/101.html</link>
- <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-
- <guid>https://community.apache.org/gettingStarted/101.html</guid>
- <description>Where do I start? &para; If you have no idea where to start your engagement with an Apache project, this is the page for you.
-Finding the right project &para; The key to working on projects at Apache (and on any open source project, for that matter) is to have a personal reason for being involved. You might be trying to solve a day job issue or learn a new technology, or simply want to do something fun in your free time.</description>
- </item>
-
- </channel>
-</rss>
diff --git a/content/gsoc/experiences.html b/content/gsoc/experiences.html
index da32aa5..55e611e 100644
--- a/content/gsoc/experiences.html
+++ b/content/gsoc/experiences.html
@@ -9,11 +9,25 @@
<meta property="og:title" content="Apache in GSoC" />
<meta property="og:description" content="This should be in the GSoC directory
This is a place for collecting information about GSoC activities each year for historical tracking. It was started in 2012 so is missing plenty of detail in the early years. Your help filling it out would be appreciated.
-2018 Overview ¶ Students accepted: ? Students who passed final: 29 2017 Overview ¶ Students accepted: ? Students who passed final: 27 2016 Overview ¶ Students accepted: 49 Students who passed final: 35 2015 Overview ¶ Students accepted: 56 Students who passed final: 47 2014 Overview ¶ Students accepted: 42 Students who passed final: 35 2013 Overview ¶ Students accepted: 51 Students who passed final: 44 2012 Overview ¶ Students accepted: 41 Students who [...]
+2018 Overview Students accepted: ? Students who passed final: 29 2017 Overview Students accepted: ? Students who passed final: 27 2016 Overview Students accepted: 49 Students who passed final: 35 2015 Overview Students accepted: 56 Students who passed final: 47 2014 Overview Students accepted: 42 Students who passed final: 35 2013 Overview Students accepted: 51 Students who passed final: 44 2012 Overview Students accepted: 41 Students who passed midterm: 40 26 projects mento [...]
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/gsoc/experiences.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="gsoc" />
+<meta property="og:url" content="https://community.apache.org/gsoc/experiences.html" />
+
+
+
+
+<meta property="article:modified_time" content="2023-03-21T10:25:42+07:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2023-03-21T10:25:42+07:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Apache in GSoC</title>
@@ -189,55 +203,74 @@ This is a place for collecting information about GSoC activities each year for h
<hr>
- <p><em>This should be in the GSoC directory</em></p>
+
+
+<p><em>This should be in the GSoC directory</em></p>
+
<p>This is a place for
collecting information about GSoC activities each year for historical tracking. It
was started in 2012 so is missing plenty of detail in the early years. Your help
filling it out would be appreciated.</p>
-<h1 id="2018-overview">2018 Overview <a class="headerlink" title="Permalink" href="#2018-overview">¶</a></h1>
+
+<h1 id="2018-overview">2018 Overview</h1>
+
<ul>
<li>Students accepted: ?</li>
<li>Students who passed final: 29</li>
</ul>
-<h1 id="2017-overview">2017 Overview <a class="headerlink" title="Permalink" href="#2017-overview">¶</a></h1>
+
+<h1 id="2017-overview">2017 Overview</h1>
+
<ul>
<li>Students accepted: ?</li>
<li>Students who passed final: 27</li>
</ul>
-<h1 id="2016-overview">2016 Overview <a class="headerlink" title="Permalink" href="#2016-overview">¶</a></h1>
+
+<h1 id="2016-overview">2016 Overview</h1>
+
<ul>
<li>Students accepted: 49</li>
<li>Students who passed final: 35</li>
</ul>
-<h1 id="2015-overview">2015 Overview <a class="headerlink" title="Permalink" href="#2015-overview">¶</a></h1>
+
+<h1 id="2015-overview">2015 Overview</h1>
+
<ul>
<li>Students accepted: 56</li>
<li>Students who passed final: 47</li>
</ul>
-<h1 id="2014-overview">2014 Overview <a class="headerlink" title="Permalink" href="#2014-overview">¶</a></h1>
+
+<h1 id="2014-overview">2014 Overview</h1>
+
<ul>
<li>Students accepted: 42</li>
<li>Students who passed final: 35</li>
</ul>
-<h1 id="2013-overview">2013 Overview <a class="headerlink" title="Permalink" href="#2013-overview">¶</a></h1>
+
+<h1 id="2013-overview">2013 Overview</h1>
+
<ul>
<li>Students accepted: 51</li>
<li>Students who passed final: 44</li>
</ul>
-<h1 id="2012-overview">2012 Overview <a class="headerlink" title="Permalink" href="#2012-overview">¶</a></h1>
+
+<h1 id="2012-overview">2012 Overview</h1>
+
<ul>
<li>Students accepted: 41</li>
<li>Students who passed midterm: 40</li>
<li>26 projects mentoring (17 TLPs and 9 Podlings)
+
<ul>
<li>Participating TLPS are: Xerces, Pig, OODT, Hive, James, Tapestry, Ofbiz,
Gora, Synapse, Derby, Axis, POI, Whirr, Lucene, Velocity, Libcloud, Xalan</li>
<li>Participating Podlings are: ODF Toolkit, Airavata, Stanbol, Photark,
Wookie, OpenMeetings, Nuvem, Hama, VXQuery</li>
+</ul></li>
</ul>
-</li>
-</ul>
-<h2 id="2012-blogs">2012 Blogs <a class="headerlink" title="Permalink" href="#2012-blogs">¶</a></h2>
+
+<h2 id="2012-blogs">2012 Blogs</h2>
+
<ul>
<li><a href="https://scottbw.wordpress.com/2012/08/22/wookie-adds-support-for-signed-widgets-thanks-to-google-summer-of-code/">Scott Wilson: Wookie Mentor</a></li>
<li><a href="https://pushpalankajaya.blogspot.com/search/label/GSoC">Pushpalanka: Wookie Student</a></li>
@@ -245,18 +278,24 @@ Wookie, OpenMeetings, Nuvem, Hama, VXQuery</li>
<li><a href="https://summerwithairavata.blogspot.com/">Bhathiya Jayasekara: Airavata Student</a></li>
<li><a href="https://blogs.apache.org/openmeetings/entry/google_summer_of_code_2012">OpenMeetings Mentors: Sebastian Wagner, Alexei Fedotov, Maxim Solodovnik - Students: Ankur Ankan, German Grekhov, Dmitry Zamula, Josh Dolitsky </a></li>
</ul>
-<h1 id="2011-overview">2011 Overview <a class="headerlink" title="Permalink" href="#2011-overview">¶</a></h1>
+
+<h1 id="2011-overview">2011 Overview</h1>
+
<ul>
<li>Students accepted: 40</li>
<li>Students who passed midterm: 38</li>
<li>Students who passed final: 36</li>
</ul>
-<h1 id="2010-overview">2010 Overview <a class="headerlink" title="Permalink" href="#2010-overview">¶</a></h1>
+
+<h1 id="2010-overview">2010 Overview</h1>
+
<ul>
<li>Students accepted: 44</li>
<li>Students who passed final: 39</li>
</ul>
-<h1 id="2005">2005 <a class="headerlink" title="Permalink" href="#2005">¶</a></h1>
+
+<h1 id="2005">2005</h1>
+
<p>First year Apache participated</p>
diff --git a/content/gsoc/gsoc-admin-tasks.html b/content/gsoc/gsoc-admin-tasks.html
index a683552..a2b27a8 100644
--- a/content/gsoc/gsoc-admin-tasks.html
+++ b/content/gsoc/gsoc-admin-tasks.html
@@ -9,11 +9,25 @@
<meta property="og:title" content="GSoC admins" />
<meta property="og:description" content="A comprehensive guide to being a GSoC admin for the ASF
List of duties:
-Make sure the ASF has an extensive list of project ideas ready shortly after Google announces the program (around the end of January). Projects must create Jira issues for their ideas and label them with gsoc<year>; and mentor. If a project doesn’t use Jira, have them create the ideas in the GSOC Jira project. Create a Jira filter for these ideas to use in the application (see next)." />
+ Make sure the ASF has an extensive list of project ideas ready shortly after Google announces the program (around the end of January). Projects must create Jira issues for their ideas and label them with gsoc<year>; and mentor. If a project doesn’t use Jira, have them create the ideas in the GSOC Jira project. Create a Jira filter for these ideas to use in the application (see next)." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/gsoc/gsoc-admin-tasks.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="gsoc" />
+<meta property="og:url" content="https://community.apache.org/gsoc/gsoc-admin-tasks.html" />
+
+
+
+
+<meta property="article:modified_time" content="2023-03-29T19:28:51+01:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2023-03-29T19:28:51+01:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - GSoC admins</title>
@@ -190,7 +204,9 @@ Make sure the ASF has an extensive list of project ideas ready shortly after Goo
<hr>
<p>A comprehensive guide to being a GSoC admin for the ASF</p>
+
<p>List of duties:</p>
+
<ol>
<li>Make sure the ASF has an extensive list of project ideas ready shortly after Google announces the
program (around the end of January). Projects must create Jira issues for their ideas and
@@ -199,6 +215,7 @@ Jira project. Create a Jira filter for these ideas to use in the application (se
prospective mentors subscribe to <code>mentors@community.apache.org</code>. The following is an email sent to <code>pmcs@a.o</code>
explaining the procedures to them:</li>
</ol>
+
<pre>
Hello PMCs,
@@ -230,73 +247,63 @@ Uli
[2] https://s.apache.org/gsoc2011tasks
[3] https://community.apache.org/gsoc/
</pre>
+
<ol>
-<li>
-<p>Update our GSoC pages at <a href="/gsoc/">https://community.apache.org/gsoc/</a> with the
-current year’s timeline and at <a href="guide-to-being-a-mentor.html">https://community.apache.org/gsoc/guide-to-being-a-mentor.html</a>.</p>
-</li>
-<li>
-<p>Apply for the ASF to be a mentoring organization for Google Summer of Code.
+<li><p>Update our GSoC pages at <a href="/gsoc/">https://community.apache.org/gsoc/</a> with the
+current year’s timeline and at <a href="guide-to-being-a-mentor.html">https://community.apache.org/gsoc/guide-to-being-a-mentor.html</a>.</p></li>
+
+<li><p>Apply for the ASF to be a mentoring organization for Google Summer of Code.
I faintly remember that they wanted to know some stats like how often we have
already participated and what the number of students was last year. I believe
-the ASF has participated since GSoC’s inception in 2005. Consult <a href="http://community.apache.org/gsoc/experiences.html">participation statistics</a>, although the page may not be up to date.</p>
-</li>
-<li>
-<p>Once our application is accepted, write a press release and
+the ASF has participated since GSoC’s inception in 2005. Consult <a href="http://community.apache.org/gsoc/experiences.html">participation statistics</a>, although the page may not be up to date.</p></li>
+
+<li><p>Once our application is accepted, write a press release and
request press@ to send it out. We don’t have a template yet, so work
with th <code>dev@community.apache.org</code> and <code>press@apache.org</code> lists to get one
-written and add it here.</p>
-</li>
-<li>
-<p>Check with Google whether they changed the ranking process – again. Find out
+written and add it here.</p></li>
+
+<li><p>Check with Google whether they changed the ranking process – again. Find out
what we need to be change to our internal ranking process in order to be compatible
with melange (the system Google uses to administer GSOC) and update the <a href="mentee-ranking-process.html">mentee ranking process</a> page
accordingly. In 2011 we used a Google Docs spreadsheet and did our ranking there. The
-org admin (and only the org admin) then transferred the rankings to Melange.</p>
-</li>
-<li>
-<p>Once the application phase starts, make sure that mentors rank the proposals. They
+org admin (and only the org admin) then transferred the rankings to Melange.</p></li>
+
+<li><p>Once the application phase starts, make sure that mentors rank the proposals. They
should complete this at least one week before Google’s official deadline in order to have
-some time for changes that might become necessary. Send reminders.</p>
-</li>
-<li>
-<p>Once Google has assigned our slots and we know who is accepted,
+some time for changes that might become necessary. Send reminders.</p></li>
+
+<li><p>Once Google has assigned our slots and we know who is accepted,
mail each mentee with details of the <code>dev@community.apache.org</code> list, which they can
use for general assistance with the ASF. They should seek project-specific
assistance on the project’s <code>dev</code> list. We don’t have a
-template for this yet. Please add it here when one is written.</p>
-</li>
-<li>
-<p>Once GSoC is under way, make sure we meet deadlines for midterm and final evaluations. Make it clear to the mentors that we’d like to see their evaluation way before
+template for this yet. Please add it here when one is written.</p></li>
+
+<li><p>Once GSoC is under way, make sure we meet deadlines for midterm and final evaluations. Make it clear to the mentors that we’d like to see their evaluation way before
the end of the deadline. If a mentor still hasn’t submitted their evaluation three days
before the end of the deadline period, mail their PMC and ask them whether they know of
-any reason why the mentor might not be able to do the evaluation.</p>
-</li>
-<li>
-<p>Once GSoC is done, get a PO# from Google to invoice against. Supplier name is The
+any reason why the mentor might not be able to do the evaluation.</p></li>
+
+<li><p>Once GSoC is done, get a PO# from Google to invoice against. Supplier name is The
Apache Software Foundation, 1901 Munsey Drive, Forest Hill, MD 21050-2747. Our vendor ID
-with Google is 13039.</p>
-</li>
-<li>
-<p>Issue a press release congratulating those who have passed and
+with Google is 13039.</p></li>
+
+<li><p>Issue a press release congratulating those who have passed and
thanking our wonderful mentors. We should invite everyone to come and
contribute to ASF projects. We should include some stats such as the
number of full committers resulting from GSoC, the number of issues
closed etc. We don’t have a template yet but work with the
<code>dev@community.apache.org</code> and <code>press@apache.org</code> lists to get one written
-and add it here.</p>
-</li>
-<li>
-<p>Decide who is going to the mentor summit. If you are going, book your flight (or arrange the details for attending virtually) and
+and add it here.</p></li>
+
+<li><p>Decide who is going to the mentor summit. If you are going, book your flight (or arrange the details for attending virtually) and
nag the comdev PMC chair to submit your travel expenses to financials/Bills/received (if
-you don’t have access yourself) and move them to <code>financials/Bills/approved</code>.</p>
-</li>
-<li>
-<p>Ask treasurer to invoice Google. The amount is number of students * USD 500 (at time
+you don’t have access yourself) and move them to <code>financials/Bills/approved</code>.</p></li>
+
+<li><p>Ask treasurer to invoice Google. The amount is number of students * USD 500 (at time
of writing) + actual travel expenses up to USD 2,000. Attach PO document (you’ll get that
-from Google at some point). Example:</p>
-</li>
+from Google at some point). Example:</p></li>
</ol>
+
<pre>
Geir,
diff --git a/content/gsoc/guide-to-being-a-mentor.html b/content/gsoc/guide-to-being-a-mentor.html
index 0534c93..2a60acf 100644
--- a/content/gsoc/guide-to-being-a-mentor.html
+++ b/content/gsoc/guide-to-being-a-mentor.html
@@ -7,12 +7,27 @@
<meta name="keywords" content="apache, apache community, community development, opensource"/>
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="guide to being a mentor" />
-<meta property="og:description" content="Submitting ideas to the mentoring programme ¶ We invite all ASF projects to submit their ideas for consideration in the ASF mentoring programme. Any Apache member and experienced committers can submit ideas via Jira (if your project does not use Jira you can use the Comdev Issue Tracker For GSoC Tasks. We are looking for as many interesting projects as we can come up with.
-Important Steps ¶ Add an issue to Jira (if your project does not use Jira you can use the Comdev GSoC Issue Tracker For GSoC Tasks Add sub-tasks if necessary Label the main issue with “mentor” (these will show up at the ASF-wide list of issues) Label the main issue with “gsoc2023” if appropriate (these will show up at GSoC 2023 Ideas) Size of project Starting this year there are 2 types of projects available." />
+<meta property="og:description" content="Submitting ideas to the mentoring programme We invite all ASF projects to submit their ideas for consideration in the ASF mentoring programme. Any Apache member and experienced committers can submit ideas via Jira (if your project does not use Jira you can use the Comdev Issue Tracker For GSoC Tasks. We are looking for as many interesting projects as we can come up with.
+
+Important Steps Add an issue to Jira (if your project does not use Jira you can use the Comdev GSoC Issue Tracker For GSoC Tasks Add sub-tasks if necessary Label the main issue with “mentor” (these will show up at the ASF-wide list of issues) Label the main issue with “gsoc2023” if appropriate (these will show up at GSoC 2023 Ideas) Size of project Starting this year there are 2 types of projects available." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/gsoc/guide-to-being-a-mentor.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="gsoc" />
+<meta property="og:url" content="https://community.apache.org/gsoc/guide-to-being-a-mentor.html" />
+
+
+
+
+<meta property="article:modified_time" content="2023-03-29T19:28:51+01:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2023-03-29T19:28:51+01:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - guide to being a mentor</title>
@@ -188,34 +203,47 @@ Important Steps ¶ Add an issue to Jira (if your project does not use Jira y
<hr>
- <!--
+
+
+<!--
Note: This document is bout GSoC, not about a generic Mentoring Program.
-->
+
<p><a name="guidetobeingamentor-Submittingideastothementoringprogramme"></a></p>
-<h1 id="submitting-ideas-to-the-mentoring-programme">Submitting ideas to the mentoring programme <a class="headerlink" title="Permalink" href="#submitting-ideas-to-the-mentoring-programme">¶</a></h1>
+
+<h1 id="submitting-ideas-to-the-mentoring-programme">Submitting ideas to the mentoring programme</h1>
+
<p>We invite all ASF projects to submit their ideas for consideration in the
ASF mentoring programme. Any Apache member and experienced committers can
submit ideas via Jira (if your project does not use Jira you can <a href="use-the-comdev-issue-tracker-for-gsoc-tasks.html">use the Comdev Issue Tracker For GSoC Tasks</a>. We are looking for as many interesting projects as we can come up with.</p>
+
<p><a name="guidetobeingamentor-Summary"></a></p>
-<h2 id="important-steps">Important Steps <a class="headerlink" title="Permalink" href="#important-steps">¶</a></h2>
+
+<h2 id="important-steps">Important Steps</h2>
+
<ul>
<li>Add an issue to Jira (if your project does not use Jira you can <a href="use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.html">use the Comdev GSoC Issue Tracker For GSoC Tasks</a>
+
<ul>
<li>Add sub-tasks if necessary</li>
-</ul>
-</li>
+</ul></li>
<li>Label the main issue with “<em>mentor</em>” (these will show up at the <a href="https://issues.apache.org/jira/issues?jql=labels%20in%20(gsoc2023)%20AND%20labels%20in%20(mentor,%20Mentor)">ASF-wide list of issues</a>)</li>
<li>Label the main issue with “<em>gsoc2023</em>” if appropriate (these will show up at <a href="https://s.apache.org/gsoc2023ideas">GSoC 2023 Ideas</a>)</li>
</ul>
+
<div class="card border-success mb-3">
<div class="card-header">Size of project</div>
<div class="card-body text-success">
<p class="card-text">Starting this year there are 2 types of projects available.<br> Please put "<em>full-time</em>" label for ~350 hours project and<br> "<em>part-time</em>" label for ~175 hours project</p>
</div>
</div>
+
<p>Please NOTE Ideas list is manually updated by GSoC admins, please ping mentors (at) community.apache.org if the page is not being updated .. :))</p>
+
<p><a name="guidetobeingamentor-Detail"></a></p>
-<h2 id="details">Details <a class="headerlink" title="Permalink" href="#details">¶</a></h2>
+
+<h2 id="details">Details</h2>
+
<p>To ensure we include your Jira issues in our list of mentored projects,
please add the label “mentor” to the issue. If you want it to be included
in the Google Summer of Code lists also add the “gsoc” label. If you want
@@ -223,69 +251,97 @@ to include a number of issues in a single mentored project, please create a
parent issue, label that one appropriately and add the other issues as
sub-tasks. Do not label each individual sub-task as that would make them appear as
separate tasks.</p>
+
<p>If you have identifed a mentor, assign the issue to that
mentor.</p>
+
<p>ASF Members and committers can volunteer to mentor or co-mentor proposals.
When in doubt about all this, contact <code>mentors@community.apache.org</code>.</p>
+
<p>For more information about what it means to be a mentor and on how to write
a proposal, see:</p>
+
<ul>
<li><a href="https://developers.google.com/open-source/gsoc/resources/guide#mentor_guide">GSoC Mentoring Guide</a></li>
<li><a href="https://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/">Gnome HowTo on mentoring</a></li>
<li><a href="https://ploum.net/221-how-to-be-a-lazy-but-successful-googlesoc-mentor/">How to be a lazy but successful Google SoC mentor</a></li>
</ul>
+
<p>Note that interest, even by a qualified student, does not mean that any of
those project will automatically go ahead. Depending on the number of
projects; the number of people able to mentor, and the timing we will
probably have to make a smaller selection.</p>
+
<p><a name="guidetobeingamentor-Publicisingyourmentoredissues"></a></p>
-<h3 id="publicising-your-mentored-issues">Publicising your mentored issues <a class="headerlink" title="Permalink" href="#publicising-your-mentored-issues">¶</a></h3>
+
+<h3 id="publicising-your-mentored-issues">Publicising your mentored issues</h3>
+
<p>You can link to the <a href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?requestId=12315361">ASF wide list of issues</a>
-or you can create your own lists and feeds within your own website.</p>
+ or you can create your own lists and feeds within your own website.</p>
+
<p>Since your mentored issues appear alongside your normal Jira issues, you
can create and use filters to help people find them. You can provide RSS
feeds, JSON exports and many more goodies for helping to get the message
out.</p>
+
<p>If you have any cool ideas for using this data, let us know so we can
share them with other projects (mail <code>dev@community.apache.org</code>).</p>
+
<p><a name="guidetobeingamentor-Examples"></a></p>
-<h2 id="examples">Examples <a class="headerlink" title="Permalink" href="#examples">¶</a></h2>
+
+<h2 id="examples">Examples</h2>
+
<ul>
<li><a href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?requestId=12315360">Wookie GSoC Issues</a></li>
<li><a href="https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-rss/12315360/SearchRequest-12315360.xml?tempMax=1000">Wookie RSS GSoC feed</a></li>
<li><a href="https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/12315360/SearchRequest-12315360.xml?tempMax=1000">Wookie XML GSoC feed</a></li>
</ul>
+
<p><a name="guidetobeingamentor-Stayingintouch"></a></p>
-<h1 id="staying-in-touch">Staying in touch <a class="headerlink" title="Permalink" href="#staying-in-touch">¶</a></h1>
+
+<h1 id="staying-in-touch">Staying in touch</h1>
+
<p>All mentors/prospective mentors <strong>must</strong> subscribe to <code>mentors@community.apache.org</code>, our list for
coordinating mentor activities.
This is where mentor specific issues are dealt with, and where announcements will be made.</p>
+
<p>We only accept subscriptions to mentors@ from addresses known to
belong to ASF committers, so please use your @apache.org address to
subscribe if possible, or at least an address that we can match to your
<code>@apache.org</code> address via the ASF’s private/committers/info or
private/committers/MailAlias.txt data.</p>
+
<p>Once the ASF is confirmed as a mentoring organisation mentors must register
with the GSoC webapp, and request to become a mentor for the ASF organization.
Make sure that the email address you use for that (it’s often your @gmail.com address by default)
-is ‘‘‘registered as a mail alias for your Apache account at (<a href="https://id.apache.org">https://id.apache.org</a>)’’’
+is ‘‘‘registered as a mail alias for your Apache account at (<a href="https://id.apache.org)’’’">https://id.apache.org)’’’</a>
so that we can match it to your ASF account.</p>
+
<p>If you are interested in mentor programme administration please also
subscribe to <code>dev@community.apache.org</code>.</p>
+
<p>If you are planning on mentoring as part of the GSoC programme you also
need to register with Google. See our <a href="/gsoc/">GSoC</a> page for more information.</p>
+
<p><a name="guidetobeingamentor-Howmucheffortisinvolvedwithbeingamentor"></a></p>
-<h2 id="how-much-effort-is-involved-with-being-a-mentor">How much effort is involved with being a mentor? <a class="headerlink" title="Permalink" href="#how-much-effort-is-involved-with-being-a-mentor">¶</a></h2>
+
+<h2 id="how-much-effort-is-involved-with-being-a-mentor">How much effort is involved with being a mentor?</h2>
+
<p>Most mentors spend between three and five hours per week with their students. Most
of this time is spent encouraging them.</p>
+
<p>Within the ASF we like to think that the whole project community will help
the student, just as they would any other community member. If your
project is supportive in this way, you may be able to get away with spending
less time yourself. However, as mentor <em>you</em> are responsible for evaluating the
student and helping them deliver on their commitments.</p>
+
<p>The <a href="https://developers.google.com/open-source/gsoc/resources/guide#mentor_guide">GSoC Mentoring Guide</a> has plenty of useful materials for mentors.</p>
+
<p><a name="guidetobeingamentor-Anoteabouteligibility"></a></p>
-<h2 id="a-note-about-eligibility">A note about eligibility <a class="headerlink" title="Permalink" href="#a-note-about-eligibility">¶</a></h2>
+
+<h2 id="a-note-about-eligibility">A note about eligibility</h2>
+
<p>If your project has any restrictions on who can participate (as is the case
with Harmony, for example) be sure to clarify these with potential
students as early as possible. It causes unnecessary confusion and
diff --git a/content/gsoc/index.html b/content/gsoc/index.html
index 6b4a064..5effd77 100644
--- a/content/gsoc/index.html
+++ b/content/gsoc/index.html
@@ -9,7 +9,21 @@
<meta property="og:title" content="GSoC" />
<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/gsoc/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+<meta property="og:url" content="https://community.apache.org/gsoc/" />
+
+
+
+<meta property="og:updated_time" content="2023-03-29T11:49:44+02:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
<title>Apache Community Development - GSoC</title>
@@ -182,7 +196,9 @@
<hr>
- <div class="card mb-3">
+
+
+<div class="card mb-3">
<div class="card-header">
Currently happening
</div>
@@ -190,12 +206,16 @@
<h5 class="card-title text-info">ASF is accepted as mentoring organisation! collect your ideas, answer participant's emails :)</h5>
</div>
</div>
+
<p>Google is sponsoring the <a href="https://summerofcode.withgoogle.com/">2023 Summer of Code</a> and
<a href="https://www.apache.org/">The Apache Software Foundation</a> (ASF) registered as a mentoring organization.
This page is your entry point to the ASF GSoC program.
Please watch this page for updates concerning our participating in 2023.</p>
+
<p><a name="GSoC-Students:readthis"></a></p>
-<h1 id="students-read-this">Students: read this <a class="headerlink" title="Permalink" href="#students-read-this">¶</a></h1>
+
+<h1 id="students-read-this">Students: read this</h1>
+
<ul>
<li>Learn <a href="https://summerofcode.withgoogle.com/about/">about GSoC</a></li>
<li>Decide if you are <a href="https://summerofcode.withgoogle.com/get-started/">eligible</a> for GSoC?</li>
@@ -204,19 +224,24 @@ to make sure you really want to apply to GSoC.</li>
<li>Watch <a href="https://www.youtube.com/watch?v=S6IP_6HG2QE">GSoC video presentation</a>
for students.</li>
<li>Examine the list of <a href="https://s.apache.org/gsoc2023ideas">available ASF GSoC 2023 projects</a>
+
<ul>
<li><span class="text-primary"><strong>NOTE</strong></span> that you can search the issue tracker for GSoC projects by
filtering using the “<em>gsoc2023</em>” label, this allows you to narrow down the list
to the projects you are interested in.<br/>
Or simply use this link <a href="https://issues.apache.org/jira/issues/?jql=labels+%3D+gsoc2023">https://issues.apache.org/jira/issues/?jql=labels+%3D+gsoc2023</a></li>
-</ul>
-</li>
+</ul></li>
<li>If you do not see any interesting projects from the proposed ideas, we encourage you to contact one of the Apache Project’s mailing list and propose a new idea. But these ideas have to be vetted on the project dev list. The ASF does not encourage and will not respond to your personal new open source project ideas which are unrelated to any Apache projects.</li>
</ul>
+
<p><a name="GSoC-ApplyingforGSoC"></a></p>
-<h3 id="applying-for-gsoc">Applying for GSoC <a class="headerlink" title="Permalink" href="#applying-for-gsoc">¶</a></h3>
+
+<h3 id="applying-for-gsoc">Applying for GSoC</h3>
+
<p>Details are announced now and we are in the project discussion phase. We encourage you to discuss you application with the project community.</p>
+
<p>In order to apply we ask that you create</p>
+
<ul>
<li>a list of deliverables, quantifiable results for the Apache community,</li>
<li>a detailed description / design document,</li>
@@ -224,60 +249,99 @@ Or simply use this link <a href="https://issues.apache.org/jira/issues/?jql=labe
<li>an approximate schedule and</li>
<li>something of a background text.</li>
</ul>
+
<p>We also need you to let us know what other commitments you
have for the period of GSoC, for example, do you have any exams or a part
time job? In other words - sell yourselves, as if this was an actual job.</p>
+
<p>In drawing up your proposal you should work with your chosen projects
community.</p>
+
<p>One of our evaluation criteria is that you have already engaged
with the community to ensure that you understand the needs of the project
and the commitment you need to make to your mentors.</p>
+
<p>Once open applications are made through the <a href="https://summerofcode.withgoogle.com/">GSoC site</a></p>
-<h3 id="application-template">Application template <a class="headerlink" title="Permalink" href="#application-template">¶</a></h3>
+
+<h3 id="application-template">Application template</h3>
+
<p><em>This is just a suggested template, feel free to add and remove sections as appropriate. Be brief, don’t write a large essay!</em></p>
-<h4 id="about-me">About me <a class="headerlink" title="Permalink" href="#about-me">¶</a></h4>
+
+<h4 id="about-me">About me</h4>
+
<p><em>What relevant experience have you got, including university, work and hobby activities?</em></p>
-<h4 id="background">Background <a class="headerlink" title="Permalink" href="#background">¶</a></h4>
+
+<h4 id="background">Background</h4>
+
<p><em>What exists already? What is the identified need? What can you reuse, what needs to he replaced?</em></p>
+
<p><em>Example: Apache Foo has already got support for HTTP client requests, but this does not work well with OAuth-based services. The main interface for requests can be reused, but this project proposes to replace the backend code with a modular approach based on Apache Bar.</em></p>
-<h4 id="design--description-of-work">Design / description of work <a class="headerlink" title="Permalink" href="#design--description-of-work">¶</a></h4>
+
+<h4 id="design-description-of-work">Design / description of work</h4>
+
<p><em>Brief list of things you will do / create, in some rough chronological order.</em></p>
+
<p><em>Show which bits are essential, and which are optional. Highlight what is new, what are modifications, and how your work fits into the existing architecture.</em></p>
+
<p><em>Example:</em></p>
+
<ul>
<li><em>Investigate REST client libraries</em></li>
<li><em>Develop JavaScript functions for browsing files (optional)</em></li>
<li><em>Integrate with Apache Foo’s request system (essential)</em></li>
</ul>
-<h4 id="results-for-the-apache-community">Results for the Apache community <a class="headerlink" title="Permalink" href="#results-for-the-apache-community">¶</a></h4>
+
+<h4 id="results-for-the-apache-community">Results for the Apache community</h4>
+
<p><em>Benefit of your work to Apache $Project users and developers. What will be the legacy of your work after you finish?</em></p>
-<h4 id="deliverables">Deliverables <a class="headerlink" title="Permalink" href="#deliverables">¶</a></h4>
+
+<h4 id="deliverables">Deliverables</h4>
+
<p><em>Including milestones, components, documentation, tests.</em></p>
-<h4 id="scheduling">Scheduling <a class="headerlink" title="Permalink" href="#scheduling">¶</a></h4>
+
+<h4 id="scheduling">Scheduling</h4>
+
<p><em>Not too detailed, but some milestones and checkpoints. Rough estimates per work item (weeks/days). Remember to leave time for slack and bugfixing!</em></p>
-<h4 id="other-commitments">Other commitments <a class="headerlink" title="Permalink" href="#other-commitments">¶</a></h4>
+
+<h4 id="other-commitments">Other commitments</h4>
+
<p><em>Exams, part time work, holidays, lectures.</em></p>
-<h4 id="community-engagement">Community engagement <a class="headerlink" title="Permalink" href="#community-engagement">¶</a></h4>
+
+<h4 id="community-engagement">Community engagement</h4>
+
<p><em>In particular with Apache $Project, including project mailing lists, wikis, issue trackers, test systems.</em></p>
+
<p><em>This should show a rough understanding of working with open source communities. You should be engaged with the rest of the community both before coding start (e.g. to develop this proposal) and during the project.</em></p>
+
<p><em>Include any planned user testing, prototypes, code review.</em></p>
+
<p><a name="GSoC-ContactingtheASF"></a></p>
-<h2 id="contacting-the-asf">Contacting the ASF <a class="headerlink" title="Permalink" href="#contacting-the-asf">¶</a></h2>
+
+<h2 id="contacting-the-asf">Contacting the ASF</h2>
+
<p>The ASF is not just one project, it is a federation of projects, see the
lists at <a href="https://www.apache.org">https://www.apache.org/</a> and <a href="https://incubator.apache.org/">https://incubator.apache.org/</a>. Each of our
projects has its own community of users, contributors and committers. GSoC
students will usually be interacting with just one of these communities.</p>
+
<p>Each of the proposed subjects (link to be provided if we are confirmed as a
mentoring organisation) applies to a single ASF project. You will need to
engage with that project community.</p>
-<p>Please contact <a href="mailto:dev@community.apache.org">dev@community.apache.org</a> if you have questions/difficulties.</p>
+
+<p>Please contact dev@community.apache.org if you have questions/difficulties.</p>
+
<p><a name="GSoC-ASFGSoCTimeline"></a></p>
-<h1 id="asf-gsoc-2023-timeline">ASF GSoC 2023 Timeline <a class="headerlink" title="Permalink" href="#asf-gsoc-2023-timeline">¶</a></h1>
+
+<h1 id="asf-gsoc-2023-timeline">ASF GSoC 2023 Timeline</h1>
+
<p>Below is a timeline of events for The Apache Software Foundation’s
involvement in GSoC. Unless otherwise stated deadlines are 24:00 UTC on the
date indicated.</p>
+
<p><a name="GSoC-StudentApplicationandSelection"></a></p>
-<h2 id="student-application-and-selection">Student Application and Selection <a class="headerlink" title="Permalink" href="#student-application-and-selection">¶</a></h2>
+
+<h2 id="student-application-and-selection">Student Application and Selection</h2>
+
<ul>
<li>2023-02-22: Potential GSoC contributors discuss application ideas with mentoring organizations</li>
<li>2023-03-20: GSoC contributor application period begins</li>
@@ -286,35 +350,51 @@ date indicated.</p>
<li>2023-04-26: Proposal scoring must be completed. Proposals without a score will be rejected, no exceptions.</li>
<li>2023-05-04: Accepted student proposals announced on the Google Summer of Code site.</li>
</ul>
+
<p><a name="GSoC-GSocisunderway"></a></p>
-<h2 id="gsoc-is-underway">GSoC is underway <a class="headerlink" title="Permalink" href="#gsoc-is-underway">¶</a></h2>
+
+<h2 id="gsoc-is-underway">GSoC is underway</h2>
+
<ul>
<li>2023-05-04: Community bonding start</li>
<li>2023-05-28: Community bonding end</li>
<li>2023-05-29: Coding start</li>
<li>2023-07-10: Mentors and GSoC contributors can begin submitting Phase 1 evaluations</li>
-<li>2023-07-13: Phase 1 Evaluation deadline (standard coding period)</li>
+<li>2023-07-13: Phase 1 Evaluation deadline (standard coding period)
+<br /></li>
</ul>
+
<p><a name="GSoC-Winddown"></a></p>
-<h2 id="wind-down">Wind down <a class="headerlink" title="Permalink" href="#wind-down">¶</a></h2>
+
+<h2 id="wind-down">Wind down</h2>
+
<ul>
<li>2023-08-21: GSoC contributors submit their final work product and their final mentor evaluation (standard coding period)</li>
<li>2023-08-28: ASF Mentors evaluations can be submitted</li>
<li>2023-09-03: ASF Mentors final evaluations deadline</li>
<li>2023-09-05: Initial results of Google Summer of Code 2023 announced</li>
</ul>
+
<p><a name="GSoC-Extended"></a></p>
-<h2 id="extended-coding-period">Extended coding period <a class="headerlink" title="Permalink" href="#extended-coding-period">¶</a></h2>
+
+<h2 id="extended-coding-period">Extended coding period</h2>
+
<ul>
<li>2023-09-04: GSoC contributors with extended timelines continue coding</li>
<li>2023-11-05: Final date for all GSoC contributors to submit their final work product and final evaluation</li>
<li>2023-11-12: Final date for mentors to submit evaluations for GSoC contributor projects with extended deadlines</li>
</ul>
+
<p><a name="GSoC-Vouching"></a></p>
-<h1 id="organization-vouching">Organization Vouching <a class="headerlink" title="Permalink" href="#organization-vouching">¶</a></h1>
+
+<h1 id="organization-vouching">Organization Vouching</h1>
+
<p>The ASF currently has no policy establishing the criteria on what basis to vouch for another organization. Until one is established the ASF therefore doesn’t vouch for any organization.</p>
+
<p><a name="GSoC-UsefulLinks"></a></p>
-<h1 id="useful-links">Useful Links <a class="headerlink" title="Permalink" href="#useful-links">¶</a></h1>
+
+<h1 id="useful-links">Useful Links</h1>
+
<ul>
<li><a href="https://summerofcode.withgoogle.com">Summer of Code home</a></li>
<li><a href="https://developers.google.com/open-source/gsoc/timeline">Official Google Summer of Code 2023 Timeline, FAQs</a></li>
diff --git a/content/gsoc/index.xml b/content/gsoc/index.xml
index 0bede6c..242b22d 100644
--- a/content/gsoc/index.xml
+++ b/content/gsoc/index.xml
@@ -1,11 +1,16 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>GSoC on Apache Comdev</title>
<link>https://community.apache.org/gsoc/</link>
<description>Recent content in GSoC on Apache Comdev</description>
<generator>Hugo -- gohugo.io</generator>
- <language>en</language><atom:link href="https://community.apache.org/gsoc/index.xml" rel="self" type="application/rss+xml" />
+ <language>en</language>
+ <lastBuildDate>Wed, 29 Mar 2023 11:49:44 +0200</lastBuildDate>
+
+ <atom:link href="https://community.apache.org/gsoc/index.xml" rel="self" type="application/rss+xml" />
+
+
<item>
<title>Apache in GSoC</title>
<link>https://community.apache.org/gsoc/experiences.html</link>
@@ -14,7 +19,7 @@
<guid>https://community.apache.org/gsoc/experiences.html</guid>
<description>This should be in the GSoC directory
This is a place for collecting information about GSoC activities each year for historical tracking. It was started in 2012 so is missing plenty of detail in the early years. Your help filling it out would be appreciated.
-2018 Overview &para; Students accepted: ? Students who passed final: 29 2017 Overview &para; Students accepted: ? Students who passed final: 27 2016 Overview &para; Students accepted: 49 Students who passed final: 35 2015 Overview &para; Students accepted: 56 Students who passed final: 47 2014 Overview &para; Students accepted: 42 Students who passed final: 35 2013 Overview &para; Students accepted: 51 Students who passed final: 44 2012 Overview &para; Student [...]
+2018 Overview Students accepted: ? Students who passed final: 29 2017 Overview Students accepted: ? Students who passed final: 27 2016 Overview Students accepted: 49 Students who passed final: 35 2015 Overview Students accepted: 56 Students who passed final: 47 2014 Overview Students accepted: 42 Students who passed final: 35 2013 Overview Students accepted: 51 Students who passed final: 44 2012 Overview Students accepted: 41 Students who passed midterm: 40 26 projects mento [...]
</item>
<item>
@@ -25,17 +30,7 @@ This is a place for collecting information about GSoC activities each year for h
<guid>https://community.apache.org/gsoc/gsoc-admin-tasks.html</guid>
<description>A comprehensive guide to being a GSoC admin for the ASF
List of duties:
-Make sure the ASF has an extensive list of project ideas ready shortly after Google announces the program (around the end of January). Projects must create Jira issues for their ideas and label them with gsoc&lt;year&gt;; and mentor. If a project doesn&rsquo;t use Jira, have them create the ideas in the GSOC Jira project. Create a Jira filter for these ideas to use in the application (see next).</description>
- </item>
-
- <item>
- <title>guide to being a mentor</title>
- <link>https://community.apache.org/gsoc/guide-to-being-a-mentor.html</link>
- <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-
- <guid>https://community.apache.org/gsoc/guide-to-being-a-mentor.html</guid>
- <description>Submitting ideas to the mentoring programme &para; We invite all ASF projects to submit their ideas for consideration in the ASF mentoring programme. Any Apache member and experienced committers can submit ideas via Jira (if your project does not use Jira you can use the Comdev Issue Tracker For GSoC Tasks. We are looking for as many interesting projects as we can come up with.
-Important Steps &para; Add an issue to Jira (if your project does not use Jira you can use the Comdev GSoC Issue Tracker For GSoC Tasks Add sub-tasks if necessary Label the main issue with &ldquo;mentor&rdquo; (these will show up at the ASF-wide list of issues) Label the main issue with &ldquo;gsoc2023&rdquo; if appropriate (these will show up at GSoC 2023 Ideas) Size of project Starting this year there are 2 types of projects available.</description>
+ Make sure the ASF has an extensive list of project ideas ready shortly after Google announces the program (around the end of January). Projects must create Jira issues for their ideas and label them with gsoc&lt;year&gt;; and mentor. If a project doesn&rsquo;t use Jira, have them create the ideas in the GSOC Jira project. Create a Jira filter for these ideas to use in the application (see next).</description>
</item>
<item>
@@ -56,8 +51,19 @@ Remember, mentoring is all about the mentee and open source as a whole. It is no
<guid>https://community.apache.org/gsoc/use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.html</guid>
<description>If your project does not use the ASF Jira for issue tracking, you can use the ComDev GSoC Jira project to record your GSoC tasks.
-Add tasks to the GSOC project Ensure you add the labels gsoc2023, mentor and _YOUR_PROJECT_NAME_ Your issues will appear in the list of projects We use the label _YOUR_PROJECT_NAME_ to map COMDEV issues to the real project when we create the ideas list Please contact dev@community.</description>
+ Add tasks to the GSOC project Ensure you add the labels gsoc2023, mentor and _YOUR_PROJECT_NAME_ Your issues will appear in the list of projects We use the label _YOUR_PROJECT_NAME_ to map COMDEV issues to the real project when we create the ideas list Please contact dev@community.</description>
+ </item>
+
+ <item>
+ <title>guide to being a mentor</title>
+ <link>https://community.apache.org/gsoc/guide-to-being-a-mentor.html</link>
+ <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+
+ <guid>https://community.apache.org/gsoc/guide-to-being-a-mentor.html</guid>
+ <description>Submitting ideas to the mentoring programme We invite all ASF projects to submit their ideas for consideration in the ASF mentoring programme. Any Apache member and experienced committers can submit ideas via Jira (if your project does not use Jira you can use the Comdev Issue Tracker For GSoC Tasks. We are looking for as many interesting projects as we can come up with.
+
+Important Steps Add an issue to Jira (if your project does not use Jira you can use the Comdev GSoC Issue Tracker For GSoC Tasks Add sub-tasks if necessary Label the main issue with &ldquo;mentor&rdquo; (these will show up at the ASF-wide list of issues) Label the main issue with &ldquo;gsoc2023&rdquo; if appropriate (these will show up at GSoC 2023 Ideas) Size of project Starting this year there are 2 types of projects available.</description>
</item>
</channel>
-</rss>
+</rss>
\ No newline at end of file
diff --git a/content/gsoc/mentee-ranking-process.html b/content/gsoc/mentee-ranking-process.html
index eff2be1..59e0633 100644
--- a/content/gsoc/mentee-ranking-process.html
+++ b/content/gsoc/mentee-ranking-process.html
@@ -11,9 +11,23 @@
The ranking process makes sure the most promising applicants get a mentor with an ASF project. The goal is not to identify the “best” projects for the ASF, but the best mentees who have applied to the ASF.
Remember, mentoring is all about the mentee and open source as a whole. It is not about the mentors or their projects." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/gsoc/mentee-ranking-process.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="gsoc" />
+<meta property="og:url" content="https://community.apache.org/gsoc/mentee-ranking-process.html" />
+
+
+
+
+<meta property="article:modified_time" content="2023-03-21T10:25:42+07:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2023-03-21T10:25:42+07:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Mentee Ranking Process</title>
@@ -189,97 +203,112 @@ Remember, mentoring is all about the mentee and open source as a whole. It is no
<hr>
- <p>This page describes the ranking process The Apache Software
+
+
+<p>This page describes the ranking process The Apache Software
Foundation uses to evaluate mentee proposals.</p>
+
<p>The ranking process makes sure the most promising
applicants get a mentor with an ASF project. The goal is <em>not</em> to
identify the “best” projects for the ASF, but the best mentees who have
applied to the ASF.</p>
+
<p>Remember, mentoring is all about the mentee and open source as a whole. It
is not about the mentors or their projects.</p>
+
<p>Any ASF committer can help with the ranking: all you need to do is register
as a potential mentor (you don’t actually have to <em>become</em> a mentor).</p>
+
<p>The instructions below described ranking proposals using the Google Summer
of Code application.</p>
+
<p><a name="MenteeRankingProcess-ScoringSystem"></a></p>
-<h1 id="scoring-system">Scoring System <a class="headerlink" title="Permalink" href="#scoring-system">¶</a></h1>
+
+<h1 id="scoring-system">Scoring System</h1>
+
<p>We rank projects using this scoring system:</p>
-<h2 id="pre-selection-phase--a-mentor-does-this-when-accepting-to-be-mentor-of-a-given-proposal"><em>Pre-Selection Phase</em> : a mentor does this when accepting to be mentor of a given proposal <a class="headerlink" title="Permalink" href="#pre-selection-phase--a-mentor-does-this-when-accepting-to-be-mentor-of-a-given-proposal">¶</a></h2>
+
+<h2 id="pre-selection-phase-a-mentor-does-this-when-accepting-to-be-mentor-of-a-given-proposal"><em>Pre-Selection Phase</em> : a mentor does this when accepting to be mentor of a given proposal</h2>
+
<ul>
<li>if the proposal is for a project you will be mentoring and you feel the
proposal looks good enough for you to commit your time to it, click the
“I am willing to Mentor” button in Melange (the software that administers the Google Summer of Code).</li>
</ul>
+
<p>Please only offer to mentor a single project unless you have discussed why you should mentor more than one on
-<a href="mailto:mentors@community.apache.org">mentors@community.apache.org</a> first. We encourage multiple mentors per project, though.</p>
+mentors@community.apache.org first. We encourage multiple mentors per project, though.</p>
+
<p>Other community members are free to comment on proposals as they see fit.
In the re-evaluation phase (see below) admins use
comments provided by mentors and community members.</p>
+
<p>##<em>Selection Phase</em> : a mentor does this during ranking time</p>
+
<p>In this phase mentors evaluate each proposal. We do all scoring in the Google Docs spreadsheet shared on
-<a href="mailto:mentors@community.apache.org">mentors@community.apache.org</a>. Add an explanation to every score, using the criteria below, to help admins in the later stages of evaluation.
+mentors@community.apache.org. Add an explanation to every score, using the criteria below, to help admins in the later stages of evaluation.
DO NOT ADD SCORES IN MELANGE! Use integer numbers only!</p>
+
<p><em>Please do not add scores outside these criteria.</em></p>
-<p>Address any questions to the admins on <a href="mailto:mentors@community.apache.org">mentors@community.apache.org</a></p>
+
+<p>Address any questions to the admins on mentors@community.apache.org</p>
+
<ul>
-<li>
-<p>Did the student demonstrate that they have the required skills to start
+<li><p>Did the student demonstrate that they have the required skills to start
the project and learn what’s needed along the way? And how happy are we
-with the results? (0-4 points)</p>
-</li>
-<li>
-<p>How do we rate the quality of the student’s proposal, in terms of
+with the results? (0-4 points)</p></li>
+
+<li><p>How do we rate the quality of the student’s proposal, in terms of
technical relevance, completeness, awareness of issues, and realistic planning
-(less copy and paste)? (0-4 points)</p>
-</li>
-<li>
-<p>How does the mentor rate the student’s chances of success, based on an
+(less copy and paste)? (0-4 points)</p></li>
+
+<li><p>How does the mentor rate the student’s chances of success, based on an
in-person (face-to-face, video, audio, IRC, email) interview? (0-3 points, or
-0-1 if email interview only)</p>
-</li>
-<li>
-<p>How do we rate the originality of the student’s contributions to the
+0-1 if email interview only)</p></li>
+
+<li><p>How do we rate the originality of the student’s contributions to the
proposal? (0-2 points: 0 if mentor provides proposal, 1 if student builds
-proposal from suggested ideas, 2 if proposal is original idea from student)</p>
-</li>
-<li>
-<p>Did the student work with the project community, on our public mailing lists,
-to create the proposal? (0-2 points)</p>
-</li>
-<li>
-<p>Did the student explicitly indicate how much time they are going to dedicate
+proposal from suggested ideas, 2 if proposal is original idea from student)</p></li>
+
+<li><p>Did the student work with the project community, on our public mailing lists,
+to create the proposal? (0-2 points)</p></li>
+
+<li><p>Did the student explicitly indicate how much time they are going to dedicate
to GSoC for the project’s duration, and mention any other committments that
could conflict with the project (holidays, course work, etc.)? Are we happy with
-this commitment (it should be their major occupation during the summer)? (0-2 points)</p>
-</li>
-<li>
-<p>Did the student respond quickly to mentor inquiries? (0-2 points)</p>
-</li>
-<li>
-<p>Are you or your student affiliated in any way (e.g. share(d) the same employer or will do so in the foreseeable future, are
-you their adviser at university, personal relationships, etc.)? (yes/no)</p>
-</li>
+this commitment (it should be their major occupation during the summer)? (0-2 points)</p></li>
+
+<li><p>Did the student respond quickly to mentor inquiries? (0-2 points)</p></li>
+
+<li><p>Are you or your student affiliated in any way (e.g. share(d) the same employer or will do so in the foreseeable future, are
+you their adviser at university, personal relationships, etc.)? (yes/no)</p></li>
</ul>
+
<p>Other community members are free to comment on proposals inside Melange as they see fit.
However, DO NOT ADD A SCORE TO THE PROPOSAL. In the re-evaluation phase (see below) admins use
comments provided by mentors and community members.</p>
+
<p>At the end of the selection phase proposals to be considered for support
will have a score of between 0 and +19, and should only have scores from
the assigned mentor and admins (at this stage admin scores are only
corrections). The admins check in periodically during the selection phase
to look for problems by scanning the scores (i.e. anything
over +19 has an error).</p>
+
<p>At the end of this selection phase we know the minimum score a proposal
must have in order to be selected (i.e. if we have 30 slots, projects with
a score at or above the project ranked 30th will go forward to the next
phase). Before progressing to the next phase, admins read all proposals
above or near the minimum score and ensure that there are no errors
in this phase of ranking.</p>
-<h2 id="re-evaluation--admins-do-this-during-or-after-selection-phase"><em>Re-Evaluation</em> : admins do this during or after selection phase <a class="headerlink" title="Permalink" href="#re-evaluation--admins-do-this-during-or-after-selection-phase">¶</a></h2>
+
+<h2 id="re-evaluation-admins-do-this-during-or-after-selection-phase"><em>Re-Evaluation</em> : admins do this during or after selection phase</h2>
+
<p>In this phase admins evaluate all proposals above the required score and
those that are just below it. We check those just below the required score
to ensure that the scores have been equally assigned across all proposals
(some mentors are more generous than others).</p>
+
<ul>
<li>Has the mentor fully engaged with the student during the writing of the
proposal? (0-4 points)</li>
@@ -290,14 +319,21 @@ community members to mark a proposal up or down (-4 to +4).</li>
<li>Admin discretionary points (-10 to +10 points, only used to break
“deadlocks” across the cut-off point, see below).</li>
</ul>
+
<p>The admins transfer the scores to Melange.</p>
+
<p>At the end of this phase there is a short window for the community to
verify the admins’ work before the final selection is made.</p>
+
<p><a name="MenteeRankingProcess-Whatarewelookingforinagoodproposal?"></a></p>
-<h1 id="what-are-we-looking-for-in-a-good-proposal">What are we looking for in a good proposal? <a class="headerlink" title="Permalink" href="#what-are-we-looking-for-in-a-good-proposal">¶</a></h1>
+
+<h1 id="what-are-we-looking-for-in-a-good-proposal">What are we looking for in a good proposal?</h1>
+
<p>In general we much prefer new mentees to repeat mentees. The goal is to
enable new people to learn about open source software development.</p>
+
<p>In past years we have seen some consistent patterns in high-quality proposals:</p>
+
<ul>
<li>Detailed proposal with realistic and measurable milestones</li>
<li>Engagement with the project communication during proposal writing</li>
@@ -306,65 +342,96 @@ requests for more info)</li>
<li>Acknowledgment of weaknesses in existing skill set and a plan for
addressing those weaknesses</li>
</ul>
+
<p><a name="MenteeRankingProcess-Warningsignsinabadproposal"></a></p>
-<h1 id="warning-signs-in-a-bad-proposal">Warning signs in a bad proposal <a class="headerlink" title="Permalink" href="#warning-signs-in-a-bad-proposal">¶</a></h1>
+
+<h1 id="warning-signs-in-a-bad-proposal">Warning signs in a bad proposal</h1>
+
<ul>
<li>No engagement with project community</li>
<li>Lack of understanding of what open source is and how it is developed</li>
<li>Indication of external commitments (exams, job etc.)</li>
<li>Previous failures within the mentor programme</li>
</ul>
+
<p><a name="MenteeRankingProcess-Whathappensnext?"></a></p>
-<h1 id="what-happens-next">What happens next? <a class="headerlink" title="Permalink" href="#what-happens-next">¶</a></h1>
+
+<h1 id="what-happens-next">What happens next?</h1>
+
<p>Towards the end of the ranking period Google announces how many slots
the ASF has. Shortly after that we ask ASF committers to
stop ranking, and the ASF GSoC admins adjust the rankings to
ensure that the right number of projects are ranked above the cut-off line.</p>
+
<p>In this last stage we avoid adjusting community rankings; however, in past
years there has been a cluster of students with equal rankings around the
cut-off point. In this case the admins cast a final vote on those
projects to ensure that Google can assign awards as appropriate.</p>
+
<p>For example, imagine that 7 is the number of points that causes the
clustering, and we have the following projects ranked at 7:</p>
-<h1 id="a">A <a class="headerlink" title="Permalink" href="#a">¶</a></h1>
-<h1 id="b">B <a class="headerlink" title="Permalink" href="#b">¶</a></h1>
-<h1 id="c">C <a class="headerlink" title="Permalink" href="#c">¶</a></h1>
-<h1 id="d">D <a class="headerlink" title="Permalink" href="#d">¶</a></h1>
-<h1 id="e">E <a class="headerlink" title="Permalink" href="#e">¶</a></h1>
+
+<h1 id="a">A</h1>
+
+<h1 id="b">B</h1>
+
+<h1 id="c">C</h1>
+
+<h1 id="d">D</h1>
+
+<h1 id="e">E</h1>
+
<p>Now imagine the cut-off point for selection is currently at the third
-position (C).</p>
+position ©.</p>
+
<p>The admins need to look at these projects and ensure they are ordered in the
webapp to make the most appropriate appear at the top of the list. This
ensures that they are most likely to receive a slot. So we may end up
with:</p>
-<h1 id="b-1">B <a class="headerlink" title="Permalink" href="#b-1">¶</a></h1>
-<h1 id="c-1">C <a class="headerlink" title="Permalink" href="#c-1">¶</a></h1>
-<h1 id="a-1">A <a class="headerlink" title="Permalink" href="#a-1">¶</a></h1>
-<h1 id="e-1">E <a class="headerlink" title="Permalink" href="#e-1">¶</a></h1>
-<h1 id="d-1">D <a class="headerlink" title="Permalink" href="#d-1">¶</a></h1>
+
+<h1 id="b-1">B</h1>
+
+<h1 id="c-1">C</h1>
+
+<h1 id="a-1">A</h1>
+
+<h1 id="e-1">E</h1>
+
+<h1 id="d-1">D</h1>
+
<p>Unfortunately this process needs to happen very quickly and there is no
time for community discussion around these points. Therefore it is
important that mentors and mentees provide as much information in the
previous ranking stages as possible.</p>
+
<p>The problem becomes a little more complicated when we remember that the
cut-off point may move as well, so Google may give us one extra slot. So we
need to ensure that all rank-7 projects are correctly ordered, not just the
best.</p>
+
<p><a name="MenteeRankingProcess-Theprocessofbreakingclusters"></a></p>
-<h2 id="the-process-of-breaking-clusters">The process of breaking clusters <a class="headerlink" title="Permalink" href="#the-process-of-breaking-clusters">¶</a></h2>
+
+<h2 id="the-process-of-breaking-clusters">The process of breaking clusters</h2>
+
<p>Admins work through all applications, adding a +8 to all those ranked above
the cut off score. This has the effect of increasing the “space” we have to
work with in re-ranking the clustered projects.</p>
+
<p>Admins then work through all the clustered applications, adding scores as
defined above (with a comment justifying the ranking).</p>
+
<p>If there is still a cluster of projects around the cut-off point, the
lead admin looks at the mentors and projects involved. If a project/mentor
already has a higher scored application, the lead admin reduces the
score for this one (i.e. to try to spread the love).</p>
+
<p>It’s not practical to ask the community to comment at this point as we are
on a tight deadline. We ask that the community trust the assigned admins.</p>
+
<p><a name="MenteeRankingProcess-Resolveconflicts"></a></p>
-<h1 id="resolve-conflicts">Resolve conflicts <a class="headerlink" title="Permalink" href="#resolve-conflicts">¶</a></h1>
+
+<h1 id="resolve-conflicts">Resolve conflicts</h1>
+
<p>Inevitably there will be one or two students who have been accepted in
multiple organizations. We resolve these conflicts during an IRC meeting with Google
admins during the final hours of ranking. In these cases the admins
diff --git a/content/gsoc/use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.html b/content/gsoc/use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.html
index a8e10f0..091bba5 100644
--- a/content/gsoc/use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.html
+++ b/content/gsoc/use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.html
@@ -8,11 +8,25 @@
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="Use the Comdev Issue Tracker For GSoC Tasks" />
<meta property="og:description" content="If your project does not use the ASF Jira for issue tracking, you can use the ComDev GSoC Jira project to record your GSoC tasks.
-Add tasks to the GSOC project Ensure you add the labels gsoc2023, mentor and _YOUR_PROJECT_NAME_ Your issues will appear in the list of projects We use the label _YOUR_PROJECT_NAME_ to map COMDEV issues to the real project when we create the ideas list Please contact dev@community." />
+ Add tasks to the GSOC project Ensure you add the labels gsoc2023, mentor and _YOUR_PROJECT_NAME_ Your issues will appear in the list of projects We use the label _YOUR_PROJECT_NAME_ to map COMDEV issues to the real project when we create the ideas list Please contact dev@community." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/gsoc/use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="gsoc" />
+<meta property="og:url" content="https://community.apache.org/gsoc/use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.html" />
+
+
+
+
+<meta property="article:modified_time" content="2023-03-21T13:35:34+05:30"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2023-03-21T13:35:34+05:30" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Use the Comdev Issue Tracker For GSoC Tasks</title>
@@ -190,13 +204,16 @@ Add tasks to the GSOC project Ensure you add the labels gsoc2023, mentor and _YO
<p>If your project does not use the ASF Jira for issue tracking, you can use
the ComDev GSoC Jira project to record your GSoC tasks.</p>
+
<ul>
<li>Add tasks to the <a href="https://issues.apache.org/jira/browse/GSOC">GSOC project</a></li>
<li>Ensure you add the labels <code>gsoc2023</code>, <code>mentor</code> and <code>_YOUR_PROJECT_NAME_</code></li>
<li>Your issues will appear in the <a href="https://s.apache.org/gsoc2023ideas">list of projects</a></li>
<li>We use the label <code>_YOUR_PROJECT_NAME_</code> to map COMDEV issues to the real project when we create the ideas list</li>
</ul>
-<p>Please contact <a href="mailto:dev@community.apache.org">dev@community.apache.org</a> if you have questions/difficulties.</p>
+
+<p>Please contact dev@community.apache.org if you have questions/difficulties.</p>
+
<p>You can then link to the task tickets from your own site and access XML, RSS feeds.</p>
diff --git a/content/history.html b/content/history.html
index 896146c..7b0d410 100644
--- a/content/history.html
+++ b/content/history.html
@@ -9,7 +9,21 @@
<meta property="og:title" content="Histories" />
<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/history.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+<meta property="og:url" content="https://community.apache.org/history.html" />
+
+
+
+
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
<title>Apache Community Development - Histories</title>
diff --git a/content/history/boardresolution.html b/content/history/boardresolution.html
index 42c9fdc..81c0bbe 100644
--- a/content/history/boardresolution.html
+++ b/content/history/boardresolution.html
@@ -8,11 +8,25 @@
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="ComDevBoardResolution" />
<meta property="og:description" content="The Apache Community Development Project was created in November 2009.
-Board Resolution Creating the Apache Community Development Project Establish the Apache Community Development Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with coordinating community development efforts. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Community Development Project& [...]
+Board Resolution Creating the Apache Community Development Project Establish the Apache Community Development Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with coordinating community development efforts. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Community Development Projec [...]
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/history/boardresolution.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="history" />
+<meta property="og:url" content="https://community.apache.org/history/boardresolution.html" />
+
+
+
+
+<meta property="article:modified_time" content="2023-03-27T22:49:45+01:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2023-03-27T22:49:45+01:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - ComDevBoardResolution</title>
@@ -189,11 +203,14 @@ Board Resolution Creating the Apache Community Development Project Establish the
<hr>
<p>The Apache Community Development Project was created in November 2009.</p>
+
<div class="code panel" style="border-style: solid;border-width: 1px;">
<div class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;">
<b>Board Resolution Creating the Apache Community Development Project</b>
</div>
- <div class="codeContent panelContent">
+
+<p><div class="codeContent panelContent"></p>
+
<pre><code> Establish the Apache Community Development Project
WHEREAS, the Board of Directors deems it to be in the best
@@ -249,8 +266,10 @@ Board Resolution Creating the Apache Community Development Project Establish the
Furthermore, the board requested that this PMC take over the
stewardship of the community@ and women@ mailing lists.
</code></pre>
- </div>
-</div>
+
+<p></div>
+</div></p>
+
</div>
</main>
diff --git a/content/history/index.xml b/content/history/index.xml
index 69f34e9..1272bfa 100644
--- a/content/history/index.xml
+++ b/content/history/index.xml
@@ -1,11 +1,15 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Histories on Apache Comdev</title>
<link>https://community.apache.org/history.html</link>
<description>Recent content in Histories on Apache Comdev</description>
<generator>Hugo -- gohugo.io</generator>
- <language>en</language><atom:link href="https://community.apache.org/history/index.xml" rel="self" type="application/rss+xml" />
+ <language>en</language>
+
+ <atom:link href="https://community.apache.org/history/index.xml" rel="self" type="application/rss+xml" />
+
+
<item>
<title>ComDevBoardResolution</title>
<link>https://community.apache.org/history/boardresolution.html</link>
@@ -13,7 +17,7 @@
<guid>https://community.apache.org/history/boardresolution.html</guid>
<description>The Apache Community Development Project was created in November 2009.
-Board Resolution Creating the Apache Community Development Project Establish the Apache Community Development Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with coordinating community development efforts. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the &quot;Apache Community Development Proj [...]
+Board Resolution Creating the Apache Community Development Project Establish the Apache Community Development Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with coordinating community development efforts. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the &quot;Apache Community Development Pr [...]
</item>
<item>
@@ -23,9 +27,9 @@ Board Resolution Creating the Apache Community Development Project Establish the
<guid>https://community.apache.org/history/mentoringprogramme-icfoss-pilot.html</guid>
<description>Note that this information is about a pilot program that happened back in 2013.
-The ASF has been participating in many mentoring initiatives, and it&rsquo;s now partnering in a pilot project with India ICFOSS to provide mentoring for undergraduate and graduate students that have interest in learning how to participate in open source communities at ASF.
+ The ASF has been participating in many mentoring initiatives, and it&rsquo;s now partnering in a pilot project with India ICFOSS to provide mentoring for undergraduate and graduate students that have interest in learning how to participate in open source communities at ASF.
The mentoring programme is not here to teach you to write documentation or code.</description>
</item>
</channel>
-</rss>
+</rss>
\ No newline at end of file
diff --git a/content/history/mentoringprogramme-icfoss-pilot.html b/content/history/mentoringprogramme-icfoss-pilot.html
index c58c0d5..05dac3d 100644
--- a/content/history/mentoringprogramme-icfoss-pilot.html
+++ b/content/history/mentoringprogramme-icfoss-pilot.html
@@ -8,12 +8,26 @@
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="Pilot Mentoring Programme with India ICFOSS" />
<meta property="og:description" content="Note that this information is about a pilot program that happened back in 2013.
-The ASF has been participating in many mentoring initiatives, and it’s now partnering in a pilot project with India ICFOSS to provide mentoring for undergraduate and graduate students that have interest in learning how to participate in open source communities at ASF.
+ The ASF has been participating in many mentoring initiatives, and it’s now partnering in a pilot project with India ICFOSS to provide mentoring for undergraduate and graduate students that have interest in learning how to participate in open source communities at ASF.
The mentoring programme is not here to teach you to write documentation or code." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/history/mentoringprogramme-icfoss-pilot.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="history" />
+<meta property="og:url" content="https://community.apache.org/history/mentoringprogramme-icfoss-pilot.html" />
+
+
+
+
+<meta property="article:modified_time" content="2023-03-17T12:26:02-04:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2023-03-17T12:26:02-04:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Pilot Mentoring Programme with India ICFOSS</title>
@@ -189,14 +203,18 @@ The mentoring programme is not here to teach you to write documentation or code.
<hr>
- <blockquote>
+
+
+<blockquote>
<p>Note that this information is about a pilot program that
happened back in 2013.</p>
</blockquote>
+
<p>The ASF has been participating in many mentoring initiatives, and it’s now
partnering in a pilot project with India ICFOSS to provide mentoring for
undergraduate and graduate students that have interest in learning how
to participate in open source communities at ASF.</p>
+
<p>The mentoring programme is not here to teach you to write documentation or
code. It is here to help you understand how to make a valuable contribution
to an Apache project. You can expect to be guided through our contribution
@@ -205,91 +223,121 @@ your chosen project. You cannot expect your mentor to be a “teacher”
will provide enough information for you to progress within the project. You
need to bring the confidence to take their guidance and discover the detail
for yourself.</p>
+
<p><a name="Schedule"></a></p>
-<h2 id="proposed-schedule">Proposed Schedule <a class="headerlink" title="Permalink" href="#proposed-schedule">¶</a></h2>
+
+<h2 id="proposed-schedule">Proposed Schedule</h2>
+
<table>
<thead>
<tr>
-<th style="text-align:left">Date</th>
-<th style="text-align:left">Description</th>
+<th align="left">Date</th>
+<th align="left">Description</th>
</tr>
</thead>
+
<tbody>
<tr>
-<td style="text-align:left">June 20</td>
-<td style="text-align:left">Local Workshop at ICFOSS headquarters in Kerala - India</td>
+<td align="left">June 20</td>
+<td align="left">Local Workshop at ICFOSS headquarters in Kerala - India</td>
</tr>
+
<tr>
-<td style="text-align:left">June 24 - July 12</td>
-<td style="text-align:left">Would-be student participants discuss application ideas with ASF projects</td>
+<td align="left">June 24 - July 12</td>
+<td align="left">Would-be student participants discuss application ideas with ASF projects</td>
</tr>
+
<tr>
-<td style="text-align:left">July 15</td>
-<td style="text-align:left">Students project proposal submission opens</td>
+<td align="left">July 15</td>
+<td align="left">Students project proposal submission opens</td>
</tr>
+
<tr>
-<td style="text-align:left">July 19</td>
-<td style="text-align:left">Students project proposal submission deadline</td>
+<td align="left">July 19</td>
+<td align="left">Students project proposal submission deadline</td>
</tr>
+
<tr>
-<td style="text-align:left">July 22 - August 02</td>
-<td style="text-align:left">Mentors review and rank students project proposals</td>
+<td align="left">July 22 - August 02</td>
+<td align="left">Mentors review and rank students project proposals</td>
</tr>
+
<tr>
-<td style="text-align:left">August 05</td>
-<td style="text-align:left">Accepted student proposals announced</td>
+<td align="left">August 05</td>
+<td align="left">Accepted student proposals announced</td>
</tr>
+
<tr>
-<td style="text-align:left">August 05</td>
-<td style="text-align:left">Students start coding their project proposal with Mentor guidance</td>
+<td align="left">August 05</td>
+<td align="left">Students start coding their project proposal with Mentor guidance</td>
</tr>
+
<tr>
-<td style="text-align:left">September 09</td>
-<td style="text-align:left">Mentors and students can begin submitting mid-term evaluations</td>
+<td align="left">September 09</td>
+<td align="left">Mentors and students can begin submitting mid-term evaluations</td>
</tr>
+
<tr>
-<td style="text-align:left">September 13</td>
-<td style="text-align:left">Mid-term evaluation deadline</td>
+<td align="left">September 13</td>
+<td align="left">Mid-term evaluation deadline</td>
</tr>
+
<tr>
-<td style="text-align:left">October 21</td>
-<td style="text-align:left">Suggested ‘DCUT’ date, where students should then scrub code, enhance documentation, etc</td>
+<td align="left">October 21</td>
+<td align="left">Suggested ‘DCUT’ date, where students should then scrub code, enhance documentation, etc</td>
</tr>
+
<tr>
-<td style="text-align:left">October 28</td>
-<td style="text-align:left">Mentors and students can begin submitting final evaluations</td>
+<td align="left">October 28</td>
+<td align="left">Mentors and students can begin submitting final evaluations</td>
</tr>
+
<tr>
-<td style="text-align:left">November 1</td>
-<td style="text-align:left">Final evaluation deadline</td>
+<td align="left">November 1</td>
+<td align="left">Final evaluation deadline</td>
</tr>
</tbody>
</table>
+
<p><a name="MentoringProgramme-WorkshopMaterials"></a></p>
-<h2 id="workshop-materials">Workshop Materials <a class="headerlink" title="Permalink" href="#workshop-materials">¶</a></h2>
+
+<h2 id="workshop-materials">Workshop Materials</h2>
+
<p>The slides used for the local workshop at ICFOSS headquarters in Kerala are available for <a href="https://people.apache.org/~lresende/presentations/asf-icfoss-mentoring.pdf">download</a>.</p>
+
<p><a name="MentoringProgramme-ProjectIdeas"></a></p>
-<h2 id="project-ideas">Project Ideas <a class="headerlink" title="Permalink" href="#project-ideas">¶</a></h2>
+
+<h2 id="project-ideas">Project Ideas</h2>
+
<p>Project ideas are jira created by possible mentors and can be viewed at:</p>
+
<ul>
<li><a href="https://s.apache.org/icfoss2013ideas">2013 ICFOSS Programme Project Ideas</a></li>
<li><a href="https://s.apache.org/gsoc2013ideas">2013 GSoC Project Ideas</a></li>
</ul>
+
<p><a name="MentoringProgramme-ApplyingfortheMentorProgramme"></a></p>
-<h2 id="applying-for-the-mentor-programme">Applying for the Mentor Programme <a class="headerlink" title="Permalink" href="#applying-for-the-mentor-programme">¶</a></h2>
+
+<h2 id="applying-for-the-mentor-programme">Applying for the Mentor Programme</h2>
+
<p>Students can propose their own project ideas, or select one from the ASF provided list. After selecting the project ideas. students should create a project proposal following guidance from the <strong>mentor</strong> and the <strong>project community</strong>.</p>
+
<p>The project proposal should have, at minimum :</p>
+
<ul>
<li><strong>WHAT</strong> Detailed description of the what is being implemented as part of the project.</li>
<li><strong>HOW</strong> How the project is going to be implemented. Here you would describe your approach towards solving the problem, as well as technical details (which shows to the mentor that you have a clear idea of what needs to be implemented). High level system design diagrams is a plus.</li>
<li><strong>WHEN</strong> A detailed schedule of what tasks you are going to implement by when.</li>
</ul>
+
<p>See the proposals examples below as guidance:</p>
+
<ul>
<li><a href="https://cwiki.apache.org/confluence/display/TUSCANYWIKI/Searching+artifacts+across+SCA+domain">Searching artifact across SCA Domains</a></li>
<li><a href="http://students.fim.uni-passau.de/~grosser/gcc_soc/">GIMPLE to GRAPHITE transformation</a></li>
<li><a href="http://opendz.org/users/tixxdz/gsoc/gsoc_2010_proposal_nmap_scripting_engine_short_version.pdf">Nmap Scripting Engine – Infrastructure Manager</a></li>
</ul>
+
<p>Note that the proposals below are just examples from previous GSoC programs, and each one have different strengths. But you should always follow your mentors advice, as he is the one that is going to be judging your proposals.</p>
diff --git a/content/index.html b/content/index.html
index 6db8483..4024bec 100644
--- a/content/index.html
+++ b/content/index.html
@@ -3,14 +3,28 @@
<html lang="en">
<head>
- <meta name="generator" content="Hugo 0.111.3">
+ <meta name="generator" content="Hugo 0.40.1" />
<meta name="description" content="Apache Community Development"/>
<meta name="keywords" content="apache, apache community, community development, opensource"/>
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="Apache Community Development - Welcome" />
<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+<meta property="og:url" content="https://community.apache.org/" />
+
+
+
+<meta property="og:updated_time" content="2023-03-29T19:12:27+01:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
<title>Apache Community Development - Apache Community Development - Welcome</title>
@@ -177,87 +191,150 @@
<hr>
- <div class="jumbotron">
+ <p><link href="/_pagefind/pagefind-ui.css" rel="stylesheet">
+<script src="/_pagefind/pagefind-ui.js" type="text/javascript"></script>
+<div id="search"></div>
+<script>
+ window.addEventListener(‘DOMContentLoaded’, (event) => {
+ new PagefindUI({ element: “#search” });
+ });
+</script></p>
+
+<div class="jumbotron">
<a href="https://www.apache.org/events/current-event.html"><img src="https://www.apache.org/events/current-event-125x125.png" style="float: right;"/></a>
-<h2 id="apache-community-development">Apache Community Development! <a class="headerlink" title="Permalink" href="#apache-community-development">¶</a></h2>
-<p>Mission: The Community Development project creates and provides tools,
+
+## Apache Community Development!
+
+Mission: The Community Development project creates and provides tools,
processes, and advice to help open-source projects improve their own
community health. We are primarily focused on Apache Software Foundation (ASF)
projects; however, because we believe that the Apache Way is the
best way to manage a software project, we strive also to make these
-artifacts releasable to the open-source community as a whole.</p>
-<p>Here, we focus on the common processes and policies
+artifacts releasable to the open-source community as a whole.
+
+Here, we focus on the common processes and policies
(called The Apache Way) found in most ASF projects. Our goal is to help you
<em>understand how the ASF works</em> and give you the confidence to participate
-in the specific Apache projects that interest you.</p>
+in the specific Apache projects that interest you.
+
</div>
+
<p><a name="Index-Startingpoints"></a></p>
+
<!-- Row 1 -->
+
<div class="row">
<div class="col-md-4">
-<h4 id="newcomers-to-the-asf">Newcomers to the ASF <a class="headerlink" title="Permalink" href="#newcomers-to-the-asf">¶</a></h4>
-<p>If you are new to open source, our <a href="newcomers/index.html"><b>newcomers section</b></a> explains basic concepts, first steps to get started, and where to ask for help.</p>
-<p>To get our software, see our <a href="https://projects.apache.org/projects.html?category" target="_blank">categorized listing of all Apache projects</a>, which are <a href="https://www.apache.org/free/"><b>always free</b> to download and use</a>.</p>
-<p>The ASF is a large organization made up of many separate projects. Each project community may have its own ways of working, while still following the basic Apache Way process.</p>
+
+#### Newcomers to the ASF
+
+If you are new to open source, our <a href="newcomers/index.html"><b>newcomers section</b></a> explains basic concepts, first steps to get started, and where to ask for help.
+
+To get our software, see our <a href="https://projects.apache.org/projects.html?category" target="_blank">categorized listing of all Apache projects</a>, which are <a href="https://www.apache.org/free/"><b>always free</b> to download and use</a>.
+
+The ASF is a large organization made up of many separate projects. Each project community may have its own ways of working, while still following the basic Apache Way process.
+
</div>
<div class="col-md-4">
-<h4 id="events">Events <a class="headerlink" title="Permalink" href="#events">¶</a></h4>
-<p>Producers should read our <a href="https://www.apache.org/foundation/marks/events">Event Branding Policy</a> for ticketed events, and we have some <a href="events/small-events.html">tips for organizing small community events</a> about Apache projects.</p>
-<p>The <a href="https://events.apache.org/event/calendar.html">event calendar</a> lists approved Apache-related events, including Community Over Code (formerly ApacheCon) and project summits.</p>
+
+#### Events
+
+Producers should read our <a href="https://www.apache.org/foundation/marks/events">Event Branding Policy</a> for ticketed events, and we have some <a href="events/small-events.html">tips for organizing small community events</a> about Apache projects.
+
+The <a href="https://events.apache.org/event/calendar.html">event calendar</a> lists approved Apache-related events, including Community Over Code (formerly ApacheCon) and project summits.
+
</div>
<div class="col-md-4">
-<h4 id="the-foundation">The Foundation <a class="headerlink" title="Permalink" href="#the-foundation">¶</a></h4>
-<p>The Apache Software Foundation (ASF) is a <a href="https://www.apache.org/foundation/">US 501(c)3 non-profit public charity</a>. The Foundation is <a href="https://www.apache.org/foundation/governance/">governed by a Board of Directors</a>, elected by our Membership, and we publish our <a href="https://www.apache.org/foundation/board/calendar.html">monthly board meeting minutes</a>.</p>
-<p>Our mission is to create software for the public good that we <a href="https://www.apache.org/free/">give away for free</a>. You can read how <a href="https://www.apache.org/foundation/governance/" target="_blank">ASF and Apache projects are governed</a>. We <a href="https://www.apache.org/foundation/contributing.html" target="_blank">welcome your support of Apache</a>.</p>
+
+#### The Foundation
+
+The Apache Software Foundation (ASF) is a <a href="https://www.apache.org/foundation/">US 501(c)3 non-profit public charity</a>. The Foundation is <a href="https://www.apache.org/foundation/governance/">governed by a Board of Directors</a>, elected by our Membership, and we publish our <a href="https://www.apache.org/foundation/board/calendar.html">monthly board meeting minutes</a>.
+
+Our mission is to create software for the public good that we <a href="https://www.apache.org/free/">give away for free</a>. You can read how <a href="https://www.apache.org/foundation/governance/" target="_blank">ASF and Apache projects are governed</a>. We <a href="https://www.apache.org/foundation/contributing.html" target="_blank">welcome your support of Apache</a>.
+
</div>
</div>
+
<!-- Row 2 -->
+
<div class="row">
<div class="col-md-4">
-<h4 id="open-source-contributors">Open Source Contributors <a class="headerlink" title="Permalink" href="#open-source-contributors">¶</a></h4>
-<p>If you know a little about open source, and want to understand how the ASF works, our <a href="contributors/index.html">contributors’ section</a> is for you.</p>
-<p>We also have a collection of <a href="links.html">links</a> to relevant information.</p>
-<p>Apache Committers should read our <a href="committers/index.html">committers’ section</a> and see the <a href="https://www.apache.org/dev/">Developer Information site</a>.</p>
+
+#### Open Source Contributors
+
+If you know a little about open source, and want to understand how the ASF works, our <a href="contributors/index.html">contributors' section</a> is for you.
+
+We also have a collection of <a href="links.html">links</a> to relevant information.
+
+Apache Committers should read our <a href="committers/index.html">committers' section</a> and see the <a href="https://www.apache.org/dev/">Developer Information site</a>.
+
</div>
<div class="col-md-4">
-<h4 id="how-apache-works">How Apache works <a class="headerlink" title="Permalink" href="#how-apache-works">¶</a></h4>
-<p>Our <a href="apache-way/apache-project-maturity-model.html">Apache Project Maturity Model</a> defines a structure for evaluating our projects (communities & technology) that can serve as an example for other communities.</p>
-<p>Our <a href="https://www.apache.org/foundation/how-it-works.html" target="_blank">how Apache works</a> guide describes key ASF
-concepts, such as the difference between ASF Members and project committers, how decisions are made (voting), how elections take place,
-and the ASF’s structure and organization.</p>
+
+#### How Apache works
+
+Our <a href="apache-way/apache-project-maturity-model.html">Apache Project Maturity Model</a> defines a structure for evaluating our projects (communities & technology) that can serve as an example for other communities.
+
+Our <a href="https://www.apache.org/foundation/how-it-works.html" target="_blank">how Apache works</a> guide describes key ASF
+concepts, such as the difference between ASF Members and project committers, how decisions are made (voting), how elections take place,
+and the ASF's structure and organization.
+
</div>
<div class="col-md-4">
-<h4 id="faq--code-of-conduct">FAQ & Code of Conduct <a class="headerlink" title="Permalink" href="#faq--code-of-conduct">¶</a></h4>
-<p>Please be nice! The ASF has a <a href="https://www.apache.org/foundation/policies/conduct">Code of Conduct</a> that we expect participants to abide by.</p>
-<p>If you still haven’t found what you are looking for, try our <a href="newbiefaq.html">FAQ</a>, send us an e-mail at <code><a href="mailto:dev@community.apache.org">dev@community.apache.org</a></code>, or read the <a href="https://lists.apache.org/list.html?dev@community.apache.org:lte=3M:" target="_blank">Community mail archives</a>.</p>
+
+#### FAQ & Code of Conduct
+
+Please be nice! The ASF has a <a href="https://www.apache.org/foundation/policies/conduct">Code of Conduct</a> that we expect participants to abide by.
+
+If you still haven't found what you are looking for, try our <a href="newbiefaq.html">FAQ</a>, send us an e-mail at <code>dev@community.apache.org</code>, or read the <a href="https://lists.apache.org/list.html?dev@community.apache.org:lte=3M:" target="_blank">Community mail archives</a>.
+
</div>
+
<!-- Row 3 -->
+
<div class="row">
<div class="col-md-4">
-<h4 id="diversity-and-inclusion">Diversity and Inclusion <a class="headerlink" title="Permalink" href="#diversity-and-inclusion">¶</a></h4>
-<p>The <a href="http://diversity.apache.org/">Apache Diversity</a> website has more information
-on that project, dedicated to understanding and promoting diversity and inclusion in ASF communities.</p>
+
+#### Diversity and Inclusion
+
+The <a href="http://diversity.apache.org/">Apache Diversity</a> website has more information
+on that project, dedicated to understanding and promoting diversity and inclusion in ASF communities.
+
</div>
<div class="col-md-4">
-<h4 id="google-summer-of-code-program-gsoc">Google Summer of Code program (GSoC) <a class="headerlink" title="Permalink" href="#google-summer-of-code-program-gsoc">¶</a></h4>
-<p>The Community Development project also manages the <a href="/gsoc/">ASF’s participation in the Google Summer of Code program</a>. Each year since 2005, we’ve taken on between 30 and 45 students. Many have gone on to become long-term committers to projects, and even Members of the Foundation.</p>
-<p>Read about a few of our <a href="/gsoc/experiences.html">GSoC successes</a>.</p>
+
+#### Google Summer of Code program (GSoC)
+
+The Community Development project also manages the <a href="/gsoc/">ASF's participation in the Google Summer of Code program</a>. Each year since 2005, we've taken on between 30 and 45 students. Many have gone on to become long-term committers to projects, and even Members of the Foundation.
+
+Read about a few of our <a href="/gsoc/experiences.html">GSoC successes</a>.
+
</div>
<div class="col-md-4">
-<h4 id="apache-local-community-alc">Apache Local Community (ALC) <a class="headerlink" title="Permalink" href="#apache-local-community-alc">¶</a></h4>
-<p>The <a href="https://s.apache.org/alc">Apache Local Community</a> comprises local groups of Apache (Open Source) enthusiasts, called an ‘ALC Chapter’. There will be a single ALC chapter per town/city.</p>
-<p>The ALC Chapters spread awareness of the ASF in local communities, hosting local events to share information about the ASF, The Apache Way, and various Apache projects by bringing together project users and developers.</p>
+
+#### Apache Local Community (ALC)
+
+The <a href="https://s.apache.org/alc">Apache Local Community</a> comprises local groups of Apache (Open Source) enthusiasts, called an 'ALC Chapter'. There will be a single ALC chapter per town/city.
+
+The ALC Chapters spread awareness of the ASF in local communities, hosting local events to share information about the ASF, The Apache Way, and various Apache projects by bringing together project users and developers.
+
</div>
</div>
+
<div>
-<h4 id="how-to-ask-questions">How to ask questions <a class="headerlink" title="Permalink" href="#how-to-ask-questions">¶</a></h4>
-<p>All Apache projects use <a href="https://lists.apache.org/">publicly-archived mailing lists</a> that anyone may subscribe
+
+#### How to ask questions
+
+All Apache projects use <a href="https://lists.apache.org/">publicly-archived mailing lists</a> that anyone may subscribe
to. There you can ask questions related to that specific project and gain a sense of its current activities and focus. Most projects have a
-<code><a href="mailto:dev@project.apache.org">dev@project.apache.org</a></code> mailing list for technical discussions about the code, and a
-<code>user@</code> or <code>users@</code> mailing list for questions about the product or features.</p>
-<p>We have a <a href="/contributors/etiquette">Code of Conduct and Etiquette guidelines</a> to help you write good emails.</p>
-<p>The ComDev project has our own mailing list where you can ask general questions
-about Apache at <a href="https://lists.apache.org/list.html?dev@community.apache.org:lte=3M:"><a href="mailto:dev@community.apache.org">dev@community.apache.org</a></a>.</p>
+<code>dev@project.apache.org</code> mailing list for technical discussions about the code, and a
+<code>user@</code> or <code>users@</code> mailing list for questions about the product or features.
+
+We have a <a href="/contributors/etiquette">Code of Conduct and Etiquette guidelines</a> to help you write good emails.
+
+The ComDev project has our own mailing list where you can ask general questions
+about Apache at <a href="https://lists.apache.org/list.html?dev@community.apache.org:lte=3M:">dev@community.apache.org</a>.
+
</div>
diff --git a/content/index.xml b/content/index.xml
index 638d0f9..76cd21a 100644
--- a/content/index.xml
+++ b/content/index.xml
@@ -1,11 +1,16 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Apache Community Development - Welcome on Apache Comdev</title>
<link>https://community.apache.org/</link>
<description>Recent content in Apache Community Development - Welcome on Apache Comdev</description>
<generator>Hugo -- gohugo.io</generator>
- <language>en</language><atom:link href="https://community.apache.org/index.xml" rel="self" type="application/rss+xml" />
+ <language>en</language>
+ <lastBuildDate>Wed, 29 Mar 2023 19:12:27 +0100</lastBuildDate>
+
+ <atom:link href="https://community.apache.org/index.xml" rel="self" type="application/rss+xml" />
+
+
<item>
<title></title>
<link>https://community.apache.org/proposals/ZestProposal.html</link>
@@ -13,8 +18,8 @@
<guid>https://community.apache.org/proposals/ZestProposal.html</guid>
<description>title: Zest Proposal
-Abstract &para; qi4j = new Energy4Java(); That is how to create the Qi4j runtime, and it captures the essence of its spirit. Qi4j is a platform to develop Composite Oriented Programming applications in Java in a new, exciting and productive manner.
-Governance of Provisional Top Level Project &para; Provisional Top Level Project is a new idea at the ASF, and the Qi4j community is willing to try the idea, instead of simply debating it.</description>
+Abstract qi4j = new Energy4Java(); That is how to create the Qi4j runtime, and it captures the essence of its spirit. Qi4j is a platform to develop Composite Oriented Programming applications in Java in a new, exciting and productive manner.
+Governance of Provisional Top Level Project Provisional Top Level Project is a new idea at the ASF, and the Qi4j community is willing to try the idea, instead of simply debating it.</description>
</item>
<item>
@@ -24,29 +29,28 @@ Governance of Provisional Top Level Project &para; Provisional Top Level Pro
<guid>https://community.apache.org/apache-way/apache-project-maturity-model.html</guid>
<description>The Apache Project Maturity Model provides a suggested framework for evaluating the overall maturity of an Apache project community and the codebase that it maintains. While this model is specific to projects of the Apache Software Foundation (ASF), many of these factors apply to any open source project.
-Overview &para; The goals of this maturity model are to describe how Apache projects operate in a concise and high-level way, and to provide a basic framework that projects may choose to use to evaluate themselves.</description>
+Overview The goals of this maturity model are to describe how Apache projects operate in a concise and high-level way, and to provide a basic framework that projects may choose to use to evaluate themselves.</description>
</item>
<item>
- <title>Apache Conferences Calendar</title>
- <link>https://community.apache.org/calendars/conferences.html</link>
+ <title>ASF Community Etiquette Guidelines</title>
+ <link>https://community.apache.org/contributors/etiquette.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
- <guid>https://community.apache.org/calendars/conferences.html</guid>
- <description>Deprecated - See New Calendar instead &para; This calendar is no longer maintained; please see this page instead.
-This Calendar is maintained by the Apache Community Development Committee (ComDev), to have your event listed considered for addition please mail dev@community.apache.org. Note that to be listed in this calendar events must conform to the Third Party Event Branding Policy.
-Upcoming events &para; List loading This Calendar is also available as an iCal feed</description>
+ <guid>https://community.apache.org/contributors/etiquette.html</guid>
+ <description>The ASF and our many projects welcome all participants. Before you begin, it is important to review and respect our community guidelines. We have a few ASF-specific tips below.
+Code of Conduct The ASF has adopted a Code of Conduct which covers interactions in all the online spaces that ASF projects use - email, issue trackers, wikis, websites, IRC, and the like. ASF projects are made up of volunteers, and we work to ensure that all productive contributions are welcomed.</description>
</item>
<item>
- <title>Apache in GSoC</title>
- <link>https://community.apache.org/gsoc/experiences.html</link>
+ <title>Apache Conferences Calendar</title>
+ <link>https://community.apache.org/calendars/conferences.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
- <guid>https://community.apache.org/gsoc/experiences.html</guid>
- <description>This should be in the GSoC directory
-This is a place for collecting information about GSoC activities each year for historical tracking. It was started in 2012 so is missing plenty of detail in the early years. Your help filling it out would be appreciated.
-2018 Overview &para; Students accepted: ? Students who passed final: 29 2017 Overview &para; Students accepted: ? Students who passed final: 27 2016 Overview &para; Students accepted: 49 Students who passed final: 35 2015 Overview &para; Students accepted: 56 Students who passed final: 47 2014 Overview &para; Students accepted: 42 Students who passed final: 35 2013 Overview &para; Students accepted: 51 Students who passed final: 44 2012 Overview &para; Student [...]
+ <guid>https://community.apache.org/calendars/conferences.html</guid>
+ <description>Deprecated - See New Calendar instead This calendar is no longer maintained; please see this page instead.
+This Calendar is maintained by the Apache Community Development Committee (ComDev), to have your event listed considered for addition please mail dev@community.apache.org. Note that to be listed in this calendar events must conform to the Third Party Event Branding Policy.
+Upcoming events List loading This Calendar is also available as an iCal feed</description>
</item>
<item>
@@ -57,7 +61,18 @@ This is a place for collecting information about GSoC activities each year for h
<guid>https://community.apache.org/newbiefaq.html</guid>
<description>These answers to frequently asked questions may help newcomers to The Apache Software Foundation (ASF) and our many Apache projects understand how we work.
Index of Questions
-About The Apache Software Foundation How do I find projects or technologies at the ASF? How are projects managed at the ASF? How do I ask a question about the ASF in general? How do I get user support for an Apache project? Getting involved with Apache projects How do I choose an Apache project to work on?</description>
+ About The Apache Software Foundation How do I find projects or technologies at the ASF? How are projects managed at the ASF? How do I ask a question about the ASF in general? How do I get user support for an Apache project?</description>
+ </item>
+
+ <item>
+ <title>Apache in GSoC</title>
+ <link>https://community.apache.org/gsoc/experiences.html</link>
+ <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+
+ <guid>https://community.apache.org/gsoc/experiences.html</guid>
+ <description>This should be in the GSoC directory
+This is a place for collecting information about GSoC activities each year for historical tracking. It was started in 2012 so is missing plenty of detail in the early years. Your help filling it out would be appreciated.
+2018 Overview Students accepted: ? Students who passed final: 29 2017 Overview Students accepted: ? Students who passed final: 27 2016 Overview Students accepted: 49 Students who passed final: 35 2015 Overview Students accepted: 56 Students who passed final: 47 2014 Overview Students accepted: 42 Students who passed final: 35 2013 Overview Students accepted: 51 Students who passed final: 44 2012 Overview Students accepted: 41 Students who passed midterm: 40 26 projects mento [...]
</item>
<item>
@@ -77,29 +92,19 @@ Many Apache speakers post their slides to the SlideShare website, and the Feathe
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/newsletter/2017-04.html</guid>
- <description>Apache Committer Newsletter, April 2017 &para; Dear Apache Committer,
+ <description>Apache Committer Newsletter, April 2017 Dear Apache Committer,
In this newsletter: committer resources you might not know about, Foundation news, and upcoming community events.
Thank you for your hard work on our Apache projects. You are the reason the Foundation exists, and your work is the reason we have the reputation we enjoy.
In our recent community survey, we heard from a lot of you that you want more information about what committer resources are available, how to connect with developers from other projects, and more information about what’s going on in the Foundation at large.</description>
</item>
- <item>
- <title>ASF Community Etiquette Guidelines</title>
- <link>https://community.apache.org/contributors/etiquette.html</link>
- <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-
- <guid>https://community.apache.org/contributors/etiquette.html</guid>
- <description>The ASF and our many projects welcome all participants. Before you begin, it is important to review and respect our community guidelines. We have a few ASF-specific tips below.
-Code of Conduct &para; The ASF has adopted a Code of Conduct which covers interactions in all the online spaces that ASF projects use - email, issue trackers, wikis, websites, IRC, and the like. ASF projects are made up of volunteers, and we work to ensure that all productive contributions are welcomed.</description>
- </item>
-
<item>
<title>Becoming a committer</title>
<link>https://community.apache.org/contributors/becomingacommitter.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/contributors/becomingacommitter.html</guid>
- <description>Disclaimer &para; Nothing in this post should be construed as a guarantee. You can do everything listed here, for years, and still not become a committer. This is because the decision is made by individuals on the project PMC, who do things for their own reasons.
+ <description>Disclaimer Nothing in this post should be construed as a guarantee. You can do everything listed here, for years, and still not become a committer. This is because the decision is made by individuals on the project PMC, who do things for their own reasons.
On the contrary, this document discusses how things should work, and sometimes do work, in some Apache Software Foundation (ASF) projects, but might not on the one you’re interested in.</description>
</item>
@@ -130,7 +135,7 @@ You can read the complete list of Apache Community Development board reports. A
<guid>https://community.apache.org/history/boardresolution.html</guid>
<description>The Apache Community Development Project was created in November 2009.
-Board Resolution Creating the Apache Community Development Project Establish the Apache Community Development Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with coordinating community development efforts. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the &quot;Apache Community Development Proj [...]
+Board Resolution Creating the Apache Community Development Project Establish the Apache Community Development Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with coordinating community development efforts. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the &quot;Apache Community Development Pr [...]
</item>
<item>
@@ -149,7 +154,7 @@ Board Resolution Creating the Apache Community Development Project Establish the
<guid>https://community.apache.org/committers/consensusBuilding.html</guid>
<description>In some cases there is no obvious path to take, or you might be a new community, or a new member of an existing community. In these cases people often need to build consensus by making proposals and eliciting responses.
-Constructive discussion is the lifeblood of a successful project. However, we want to avoid unnecessary discussion and significant amounts of unnecessary mail that everyone in the community needs to read. so many ASF projects adopt a shorthand notation for showing support, or otherwise, for a proposal.</description>
+Constructive discussion is the lifeblood of a successful project. However, we want to avoid unnecessary discussion and significant amounts of unnecessary mail that everyone in the community needs to read.</description>
</item>
<item>
@@ -160,8 +165,8 @@ Constructive discussion is the lifeblood of a successful project. However, we wa
<guid>https://community.apache.org/contactpoints.html</guid>
<description>If you have a question about anything Apache, the ComDev project is here to help.
To help us help you, try to direct your question to the right mailing list - our volunteer committers do all their work on mailing lists.
-Community Questions &para; Email questions about community or issues across multiple Apache projects to dev@community.apache.org - or see our detailed Mailing List How To page.
-Technical Questions &para; If you have a technical question about this website, or one of the tools that the ComDev project builds, email us at dev@community.</description>
+Community Questions Email questions about community or issues across multiple Apache projects to dev@community.apache.org - or see our detailed Mailing List How To page.
+Technical Questions If you have a technical question about this website, or one of the tools that the ComDev project builds, email us at dev@community.</description>
</item>
<item>
@@ -186,16 +191,6 @@ This page gives a few examples of how to do that.
If you have any question about this, feel free to ask on our dev@community.</description>
</item>
- <item>
- <title>Getting started</title>
- <link>https://community.apache.org/gettingStarted/101.html</link>
- <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-
- <guid>https://community.apache.org/gettingStarted/101.html</guid>
- <description>Where do I start? &para; If you have no idea where to start your engagement with an Apache project, this is the page for you.
-Finding the right project &para; The key to working on projects at Apache (and on any open source project, for that matter) is to have a personal reason for being involved. You might be trying to solve a day job issue or learn a new technology, or simply want to do something fun in your free time.</description>
- </item>
-
<item>
<title>GSoC admins</title>
<link>https://community.apache.org/gsoc/gsoc-admin-tasks.html</link>
@@ -204,17 +199,17 @@ Finding the right project &para; The key to working on projects at Apache (a
<guid>https://community.apache.org/gsoc/gsoc-admin-tasks.html</guid>
<description>A comprehensive guide to being a GSoC admin for the ASF
List of duties:
-Make sure the ASF has an extensive list of project ideas ready shortly after Google announces the program (around the end of January). Projects must create Jira issues for their ideas and label them with gsoc&lt;year&gt;; and mentor. If a project doesn&rsquo;t use Jira, have them create the ideas in the GSOC Jira project. Create a Jira filter for these ideas to use in the application (see next).</description>
+ Make sure the ASF has an extensive list of project ideas ready shortly after Google announces the program (around the end of January). Projects must create Jira issues for their ideas and label them with gsoc&lt;year&gt;; and mentor. If a project doesn&rsquo;t use Jira, have them create the ideas in the GSOC Jira project. Create a Jira filter for these ideas to use in the application (see next).</description>
</item>
<item>
- <title>guide to being a mentor</title>
- <link>https://community.apache.org/gsoc/guide-to-being-a-mentor.html</link>
+ <title>Getting started</title>
+ <link>https://community.apache.org/gettingStarted/101.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
- <guid>https://community.apache.org/gsoc/guide-to-being-a-mentor.html</guid>
- <description>Submitting ideas to the mentoring programme &para; We invite all ASF projects to submit their ideas for consideration in the ASF mentoring programme. Any Apache member and experienced committers can submit ideas via Jira (if your project does not use Jira you can use the Comdev Issue Tracker For GSoC Tasks. We are looking for as many interesting projects as we can come up with.
-Important Steps &para; Add an issue to Jira (if your project does not use Jira you can use the Comdev GSoC Issue Tracker For GSoC Tasks Add sub-tasks if necessary Label the main issue with &ldquo;mentor&rdquo; (these will show up at the ASF-wide list of issues) Label the main issue with &ldquo;gsoc2023&rdquo; if appropriate (these will show up at GSoC 2023 Ideas) Size of project Starting this year there are 2 types of projects available.</description>
+ <guid>https://community.apache.org/gettingStarted/101.html</guid>
+ <description>Where do I start? If you have no idea where to start your engagement with an Apache project, this is the page for you.
+Finding the right project The key to working on projects at Apache (and on any open source project, for that matter) is to have a personal reason for being involved. You might be trying to solve a day job issue or learn a new technology, or simply want to do something fun in your free time.</description>
</item>
<item>
@@ -244,7 +239,7 @@ Here&rsquo;s an example of what your first email might look like:</descripti
<guid>https://community.apache.org/links.html</guid>
<description>This is a collection of links to information that&rsquo;s relevant to the Apache Way and Open Source in general.
Note that most of these links point to websites that are outside of the control of the Apache Software Foundation. Please contact their respective authors for more information or questions. General discussion on the dev@community.a.o list is fine of course.
-Books &para; Producing Open Source Software - by Karl Fogel Blog posts &para; Apache - the Switzerland of Open Source?</description>
+Books Producing Open Source Software - by Karl Fogel Blog posts Apache - the Switzerland of Open Source?</description>
</item>
<item>
@@ -254,8 +249,8 @@ Books &para; Producing Open Source Software - by Karl Fogel Blog posts &
<guid>https://community.apache.org/speakers/speakers.html</guid>
<description>If you&rsquo;re an Apache committer interested in speaking about Apache Technologies, Apache Projects or the Apache Software Foundation as a whole, we encourage you to get involved and list yourself in our speaker application!
-Finding Speakers &para; If you are organising an event and looking for speakers, see the Apache Speakers homepage for details.
-Listing yourself as a potential speaker &para; To list yourself as someone interested in being an Apache speaker, there are two steps.</description>
+Finding Speakers If you are organising an event and looking for speakers, see the Apache Speakers homepage for details.
+Listing yourself as a potential speaker To list yourself as someone interested in being an Apache speaker, there are two steps.</description>
</item>
<item>
@@ -281,17 +276,13 @@ Remember, mentoring is all about the mentee and open source as a whole. It is no
</item>
<item>
- <title>Mentoring a new committer</title>
- <link>https://community.apache.org/mentoring/committer.html</link>
+ <title>Mentoring Mentors</title>
+ <link>https://community.apache.org/mentoring/mentor.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
- <guid>https://community.apache.org/mentoring/committer.html</guid>
- <description>Mentoring a new committer &para; So I&rsquo;m a committer now. What&rsquo;s next? What rights do I have now that I didn&rsquo;t have before? What are the social conventions around making a commit?
-These things vary from one project to another, so clearly documenting them for your particular project is critical.
-Here&rsquo;s the basics that are true across (almost) all Apache projects.
-TODO
-Outline:
-Encouraging other contributors Good commit messages Becoming a PMC member </description>
+ <guid>https://community.apache.org/mentoring/mentor.html</guid>
+ <description>Mentoring Mentors The job of a mentor is to reproduce - spread the work load. Once you&rsquo;ve mentored someone, you need to encourage them to become a mentor themselves. Here&rsquo;s some ways you can do that.
+ Point out people that need a little help Encourage them to answer a question rather than answering it yourself &hellip; TODO</description>
</item>
<item>
@@ -300,18 +291,22 @@ Encouraging other contributors Good commit messages Becoming a PMC member </desc
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/mentoring/pmc.html</guid>
- <description>Mentoring a new PMC member &para; So I&rsquo;m a PMC member now. What does this mean? What rights do I have now that I didn&rsquo;t have before? What conversations belong on the private list, as opposed to the public list.
+ <description>Mentoring a new PMC member So I&rsquo;m a PMC member now. What does this mean? What rights do I have now that I didn&rsquo;t have before? What conversations belong on the private list, as opposed to the public list.
These things vary a little from one project to another, so clearly documenting them for your particular project is critical. And specifically assigning a PMC mentor to new PMC members can greatly help that new member get up to speed, and prevent problems in the future.</description>
</item>
<item>
- <title>Mentoring Mentors</title>
- <link>https://community.apache.org/mentoring/mentor.html</link>
+ <title>Mentoring a new committer</title>
+ <link>https://community.apache.org/mentoring/committer.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
- <guid>https://community.apache.org/mentoring/mentor.html</guid>
- <description>Mentoring Mentors &para; The job of a mentor is to reproduce - spread the work load. Once you&rsquo;ve mentored someone, you need to encourage them to become a mentor themselves. Here&rsquo;s some ways you can do that.
-Point out people that need a little help Encourage them to answer a question rather than answering it yourself &hellip; TODO</description>
+ <guid>https://community.apache.org/mentoring/committer.html</guid>
+ <description> Mentoring a new committer So I&rsquo;m a committer now. What&rsquo;s next? What rights do I have now that I didn&rsquo;t have before? What are the social conventions around making a commit?
+These things vary from one project to another, so clearly documenting them for your particular project is critical.
+Here&rsquo;s the basics that are true across (almost) all Apache projects.
+TODO
+Outline:
+ Encouraging other contributors Good commit messages Becoming a PMC member </description>
</item>
<item>
@@ -320,10 +315,10 @@ Point out people that need a little help Encourage them to answer a question rat
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/mentoring/firstpatch.html</guid>
- <description>Mentoring: First Patch &para; A beginner&rsquo;s first patch on a project can be an intimidating and frustrating experience. Clearly documenting the entire process from checkout to accepted patch greatly lowers the barrier for a new contributor, and makes it more likely that they&rsquo;ll come back for their second patch.
+ <description> Mentoring: First Patch A beginner&rsquo;s first patch on a project can be an intimidating and frustrating experience. Clearly documenting the entire process from checkout to accepted patch greatly lowers the barrier for a new contributor, and makes it more likely that they&rsquo;ll come back for their second patch.
Here&rsquo;s some tips on how to do that.
Outline:
-Talk to the project first Make sure it&rsquo;s wanted/welcome See if there&rsquo;s already work in progress, or suggestions Find someone to be your advocate Finding the source Writing a good commit message Following up on your pull request Learning from your struggle: Improving the documentation </description>
+ Talk to the project first Make sure it&rsquo;s wanted/welcome See if there&rsquo;s already work in progress, or suggestions Find someone to be your advocate Finding the source Writing a good commit message Following up on your pull request Learning from your struggle: Improving the documentation </description>
</item>
<item>
@@ -334,7 +329,7 @@ Talk to the project first Make sure it&rsquo;s wanted/welcome See if there&a
<guid>https://community.apache.org/newcommitter.html</guid>
<description>Identifying potential new committers, calling a vote for their recognition as a committer and processing the relevant documents are tasks to which the whole community can contribute.
Each project has a different approach to managing new committers. This page describes a common process found in many Apache projects. It also provides drafts for the various communications that are necessary.
-Guidelines for assessing new candidates for committership Ability to work cooperatively with peers.</description>
+ Guidelines for assessing new candidates for committership Ability to work cooperatively with peers.</description>
</item>
<item>
@@ -344,7 +339,7 @@ Guidelines for assessing new candidates for committership Ability to work cooper
<guid>https://community.apache.org/history/mentoringprogramme-icfoss-pilot.html</guid>
<description>Note that this information is about a pilot program that happened back in 2013.
-The ASF has been participating in many mentoring initiatives, and it&rsquo;s now partnering in a pilot project with India ICFOSS to provide mentoring for undergraduate and graduate students that have interest in learning how to participate in open source communities at ASF.
+ The ASF has been participating in many mentoring initiatives, and it&rsquo;s now partnering in a pilot project with India ICFOSS to provide mentoring for undergraduate and graduate students that have interest in learning how to participate in open source communities at ASF.
The mentoring programme is not here to teach you to write documentation or code.</description>
</item>
@@ -364,7 +359,7 @@ A community is not merely a set of rules; it is also a set of behaviors that the
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/events/small-events.html</guid>
- <description>Approval of small Apache-related events &para; The Community Development PMC is responsible for assisting with the organisation and promotion of all Apache events.
+ <description>Approval of small Apache-related events The Community Development PMC is responsible for assisting with the organisation and promotion of all Apache events.
Organizers of Apache-related events need approval for using the Apache trademarks in their event brandings.
The main steps are:
a) Get approval from the PMCs of the projects that your event is about.
@@ -379,7 +374,7 @@ c) Once brand use is approved by the respective PMCs, inform the community devel
<guid>https://community.apache.org/gsoc/use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.html</guid>
<description>If your project does not use the ASF Jira for issue tracking, you can use the ComDev GSoC Jira project to record your GSoC tasks.
-Add tasks to the GSOC project Ensure you add the labels gsoc2023, mentor and _YOUR_PROJECT_NAME_ Your issues will appear in the list of projects We use the label _YOUR_PROJECT_NAME_ to map COMDEV issues to the real project when we create the ideas list Please contact dev@community.</description>
+ Add tasks to the GSOC project Ensure you add the labels gsoc2023, mentor and _YOUR_PROJECT_NAME_ Your issues will appear in the list of projects We use the label _YOUR_PROJECT_NAME_ to map COMDEV issues to the real project when we create the ideas list Please contact dev@community.</description>
</item>
<item>
@@ -389,8 +384,19 @@ Add tasks to the GSOC project Ensure you add the labels gsoc2023, mentor and _YO
<guid>https://community.apache.org/committers/voting.html</guid>
<description>Occasionally a &ldquo;feel&rdquo; for consensus is not enough. Sometimes we need to have a measurable consensus, for example, when voting to invite new committers or to approve a release.
-Preparing for a Vote &para; It is important to ensure that the community has time to discuss the issue before voting. To do this, post an email to the list indicating the intention to call a vote and the options available. By the time a vote takes place there usually is consensus in the community on what path to take.</description>
+Preparing for a Vote It is important to ensure that the community has time to discuss the issue before voting. To do this, post an email to the list indicating the intention to call a vote and the options available. By the time a vote takes place there usually is consensus in the community on what path to take.</description>
+ </item>
+
+ <item>
+ <title>guide to being a mentor</title>
+ <link>https://community.apache.org/gsoc/guide-to-being-a-mentor.html</link>
+ <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+
+ <guid>https://community.apache.org/gsoc/guide-to-being-a-mentor.html</guid>
+ <description>Submitting ideas to the mentoring programme We invite all ASF projects to submit their ideas for consideration in the ASF mentoring programme. Any Apache member and experienced committers can submit ideas via Jira (if your project does not use Jira you can use the Comdev Issue Tracker For GSoC Tasks. We are looking for as many interesting projects as we can come up with.
+
+Important Steps Add an issue to Jira (if your project does not use Jira you can use the Comdev GSoC Issue Tracker For GSoC Tasks Add sub-tasks if necessary Label the main issue with &ldquo;mentor&rdquo; (these will show up at the ASF-wide list of issues) Label the main issue with &ldquo;gsoc2023&rdquo; if appropriate (these will show up at GSoC 2023 Ideas) Size of project Starting this year there are 2 types of projects available.</description>
</item>
</channel>
-</rss>
+</rss>
\ No newline at end of file
diff --git a/content/links.html b/content/links.html
index 56f0671..1d4ed40 100644
--- a/content/links.html
+++ b/content/links.html
@@ -9,11 +9,25 @@
<meta property="og:title" content="Links" />
<meta property="og:description" content="This is a collection of links to information that’s relevant to the Apache Way and Open Source in general.
Note that most of these links point to websites that are outside of the control of the Apache Software Foundation. Please contact their respective authors for more information or questions. General discussion on the dev@community.a.o list is fine of course.
-Books ¶ Producing Open Source Software - by Karl Fogel Blog posts ¶ Apache - the Switzerland of Open Source?" />
+Books Producing Open Source Software - by Karl Fogel Blog posts Apache - the Switzerland of Open Source?" />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/links.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="" />
+<meta property="og:url" content="https://community.apache.org/links.html" />
+
+
+
+
+<meta property="article:modified_time" content="2023-03-16T12:35:40-04:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2023-03-16T12:35:40-04:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Links</title>
@@ -183,27 +197,36 @@ Books ¶ Producing Open Source Software - by Karl Fogel Blog posts ¶ Ap
<hr>
- <p>This is a collection of links to information that’s relevant to the Apache Way and Open Source in general.</p>
+
+
+<p>This is a collection of links to information that’s relevant to the Apache Way and Open Source in general.</p>
+
<p>Note that most of these links point to websites that are outside of the control of the Apache Software Foundation. Please contact their respective
-authors for more information or questions. General discussion on the <a href="mailto:dev@community.a.o">dev@community.a.o</a> list is fine of course.</p>
-<h1 id="books">Books <a class="headerlink" title="Permalink" href="#books">¶</a></h1>
+authors for more information or questions. General discussion on the dev@community.a.o list is fine of course.</p>
+
+<h1 id="books">Books</h1>
+
<ul>
<li><a href="https://producingoss.com/">Producing Open Source Software</a> - by Karl Fogel</li>
</ul>
-<h1 id="blog-posts">Blog posts <a class="headerlink" title="Permalink" href="#blog-posts">¶</a></h1>
+
+<h1 id="blog-posts">Blog posts</h1>
+
<ul>
<li><a href="https://grep.codeconsult.ch/2009/03/30/the-asf-is-the-switzerland-of-open-source/">Apache - the Switzerland of Open Source?</a> - by Bertrand Delacretaz</li>
<li><a href="https://psteitz.blogspot.ch/2011/11/thinking-together.html">Thinking Together</a> - by Phil Steitz</li>
</ul>
-<h1 id="slides">Slides <a class="headerlink" title="Permalink" href="#slides">¶</a></h1>
+
+<h1 id="slides">Slides</h1>
+
<ul>
<li><a href="http://archive.apachecon.com/eu2007/materials/asf-intro-slides-eilebrecht.pdf">Behind the Scenes of the Apache Software Foundation</a> - by Lars Eilebrecht (PDF)</li>
</ul>
-<h1 id="apache-community-members-websites-and-links">Apache community members websites and links <a class="headerlink" title="Permalink" href="#apache-community-members-websites-and-links">¶</a></h1>
+
+<h1 id="apache-community-members-websites-and-links">Apache community members websites and links</h1>
+
<ul>
-<li>
-<p><a href="http://theapacheway.com/">Shane’s “the Apache Way”</a> - An Apache Way Primer by Shane Curcuru</p>
-</li>
+<li><a href="http://theapacheway.com/">Shane’s “the Apache Way”</a> - An Apache Way Primer by Shane Curcuru</li>
</ul>
diff --git a/content/lists.html b/content/lists.html
index 2ba8ba2..f5af4db 100644
--- a/content/lists.html
+++ b/content/lists.html
@@ -9,9 +9,23 @@
<meta property="og:title" content="Community Development Mailing Lists" />
<meta property="og:description" content="Almost everything and everyone at Apache use email lists to get work done, including this Community Development project right here! When people send email to a list, many other community members get the message, and someone usually provides a useful reply. Every email list at Apache is archived: most lists are archived publicly. That means that newcomers to a community can learn how decisions on a project have been made in the past, because all th [...]
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/lists.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="" />
+<meta property="og:url" content="https://community.apache.org/lists.html" />
+
+
+
+
+<meta property="article:modified_time" content="2020-12-15T09:34:12-04:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2020-12-15T09:34:12-04:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Community Development Mailing Lists</title>
@@ -181,45 +195,60 @@
<hr>
- <p>Almost everything and everyone at Apache use email lists to get work done, including this Community Development project right here! When people
+
+
+<p>Almost everything and everyone at Apache use email lists to get work done, including this Community Development project right here! When people
send email to a list, many other community members get the message, and
someone usually provides a useful reply. Every email list at Apache is archived: most lists are
<a href="https://www.apache.org/foundation/public-archives.html">archived publicly</a>. That means that newcomers to a community can learn how
decisions on a project have been made in the past, because all the email discussions
a project has had are archived.</p>
+
<p>If you have questions about anything at Apache, the first thing to do is
find the right mailing list - and then send your question!</p>
-<h1 id="read-this-first">Read This First <a class="headerlink" title="Permalink" href="#read-this-first">¶</a></h1>
+
+<h1 id="read-this-first">Read This First</h1>
+
<p><a href="https://www.apache.org/dev/#mail">Detailed instructions</a> on how to use Apache email lists (subscribing, sending
email, reading the archives, and other technical steps) are available on our main developer site. You can email most
lists without subscribing, but some lists require that you subscribe first. Most emails
are moderated, so they won’t show up on the list immediately. You may need to wait
a day, especially if you are new.</p>
+
<p>Please be sure your <a href="https://infra.apache.org/contrib-email-tips">question is on topic for the list</a>, and that you have at
least checked the relevant documentation first. Everyone at Apache is a volunteer,
and if you don’t do your homework, we probably can’t help you.
It’s also best to follow our <a href="/contributors/etiquette">email etiquette guidelines</a>.</p>
-<h1 id="find-the-right-email-list">Find The Right Email List <a class="headerlink" title="Permalink" href="#find-the-right-email-list">¶</a></h1>
+
+<h1 id="find-the-right-email-list">Find The Right Email List</h1>
+
<p>Finding the right list helps get your question in front of people who will know
the answer. Each project at Apache uses their own dev@, user@, and
other email lists - so asking about Apache Tomcat on the Apache Cassandra
lists is likely going to be ignored.</p>
+
<p>Most projects have a <code>Mailing Lists</code>, <code>Community</code>, or <code>Contact Us</code> link on their homepage,
so start there if you know which project you’re asking about. If you don’t know which
kind of list to ask on, consult our full list of all <a href="https://www.apache.org/foundation/mailinglists.html">Apache-wide mailing lists</a>.</p>
+
<p>If you have <strong>any non-technical questions</strong> - or a question for us here in community
-development - ask here by sending email to <strong><code>dev@community.apache.org</code></strong>!<br>
+development - ask here by sending email to <strong><code>dev@community.apache.org</code></strong>!<br />
You can also <a href="https://lists.apache.org/list.html?dev@community.apache.org:lte=12M:">read the archives of our dev@community</a> email list to see what other people have asked and learned.</p>
-<h1 id="read-the-list-archives">Read The List Archives <a class="headerlink" title="Permalink" href="#read-the-list-archives">¶</a></h1>
+
+<h1 id="read-the-list-archives">Read The List Archives</h1>
+
<p>Almost every list at Apache is archived publicly. Browsing the archives is a great way to learn about
how a community has done things in the past, or to learn about <em>why</em> a project
operates the way they do. The ASF maintains an official archive and allows both
browsing and searching through all public email archives:</p>
+
<ul>
<li><a href="https://lists.apache.org/">https://lists.apache.org/</a></li>
</ul>
+
<p>Several other organizations also archive many/most Apache email lists, and some
offer useful search or sending functionality:</p>
+
<ul>
<li>MarkMail <a href="https://apache.markmail.org/">https://apache.markmail.org/</a> - natural language search</li>
<li>MARC <a href="https://marc.info/">https://marc.info/</a></li>
diff --git a/content/mentor-request-mail.html b/content/mentor-request-mail.html
index 2505238..3433bb2 100644
--- a/content/mentor-request-mail.html
+++ b/content/mentor-request-mail.html
@@ -10,9 +10,23 @@
<meta property="og:description" content="Having identified a Top Level Project (TLP) and an issue you would like to work on, it is a good idea to introduce yourself to the project community and outline your plans for tackling the issue. This lets the community know you are working on the issue and gives the community an early opportunity to help course correct your proposal, if necessary (which can save you lots of time).
Here’s an example of what your first email might look like:" />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/mentor-request-mail.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="" />
+<meta property="og:url" content="https://community.apache.org/mentor-request-mail.html" />
+
+
+
+
+<meta property="article:modified_time" content="2020-12-13T09:34:53-04:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2020-12-13T09:34:53-04:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - How To: Write A Mentor Request Email</title>
@@ -187,47 +201,48 @@ good idea to introduce yourself to the project community and outline your
plans for tackling the issue. This lets the community know you are working
on the issue and gives the community an early opportunity to help course
correct your proposal, if necessary (which can save you lots of time).</p>
+
<p>Here’s an example of what your first email might look like:</p>
-<div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-text" data-lang="text"><span style="display:flex;"><span>SUBJECT: A proposal for Skinnable widgets (WOOKIE-131)
-</span></span><span style="display:flex;"><span>
-</span></span><span style="display:flex;"><span>Hi, I'm new to the Wookie project but I'd like to tackle the "Skinnablewidgets"
-</span></span><span style="display:flex;"><span>issue (WOOKIE-131, see [1]). Before I start implementing this I'd like to
-</span></span><span style="display:flex;"><span>run my ideas past you to make sure I'm not missing something important.
-</span></span><span style="display:flex;"><span>
-</span></span><span style="display:flex;"><span>If I understand the issue correctly, we need to define the structure of a minimal
-</span></span><span style="display:flex;"><span>widget. For example:
-</span></span><span style="display:flex;"><span>
-</span></span><span style="display:flex;"><span><div id="wookie-widget">
-</span></span><span style="display:flex;"><span> <div id="wookie-toolbar">This is where the toolbar will be</div>
-</span></span><span style="display:flex;"><span> <div id="wookie-content">This is where the content will be</div>
-</span></span><span style="display:flex;"><span> <div id="wookie-footer">This is where the footer will be</div>
-</span></span><span style="display:flex;"><span></div>
-</span></span><span style="display:flex;"><span>
-</span></span><span style="display:flex;"><span>We also need to provide a default CSS for rendering this as, for example:
-</span></span><span style="display:flex;"><span>
-</span></span><span style="display:flex;"><span>+-----------------------+
-</span></span><span style="display:flex;"><span>|TOOLBAR |
-</span></span><span style="display:flex;"><span>+-----------------------+
-</span></span><span style="display:flex;"><span>| |
-</span></span><span style="display:flex;"><span>|CONTENT |
-</span></span><span style="display:flex;"><span>| |
-</span></span><span style="display:flex;"><span>+-----------------------+
-</span></span><span style="display:flex;"><span>|FOOTER |
-</span></span><span style="display:flex;"><span>+-----------------------+
-</span></span><span style="display:flex;"><span>
-</span></span><span style="display:flex;"><span>We need to document all this (how to use it and how to extend it) on the Wookie website, and change all widgets to conform to
-</span></span><span style="display:flex;"><span>this format.
-</span></span><span style="display:flex;"><span>
-</span></span><span style="display:flex;"><span>Once all this is in place I would like to start extending it to provide documented
-</span></span><span style="display:flex;"><span>CSS identifiers to use in common cases. For example, we may want to define a
-</span></span><span style="display:flex;"><span>"wookie-navigation" style for a common navigation menu. We can then provide
-</span></span><span style="display:flex;"><span>various CSS alternatives for rending this as a vertical navigation menu, drop down
-</span></span><span style="display:flex;"><span>menu, or whatever.
-</span></span><span style="display:flex;"><span>
-</span></span><span style="display:flex;"><span>Am I on the right track? Are there any important points I'm missing?
-</span></span><span style="display:flex;"><span>
-</span></span><span style="display:flex;"><span>[1] https://issues.apache.org/jira/browse/WOOKIE-131
-</span></span></code></pre></div><p>There are two main advantages to sending a mail like this. First, you
+<div class="highlight"><pre style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-text" data-lang="text">SUBJECT: A proposal for Skinnable widgets (WOOKIE-131)
+
+Hi, I'm new to the Wookie project but I'd like to tackle the "Skinnablewidgets"
+issue (WOOKIE-131, see [1]). Before I start implementing this I'd like to
+run my ideas past you to make sure I'm not missing something important.
+
+If I understand the issue correctly, we need to define the structure of a minimal
+widget. For example:
+
+<div id="wookie-widget">
+ <div id="wookie-toolbar">This is where the toolbar will be</div>
+ <div id="wookie-content">This is where the content will be</div>
+ <div id="wookie-footer">This is where the footer will be</div>
+</div>
+
+We also need to provide a default CSS for rendering this as, for example:
+
++-----------------------+
+|TOOLBAR |
++-----------------------+
+| |
+|CONTENT |
+| |
++-----------------------+
+|FOOTER |
++-----------------------+
+
+We need to document all this (how to use it and how to extend it) on the Wookie website, and change all widgets to conform to
+this format.
+
+Once all this is in place I would like to start extending it to provide documented
+CSS identifiers to use in common cases. For example, we may want to define a
+"wookie-navigation" style for a common navigation menu. We can then provide
+various CSS alternatives for rending this as a vertical navigation menu, drop down
+menu, or whatever.
+
+Am I on the right track? Are there any important points I'm missing?
+
+[1] https://issues.apache.org/jira/browse/WOOKIE-131</code></pre></div>
+<p>There are two main advantages to sending a mail like this. First, you
force yourself to think carefully about what the project requires and whether you
have the skills to do it (and thus where you will need help). Second, it lets
people in the community provide input. For example, in the above case
diff --git a/content/mentoring/committer.html b/content/mentoring/committer.html
index df1db0c..54a59ec 100644
--- a/content/mentoring/committer.html
+++ b/content/mentoring/committer.html
@@ -7,16 +7,30 @@
<meta name="keywords" content="apache, apache community, community development, opensource"/>
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="Mentoring a new committer" />
-<meta property="og:description" content="Mentoring a new committer ¶ So I’m a committer now. What’s next? What rights do I have now that I didn’t have before? What are the social conventions around making a commit?
+<meta property="og:description" content=" Mentoring a new committer So I’m a committer now. What’s next? What rights do I have now that I didn’t have before? What are the social conventions around making a commit?
These things vary from one project to another, so clearly documenting them for your particular project is critical.
Here’s the basics that are true across (almost) all Apache projects.
TODO
Outline:
-Encouraging other contributors Good commit messages Becoming a PMC member " />
+ Encouraging other contributors Good commit messages Becoming a PMC member " />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/mentoring/committer.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="mentoring" />
+<meta property="og:url" content="https://community.apache.org/mentoring/committer.html" />
+
+
+
+
+<meta property="article:modified_time" content="2023-03-17T12:26:02-04:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2023-03-17T12:26:02-04:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Mentoring a new committer</title>
@@ -192,15 +206,23 @@ Encouraging other contributors Good commit messages Becoming a PMC member " />
<hr>
- <h1 id="mentoring-a-new-committer">Mentoring a new committer <a class="headerlink" title="Permalink" href="#mentoring-a-new-committer">¶</a></h1>
+
+
+<h1 id="mentoring-a-new-committer">Mentoring a new committer</h1>
+
<p>So I’m a committer now. What’s next? What rights do I have now that I
didn’t have before? What are the social conventions around making a
commit?</p>
+
<p>These things vary from one project to another, so clearly documenting
them for your particular project is critical.</p>
+
<p>Here’s the basics that are true across (almost) all Apache projects.</p>
+
<p>TODO</p>
+
<p>Outline:</p>
+
<ul>
<li>Encouraging other contributors</li>
<li>Good commit messages</li>
diff --git a/content/mentoring/firstpatch.html b/content/mentoring/firstpatch.html
index 7640181..668bf75 100644
--- a/content/mentoring/firstpatch.html
+++ b/content/mentoring/firstpatch.html
@@ -7,14 +7,28 @@
<meta name="keywords" content="apache, apache community, community development, opensource"/>
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="Mentoring: First Patch" />
-<meta property="og:description" content="Mentoring: First Patch ¶ A beginner’s first patch on a project can be an intimidating and frustrating experience. Clearly documenting the entire process from checkout to accepted patch greatly lowers the barrier for a new contributor, and makes it more likely that they’ll come back for their second patch.
+<meta property="og:description" content=" Mentoring: First Patch A beginner’s first patch on a project can be an intimidating and frustrating experience. Clearly documenting the entire process from checkout to accepted patch greatly lowers the barrier for a new contributor, and makes it more likely that they’ll come back for their second patch.
Here’s some tips on how to do that.
Outline:
-Talk to the project first Make sure it’s wanted/welcome See if there’s already work in progress, or suggestions Find someone to be your advocate Finding the source Writing a good commit message Following up on your pull request Learning from your struggle: Improving the documentation " />
+ Talk to the project first Make sure it’s wanted/welcome See if there’s already work in progress, or suggestions Find someone to be your advocate Finding the source Writing a good commit message Following up on your pull request Learning from your struggle: Improving the documentation " />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/mentoring/firstpatch.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="mentoring" />
+<meta property="og:url" content="https://community.apache.org/mentoring/firstpatch.html" />
+
+
+
+
+<meta property="article:modified_time" content="2023-03-17T12:26:02-04:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2023-03-17T12:26:02-04:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Mentoring: First Patch</title>
@@ -190,22 +204,28 @@ Talk to the project first Make sure it’s wanted/welcome See if there&rsquo
<hr>
- <h1 id="mentoring-first-patch">Mentoring: First Patch <a class="headerlink" title="Permalink" href="#mentoring-first-patch">¶</a></h1>
+
+
+<h1 id="mentoring-first-patch">Mentoring: First Patch</h1>
+
<p>A beginner’s first patch on a project can be an intimidating and
frustrating experience. Clearly documenting the entire process from
checkout to accepted patch greatly lowers the barrier for a new
contributor, and makes it more likely that they’ll come back for their
second patch.</p>
+
<p>Here’s some tips on how to do that.</p>
+
<p>Outline:</p>
+
<ul>
<li>Talk to the project first
+
<ul>
<li>Make sure it’s wanted/welcome</li>
<li>See if there’s already work in progress, or suggestions</li>
<li>Find someone to be your advocate</li>
-</ul>
-</li>
+</ul></li>
<li>Finding the source</li>
<li>Writing a good commit message</li>
<li>Following up on your pull request</li>
diff --git a/content/mentoring/index.html b/content/mentoring/index.html
index efd7e49..31019aa 100644
--- a/content/mentoring/index.html
+++ b/content/mentoring/index.html
@@ -9,7 +9,21 @@
<meta property="og:title" content="Mentoring" />
<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/mentoring/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+<meta property="og:url" content="https://community.apache.org/mentoring/" />
+
+
+
+<meta property="og:updated_time" content="2023-03-29T11:49:44+02:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
<title>Apache Community Development - Mentoring</title>
@@ -182,15 +196,21 @@
<hr>
- <h1 id="mentoring">Mentoring <a class="headerlink" title="Permalink" href="#mentoring">¶</a></h1>
+
+
+<h1 id="mentoring">Mentoring</h1>
+
<p>A major job of Community Development is mentoring. Mentoring is the
process of actively bringing someone along in a discipline - investing
your time into influencing the future. Time spent mentoring today will
pay off for years to come.</p>
+
<p>Anyone can be a mentor. You just have to take a moment to encourage
someone else to participate.</p>
+
<p>Here’s some concrete ways you can provide mentoring to other members of
your community.</p>
+
<ul>
<li><a href="/gsoc/">GSoC</a></li>
<li><a href="https://incubator.apache.org/">Participate in the incubator</a></li>
diff --git a/content/mentoring/index.xml b/content/mentoring/index.xml
index 8460a5b..4f7f3a8 100644
--- a/content/mentoring/index.xml
+++ b/content/mentoring/index.xml
@@ -1,23 +1,24 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Mentoring on Apache Comdev</title>
<link>https://community.apache.org/mentoring/</link>
<description>Recent content in Mentoring on Apache Comdev</description>
<generator>Hugo -- gohugo.io</generator>
- <language>en</language><atom:link href="https://community.apache.org/mentoring/index.xml" rel="self" type="application/rss+xml" />
+ <language>en</language>
+ <lastBuildDate>Wed, 29 Mar 2023 11:49:44 +0200</lastBuildDate>
+
+ <atom:link href="https://community.apache.org/mentoring/index.xml" rel="self" type="application/rss+xml" />
+
+
<item>
- <title>Mentoring a new committer</title>
- <link>https://community.apache.org/mentoring/committer.html</link>
+ <title>Mentoring Mentors</title>
+ <link>https://community.apache.org/mentoring/mentor.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
- <guid>https://community.apache.org/mentoring/committer.html</guid>
- <description>Mentoring a new committer &para; So I&rsquo;m a committer now. What&rsquo;s next? What rights do I have now that I didn&rsquo;t have before? What are the social conventions around making a commit?
-These things vary from one project to another, so clearly documenting them for your particular project is critical.
-Here&rsquo;s the basics that are true across (almost) all Apache projects.
-TODO
-Outline:
-Encouraging other contributors Good commit messages Becoming a PMC member </description>
+ <guid>https://community.apache.org/mentoring/mentor.html</guid>
+ <description>Mentoring Mentors The job of a mentor is to reproduce - spread the work load. Once you&rsquo;ve mentored someone, you need to encourage them to become a mentor themselves. Here&rsquo;s some ways you can do that.
+ Point out people that need a little help Encourage them to answer a question rather than answering it yourself &hellip; TODO</description>
</item>
<item>
@@ -26,18 +27,22 @@ Encouraging other contributors Good commit messages Becoming a PMC member </desc
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/mentoring/pmc.html</guid>
- <description>Mentoring a new PMC member &para; So I&rsquo;m a PMC member now. What does this mean? What rights do I have now that I didn&rsquo;t have before? What conversations belong on the private list, as opposed to the public list.
+ <description>Mentoring a new PMC member So I&rsquo;m a PMC member now. What does this mean? What rights do I have now that I didn&rsquo;t have before? What conversations belong on the private list, as opposed to the public list.
These things vary a little from one project to another, so clearly documenting them for your particular project is critical. And specifically assigning a PMC mentor to new PMC members can greatly help that new member get up to speed, and prevent problems in the future.</description>
</item>
<item>
- <title>Mentoring Mentors</title>
- <link>https://community.apache.org/mentoring/mentor.html</link>
+ <title>Mentoring a new committer</title>
+ <link>https://community.apache.org/mentoring/committer.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
- <guid>https://community.apache.org/mentoring/mentor.html</guid>
- <description>Mentoring Mentors &para; The job of a mentor is to reproduce - spread the work load. Once you&rsquo;ve mentored someone, you need to encourage them to become a mentor themselves. Here&rsquo;s some ways you can do that.
-Point out people that need a little help Encourage them to answer a question rather than answering it yourself &hellip; TODO</description>
+ <guid>https://community.apache.org/mentoring/committer.html</guid>
+ <description> Mentoring a new committer So I&rsquo;m a committer now. What&rsquo;s next? What rights do I have now that I didn&rsquo;t have before? What are the social conventions around making a commit?
+These things vary from one project to another, so clearly documenting them for your particular project is critical.
+Here&rsquo;s the basics that are true across (almost) all Apache projects.
+TODO
+Outline:
+ Encouraging other contributors Good commit messages Becoming a PMC member </description>
</item>
<item>
@@ -46,11 +51,11 @@ Point out people that need a little help Encourage them to answer a question rat
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/mentoring/firstpatch.html</guid>
- <description>Mentoring: First Patch &para; A beginner&rsquo;s first patch on a project can be an intimidating and frustrating experience. Clearly documenting the entire process from checkout to accepted patch greatly lowers the barrier for a new contributor, and makes it more likely that they&rsquo;ll come back for their second patch.
+ <description> Mentoring: First Patch A beginner&rsquo;s first patch on a project can be an intimidating and frustrating experience. Clearly documenting the entire process from checkout to accepted patch greatly lowers the barrier for a new contributor, and makes it more likely that they&rsquo;ll come back for their second patch.
Here&rsquo;s some tips on how to do that.
Outline:
-Talk to the project first Make sure it&rsquo;s wanted/welcome See if there&rsquo;s already work in progress, or suggestions Find someone to be your advocate Finding the source Writing a good commit message Following up on your pull request Learning from your struggle: Improving the documentation </description>
+ Talk to the project first Make sure it&rsquo;s wanted/welcome See if there&rsquo;s already work in progress, or suggestions Find someone to be your advocate Finding the source Writing a good commit message Following up on your pull request Learning from your struggle: Improving the documentation </description>
</item>
</channel>
-</rss>
+</rss>
\ No newline at end of file
diff --git a/content/mentoring/mentor.html b/content/mentoring/mentor.html
index c4d829a..68ddc47 100644
--- a/content/mentoring/mentor.html
+++ b/content/mentoring/mentor.html
@@ -7,12 +7,26 @@
<meta name="keywords" content="apache, apache community, community development, opensource"/>
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="Mentoring Mentors" />
-<meta property="og:description" content="Mentoring Mentors ¶ The job of a mentor is to reproduce - spread the work load. Once you’ve mentored someone, you need to encourage them to become a mentor themselves. Here’s some ways you can do that.
-Point out people that need a little help Encourage them to answer a question rather than answering it yourself … TODO" />
+<meta property="og:description" content="Mentoring Mentors The job of a mentor is to reproduce - spread the work load. Once you’ve mentored someone, you need to encourage them to become a mentor themselves. Here’s some ways you can do that.
+ Point out people that need a little help Encourage them to answer a question rather than answering it yourself … TODO" />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/mentoring/mentor.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="mentoring" />
+<meta property="og:url" content="https://community.apache.org/mentoring/mentor.html" />
+
+
+
+
+<meta property="article:modified_time" content="2020-03-24T15:03:46+01:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2020-03-24T15:03:46+01:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Mentoring Mentors</title>
@@ -188,15 +202,20 @@ Point out people that need a little help Encourage them to answer a question rat
<hr>
- <h1 id="mentoring-mentors">Mentoring Mentors <a class="headerlink" title="Permalink" href="#mentoring-mentors">¶</a></h1>
+
+
+<h1 id="mentoring-mentors">Mentoring Mentors</h1>
+
<p>The job of a mentor is to reproduce - spread the work load. Once you’ve
mentored someone, you need to encourage them to become a mentor
themselves. Here’s some ways you can do that.</p>
+
<ul>
<li>Point out people that need a little help</li>
<li>Encourage them to answer a question rather than answering it yourself</li>
<li>…</li>
</ul>
+
<p>TODO</p>
diff --git a/content/mentoring/pmc.html b/content/mentoring/pmc.html
index fd64871..28a8def 100644
--- a/content/mentoring/pmc.html
+++ b/content/mentoring/pmc.html
@@ -7,12 +7,26 @@
<meta name="keywords" content="apache, apache community, community development, opensource"/>
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="Mentoring a new PMC member" />
-<meta property="og:description" content="Mentoring a new PMC member ¶ So I’m a PMC member now. What does this mean? What rights do I have now that I didn’t have before? What conversations belong on the private list, as opposed to the public list.
+<meta property="og:description" content="Mentoring a new PMC member So I’m a PMC member now. What does this mean? What rights do I have now that I didn’t have before? What conversations belong on the private list, as opposed to the public list.
These things vary a little from one project to another, so clearly documenting them for your particular project is critical. And specifically assigning a PMC mentor to new PMC members can greatly help that new member get up to speed, and prevent problems in the future." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/mentoring/pmc.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="mentoring" />
+<meta property="og:url" content="https://community.apache.org/mentoring/pmc.html" />
+
+
+
+
+<meta property="article:modified_time" content="2023-03-17T12:26:02-04:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2023-03-17T12:26:02-04:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Mentoring a new PMC member</title>
@@ -188,18 +202,26 @@ These things vary a little from one project to another, so clearly documenting t
<hr>
- <h1 id="mentoring-a-new-pmc-member">Mentoring a new PMC member <a class="headerlink" title="Permalink" href="#mentoring-a-new-pmc-member">¶</a></h1>
+
+
+<h1 id="mentoring-a-new-pmc-member">Mentoring a new PMC member</h1>
+
<p>So I’m a PMC member now. What does this mean? What rights do I have now
that I didn’t have before? What conversations belong on the private
list, as opposed to the public list.</p>
+
<p>These things vary a little from one project to another, so clearly
documenting them for your particular project is critical. And
specifically assigning a PMC mentor to new PMC members can greatly help
that new member get up to speed, and prevent problems in the future.</p>
+
<p>Here’s the basic things that a new PMC member needs to know, and how you
can help them in their new job.</p>
+
<p>TODO</p>
+
<p>Outline:</p>
+
<ul>
<li>The PMC chair is not the project lead</li>
<li>Any PMC member can nominate committers, PMC members</li>
diff --git a/content/newbiefaq.html b/content/newbiefaq.html
index 06700bd..669995d 100644
--- a/content/newbiefaq.html
+++ b/content/newbiefaq.html
@@ -9,11 +9,25 @@
<meta property="og:title" content="Apache Newcomer FAQs" />
<meta property="og:description" content="These answers to frequently asked questions may help newcomers to The Apache Software Foundation (ASF) and our many Apache projects understand how we work.
Index of Questions
-About The Apache Software Foundation How do I find projects or technologies at the ASF? How are projects managed at the ASF? How do I ask a question about the ASF in general? How do I get user support for an Apache project? Getting involved with Apache projects How do I choose an Apache project to work on?" />
+ About The Apache Software Foundation How do I find projects or technologies at the ASF? How are projects managed at the ASF? How do I ask a question about the ASF in general? How do I get user support for an Apache project?" />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/newbiefaq.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="" />
+<meta property="og:url" content="https://community.apache.org/newbiefaq.html" />
+
+
+
+
+<meta property="article:modified_time" content="2023-03-17T12:26:02-04:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2023-03-17T12:26:02-04:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Apache Newcomer FAQs</title>
@@ -183,39 +197,50 @@ About The Apache Software Foundation How do I find projects or technologies at t
<hr>
- <p>These answers to frequently asked questions may help newcomers to
+
+
+<p>These answers to frequently asked questions may help newcomers to
The Apache Software Foundation (ASF) and our many Apache projects understand how we work.</p>
+
<p><em>Index of Questions</em></p>
+
<ul>
<li><a href="#NewbieFAQ-AboutTheApacheSoftwareFoundation">About The Apache Software Foundation</a>
+
<ul>
<li><a href="#NewbieFAQ-WhatprojectscanIfindinTheApacheSoftwareFoundation?">How do I find projects or technologies at the ASF?</a></li>
<li><a href="#NewbieFAQ-HowareprojectsmanagedinTheApacheSoftwareFoundation">How are projects managed at the ASF?</a></li>
<li><a href="#NewbieFAQ-HowdoIaskaquestionabouttheASFingeneral?">How do I ask a question about the ASF in general?</a></li>
<li><a href="#NewbieFAQ-HowdoIgetusersupportforanASFproject?">How do I get user support for an Apache project?</a></li>
-</ul>
-</li>
+</ul></li>
<li><a href="#NewbieFAQ-GettingInvolvedwithApacheprojects">Getting involved with Apache projects</a>
+
<ul>
<li><a href="#NewbieFAQ-HowdoIchooseanApacheprojecttoworkon?">How do I choose an Apache project to work on?</a></li>
<li><a href="#NewbieFAQ-HowdoIgetinvolvedwithanApacheproject?">How do I get involved with an Apache project?</a></li>
<li><a href="#NewbieFAQ-IsthereaCodeofConductforApacheprojects?">Is there a Code of Conduct for Apache projects?</a></li>
-</ul>
-</li>
+</ul></li>
<li><a href="#websitecms">How do I suggest or make changes to this website?</a></li>
<li><a href="#comdevweb">What other useful websites about Apache are there?</a></li>
-<li><a href="#comdevbug">How do I report a bug for Comdev websites or tools?</a></li>
+<li><a href="#comdevbug">How do I report a bug for Comdev websites or tools?</a><br /></li>
</ul>
+
<p>We are always looking for better ways to help newcomers to the ASF find
the information they’re looking for. Please ask questions or give us suggestions on
<a href="mailto:dev@community.apache.org">dev@community.apache.org</a> (subscribe by sending an email to
<a href="mailto:dev-subscribe@community.apache.org">dev-subscribe@community.apache.org</a> first).</p>
+
<p><a name="NewbieFAQ-AboutTheApacheSoftwareFoundation"></a></p>
-<h1 id="about-the-apache-software-foundation">About The Apache Software Foundation <a class="headerlink" title="Permalink" href="#about-the-apache-software-foundation">¶</a></h1>
+
+<h1 id="about-the-apache-software-foundation">About The Apache Software Foundation</h1>
+
<p><a name="NewbieFAQ-WhatprojectscanIfindinTheApacheSoftwareFoundation?"></a></p>
-<h2 id="what-projects-can-i-find-in-the-apache-software-foundation">What projects can I find in The Apache Software Foundation? <a class="headerlink" title="Permalink" href="#what-projects-can-i-find-in-the-apache-software-foundation">¶</a></h2>
+
+<h2 id="what-projects-can-i-find-in-the-apache-software-foundation">What projects can I find in The Apache Software Foundation?</h2>
+
<p>There are over 350 separate projects and communities hosted at the Apache Software Foundation. We have
three classes, or types, of project (in terms of their community, not in terms of technology):</p>
+
<ul>
<li><a href="https://projects.apache.org">Top Level Projects</a> (TLPs): these are projects with healthy communities and active development; and supported software products you can find here: <a href="https://projects.apache.org/">listing by technologies</a>.</li>
<li><a href="https://incubator.apache.org">Incubating Projects</a>: these are projects that have yet to build a sustainable community, but
@@ -223,8 +248,11 @@ have active development and are moving towards graduating to become TLPs.</li>
<li><a href="https://attic.apache.org">Attic</a>: these are end-of-life projects that are no longer receiving active
development, but may still be useful.</li>
</ul>
+
<p><a name="NewbieFAQ-HowareprojectsmanagedinTheApacheSoftwareFoundation"></a></p>
-<h2 id="how-are-projects-managed-in-the-apache-software-foundation">How are projects managed in the Apache Software Foundation? <a class="headerlink" title="Permalink" href="#how-are-projects-managed-in-the-apache-software-foundation">¶</a></h2>
+
+<h2 id="how-are-projects-managed-in-the-apache-software-foundation">How are projects managed in the Apache Software Foundation?</h2>
+
<p>Apache project participants all believe that if we look after the community, good
code will emerge from that community. That is, when people with similar
needs come together, they will work out a way to solve their common
@@ -235,34 +263,45 @@ However, these communities seek to be flat in structure. No single person
in any community has more influence than the next; a newcomer with a good
idea has just as much input and influence as the original creator of the
project.</p>
+
<p>We do have a system, <em>meritocracy</em>, that allows those who have
demonstrated commitment and understanding to the community to earn certain
privileges, such as being able to make changes directly to documentation
and program code. However, these privileges simply streamline the
process; they do not (in most cases) give additional powers over the
project.</p>
+
<p>In summary, Apache projects work because people like you participate
constructively within them!</p>
+
<p>To learn more about “The Apache Way” in general, see the <a href="https://apache.org/foundation/how-it-works.html">How it Works</a>
-pages. We also have <a href="https://www.apache.org/foundation/governance/">detailed overviews of how the ASF and projects are governed</a>.</p>
+ pages. We also have <a href="https://www.apache.org/foundation/governance/">detailed overviews of how the ASF and projects are governed</a>.</p>
+
<p><a name="NewbieFAQ-HowdoIaskaquestionabouttheASFingeneral?"></a></p>
-<h2 id="generalquestion">How do I ask a question about the ASF in general? <a class="headerlink" title="Permalink" href="#generalquestion">¶</a></h2>
+
+<h2 id="generalquestion">How do I ask a question about the ASF in general?</h2>
+
<p>The Community Development Project is here for this very purpose. Check out
the resources on this site first. If you don’t find the answer to your question, send an email
to <code>dev@community.apache.org</code> (subscribe first by sending an email to
<code>dev-subscribe@community.apache.org</code>).</p>
+
<p><a name="NewbieFAQ-HowdoIgetusersupportforanASFproject?"></a></p>
-<h2 id="how-do-i-get-user-support-for-an-asf-project">How do I get user support for an ASF project? <a class="headerlink" title="Permalink" href="#how-do-i-get-user-support-for-an-asf-project">¶</a></h2>
+
+<h2 id="how-do-i-get-user-support-for-an-asf-project">How do I get user support for an ASF project?</h2>
+
<p>Everyone active in ASF projects is here as a volunteer. You need to be
careful not to waste people’s time, so do your homework. Generally, if
people can see that you have tried to solve your problem before asking for help, they are more
likely to respond. So, before asking a question, do the following:</p>
+
<ul>
<li>Search that project’s documentation</li>
<li>Search that <a href="https://mail-archives.apache.org/mod_mbox/">project’s user@ mailing list archives</a></li>
<li>Search the project issue tracker for any related known issues</li>
<li>Search the web in general</li>
</ul>
+
<p>If you don’t find a solution, send a concise, but detailed, request for
support to the appropriate <code>users@</code> mailing list (you will usually need to
subscribe first, by sending an email to <code>users-subscribe@</code>). Indicate that you have read the appropriate documentation
@@ -271,11 +310,13 @@ actually happens. All Apache projects should have a “Mailing List”,
“How to Contribute” or similar link on their home page that tells you how to subscribe
to that project’s specific lists. Mailing lists at Apache are also
<a href="https://mail-archives.apache.org/mod_mbox/">publicly archived</a> at the ASF and <a href="https://apache.markmail.org/">elsewhere</a>.</p>
+
<p>Be patient waiting for a response: give it at least three working days
before you send a second message. People are busy, and they will deal with your
request when they can. If you need urgent help it is best not to rely on
the community support channels, but to find an outside organization willing to support you for
a fee. Remember that committers on Apache mailing lists are generally working as volunteers.</p>
+
<p>It is worth noting that people are more willing to help those who
contribute back to the project in some way. If you hit a problem that was
not documented, it is likely others will, too. A good idea is to propose a
@@ -283,28 +324,39 @@ patch to the project to improve its documentation. Then those
who follow in your footsteps get an answer in the first step above and you
start to build merit in the community that will result in further help in
the future.</p>
+
<p>A second way of contributing is to provide user support to others as your
expertise grows. Again, earning merit in this way will help you to get
the support you need in the future.</p>
+
<p><a name="NewbieFAQ-GettingInvolvedwithApacheprojects"></a></p>
-<h1 id="getting-involved-with-apache-projects">Getting Involved with Apache projects <a class="headerlink" title="Permalink" href="#getting-involved-with-apache-projects">¶</a></h1>
+
+<h1 id="getting-involved-with-apache-projects">Getting Involved with Apache projects</h1>
+
<p><a name="NewbieFAQ-HowdoIchooseanApacheprojecttoworkon?"></a></p>
-<h2 id="how-do-i-choose-an-apache-project-to-work-on">How do I choose an Apache project to work on? <a class="headerlink" title="Permalink" href="#how-do-i-choose-an-apache-project-to-work-on">¶</a></h2>
+
+<h2 id="how-do-i-choose-an-apache-project-to-work-on">How do I choose an Apache project to work on?</h2>
+
<p>The key to working on projects at Apache (and any open source project, for that
matter) is to have a personal reason for being involved. You might be
trying to solve a day job issue, you might be looking to learn a new
technology or you might simply want to do something fun in your free time.
The key is that you must <em>want</em> to get involved. It is also important that
you have appropriate skills to be able to help the project.</p>
+
<p>Our <a href="https://projects.apache.org/">projects page</a> provides a list of projects that you can sort alphabetically, by category or by language. When you view a project’s details
page you can find out about its mailing lists, issue tracker and other resources.</p>
+
<p>In the project’s issue tracker you will find details of bugs and feature
requests the project would like help with. This should give you some
inspiration about how you might be able to help the project community. If
you see an issue you would like to tackle, it’s time to join the project’s
mailing list and get started.</p>
+
<p><a name="NewbieFAQ-HowdoIgetinvolvedwithanApacheproject?"></a></p>
-<h2 id="how-do-i-get-involved-with-an-apache-project">How do I get involved with an Apache project? <a class="headerlink" title="Permalink" href="#how-do-i-get-involved-with-an-apache-project">¶</a></h2>
+
+<h2 id="how-do-i-get-involved-with-an-apache-project">How do I get involved with an Apache project?</h2>
+
<p>You can improve your programming skills by watching the <code>commit</code>
lists, receiving code reviews and participating in discussions. However,
this learning opportunity is a healthy side effect of open source
@@ -312,50 +364,66 @@ activities rather than a goal in itself. Nobody in an Apache project is
going to spend time teaching you Programming 101, technical writing or
testing (to mention just a few of the skills we need). You need to know the basics
and be willing to research the rest.</p>
+
<p>To learn more about getting involved with an Apache Project, see our <a href="/gettingStarted/101.html">getting
started guide</a>. You will also find our <a href="https://apache.org/foundation/getinvolved.html">get involved</a> page a useful starting point.</p>
+
<p><a name="NewbieFAQ-IsthereaCodeofConductforApacheprojects?"></a></p>
-<h2 id="is-there-a-code-of-conduct-for-apache-projects">Is there a Code of Conduct for Apache projects? <a class="headerlink" title="Permalink" href="#is-there-a-code-of-conduct-for-apache-projects">¶</a></h2>
+
+<h2 id="is-there-a-code-of-conduct-for-apache-projects">Is there a Code of Conduct for Apache projects?</h2>
+
<p>Our code of conduct is posted at
<a href="https://www.apache.org/foundation/policies/conduct.html">https://www.apache.org/foundation/policies/conduct.html</a>.
The ASF expects that everyone participating on an Apache project, whether it be improving websites; contributing to email lists, bugtrackers, or forums hosted at <code>apache.org</code>; or contributing code will abide by our code of conduct.</p>
+
<p>PMCs are allowed to define their own additional codes of conduct for their individual communities, but all PMCs are expected to abide by the Foundation-wide policy.</p>
+
<p>The <a href="https://incubator.apache.org/guides/committer.html">Incubator document</a> also
has some really useful information for both the newbie and the
old hands. The section on <strong>ASF Mottos</strong> is especially useful as a reminder of the way things are in most ASF
projects. This section includes such gems as:</p>
+
<ul>
<li>Put community before code.</li>
<li>Let them who do the work make the decisions.</li>
<li>If it didn’t happen on a mailing list, it didn’t happen.</li>
<li>Don’t feed the trolls.</li>
</ul>
-<h1 id="websitecms">How do I suggest changes to this website? <a class="headerlink" title="Permalink" href="#websitecms">¶</a></h1>
+
+<h1 id="websitecms">How do I suggest changes to this website?</h1>
+
<p>The content for the <code>community.apache.org</code> website is written in Markdown
and published automatically using a <a href="https://builds.apache.org/job/comdev-site/">Jenkins job</a>.
Any contributor is able to submit changes via pull requests. Comdev committers are able to merge
proposed changes.</p>
-<p>Website sources are available via:</p>
-<ul>
-<li>GitHub: <a href="https://github.com/apache/comdev-site">https://github.com/apache/comdev-site</a></li>
-<li>Gitbox: <a href="https://gitbox.apache.org/repos/asf/comdev-site.git">https://gitbox.apache.org/repos/asf/comdev-site.git</a></li>
-</ul>
+
+<p>Website sources are available via:
+- GitHub: <a href="https://github.com/apache/comdev-site">https://github.com/apache/comdev-site</a>
+- Gitbox: <a href="https://gitbox.apache.org/repos/asf/comdev-site.git">https://gitbox.apache.org/repos/asf/comdev-site.git</a></p>
+
<p>For general questions you can <a href="#generalquestion">ask us on dev@community</a>
or read our <a href="https://lists.apache.org/list.html?dev@community.apache.org:lte=3M:">mailing list archives</a> for past questions and answers.</p>
+
<p>For technical website details, see <a href="/about/#about-this-website">About this Website</a>.
To submit a formal bug, see our <a href="#comdevbug">COMDEV JIRA</a>.</p>
-<h1 id="comdevweb">What else does Community Development publish or manage? <a class="headerlink" title="Permalink" href="#comdevweb">¶</a></h1>
+
+<h1 id="comdevweb">What else does Community Development publish or manage?</h1>
+
<p>The Community Development project maintains several other tools
that help you navigate the ASF.</p>
+
<ul>
<li>The <a href="https://projects.apache.org/">Apache Projects Directory</a> lists all our software technologies, and you can learn <a href="https://projects.apache.org/about.html">how it works</a> and what JSON data feeds are available.</li>
-<li><a href="https://home.apache.org/">Home.apache.org</a> serves as a telephone directory of all Apache committers.</li>
+<li><a href="https://home.apache.org/">Home.apache.org</a> serves as a telephone directory of all Apache committers.<br /></li>
<li>Apache committers can log in to the <a href="https://reporter.apache.org/">Project Reporting Tool</a> that helps PMCs create quarterly board reports; you can <a href="https://svn.apache.org/repos/asf/comdev/reporter.apache.org/">see the code that does this</a>.</li>
<li>A <a href="https://cwiki.apache.org/confluence/display/COMDEV/ComDev+Wiki">ComDev Wiki</a> is also available for scratch or experimental work, although most permanent content should be here in the website.</li>
</ul>
-<h1 id="comdevbug">How do I report a bug for Comdev websites or tools? <a class="headerlink" title="Permalink" href="#comdevbug">¶</a></h1>
+
+<h1 id="comdevbug">How do I report a bug for Comdev websites or tools?</h1>
+
<p>The Community Development project has a Jira issue tracker queue where you
can submit bug reports related to any of our services or websites.</p>
+
<ul>
<li><a href="https://issues.apache.org/jira/browse/COMDEV">https://issues.apache.org/jira/browse/COMDEV</a></li>
</ul>
diff --git a/content/newcomers/index.html b/content/newcomers/index.html
index 7959a6a..cf5d49a 100644
--- a/content/newcomers/index.html
+++ b/content/newcomers/index.html
@@ -9,7 +9,21 @@
<meta property="og:title" content="Welcome, Apache newcomers!" />
<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/newcomers/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+<meta property="og:url" content="https://community.apache.org/newcomers/" />
+
+
+
+<meta property="og:updated_time" content="2023-03-29T11:49:44+02:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
<title>Apache Community Development - Welcome, Apache newcomers!</title>
@@ -182,10 +196,13 @@
<hr>
- <p>In this section we’ll help you take your first steps as an open source
+
+
+<p>In this section we’ll help you take your first steps as an open source
developer in one of our many Apache project communities. As an all-volunteer
run organization, Apache and the many Apache projects rely on people like
you stepping up to help out.</p>
+
<ul>
<li><a href="/gettingStarted/101.html">Where do I start?</a> - a guide to your first engagement with an Apache project</li>
<li><a href="/contributors/etiquette">How should I behave?</a> - etiquette and codes of conduct at Apache</li>
@@ -193,17 +210,23 @@ you stepping up to help out.</p>
<li><a href="https://projects.apache.org/">How many projects are at Apache?</a> - we have a <strong>LOT</strong> of different project communities!</li>
<li><a href="https://www.apache.org/dev/">Just show me the code!</a> - site index of technical questions (where’s SVN, how to log in, etc.)</li>
</ul>
+
<p><a name="Index-FirstContributions"></a></p>
-<h1 id="first-contributions">First Contributions <a class="headerlink" title="Permalink" href="#first-contributions">¶</a></h1>
+
+<h1 id="first-contributions">First Contributions</h1>
+
<p><em>The more you give the more you get out</em>.</p>
+
<p>It’s natural to assume that, as a newcomer,
you have little to offer the ASF. However, you will be surprised at
how much you can help, even now.</p>
+
<p>Since we aim to be a place for newcomers to learn
about the ASF as a whole and you are (probably) a newcomer, <em>any feedback
you can give or unanswered questions you can ask us here</em> will help us improve what
we offer to those who come after you. Our <a href="/contributors/etiquette">etiquette tips</a> can help you
write emails that will get some answers.</p>
+
<p>You can provide feedback on this website and ask questions about anything Apache by subscribing to our mailing
list. Send an email to
<a href="mailto:dev-subscribe@community.apache.org">dev-subscribe@community.apache.org</a>. Once subscribed you can send your questions or feedback to
diff --git a/content/newcomers/index.xml b/content/newcomers/index.xml
index 7caf9d2..214bfe8 100644
--- a/content/newcomers/index.xml
+++ b/content/newcomers/index.xml
@@ -1,10 +1,15 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Welcome, Apache newcomers! on Apache Comdev</title>
<link>https://community.apache.org/newcomers/</link>
<description>Recent content in Welcome, Apache newcomers! on Apache Comdev</description>
<generator>Hugo -- gohugo.io</generator>
- <language>en</language><atom:link href="https://community.apache.org/newcomers/index.xml" rel="self" type="application/rss+xml" />
+ <language>en</language>
+ <lastBuildDate>Wed, 29 Mar 2023 11:49:44 +0200</lastBuildDate>
+
+ <atom:link href="https://community.apache.org/newcomers/index.xml" rel="self" type="application/rss+xml" />
+
+
</channel>
-</rss>
+</rss>
\ No newline at end of file
diff --git a/content/newcommitter.html b/content/newcommitter.html
index 410eb36..2155cae 100644
--- a/content/newcommitter.html
+++ b/content/newcommitter.html
@@ -9,11 +9,25 @@
<meta property="og:title" content="New Committer" />
<meta property="og:description" content="Identifying potential new committers, calling a vote for their recognition as a committer and processing the relevant documents are tasks to which the whole community can contribute.
Each project has a different approach to managing new committers. This page describes a common process found in many Apache projects. It also provides drafts for the various communications that are necessary.
-Guidelines for assessing new candidates for committership Ability to work cooperatively with peers." />
+ Guidelines for assessing new candidates for committership Ability to work cooperatively with peers." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/newcommitter.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="" />
+<meta property="og:url" content="https://community.apache.org/newcommitter.html" />
+
+
+
+
+<meta property="article:modified_time" content="2023-03-29T19:28:51+01:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2023-03-29T19:28:51+01:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - New Committer</title>
@@ -183,169 +197,227 @@ Guidelines for assessing new candidates for committership Ability to work cooper
<hr>
- <p>Identifying potential new committers, calling a vote for their recognition
+
+
+<p>Identifying potential new committers, calling a vote for their recognition
as a committer and processing the relevant documents are tasks to which
the whole community can contribute.</p>
+
<p>Each project has a different approach to managing new committers. This page
describes a common process found in many Apache projects. It also provides
drafts for the various communications that are necessary.</p>
+
<nav id="TableOfContents">
- <ul>
- <li><a href="#guidelines-for-assessing-new-candidates-for-committership">Guidelines for assessing new candidates for committership</a>
- <ul>
- <li><a href="#ability-to-work-cooperatively-with-peers">Ability to work cooperatively with peers.</a></li>
- <li><a href="#ability-to-be-a-mentor">Ability to be a mentor.</a></li>
- <li><a href="#community">Community</a></li>
- <li><a href="#commitment">Commitment</a></li>
- <li><a href="#personal-skillability">Personal skill/ability</a></li>
- </ul>
- </li>
- <li><a href="#new-committer-process">New Committer Process</a>
- <ul>
- <li><a href="#summary">Summary</a></li>
- <li><a href="#discussion">Discussion</a></li>
- </ul>
- </li>
- <li><a href="#email-templates">Email Templates</a>
- <ul>
- <li><a href="#committer-vote-template">Committer Vote Template</a></li>
- <li><a href="#pmc-vote-template">PMC Vote Template</a></li>
- <li><a href="#close-vote">Close Vote</a></li>
- <li><a href="#notify-board-of-new-pmc-member">Notify Board of new PMC member</a></li>
- <li><a href="#committer-invite-template">Committer Invite Template</a></li>
- <li><a href="#committer-account-creation">Committer Account Creation</a></li>
- <li><a href="#committer-announce-template">Committer Announce Template</a></li>
- <li><a href="#committer-done-template">Committer Done Template</a></li>
- </ul>
- </li>
- </ul>
+<ul>
+<li>
+<ul>
+<li><a href="#guidelines-for-assessing-new-candidates-for-committership">Guidelines for assessing new candidates for committership</a>
+<ul>
+<li><a href="#ability-to-work-cooperatively-with-peers">Ability to work cooperatively with peers.</a></li>
+<li><a href="#ability-to-be-a-mentor">Ability to be a mentor.</a></li>
+<li><a href="#community">Community</a></li>
+<li><a href="#commitment">Commitment</a></li>
+<li><a href="#personal-skill-ability">Personal skill/ability</a></li>
+</ul></li>
+<li><a href="#new-committer-process">New Committer Process</a>
+<ul>
+<li><a href="#summary">Summary</a></li>
+<li><a href="#discussion">Discussion</a></li>
+</ul></li>
+<li><a href="#email-templates">Email Templates</a>
+<ul>
+<li><a href="#committer-vote-template">Committer Vote Template</a></li>
+<li><a href="#pmc-vote-template">PMC Vote Template</a></li>
+<li><a href="#close-vote">Close Vote</a></li>
+<li><a href="#notify-board-of-new-pmc-member">Notify Board of new PMC member</a></li>
+<li><a href="#committer-invite-template">Committer Invite Template</a></li>
+<li><a href="#committer-account-creation">Committer Account Creation</a></li>
+<li><a href="#committer-announce-template">Committer Announce Template</a></li>
+<li><a href="#committer-done-template">Committer Done Template</a></li>
+</ul></li>
+</ul></li>
+</ul>
</nav>
+
<p><a name="NewCommitter-Guidelinesforassessingnewcandidatesforcommittership"></a></p>
-<h2 id="guidelines-for-assessing-new-candidates-for-committership">Guidelines for assessing new candidates for committership <a class="headerlink" title="Permalink" href="#guidelines-for-assessing-new-candidates-for-committership">¶</a></h2>
+
+<h2 id="guidelines-for-assessing-new-candidates-for-committership">Guidelines for assessing new candidates for committership</h2>
+
<p>When voting, all PMC members need to make up their own minds as to whether a candidate
should be approved to become a committer. They might search mailing lists and Jira to see
how the candidate interacts with others, and the contributions (code or doc patches, suggestions, engagement in conversation) they have made.</p>
+
<p>All new committers <strong>must</strong> adhere to the <a href="https://www.apache.org/foundation/policies/conduct.html">Apache Code of Conduct</a>.</p>
+
<p>Each PMC may want to create their own supplemental committer guidelines; here are the <a href="https://forrest.apache.org/committed.html">Apache Forrest committer guidelines</a>.</p>
+
<p>The following are some points to consider when assessing a candidate’s qualifications for committership.</p>
+
<p><a name="NewCommitter-Abilitytoworkco-operativelywithpeers."></a></p>
-<h3 id="ability-to-work-cooperatively-with-peers">Ability to work cooperatively with peers. <a class="headerlink" title="Permalink" href="#ability-to-work-cooperatively-with-peers">¶</a></h3>
+
+<h3 id="ability-to-work-cooperatively-with-peers">Ability to work cooperatively with peers.</h3>
+
<p>How do we evaluate?</p>
+
<ul>
<li>By the interactions they have through email.</li>
<li>By how they respond to criticism.</li>
<li>By how they participate in the group decision-making process.</li>
</ul>
+
<p><a name="NewCommitter-Abilitytobeamentor."></a></p>
-<h3 id="ability-to-be-a-mentor">Ability to be a mentor. <a class="headerlink" title="Permalink" href="#ability-to-be-a-mentor">¶</a></h3>
+
+<h3 id="ability-to-be-a-mentor">Ability to be a mentor.</h3>
+
<p>How do we evaluate?</p>
+
<ul>
<li>By the interactions they have through email.</li>
<li>By how clear they are and how willing they are to identify or even create appropriate background
materials.</li>
</ul>
+
<p><a name="NewCommitter-Community"></a></p>
-<h3 id="community">Community <a class="headerlink" title="Permalink" href="#community">¶</a></h3>
+
+<h3 id="community">Community</h3>
+
<p>How do we evaluate?</p>
+
<ul>
<li>By the interactions they have through email.</li>
<li>Do they help to answer questions raised on the mailing list; do they show a helpful
attitude and respect for other people’s ideas?</li>
</ul>
+
<p><a name="NewCommitter-Committment"></a></p>
-<h3 id="commitment">Commitment <a class="headerlink" title="Permalink" href="#commitment">¶</a></h3>
+
+<h3 id="commitment">Commitment</h3>
+
<p>How do we evaluate?</p>
+
<ul>
<li>By time already given to the project.</li>
<li>By how well they stick with the process through tough issues.</li>
<li>By how they help on not-so-fun tasks.</li>
</ul>
+
<p><a name="NewCommitter-Personalskill/ability"></a></p>
-<h3 id="personal-skillability">Personal skill/ability <a class="headerlink" title="Permalink" href="#personal-skillability">¶</a></h3>
+
+<h3 id="personal-skill-ability">Personal skill/ability</h3>
+
<p>How do we evaluate?</p>
+
<ul>
<li>A solid general understanding of the project.</li>
<li>Quality of discussion in email.</li>
<li>Whether their patches (where applicable) are easy to apply with only a cursory review.</li>
</ul>
+
<p><a name="NewCommitter-NewCommitterProcess"></a></p>
-<h2 id="new-committer-process">New Committer Process <a class="headerlink" title="Permalink" href="#new-committer-process">¶</a></h2>
+
+<h2 id="new-committer-process">New Committer Process</h2>
+
<p>This section describes a typical Apache project’s process for handling the
vote to add a new committer. Templates mentioned in the process appear
later in this document.</p>
+
<p><a name="NewCommitter-Summary"></a></p>
-<h3 id="summary">Summary <a class="headerlink" title="Permalink" href="#summary">¶</a></h3>
+
+<h3 id="summary">Summary</h3>
+
<ol>
<li>Discuss the proposed committer or PMC member. If the discussion seems to be going positively, call a vote (templates/committerVote.txt)</li>
<li>Close the vote (templates/closeVote.txt)</li>
<li>If the result is positive, invite the new committer (templates/committerInvite.txt)</li>
</ol>
+
<p>If they accept, then:</p>
+
<ol>
<li>If they already have an Apache id, grant appropriate commit privileges.
Use the Whimsy tool to update the roster via <a href="https://whimsy.apache.org/roster/committee/">https://whimsy.apache.org/roster/committee/</a> or <a href="https://whimsy.apache.org/roster/ppmc/">https://whimsy.apache.org/roster/ppmc/</a></li>
<li>If they have already filed an ICLA, request creation of the committer account.
If they need to change anything in a previously filed ICLA, wait until the new ICLA is filed,
then request the account.
+
<ol>
<li>Wait until root says it is done</li>
<li>PMC Chair updates LDAP group membership which enables svn, gitbox and other access.
If the committer uses GitHub, they are responsible for linking it to their ASF account.</li>
<li>Add committer to the appropriate groups in Jira and CWiki</li>
-</ol>
-</li>
+</ol></li>
<li>Notify the committer of completion (template/committerDone.txt)</li>
<li>If committer is also to be a PMC member, PMC Chair sends email to board@ asking for acknowledgement of new PMC member
(templates/email-member-ack.txt)</li>
<li>Announce the new committer (template/committerAnnounce.txt)</li>
</ol>
+
<p><a name="NewCommitter-Discussion"></a></p>
-<h3 id="discussion">Discussion <a class="headerlink" title="Permalink" href="#discussion">¶</a></h3>
+
+<h3 id="discussion">Discussion</h3>
+
<p>We do the discussion and vote on the <code>private@</code> mailing list to enable a frank
discussion. Any PMC member may propose a potential committer or PMC
member. This is <strong>not</strong> the sole responsibility or right of the PMC
chair.</p>
+
<p>We invite people to join as committers/PMC members, not github ids. It is
fine to refer to the candidate’s github id for context, but the person should
be referred to by their name. It is not necessary to have their full legal
name (that will be kept private) but it is important to use their name, as
they refer to themselves in email. If a person is known only by their github
id, it is ok to ask them for their real name prior to holding a VOTE.</p>
+
<p>Start a separate [VOTE] thread for each new person. This makes it much easier
to review the email archives.</p>
+
<p>We need to be sure that they are committed people with whom we can work.
They will be our peers. We will have already observed that they are
committed to the project and graceful toward users and other developers.</p>
+
<p>Don’t wait too long before proposing and don’t be too hasty. There is a
trade-off and something about timeliness. A point is reached where it
becomes obvious that we should invite them. This encourages them and keeps
them enthusiastic. If we leave it too long, then we risk them becoming
disillusioned.</p>
+
<p>On the <code>private@</code> list we can each say exactly what we feel about each person,
with no holds barred. Keep the discussion concise. The praise part can
be done later in public. Keep in mind, however, that if the member becomes
a PMC member later, they will have access to this discussion.</p>
+
<p>Let the Vote thread run for one week.</p>
+
<p>A positive result is achieved by <strong>Consensus Approval</strong>: at least 3 +1
votes and no vetoes.</p>
+
<p>Any veto must be accompanied by reasoning and the vetoer must be prepared to defend it.
Other members can attempt to encourage them to change their mind.</p>
+
<p>New committers can be either quiet or active as they choose. If we find
that certain people lapse and don’t ever contribute, then the project can take steps
to retire them.</p>
+
<p>After a positive result, record the result on the PMC list with a [RESULT][VOTE] subject
and then invite the candidate. We give candidates a chance to decline committership in private. They
can post a reply to the PMC mailing list.</p>
+
<p>After we reach a decision on the <code>private@</code> list, and after the steps above, we
announce the new committer on the <code>dev</code> list. We can then each follow up with
our praise in public.</p>
+
<p>Other notes about the process are available on the main <a href="https://www.apache.org/dev/pmc.html#newcommitter">Apache site</a>.</p>
+
<p><a name="NewCommitter-EmailTemplates"></a></p>
-<h2 id="email-templates">Email Templates <a class="headerlink" title="Permalink" href="#email-templates">¶</a></h2>
-<h3 id="committer-vote-template">Committer Vote Template <a class="headerlink" title="Permalink" href="#committer-vote-template">¶</a></h3>
+
+<h2 id="email-templates">Email Templates</h2>
+
+<h3 id="committer-vote-template">Committer Vote Template</h3>
+
<p>This is the email to commence a vote for a new committer.
Some projects make committers PMC members automatically. If this is the case,
merge this template with the following one (PMC Vote Template).</p>
+
<pre><code>------------------------------------------------------------
To: private@[PROJECT].apache.org
Subject: [VOTE] New committer: Jo Bloggs
@@ -360,10 +432,13 @@ https://community.apache.org/newcommitter.html
------------------------------------------------------------
</code></pre>
-<h3 id="pmc-vote-template">PMC Vote Template <a class="headerlink" title="Permalink" href="#pmc-vote-template">¶</a></h3>
+
+<h3 id="pmc-vote-template">PMC Vote Template</h3>
+
<p>This is the email to commence a vote for a new <strong>PMC candidate</strong>. New PMC members need
to be voted for by the existing PMC members and subsequently approved by the Board
(or Incubator PMC for incubating projects).</p>
+
<pre><code>------------------------------------------------------------
To: private@[PROJECT].apache.org
Subject: [VOTE] New PMC candidate: Jo Bloggs
@@ -376,8 +451,11 @@ https://www.timeanddate.com/counters/customcounter.html?year=YYYY&month=MM&a
See voting guidelines at
https://community.apache.org/newcommitter.html
</code></pre>
-<h3 id="close-vote">Close Vote <a class="headerlink" title="Permalink" href="#close-vote">¶</a></h3>
+
+<h3 id="close-vote">Close Vote</h3>
+
<p>This email ends the vote and reports the result to the project.</p>
+
<pre><code>------------------------------------------------------------
To: private@[PROJECT].a.o
Subject: [RESULT] [VOTE] New committer (or PMC candidate): Jo Bloggs
@@ -392,16 +470,21 @@ Binding Votes:
The vote is ***successful/not successful***
</code></pre>
-<h3 id="notify-board-of-new-pmc-member">Notify Board of new PMC member <a class="headerlink" title="Permalink" href="#notify-board-of-new-pmc-member">¶</a></h3>
+
+<h3 id="notify-board-of-new-pmc-member">Notify Board of new PMC member</h3>
+
<p>See <a href="https://www.apache.org/dev/pmc.html#newpmc">https://www.apache.org/dev/pmc.html#newpmc</a></p>
-<h3 id="committer-invite-template">Committer Invite Template <a class="headerlink" title="Permalink" href="#committer-invite-template">¶</a></h3>
+
+<h3 id="committer-invite-template">Committer Invite Template</h3>
+
<p>This is the suggested invitation email to send to the newly elected committer,
sent after a positive result from the vote for a new committer.</p>
+
<pre><code>------------------------------------------------------------
To: JoBloggs@foo.net
Cc: private@[PROJECT].apache.org
Subject: Invitation to become [PROJECT] committer: Jo Bloggs
-
+
Hello [invitee name],
The [Project] Project Management Committee (PMC)
@@ -471,24 +554,34 @@ When recording of your ICLA is noted, you will
receive a follow-up message with the next steps for
establishing you as a committer.
</code></pre>
-<h3 id="committer-account-creation">Committer Account Creation <a class="headerlink" title="Permalink" href="#committer-account-creation">¶</a></h3>
+
+<h3 id="committer-account-creation">Committer Account Creation</h3>
+
<p>Follow the instructions
-<a href="https://www.apache.org/dev/pmc.html#newcommitter">here</a>.</p>
+ <a href="https://www.apache.org/dev/pmc.html#newcommitter">here</a>.</p>
+
<p>In summary:</p>
+
<p>If the ICLA identifies the project and a valid Apache ID, and the
[RESULT][VOTE] message has been posted to the PMC private list,
the account creation request is made by the
secretary or assistant who files the ICLA.</p>
+
<p>Otherwise, the new account request should be made by the
PMC Chair (or any <a href="https://www.apache.org/foundation/glossary.html#Member">ASF Member</a> if the chair is unavailable).</p>
+
<p>The PMC chair needs to use the <a href="https://id.apache.org/acreq/pmc-chairs/">ASF New Account Request</a> form to
send a new account request. Members may use <a href="https://id.apache.org/acreq/members/">ASF New Account
Request</a> page.</p>
+
<p>For elections held on public lists, please supply the
<a href="https://mail-archives.apache.org/">mail-archives.apache.org</a> url. For private lists, you can
use the <a href="https://mail-search.apache.org/">Mail Search tool</a> to locate the appropriate url.</p>
-<h3 id="committer-announce-template">Committer Announce Template <a class="headerlink" title="Permalink" href="#committer-announce-template">¶</a></h3>
+
+<h3 id="committer-announce-template">Committer Announce Template</h3>
+
<p>This is the email to announce the new committer to <code>[PROJECT]-dev</code> once the account has been created.</p>
+
<pre><code>------------------------------------------------------------
To: dev@[PROJECT].apache.org
Subject: new committer: ###Jo Bloggs
@@ -504,7 +597,9 @@ project since there is no need to go via the patch
submission process. This should enable better productivity.
A PMC member helps manage and guide the direction of the project.
</code></pre>
-<h3 id="committer-done-template">Committer Done Template <a class="headerlink" title="Permalink" href="#committer-done-template">¶</a></h3>
+
+<h3 id="committer-done-template">Committer Done Template</h3>
+
<pre><code>After the committer account is established.
------------------------------------------------------------
@@ -537,7 +632,7 @@ If using svn, you will probably need to 'svn switch" previous checkouts to
for example:
svn switch --relocate https://svn.apache.org/repos/asf/[PROJECT] https://svn.apache.org/repos/asf/[PROJECT]
-
+
The developer section of the website describes roles within the ASF and provides other
resources:
https://www.apache.org/foundation/how-it-works.html
diff --git a/content/newsletter/2017-04.html b/content/newsletter/2017-04.html
index de1a921..a0b71ac 100644
--- a/content/newsletter/2017-04.html
+++ b/content/newsletter/2017-04.html
@@ -7,14 +7,28 @@
<meta name="keywords" content="apache, apache community, community development, opensource"/>
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="April 2017 Community Newsletter" />
-<meta property="og:description" content="Apache Committer Newsletter, April 2017 ¶ Dear Apache Committer,
+<meta property="og:description" content="Apache Committer Newsletter, April 2017 Dear Apache Committer,
In this newsletter: committer resources you might not know about, Foundation news, and upcoming community events.
Thank you for your hard work on our Apache projects. You are the reason the Foundation exists, and your work is the reason we have the reputation we enjoy.
In our recent community survey, we heard from a lot of you that you want more information about what committer resources are available, how to connect with developers from other projects, and more information about what’s going on in the Foundation at large." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/newsletter/2017-04.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="newsletter" />
+<meta property="og:url" content="https://community.apache.org/newsletter/2017-04.html" />
+
+
+
+
+<meta property="article:modified_time" content="2020-07-20T20:22:04+02:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2020-07-20T20:22:04+02:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - April 2017 Community Newsletter</title>
@@ -190,52 +204,82 @@ In our recent community survey, we heard from a lot of you that you want more in
<hr>
- <h1 id="apache-committer-newsletter-april-2017">Apache Committer Newsletter, April 2017 <a class="headerlink" title="Permalink" href="#apache-committer-newsletter-april-2017">¶</a></h1>
+
+
+<h1 id="apache-committer-newsletter-april-2017">Apache Committer Newsletter, April 2017</h1>
+
<p>Dear Apache Committer,</p>
+
<p>In this newsletter: <a href="#committer-resources">committer resources you might not know about</a>,
<a href="#board-and-member-elections">Foundation news</a>, and <a href="#upcoming-events">upcoming community events</a>.</p>
+
<p>Thank you for your hard work on our Apache projects. You are the reason the Foundation exists, and your work is the reason we have the reputation we enjoy.</p>
+
<p>In our recent community survey, we heard from a lot of you that you want more information about what committer resources are available, how to connect with developers from other projects, and more information about what’s going on in the Foundation at large.</p>
+
<p>In this inaugural edition of the Apache Committers Newsletter, we’re trying to keep the committers better informed about what happens at Apache, and let you know about ways that you can become more involved with the Foundation as a whole.</p>
-<h2 id="committer-resources">Committer Resources <a class="headerlink" title="Permalink" href="#committer-resources">¶</a></h2>
+
+<h2 id="committer-resources">Committer Resources</h2>
+
<p>As we grow larger, it can be harder to stay connected with the larger Apache community. We offer a number of resources that make it easier to stay in touch, and find out what’s going on. We encourage you to take advantage of these opportunities, because the Apache community is what makes Apache work.</p>
+
<p>The <a href="/">Apache Community website</a> - is full of
-resources for committers, from <a href="/committers/">new committer information</a></p>
-<ul>
-<li>to <a href="https://www.apache.org/dev/">developer and contributor information</a></li>
-<li>to <a href="/about/">general information about the services provided by the Community
-Development PMC</a>.</li>
-</ul>
+resources for committers, from <a href="/committers/">new committer information</a>
+ - to <a href="https://www.apache.org/dev/">developer and contributor information</a>
+ - to <a href="/about/">general information about the services provided by the Community
+Development PMC</a>.</p>
+
<p>If you’re going to be traveling somewhere, the best way to find out what
other Apache people are in the area is the Party mailing list -
<a href="https://lists.apache.org/list.html?party@apache.org">party@apache.org</a>.
-Tell us where you’re going to be, and if you’re interested in meeting for dinner or drinks. It’s a great way to feel at home in an unfamiliar city, and also connect with other Apache community members. Subscribe by sending a message to <a href="mailto:party-subscribe@apache.org">party-subscribe@apache.org</a></p>
-<h2 id="board-and-member-elections">Board and Member Elections <a class="headerlink" title="Permalink" href="#board-and-member-elections">¶</a></h2>
+Tell us where you’re going to be, and if you’re interested in meeting for dinner or drinks. It’s a great way to feel at home in an unfamiliar city, and also connect with other Apache community members. Subscribe by sending a message to party-subscribe@apache.org</p>
+
+<h2 id="board-and-member-elections">Board and Member Elections</h2>
+
<p>Apache is governed by a Board of Directors - a 9-member board that keeps the administrative side of things running, and ensures that projects operate according to the Apache Way, in sustainable, independent ways. The board doesn’t tinker in technical decisions, so it’s possible that many committers are unaware that it’s even there. The board is elected once a year by the membership.</p>
+
<p>In the recent members meeting (March 28th) a new board of directors was elected, with two directors leaving the board, and two new directors being added. We thank outgoing directors Isabel Drost-Fromm and and Marvin Humphrey for their service, and welcome Phil Steitz and Ted Dunning for the new term.</p>
-<h2 id="apache-is-18">Apache is 18! <a class="headerlink" title="Permalink" href="#apache-is-18">¶</a></h2>
+
+<h2 id="apache-is-18">Apache is 18!</h2>
+
<p>The Apache Software Foundation turned 18 years old last week!</p>
+
<p>The Foundation was established in March of 1999, by a small group of enthusiasts that wanted to ensure a sustainable future for the projects that they were running. Since that time, we’ve had huge growth, growing from 21 members to 620, from a handful of developers to over 6,000, and from two projects to more than 300, including some of the most important software projects in the industry.</p>
+
<p>Read more in our <a href="https://blogs.apache.org/foundation/entry/the-apache-software-foundation-announces6">official press release</a>.</p>
-<h2 id="upcoming-events">Upcoming Events <a class="headerlink" title="Permalink" href="#upcoming-events">¶</a></h2>
+
+<h2 id="upcoming-events">Upcoming Events</h2>
+
<p>As you all hopefully know by now, <a href="https://apachecon.com/">ApacheCon North America 2017</a>
will be held in Miami, Florida, May 15-18. It will consist of several parallel events, which, together, make up ApacheCon.</p>
+
<p>Apache: Big Data celebrates our presence in the Big Data world, with three days, four tracks of content around our various Big Data projects.</p>
+
<p>Apache: IoT covers our projects in the Internet of Things space.</p>
+
<p>TomcatCon will have content around the ever-popular Tomcat application server, one of the oldest projects at the ASF.</p>
+
<p>CloudStack Collaboration Conference is 2 tracks of content for this popular cloud infrastructure project.</p>
+
<p>The FlexJS Summit will be a developer-focused event to work on the FlexJS project, as well as user-focused sessions.</p>
+
<p>And BarCampApache is our traditional unConference format event, where you can propose and lead sessions on any topic which is relevant to our community.</p>
+
<p>Join us Wednesday night for the Lightning Talks - 5 minute presentations by you, about any topic of interest - sometimes funny, sometimes serious, always fun and informative. This will be followed by an offsite attendee reception where you can meet your colleagues from your project, and other ASF projects.</p>
+
<p>As a committer, you have a deep discount to attend this event, since it is our event, by us and for us, and we want all of our committers to attend. Use the registration code APCOMM17 to register. (Don’t share this with your non-committer colleagues, since we check that you’re a committer when you use this code.)</p>
+
<p>Learn more about ApacheCon, see the schedule, and register, at <a href="https://apachecon.com/">apachecon.com</a></p>
-<h2 id="next-time-">Next Time … <a class="headerlink" title="Permalink" href="#next-time-">¶</a></h2>
+
+<h2 id="next-time">Next Time …</h2>
+
<p>If you want your message to appear in this newsletter, come get
involved in writing it for next time. To get involved in the crafting of
this message, join the <a href="https://lists.apache.org/list.html?dev@community.apache.org">Community Development mailing list</a>
-by sending email to <a href="mailto:dev-subscribe@community.apache.org">dev-subscribe@community.apache.org</a> where we’ll be drafting the next newsletter.</p>
+by sending email to dev-subscribe@community.apache.org where we’ll be drafting the next newsletter.</p>
+
<p>Also, please let us know how we’re doing. Was this newsletter helpful?
-Did you read all of it? Drop us a note at <a href="mailto:dev@community.apache.org">dev@community.apache.org</a> to let us know.</p>
+Did you read all of it? Drop us a note at dev@community.apache.org to let us know.</p>
</div>
diff --git a/content/newsletter/2017-05.html b/content/newsletter/2017-05.html
index ca2e3f2..a0a5b2c 100644
--- a/content/newsletter/2017-05.html
+++ b/content/newsletter/2017-05.html
@@ -11,9 +11,23 @@
(So that we didn’t put them all in the first edition)
If you blog about anything Apache related, you might want to know about http://planet.apache.org/committers/ - the Apache committer blog aggregator. It’s valuable in seeing what the rest of the Apache community is working on. To add yourself to the planet, edit the file https://svn.apache.org/repos/asf/planet/committers.ini in svn. It’s preferable if you use an ‘apache’ tag to separate out the stuff that is relevant to the community." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/newsletter/2017-05.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="newsletter" />
+<meta property="og:url" content="https://community.apache.org/newsletter/2017-05.html" />
+
+
+
+
+<meta property="article:modified_time" content="2020-07-20T20:22:04+02:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2020-07-20T20:22:04+02:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - May 2017 Community Newsletter</title>
@@ -190,8 +204,11 @@ If you blog about anything Apache related, you might want to know about http://p
<hr>
<p>Committer Resources</p>
+
<p>(So that we didn’t put them all in the first edition)</p>
-<p>If you blog about anything Apache related, you might want to know about <a href="http://planet.apache.org/committers/">http://planet.apache.org/committers/</a> - the Apache committer blog aggregator. It’s valuable in seeing what the rest of the Apache community is working on. To add yourself to the planet, edit the file <a href="https://svn.apache.org/repos/asf/planet/committers.ini">https://svn.apache.org/repos/asf/planet/committers.ini</a> in svn. It’s preferable if you use an ‘apac [...]
+
+<p>If you blog about anything Apache related, you might want to know about <a href="http://planet.apache.org/committers/">http://planet.apache.org/committers/</a> - the Apache committer blog aggregator. It’s valuable in seeing what the rest of the Apache community is working on. To add yourself to the planet, edit the file <a href="https://svn.apache.org/repos/asf/planet/committers.ini">https://svn.apache.org/repos/asf/planet/committers.ini</a> in svn. It’s preferable if you use an ‘apac [...]
+
<p>Every week Sally Khudairi, our VP Marketing, posts an update of what’s going on across the Foundation. You can always find these at the Apache blog - <a href="https://blogs.apache.org/foundation/">https://blogs.apache.org/foundation/</a> - or by following our official Twitter stream, @TheASF ( <a href="https://twitter.com/theasf">https://twitter.com/theasf</a> ). Our community Facebook page is at <a href="http://facebook.com/ApacheSoftwareFoundation">http://facebook.com/ApacheSoftware [...]
diff --git a/content/newsletter/index.html b/content/newsletter/index.html
index 50118c0..4a86d4a 100644
--- a/content/newsletter/index.html
+++ b/content/newsletter/index.html
@@ -9,7 +9,21 @@
<meta property="og:title" content="Newsletter" />
<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/newsletter/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+<meta property="og:url" content="https://community.apache.org/newsletter/" />
+
+
+
+<meta property="og:updated_time" content="2023-03-29T11:49:44+02:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
<title>Apache Community Development - Newsletter</title>
@@ -182,13 +196,17 @@
<hr>
- <h1 id="community-development-newsletter">Community Development Newsletter <a class="headerlink" title="Permalink" href="#community-development-newsletter">¶</a></h1>
+
+
+<h1 id="community-development-newsletter">Community Development Newsletter</h1>
+
<p>The Community Development project has started a monthly newsletter, to
keep the larger Apache Community informed of what’s happening across the
Foundation. If you would like to contribute content to this newsletter,
please join the <a href="https://lists.apache.org/list.html?dev@community.apache.org">ComDev mailing
list</a>
where this message is drafted.</p>
+
<ul>
<li><a href="2017-04">April 2017</a></li>
</ul>
diff --git a/content/newsletter/index.xml b/content/newsletter/index.xml
index 8fd5ad9..bd2fc4b 100644
--- a/content/newsletter/index.xml
+++ b/content/newsletter/index.xml
@@ -1,18 +1,23 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Newsletter on Apache Comdev</title>
<link>https://community.apache.org/newsletter/</link>
<description>Recent content in Newsletter on Apache Comdev</description>
<generator>Hugo -- gohugo.io</generator>
- <language>en</language><atom:link href="https://community.apache.org/newsletter/index.xml" rel="self" type="application/rss+xml" />
+ <language>en</language>
+ <lastBuildDate>Wed, 29 Mar 2023 11:49:44 +0200</lastBuildDate>
+
+ <atom:link href="https://community.apache.org/newsletter/index.xml" rel="self" type="application/rss+xml" />
+
+
<item>
<title>April 2017 Community Newsletter</title>
<link>https://community.apache.org/newsletter/2017-04.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/newsletter/2017-04.html</guid>
- <description>Apache Committer Newsletter, April 2017 &para; Dear Apache Committer,
+ <description>Apache Committer Newsletter, April 2017 Dear Apache Committer,
In this newsletter: committer resources you might not know about, Foundation news, and upcoming community events.
Thank you for your hard work on our Apache projects. You are the reason the Foundation exists, and your work is the reason we have the reputation we enjoy.
In our recent community survey, we heard from a lot of you that you want more information about what committer resources are available, how to connect with developers from other projects, and more information about what’s going on in the Foundation at large.</description>
@@ -30,4 +35,4 @@ If you blog about anything Apache related, you might want to know about http://p
</item>
</channel>
-</rss>
+</rss>
\ No newline at end of file
diff --git a/content/projectIndependence.html b/content/projectIndependence.html
index b6b6f3c..4e21bf1 100644
--- a/content/projectIndependence.html
+++ b/content/projectIndependence.html
@@ -10,9 +10,23 @@
<meta property="og:description" content="While not all ASF projects practice all aspects of the Apache Way in the same way, there are a number of rules and policies that Apache projects must follow – things like complying with PMC release voting, legal policy, brand policy, using mailing lists, etc., which are documented in various places.
A community is not merely a set of rules; it is also a set of behaviors that the participants express when interacting within that community." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/projectIndependence.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="" />
+<meta property="og:url" content="https://community.apache.org/projectIndependence.html" />
+
+
+
+
+<meta property="article:modified_time" content="2022-01-07T11:22:24-08:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2022-01-07T11:22:24-08:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Project Independence</title>
@@ -182,15 +196,19 @@ A community is not merely a set of rules; it is also a set of behaviors that the
<hr>
- <p>While not all ASF projects practice all aspects of the Apache Way in the same way, there are a number of rules and policies that Apache
+
+
+<p>While not all ASF projects practice all aspects of the Apache Way in the same way, there are a number of rules and policies that Apache
projects must follow – things like complying with PMC
<a href="https://www.apache.org/legal/release-policy.html">release voting</a>, <a href="https://www.apache.org/legal/">legal policy</a>, <a href="https://www.apache.org/foundation/marks/">brand policy</a>,
using <a href="https://www.apache.org/dev/#mail">mailing lists</a>, etc., which are <a href="https://blogs.apache.org/comdev/entry/what_makes_apache_projects_different">documented in various places</a>.</p>
+
<p>A community is not merely a set of rules; it is also a set of behaviors
that the participants express when interacting within that
community. While the ASF is happy to host
many different styles of project communities, there are some core behaviors that
we expect and require of any Apache project.</p>
+
<p>A primary purpose of the basic requirements the ASF places on its
projects is to help ensure long-lived and stable projects by having
a broad-enough community to maintain the project even in the
@@ -199,50 +217,68 @@ in that area. The <a href="https://www.apache.org/foundation/governance/">Apache
on a diverse community. This is different from other governance models,
like the “benevolent dictator” idea or the corporate-backed model that projects like
Eclipse use.</p>
+
<p><strong>Please Note:</strong> These requirements apply to <em>Apache projects</em>: that is,
to individual committer and PMC member behaviors and actions within the context
of collaboratively building software products <em>at The Apache
Software Foundation</em>. By definition, “Apache project” is the collaborative
activity of building and releasing software products at the ASF.</p>
+
<p>The ASF and all Apache projects welcome the public to broadly re-use any released
-Apache products for virtually any purpose. Our permissive <a href="https://www.apache.org/licenses/LICENSE-2.0.html">Apache License</a> and our <a href="https://www.apache.org/foundation/marks/">formal trademark policy</a> govern third-party use.<br>
+Apache products for virtually any purpose. Our permissive <a href="https://www.apache.org/licenses/LICENSE-2.0.html">Apache License</a> and our <a href="https://www.apache.org/foundation/marks/">formal trademark policy</a> govern third-party use.<br />
While many third parties create Apache licensed
software, only software released from the ASF itself is properly called “Apache software”.</p>
-<h2 id="apache-projects-are-independent">Apache projects are independent <a class="headerlink" title="Permalink" href="#apache-projects-are-independent">¶</a></h2>
+
+<h2 id="apache-projects-are-independent">Apache projects are independent</h2>
+
<p>A Project Management Committee
(PMC) controls each Apache project. A PMC represents the consensus view of the individual PMC
members by discussing and [VOTE]ing on project releases and adding new committers.
A PMC’s actions within their Apache project community and management of
their project must be in the interest of that consensus and consistent with
the ASF’s mission of producing software for the public good.</p>
+
<p>There are also certain expectations of diversity within a PMC; the board may apply extra scrutiny to PMCs
with low diversity (i.e. PMCs that are dominated by individuals with a common employer).
Similarly, the ASF does not allow corporations to participate directly in
Apache project management or other governance activities at the ASF; only individuals.</p>
+
<p>There are several important aspects to this independence: project management, project use by end users, and project code availability.</p>
-<h2 id="apache-projects-are-managed-independently">Apache projects are managed independently <a class="headerlink" title="Permalink" href="#apache-projects-are-managed-independently">¶</a></h2>
+
+<h2 id="apache-projects-are-managed-independently">Apache projects are managed independently</h2>
+
<p>Apache projects must be managed independently, and PMCs must ensure that they are acting in the best interests of the project as a whole. It is similarly important that the PMC clearly show this independence within their project community. The perception that the PMC is run independently and without favoring any specific third parties over others is important to help new contributors feel comfortable both joining the community and contributing their work. A community that obviously fa [...]
-<h2 id="apache-products-may-be-used-independently">Apache products may be used independently <a class="headerlink" title="Permalink" href="#apache-products-may-be-used-independently">¶</a></h2>
+
+<h2 id="apache-products-may-be-used-independently">Apache products may be used independently</h2>
+
<p>All Apache projects must release their code under the <a href="https://www.apache.org/licenses/LICENSE-2.0.html">Apache License</a>, which clearly specifies the minimum restrictions that users of Apache software must agree to. Apache software is all about being able to use it for whatever our users want: open source, proprietary, secret. We’re happy to have users take our software (although not our name) for virtually any purpose. While our legal guidelines allow certain other softwar [...]
+
<p>Extending this idea, users of Apache software should be able to find our software, learn how to use it, and apply it to all its common use cases solely by going to the Apache project’s own website. Apache projects should provide sufficient documentation, install features, basic user help (through mailing lists) and services for the common use cases, without users having to rely on third parties. It is important that our users can both make use of our software freely – both in terms of [...]
-<h2 id="apache-projects-are-branded-as-apache-projects">Apache projects are branded as Apache projects <a class="headerlink" title="Permalink" href="#apache-projects-are-branded-as-apache-projects">¶</a></h2>
+
+<h2 id="apache-projects-are-branded-as-apache-projects">Apache projects are branded as Apache projects</h2>
+
<p>Similar to the requirement that users can use Apache projects independently, users should understand that, when they download and use an Apache product, it is from
Apache and not from nor related to any third party. That is, the user experience when
using an Apache project in its common use cases should clearly show the Apache project
branding in the UI or in whatever other ways users would normally interact with the product.</p>
+
<p>Ensuring that Apache projects are branded as Apache projects is critical to the longevity
of our communities. As users use the software, they may discover bugs, or have ideas for
improving the software, documentation, or other aspects of the project. When a user chooses
to share these ideas or improvements, ensuring that the product they are using
is clearly branded as coming from Apache ensures that they are likely to contribute
those ideas and improvements back to Apache and our projects.</p>
+
<p>The ASF welcomes third parties who build software that builds atop, improves,
plugs into, or works with our many Apache products. However any such third party software
product must be clearly branded as such, and must follow our <a href="https://www.apache.org/foundation/marks/">formal trademark policy</a>.
In this way, users clearly understand the different sources for software products such as
Apache Foo (from the ASF) and BigCo SuperThing, Powered By Apache Foo (from BigCo).</p>
-<h2 id="apache-projects-are-non-commercial">Apache projects are non-commercial <a class="headerlink" title="Permalink" href="#apache-projects-are-non-commercial">¶</a></h2>
+
+<h2 id="apache-projects-are-non-commercial">Apache projects are non-commercial</h2>
+
<p>The ASF’s mission is to produce software for the public good. All <a href="https://www.apache.org/free/">Apache software is always available for free</a>, and solely under the Apache License. While our projects manage the technical implementation of their individual software products independently, the ASF releases all Apache software, always intending to serve the public good.</p>
+
<p>We’re happy to have third parties, including for-profit corporations, take our software and use it for their own purposes – even when in some cases it may technically compete with Apache software. However it is important in these cases to ensure that the third party not misuse the brand and reputation of the Apache project for its own purposes. It is important for the longevity and community health of our projects that they get the appropriate credit for producing our freely available [...]
diff --git a/content/proposals.html b/content/proposals.html
index ba9668d..0af8a4a 100644
--- a/content/proposals.html
+++ b/content/proposals.html
@@ -9,7 +9,21 @@
<meta property="og:title" content="Proposals" />
<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/proposals.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+<meta property="og:url" content="https://community.apache.org/proposals.html" />
+
+
+
+
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
<title>Apache Community Development - Proposals</title>
diff --git a/content/proposals/ZestProposal.html b/content/proposals/ZestProposal.html
index 04a45a3..0c29a66 100644
--- a/content/proposals/ZestProposal.html
+++ b/content/proposals/ZestProposal.html
@@ -8,12 +8,26 @@
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="" />
<meta property="og:description" content="title: Zest Proposal
-Abstract ¶ qi4j = new Energy4Java(); That is how to create the Qi4j runtime, and it captures the essence of its spirit. Qi4j is a platform to develop Composite Oriented Programming applications in Java in a new, exciting and productive manner.
-Governance of Provisional Top Level Project ¶ Provisional Top Level Project is a new idea at the ASF, and the Qi4j community is willing to try the idea, instead of simply debating it." />
+Abstract qi4j = new Energy4Java(); That is how to create the Qi4j runtime, and it captures the essence of its spirit. Qi4j is a platform to develop Composite Oriented Programming applications in Java in a new, exciting and productive manner.
+Governance of Provisional Top Level Project Provisional Top Level Project is a new idea at the ASF, and the Qi4j community is willing to try the idea, instead of simply debating it." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/proposals/ZestProposal.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="proposals" />
+<meta property="og:url" content="https://community.apache.org/proposals/ZestProposal.html" />
+
+
+
+
+<meta property="article:modified_time" content="2020-07-20T20:22:04+02:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2020-07-20T20:22:04+02:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - </title>
@@ -189,111 +203,141 @@ Governance of Provisional Top Level Project ¶ Provisional Top Level Project
<hr>
- <p>title: Zest Proposal</p>
-<h1 id="abstract">Abstract <a class="headerlink" title="Permalink" href="#abstract">¶</a></h1>
+
+
+<p>title: Zest Proposal</p>
+
+<h1 id="abstract">Abstract</h1>
+
<pre><code> qi4j = new Energy4Java();
</code></pre>
+
<p>That is how to create the Qi4j runtime, and it captures the essence of its spirit.
Qi4j is a platform to develop Composite Oriented Programming applications in Java in a new, exciting and productive manner.</p>
-<h1 id="governance-of-provisional-top-level-project">Governance of Provisional Top Level Project <a class="headerlink" title="Permalink" href="#governance-of-provisional-top-level-project">¶</a></h1>
+
+<h1 id="governance-of-provisional-top-level-project">Governance of Provisional Top Level Project</h1>
+
<p>Provisional Top Level Project is a new idea at the ASF, and the Qi4j community is willing to try the idea, instead of simply debating it. If it doesn’t work, Qi4j will re-enter via the Incubator.</p>
+
<p>In addition of regular Top Level Projects, we are making the following self-imposed suggestions to the Governance of this Provisional TLP;</p>
+
<ol>
-<li>
-<p>The initial PMC consists only of Apache Members, to ensure a solid foundation of understanding The Apache Way.</p>
-</li>
-<li>
-<p>On top of being an ASF Member, the PMC Chair is an active contributor to the project, and has a vested interest in its success.</p>
-</li>
-<li>
-<p>Raising the consensus of Releases from 3 +1 votes to 5 +1 votes.</p>
-</li>
-<li>
-<p>Disclaimer on website and releases, marked with “Provisional” and links to the pTLP status at the ASF.</p>
-</li>
-<li>
-<p>Maturity of project into a regular Top Level Project is decided separately by the Board, with input from PMC and ComDev.</p>
-</li>
+<li><p>The initial PMC consists only of Apache Members, to ensure a solid foundation of understanding The Apache Way.</p></li>
+
+<li><p>On top of being an ASF Member, the PMC Chair is an active contributor to the project, and has a vested interest in its success.</p></li>
+
+<li><p>Raising the consensus of Releases from 3 +1 votes to 5 +1 votes.</p></li>
+
+<li><p>Disclaimer on website and releases, marked with “Provisional” and links to the pTLP status at the ASF.</p></li>
+
+<li><p>Maturity of project into a regular Top Level Project is decided separately by the Board, with input from PMC and ComDev.</p></li>
</ol>
-<h1 id="project-naming">Project Naming <a class="headerlink" title="Permalink" href="#project-naming">¶</a></h1>
+
+<h1 id="project-naming">Project Naming</h1>
+
<p>Apache Zest is the proposed project name, as we have learned that “4j” in names might ultimately limit the future direction of the project.
Additionally, Qi4j will remain as the Java implementation of the composite oriented programming platform. There is also a literal port to .NET, which may be migrated to ASF as well.</p>
-<h1 id="project-description">Project Description <a class="headerlink" title="Permalink" href="#project-description">¶</a></h1>
+
+<h1 id="project-description">Project Description</h1>
+
<p>Qi4j is a platform that combines Aspects, Composition, Dependency Injection, Validation, Storage/UnitOfWork handling, Indexing/Search abstraction, Architectural enforcement and much more, in a holistic top-down approach, primarily for Domain-rich applications, even explicitly supportive of Domain Driven Design.</p>
+
<p>Composite oriented programming is a term coined in the early days of Qi4j, to capture the notion of using another paradigm for creating applications, than the prevalent object oriented programming one.
It comprises of the ability to write smaller parts of code than regular classes, and compose these so called fragments into a larger “Composite”. It is similar to aspect-oriented programming, but we take it one step further, there is no base class. The Composite consists of fragments, but no fragment has higher significance than any other fragment. However, there are explicit types of fragments, namely Composite Types, Constraints, Mixins, Concerns and Side-effects, to clearl [...]
+
<p>Qi4j also evangelizes strong typing, so the equivalent of Around-Advice in AOP, which is called Concerns, can be made type-safe or like AOP be generic (using java.lang.reflect.InvocationHandler interface). Composites can either be hard coded using annotations, or assembled dynamically during the bootstrap phase.</p>
+
<p>Qi4j is a whole new way to write Java applications, where focus lies on structures and interfaces, where classes are ‘mere’ implementation details.</p>
+
<p>Qi4j boldly challenges bad practices head-on, such as “What is a Property?”, “Why are null arguments allowed by default?” and “Is the structural assembly of the application actually the same as configuration values?”</p>
-<h1 id="background">Background <a class="headerlink" title="Permalink" href="#background">¶</a></h1>
+
+<h1 id="background">Background</h1>
+
<p>Java is NOT an object-oriented language. Neither is C# or C++. IF they were, how come an Object is DERIVED FROM a Class? A true object-oriented language should for sure have Class(es) assigned to Objects (or a similar construct), which are created ‘clean’, like stem cells can take on practically any cell’s role of the body.</p>
+
<p>Additionally, in real life, most objects have different properties and behaviors depending on the context. In front of the computer, I am primarily a ‘programmer’, but in the jungle I am primarily ‘scared prey’. Modeling this in Java (and many other languages) requires the introduction of additional Object abstractions, often resulting in many similar classes representing the same underlying entity, again reinforcing our view that Java is a Class Oriented langu [...]
+
<p>Many problems in software engineering can be attributed to (lack of) cohesion and (too tight) coupling. The original promise was that we write a Class once and we can re-use it in many different applications, subsystems and modules. In reality, the Class often contains “too much” for the next use-case. The granularity is too coarse, causing too much coupling to other parts. This have resulted in libraries being the smallest granularity that is practical, and solutions like [...]
+
<p>But we often wish that we could have smaller fragments and COMPOSE objects from these fragments. This also makes it easier to replace parts of implementations, instead of fragile overloading, library extension (assuming the library author provides that) and the famous monkey patching approach.</p>
+
<p>Aspect Oriented Programming is a concept to capture cross-cutting concerns in one place. Classic cases are Logging and Authentication. This is an excellent concept, but we claim that AspectJ/AspectWerkz and others fail in the implementations, as most rely on naming conventions and declarations separated from the code itself. It is therefor often difficult to know what aspects are in effect at a given point in the code. The code weaving involved sometimes interferes with debugging and/ [...]
-<p>Many people have architecture/design drawings, often with layers in the application, with modules within those layers. We call this Worditecture, as those layers and modules only exist in Word documents and if the code is inspected, more often than not, it is impossible to relate the code to such drawings. In Qi4j, we set out to enforce the Application Structure. Entities, Values and Services must be declared inside one or more Modules, and Modules belong inside Layers, and Layers are [...]
-<h1 id="history">History <a class="headerlink" title="Permalink" href="#history">¶</a></h1>
+
+<p>Many people have architecture/design drawings, often with layers in the application, with modules within those layers. We call this Worditecture, as those layers and modules only exist in Word documents and if the code is inspected, more often than not, it is impossible to relate the code to such drawings. In Qi4j, we set out to enforce the Application Structure. Entities, Values and Services must be declared inside one or more Modules, and Modules belong inside Layers, and Layers are [...]
+
+<h1 id="history">History</h1>
+
<p>The principles of composite oriented programming are the brain child of Rickard Öberg going back to ~2003. In early 2007, Niclas Hedhman convinced Rickard to start a new open source project around this, and Qi4j was born. First announced at Oredev conference in November 2007.</p>
+
<p>Over the years, 28 people have contributed source to the project and many others have chimed in on mailing lists around direction, concepts and design. When Qi4j had the attention of media and others, we were not able to build long-term community around the project, and we have seen activity declined, as fewer itches to scratch and fewer people willing to make larger changes.</p>
-<h1 id="rationale-for-migrating-to-asf">Rationale for migrating to ASF <a class="headerlink" title="Permalink" href="#rationale-for-migrating-to-asf">¶</a></h1>
+
+<h1 id="rationale-for-migrating-to-asf">Rationale for migrating to ASF</h1>
+
<p>Qi4j community sees direct productivity gains from using the platform, although the initial learning curve is quite overwhelming, like learning a new language. The Qi4j community recognizes that it has not been able to communicate the benefits well enough, to achieve a large user and developer community. We are confident of Qi4j’s technical merit, and would like to draw on ASF’s community merit to build a larger, sustainable and successful community around this exciting te [...]
+
<p>The technical merit stems from that Qi4j has a strong model for programming in a more strict, yet more productive environment. A platform where fragments can be leveraged, where aspects are declared on the interfaces, where null values are not allowed by default, and where persistence is integrated yet pluggable at boot time. Qi4j enforces the use of modules and layers, the infrastructure layer can not access layers above it, and presentation layers at the top can’t bypass servi [...]
All these restrictions are there to provide more guidance to the programmer, reducing the length of the rope and the number of trees to hang oneself in.</p>
+
<p>“Common things should be quick and easy, while anything should be possible”, has been the mantra since the inception. And thanks to this foresight, Qi4j can be deeply integrated with many (but not all) existing Java technologies, to provide for migration paths.</p>
+
<p>Qi4j internally contains a lot of functional structures, and the community is currently migrating Qi4j to Java 8, reducing a chunk of the codebase in the process, and will likely discover new ways of simplicity. Many argue that Qi4j should become its own programming language, but our position has always been that the refactoring tools available in Java are so powerful and should not be under-estimated. It would take endless amount of effort to even get close to that, something that ma [...]
-<h1 id="initial-goals">Initial Goals <a class="headerlink" title="Permalink" href="#initial-goals">¶</a></h1>
+
+<h1 id="initial-goals">Initial Goals</h1>
+
<p>Qi4j is already on version 2.0, and striving towards both a 2.1 release as well as a Java 8 specific 3.0 release. This will be one of the first “Java 8”-only projects at the ASF, and hopefully a lot of people find this in itself attractive and exciting.</p>
+
<p>Qi4j’s user base is relatively small, but we are convinced of its remarkable properties as a productivity enhancing platform, and there is still much to do to reach its full potential. There are a lot of low hanging fruit (more extensions and libraries) as well as serious design challenges, such as reloadable Modules via OSGi and Jigsaw integration in Java 9.</p>
+
<p>As mentioned above, the small agreeable user base also means that Qi4j can be much more aggressive in adopting newer Java versions, and currently an effort is on the way to leverage Java 8. The Stream API and closures are implemented separately in Qi4j, and we are now converting all the internal code to those features supplied in Java 8, to reduce the total code size of Qi4j Core.</p>
-<h1 id="meritocracy">Meritocracy <a class="headerlink" title="Permalink" href="#meritocracy">¶</a></h1>
+
+<h1 id="meritocracy">Meritocracy</h1>
+
<p>Qi4j has been developed under heavy influence of ASF principles and guidelines. The barrier to entry has been at the lowest possible level. A rather aggressive Commit-then-Review process has been in place, but people have in general been encouraged to do larger changes in publicly visible feature branches. The low barrier hasn’t created any major problems yet, as reverting mistakes are relatively cheap, and it has been much more important to capture the long-tail of contribution [...]
+
<p>Qi4j is not operated by any organization, and all licensing is directly from developer to the user. We will engage the legal committee to ensure the IP rights are in full order.</p>
+
<p>Qi4j’s release process has not been nearly as stringent as the one at ASF, and will be the biggest change to the community. We will work closely with willing “Overseers” (see below), change our Gradle-based build system and use available tools, such as Rat, to ensure the highest quality releases possible.</p>
-<h1 id="community">Community <a class="headerlink" title="Permalink" href="#community">¶</a></h1>
+
+<h1 id="community">Community</h1>
+
<p>The current Qi4j developer community is rather small, but passionate individuals who are all convinced of Qi4j’s merit and potential. We also think that some of the past developers will re-join the effort, once we are at ASF and some traction is attained.</p>
+
<p>Over the years there has been 28 code contributors in total, of which 8 have been considered Core Developers, i.e. allowed to make changes on the Core runtime on trunk without hand-holding. No access control was in place to enforce that, and a social contract worked very well.</p>
+
<p>We are probably not the best of community builders, and would welcome members from ASF projects, who think Qi4j is promising, to assist in the community building effort needed.</p>
-<h1 id="active-developers">Active Developers <a class="headerlink" title="Permalink" href="#active-developers">¶</a></h1>
+
+<h1 id="active-developers">Active Developers</h1>
+
<p>All the active developers are independent of each other. No two developers work for the same employer, and no employer pays anyone for working full-time on Qi4j. We consider the following developers ‘active’ at the moment, one way or the other. It is a very diverse group;</p>
+
<ul>
-<li>
-<p>Niclas Hedhman is an ASF Member, previous long-term member of the Incubator PMC and mentor of 5-10 projects. Freelancing consultant and founder of Bright Things UN Ltd</p>
-</li>
-<li>
-<p>Marcel Offermans is an ASF Member, PMC Chair of Apache ACE and on Celix, Felix and Incubator PMC, mentor of several podlings. Day time he runs Luminis Technologies in Holland.</p>
-</li>
-<li>
-<p>Rickard Oberg is one of the founders of JBoss, created Xdoclet and WebWork (now Apache Struts2). He now works at Neo Technology Inc, creators of Neo4j.</p>
-</li>
-<li>
-<p>Paul Merlin is working at his own company CodeArtisans and a volunteer stone mason of antique walls and buildings.</p>
-</li>
-<li>
-<p>Stanislav Muhametsin is working at Cometa Solutions Oy. Stan has also ported Qi4j verbatim to C# as the Qi4CS project on GitHub.</p>
-</li>
-<li>
-<p>Tibor Mlynarik works at ADLER iTech.</p>
-</li>
-<li>
-<p>Edward Yakop technical architect at ABB Malaysia.</p>
-</li>
-<li>
-<p>Marc Grue is a professional musician, but has strong interest in computer science abstractions.</p>
-</li>
-<li>
-<p>Kent Sølvsten is working with energy systems at Arosii A/S in Denmark…</p>
-</li>
-<li>
-<p>Philippe van Dyck is in the banking industry and works at BNP Paribas</p>
-</li>
-<li>
-<p>Jiri Jetmar - Independent consultant</p>
-</li>
-<li>
-<p>Jaydatt Desai - Logicom Solutions</p>
-</li>
+<li><p>Niclas Hedhman is an ASF Member, previous long-term member of the Incubator PMC and mentor of 5-10 projects. Freelancing consultant and founder of Bright Things UN Ltd</p></li>
+
+<li><p>Marcel Offermans is an ASF Member, PMC Chair of Apache ACE and on Celix, Felix and Incubator PMC, mentor of several podlings. Day time he runs Luminis Technologies in Holland.</p></li>
+
+<li><p>Rickard Oberg is one of the founders of JBoss, created Xdoclet and WebWork (now Apache Struts2). He now works at Neo Technology Inc, creators of Neo4j.</p></li>
+
+<li><p>Paul Merlin is working at his own company CodeArtisans and a volunteer stone mason of antique walls and buildings.</p></li>
+
+<li><p>Stanislav Muhametsin is working at Cometa Solutions Oy. Stan has also ported Qi4j verbatim to C# as the Qi4CS project on GitHub.</p></li>
+
+<li><p>Tibor Mlynarik works at ADLER iTech.</p></li>
+
+<li><p>Edward Yakop technical architect at ABB Malaysia.</p></li>
+
+<li><p>Marc Grue is a professional musician, but has strong interest in computer science abstractions.</p></li>
+
+<li><p>Kent Sølvsten is working with energy systems at Arosii A/S in Denmark…</p></li>
+
+<li><p>Philippe van Dyck is in the banking industry and works at BNP Paribas</p></li>
+
+<li><p>Jiri Jetmar - Independent consultant</p></li>
+
+<li><p>Jaydatt Desai - Logicom Solutions</p></li>
</ul>
+
<p>Additional important contributions over the years have come from;</p>
+
<ul>
<li>Alex Schneyderman - Voalté</li>
<li>Alin Dreghiciu - Sonatype</li>
@@ -301,97 +345,143 @@ All these restrictions are there to provide more guidance to the programmer, re
<li>Michael Hunger - Neo Technology Inc</li>
<li>Tonny Kohar - independent Apache Batik and SVG consultant</li>
</ul>
-<h1 id="alignment">Alignment <a class="headerlink" title="Permalink" href="#alignment">¶</a></h1>
+
+<h1 id="alignment">Alignment</h1>
+
<p>Apache is a natural option for any Java project, as ASF has an overwhelming percentage of Java projects.
But for Qi4j, we think that our choice to challenge every notion, not based on popularity but on technical merit, should be inspiring to existing ASF projects at large. And by doing so, we hope symbiotic relationships can be established with a variety of other projects at ASF.</p>
+
<p>Qi4j is not “finished” and a lot of work in the Big Data space is still needed. We would like to see HBase and Cassandra use-cases to be “Tackled Qi4j Style” and practical conventions to emerge. There are several other ASF projects which Qi4j could support ‘better’, if we get a little help from those communities, incl Struts, Camel, ActiveMQ, Cayenne, Karaf and others.</p>
-<h1 id="known-risks">Known Risks <a class="headerlink" title="Permalink" href="#known-risks">¶</a></h1>
-<h2 id="orphaned-products">Orphaned products <a class="headerlink" title="Permalink" href="#orphaned-products">¶</a></h2>
+
+<h1 id="known-risks">Known Risks</h1>
+
+<h2 id="orphaned-products">Orphaned products</h2>
+
<p>Qi4j is not a company product and never was. It was started by two individuals who have a long and strong community involvement dating back to 1998, also the time when they first learned to know each other.</p>
+
<p>If the community can’t be built at ASF, then we think that there must be something about Qi4j that is inherently alien to developers, and Qi4j has no broader appeal, beyond those who have both seen the advantages as well as gotten the opportunity to work with it and see for themselves the benefits. We will work hard to ensure the long-term sustainability of the project, because we think that Qi4j represents an important step towards a paradigm shift in software development.</p>
-<h2 id="inexperience-with-open-source">Inexperience with Open Source <a class="headerlink" title="Permalink" href="#inexperience-with-open-source">¶</a></h2>
+
+<h2 id="inexperience-with-open-source">Inexperience with Open Source</h2>
+
<p>Not only does Qi4j have a rather long running history of an independent open source project, 6 major releases, and a track record of operating well as such, but Niclas Hedhman was a long time member of the Incubator PMC, serving on the Legal Committee and have plenty of experience of what is required of Apache projects, as does Marcel Offermans. We wouldn’t have proposed to move Qi4j to Apache, unless we thought that the larger Qi4j community will work well at the ASF, with a li [...]
+
<p>All of Qi4j’s history, except the initial 2-3 months, were done on open mailing lists and public repositories. The practice of full discourse and discussion on asynchronous mailing lists has been respected to the fullest extent possible, and at no time has other means of communication been regular.</p>
+
<p>Full source code history may not exist, as we went from Subversion at OPS4J to GIT at OPS4J to finally GitHub, initially with sub-repositories (which didn’t work well) to finally the qi4j-sdk repository at GitHub. History has probably broken at some point.</p>
+
<p>Just like early Apache project’s mailing list history, Qi4j’s might be incomplete in public archives, but we should be able to restore that, from GMail archives and other mailboxes. We intend to restore the mail archive, as there are many worth-while nuggets in there.</p>
-<h2 id="homogenous-developers">Homogenous Developers <a class="headerlink" title="Permalink" href="#homogenous-developers">¶</a></h2>
+
+<h2 id="homogenous-developers">Homogenous Developers</h2>
+
<p>The only homogeneity of Qi4j is the individuals’ desire to go beyond the current status quo, to challenge things we do from habit, to criticize ‘good practices’ and offer radically different solutions to so called mainstream developers and accepted practices.</p>
+
<p>The contributors have a vast diversity in their backgrounds and interests, even a non-developer making large contributions.</p>
+
<p>The group came together at Qi4j, drawn by its uniqueness and different way to address common concerns. We consider this to be a non-issue.</p>
-<h2 id="reliance-on-salaried-developers">Reliance on Salaried Developers <a class="headerlink" title="Permalink" href="#reliance-on-salaried-developers">¶</a></h2>
+
+<h2 id="reliance-on-salaried-developers">Reliance on Salaried Developers</h2>
+
<p>As far as we know, no one is currently paid to work on Qi4j itself. This has been a factor in the slow down of activity in the last two years, but we think that the bottom has been reached and that we will see an uptick during 2015, as some of the core members are coming back to write applications using Qi4j.</p>
-<h2 id="relationships-with-other-apache-products">Relationships with Other Apache Products <a class="headerlink" title="Permalink" href="#relationships-with-other-apache-products">¶</a></h2>
+
+<h2 id="relationships-with-other-apache-products">Relationships with Other Apache Products</h2>
+
<p>Qi4j is such a unique and radically different platform that there is no direct alignment in Qi4j Core with other Apache (or any other for that matter) projects. We have also kept the dependencies to a minimum by choice.
But Qi4j also defines Extension mechanisms, such as storage, indexing, serialization and metrics, and we have implemented extensions for Apache Cassandra and Apache Solr. We also have libraries that integrate other technology into the Qi4j world, such as Apache Shiro, Apache Struts and Apache CXF. We expect that additional Apache projects will be used in future Extensions as well as Libraries, especially in the Big Data space, where we see great opportunities for a Qi4j approach.</p>
-<h2 id="excessive-fascination-with-the-apache-brand">Excessive Fascination with the Apache Brand <a class="headerlink" title="Permalink" href="#excessive-fascination-with-the-apache-brand">¶</a></h2>
+
+<h2 id="excessive-fascination-with-the-apache-brand">Excessive Fascination with the Apache Brand</h2>
+
<p>There is no doubt that the Apache brand is strong, no one can deny that. But our primary ‘fascination’ is around the possibility to build a stronger community at the ASF, than we otherwise seem to be able to do. Apache is a natural water cooler, where open development people can share ideas and work together. We hope to inspire other Apache projects to do greater things after being exposed to Qi4j’s unique approach to many technical challenges.</p>
-<h1 id="documentation">Documentation <a class="headerlink" title="Permalink" href="#documentation">¶</a></h1>
+
+<h1 id="documentation">Documentation</h1>
+
<pre><code> Website; http://qi4j.org
Source Repository; https://github.com/Qi4j/qi4j-sdk
Current Mailing list; https://groups.google.com/forum/#!forum/qi4j-dev
</code></pre>
-<h1 id="initial-source">Initial Source <a class="headerlink" title="Permalink" href="#initial-source">¶</a></h1>
+
+<h1 id="initial-source">Initial Source</h1>
+
<p>As mentioned earlier, Qi4j started out at OPS4J community, and the codebase was initially on Subversion, then moved to OPS4J operated GIT repositories and finally we moved to GitHub. We tried to preserve history the best we could, with reasonable effort.
So, <a href="https://github.com/Qi4j">https://github.com/Qi4j</a> contains the repositories that are relevant for the Incubator. In practice, only the qi4j-sdk is current. We suggest that the qi4j-core, qi4j-libraries and qi4j-extensions are imported but made read-only. qi4j-sandbox is imported. qi4j.github.com contains the current website, but the sources for that resides primarily inside the qi4j-sdk repository.</p>
-<h1 id="source-and-intellectual-property-submission-plan">Source and Intellectual Property Submission Plan <a class="headerlink" title="Permalink" href="#source-and-intellectual-property-submission-plan">¶</a></h1>
+
+<h1 id="source-and-intellectual-property-submission-plan">Source and Intellectual Property Submission Plan</h1>
+
<p>There are no issues that we know of. Source code is available openly and online. All code has originated directly from Qi4j contributors, marked as Apache Licensed contributions and to the best of our knowledge there is no encumbered IP issues.
As Qi4j was never a legal entity, all contributions were directly licensed (Apache License 2.0) by the developer to the public. There is no problem reaching out to all of the authors of an overwhelming part (if not all) of the codebase and ask for paperwork, if this is necessary.</p>
-<h1 id="external-dependencies">External Dependencies <a class="headerlink" title="Permalink" href="#external-dependencies">¶</a></h1>
-<p>Qi4j has few dependencies, and all dependencies in all non-optional code is ASLv2 compatible. The required dependencies are;</p>
-<ul>
-<li>ASM</li>
-<li>SLF4J (To be revised)</li>
-<li>org.json (included in source form in the repository. To be revised)</li>
-</ul>
+
+<h1 id="external-dependencies">External Dependencies</h1>
+
+<p>Qi4j has few dependencies, and all dependencies in all non-optional code is ASLv2 compatible. The required dependencies are;
+ * ASM
+ * SLF4J (To be revised)
+ * org.json (included in source form in the repository. To be revised)</p>
+
<p>There are optional libraries and extensions that have dependencies on projects with other licenses.
One very notable case, the Neo4j entity store extension, is worth mentioning here. At the time this extension was created, Neo4j was under the AGPL license. It is now under GPL, yet the Qi4j Neo4j extension is licensed under Apache License v2. Are we not violating the license requirements of Neo4j? No, we think not, as the contribution itself was made by Neo Technology under the Apache license. Neo Technology argued that they had the right to provide the extension under ALv2, yet whoever [...]
-<h1 id="cryptography">Cryptography <a class="headerlink" title="Permalink" href="#cryptography">¶</a></h1>
+
+<h1 id="cryptography">Cryptography</h1>
+
<p>Qi4j optionally depends on projects that use cryptography. As Qi4j isn’t an organization, and most developers live in Europe, we have not followed the US trade restrictions on Cryptography.
Without an extensive check of all 100+ optional dependencies, Apache Shiro stands out. We need to get feedback from legal@ on what the exact requirements are, and conduct a full review.</p>
-<h1 id="required-resources">Required Resources <a class="headerlink" title="Permalink" href="#required-resources">¶</a></h1>
-<h2 id="mailing-lists">Mailing lists <a class="headerlink" title="Permalink" href="#mailing-lists">¶</a></h2>
+
+<h1 id="required-resources">Required Resources</h1>
+
+<h2 id="mailing-lists">Mailing lists</h2>
+
<pre><code> private@zest.apache.org
dev@zest.apache.org
commits@zest.apache.org
</code></pre>
-<h2 id="git-repositories">Git Repositories <a class="headerlink" title="Permalink" href="#git-repositories">¶</a></h2>
+
+<h2 id="git-repositories">Git Repositories</h2>
+
<p>We understand that Apache operates its own Git repositories, as well as having a large number of read-only mirrors at GitHub under Apache organization.</p>
+
<pre><code> https://git-wip-us.apache.org/repos/asf/qi4j.git
https://git-wip-us.apache.org/repos/asf/qi4j-legacy-core.git
https://git-wip-us.apache.org/repos/asf/qi4j-legacy-libraries.git
https://git-wip-us.apache.org/repos/asf/qi4j-legacy-extensions.git
https://git-wip-us.apache.org/repos/asf/qi4j-sandbox.git
</code></pre>
-<h2 id="issue-tracking">Issue Tracking <a class="headerlink" title="Permalink" href="#issue-tracking">¶</a></h2>
+
+<h2 id="issue-tracking">Issue Tracking</h2>
+
<p>We also have Jira issues we wish to import from Atlassian operated <a href="https://ops4j1.jira.com/browse/QI">https://ops4j1.jira.com/browse/QI</a>, if possible, to</p>
+
<pre><code> https://issues.apache.org/jira/browse/ZEST
</code></pre>
-<h1 id="initial-pmc">Initial PMC <a class="headerlink" title="Permalink" href="#initial-pmc">¶</a></h1>
+
+<h1 id="initial-pmc">Initial PMC</h1>
+
<ul>
-<li>Alex Karasulu - <a href="mailto:akarasulu@apache.org">akarasulu@apache.org</a></li>
-<li>James Carman - <a href="mailto:jcarman@apache.org">jcarman@apache.org</a></li>
-<li>Jeff Genender - <a href="mailto:jgenender@apache.org">jgenender@apache.org</a></li>
-<li>Marcel Offermans - <a href="mailto:marrs@apache.org">marrs@apache.org</a></li>
-<li>Chris Mattmann - <a href="mailto:mattmann@apache.org">mattmann@apache.org</a></li>
-<li>Niclas Hedhman - <a href="mailto:niclas@apache.org">niclas@apache.org</a></li>
-<li>Roman Shaposhnik - <a href="mailto:rvs@apache.org">rvs@apache.org</a></li>
+<li>Alex Karasulu - akarasulu@apache.org</li>
+<li>James Carman - jcarman@apache.org</li>
+<li>Jeff Genender - jgenender@apache.org</li>
+<li>Marcel Offermans - marrs@apache.org</li>
+<li>Chris Mattmann - mattmann@apache.org</li>
+<li>Niclas Hedhman - niclas@apache.org</li>
+<li>Roman Shaposhnik - rvs@apache.org</li>
</ul>
-<h1 id="committers">Committers <a class="headerlink" title="Permalink" href="#committers">¶</a></h1>
+
+<h1 id="committers">Committers</h1>
+
<ul>
-<li>Edward Yakop - <a href="mailto:efy@apache.org">efy@apache.org</a></li>
-<li>Jaydatt Desai - <a href="mailto:jaydattdesai@gmail.com">jaydattdesai@gmail.com</a></li>
-<li>Jiri Jetmar - <a href="mailto:juergen.jetmar@gmail.com">juergen.jetmar@gmail.com</a></li>
-<li>Kent Sølvsten - <a href="mailto:kent.soelvsten@gmail.com">kent.soelvsten@gmail.com</a></li>
-<li>Marc Grue - <a href="mailto:marcgrue@gmail.com">marcgrue@gmail.com</a></li>
-<li>Paul Merlin - <a href="mailto:paul@nosphere.org">paul@nosphere.org</a></li>
-<li>Phillipe van Dyck - <a href="mailto:pvdyck@gmail.com">pvdyck@gmail.com</a></li>
-<li>Rickard Öberg - <a href="mailto:rickardoberg@gmail.com">rickardoberg@gmail.com</a></li>
-<li>Stanislav Muhametsin - <a href="mailto:stanislav.muhametsin@cometasolutions.fi">stanislav.muhametsin@cometasolutions.fi</a></li>
-<li>Tibor Mlynarik - <a href="mailto:tibor.mlynarik@gmail.com">tibor.mlynarik@gmail.com</a></li>
+<li>Edward Yakop - efy@apache.org</li>
+<li>Jaydatt Desai - jaydattdesai@gmail.com</li>
+<li>Jiri Jetmar - juergen.jetmar@gmail.com</li>
+<li>Kent Sølvsten - kent.soelvsten@gmail.com</li>
+<li>Marc Grue - marcgrue@gmail.com</li>
+<li>Paul Merlin - paul@nosphere.org</li>
+<li>Phillipe van Dyck - pvdyck@gmail.com</li>
+<li>Rickard Öberg - rickardoberg@gmail.com</li>
+<li>Stanislav Muhametsin - stanislav.muhametsin@cometasolutions.fi</li>
+<li>Tibor Mlynarik - tibor.mlynarik@gmail.com</li>
</ul>
-<h1 id="affiliations">Affiliations <a class="headerlink" title="Permalink" href="#affiliations">¶</a></h1>
+
+<h1 id="affiliations">Affiliations</h1>
+
<ul>
<li>Edward Yakop - ABB Malaysia</li>
<li>Jaydatt Desai - Logicom Solutions</li>
diff --git a/content/proposals/index.xml b/content/proposals/index.xml
index 592c387..2fbd7d9 100644
--- a/content/proposals/index.xml
+++ b/content/proposals/index.xml
@@ -1,11 +1,15 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Proposals on Apache Comdev</title>
<link>https://community.apache.org/proposals.html</link>
<description>Recent content in Proposals on Apache Comdev</description>
<generator>Hugo -- gohugo.io</generator>
- <language>en</language><atom:link href="https://community.apache.org/proposals/index.xml" rel="self" type="application/rss+xml" />
+ <language>en</language>
+
+ <atom:link href="https://community.apache.org/proposals/index.xml" rel="self" type="application/rss+xml" />
+
+
<item>
<title></title>
<link>https://community.apache.org/proposals/ZestProposal.html</link>
@@ -13,9 +17,9 @@
<guid>https://community.apache.org/proposals/ZestProposal.html</guid>
<description>title: Zest Proposal
-Abstract &para; qi4j = new Energy4Java(); That is how to create the Qi4j runtime, and it captures the essence of its spirit. Qi4j is a platform to develop Composite Oriented Programming applications in Java in a new, exciting and productive manner.
-Governance of Provisional Top Level Project &para; Provisional Top Level Project is a new idea at the ASF, and the Qi4j community is willing to try the idea, instead of simply debating it.</description>
+Abstract qi4j = new Energy4Java(); That is how to create the Qi4j runtime, and it captures the essence of its spirit. Qi4j is a platform to develop Composite Oriented Programming applications in Java in a new, exciting and productive manner.
+Governance of Provisional Top Level Project Provisional Top Level Project is a new idea at the ASF, and the Qi4j community is willing to try the idea, instead of simply debating it.</description>
</item>
</channel>
-</rss>
+</rss>
\ No newline at end of file
diff --git a/content/sitemap.xml b/content/sitemap.xml
index 2439f7d..76dad65 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -1,158 +1,265 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
xmlns:xhtml="http://www.w3.org/1999/xhtml">
+
<url>
<loc>https://community.apache.org/proposals/ZestProposal.html</loc>
<lastmod>2020-07-20T20:22:04+02:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/apache-way/apache-project-maturity-model.html</loc>
<lastmod>2021-06-21T10:25:49+02:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
+ <loc>https://community.apache.org/contributors/etiquette.html</loc>
+ <lastmod>2023-03-17T12:29:24-05:00</lastmod>
+ </url>
+
+ <url>
<loc>https://community.apache.org/</loc>
- <lastmod>2023-03-27T22:33:33+01:00</lastmod>
- </url><url>
+ <lastmod>2023-03-29T19:12:27+01:00</lastmod>
+ </url>
+
+ <url>
<loc>https://community.apache.org/calendars/conferences.html</loc>
<lastmod>2020-07-20T20:22:04+02:00</lastmod>
- </url><url>
- <loc>https://community.apache.org/gsoc/experiences.html</loc>
- <lastmod>2023-03-21T10:25:42+07:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/newbiefaq.html</loc>
<lastmod>2023-03-17T12:26:02-04:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/calendars/</loc>
<lastmod>2023-03-29T11:49:44+02:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
+ <loc>https://community.apache.org/gsoc/experiences.html</loc>
+ <lastmod>2023-03-21T10:25:42+07:00</lastmod>
+ </url>
+
+ <url>
<loc>https://community.apache.org/speakers/slides.html</loc>
<lastmod>2023-03-17T10:04:48-04:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/apache-way.html</loc>
<lastmod>2021-06-21T10:25:49+02:00</lastmod>
- </url><url>
+ <priority>0</priority>
+ </url>
+
+ <url>
<loc>https://community.apache.org/newsletter/2017-04.html</loc>
<lastmod>2020-07-20T20:22:04+02:00</lastmod>
- </url><url>
- <loc>https://community.apache.org/contributors/etiquette.html</loc>
- <lastmod>2023-03-17T12:29:24-05:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/contributors/becomingacommitter.html</loc>
<lastmod>2023-03-21T17:21:46-04:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/boardreport.html</loc>
<lastmod>2023-03-21T14:07:43-04:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/comdevboardreports.html</loc>
<lastmod>2023-03-21T13:34:10-04:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/history/boardresolution.html</loc>
<lastmod>2023-03-27T22:49:45+01:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/committers/</loc>
<lastmod>2023-03-29T11:49:44+02:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/lists.html</loc>
<lastmod>2020-12-15T09:34:12-04:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/about/</loc>
<lastmod>2023-03-29T11:49:44+02:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/committers/consensusBuilding.html</loc>
<lastmod>2020-12-02T09:52:19-04:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/contactpoints.html</loc>
<lastmod>2020-12-10T09:12:00-04:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/contributors/</loc>
<lastmod>2023-03-29T11:49:44+02:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/committers/decisionMaking.html</loc>
<lastmod>2021-01-15T09:22:16-04:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/events.html</loc>
<lastmod>2020-07-20T20:22:04+02:00</lastmod>
- </url><url>
+ <priority>0</priority>
+ </url>
+
+ <url>
<loc>https://community.apache.org/committers/funding-disclaimer.html</loc>
<lastmod>2021-07-06T11:05:05-04:00</lastmod>
- </url><url>
- <loc>https://community.apache.org/gettingStarted/101.html</loc>
- <lastmod>2023-03-29T19:28:51+01:00</lastmod>
- </url><url>
- <loc>https://community.apache.org/gettingstarted.html</loc>
- <lastmod>2023-03-29T19:28:51+01:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/gsoc/</loc>
<lastmod>2023-03-29T11:49:44+02:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/gsoc/gsoc-admin-tasks.html</loc>
<lastmod>2023-03-29T19:28:51+01:00</lastmod>
- </url><url>
- <loc>https://community.apache.org/gsoc/guide-to-being-a-mentor.html</loc>
+ </url>
+
+ <url>
+ <loc>https://community.apache.org/gettingStarted/101.html</loc>
+ <lastmod>2023-03-29T19:28:51+01:00</lastmod>
+ </url>
+
+ <url>
+ <loc>https://community.apache.org/gettingStarted.html</loc>
<lastmod>2023-03-29T19:28:51+01:00</lastmod>
- </url><url>
+ <priority>0</priority>
+ </url>
+
+ <url>
<loc>https://community.apache.org/history.html</loc>
- <lastmod>2023-03-27T22:49:45+01:00</lastmod>
- </url><url>
+ <lastmod>2023-03-17T12:26:02-04:00</lastmod>
+ <priority>0</priority>
+ </url>
+
+ <url>
<loc>https://community.apache.org/mentor-request-mail.html</loc>
<lastmod>2020-12-13T09:34:53-04:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/committers/lazyConsensus.html</loc>
<lastmod>2022-02-20T11:10:20-04:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/links.html</loc>
<lastmod>2023-03-16T12:35:40-04:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/speakers/speakers.html</loc>
<lastmod>2021-07-05T14:07:56-03:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/newsletter/2017-05.html</loc>
<lastmod>2020-07-20T20:22:04+02:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/gsoc/mentee-ranking-process.html</loc>
<lastmod>2023-03-21T10:25:42+07:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/mentoring/</loc>
<lastmod>2023-03-29T11:49:44+02:00</lastmod>
- </url><url>
- <loc>https://community.apache.org/mentoring/committer.html</loc>
- <lastmod>2023-03-17T12:26:02-04:00</lastmod>
- </url><url>
- <loc>https://community.apache.org/mentoring/pmc.html</loc>
- <lastmod>2023-03-17T12:26:02-04:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/mentoring/mentor.html</loc>
<lastmod>2020-03-24T15:03:46+01:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
+ <loc>https://community.apache.org/mentoring/pmc.html</loc>
+ <lastmod>2023-03-17T12:26:02-04:00</lastmod>
+ </url>
+
+ <url>
+ <loc>https://community.apache.org/mentoring/committer.html</loc>
+ <lastmod>2023-03-17T12:26:02-04:00</lastmod>
+ </url>
+
+ <url>
<loc>https://community.apache.org/mentoring/firstpatch.html</loc>
<lastmod>2023-03-17T12:26:02-04:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/newcommitter.html</loc>
<lastmod>2023-03-29T19:28:51+01:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/newsletter/</loc>
<lastmod>2023-03-29T11:49:44+02:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/history/mentoringprogramme-icfoss-pilot.html</loc>
<lastmod>2023-03-17T12:26:02-04:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/projectIndependence.html</loc>
<lastmod>2022-01-07T11:22:24-08:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/proposals.html</loc>
<lastmod>2020-07-20T20:22:04+02:00</lastmod>
- </url><url>
+ <priority>0</priority>
+ </url>
+
+ <url>
<loc>https://community.apache.org/events/small-events.html</loc>
<lastmod>2020-07-20T20:22:04+02:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/speakers/</loc>
<lastmod>2023-03-29T11:49:44+02:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/gsoc/use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.html</loc>
<lastmod>2023-03-21T13:35:34+05:30</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/committers/voting.html</loc>
<lastmod>2022-02-20T11:05:53-04:00</lastmod>
- </url><url>
+ </url>
+
+ <url>
<loc>https://community.apache.org/newcomers/</loc>
<lastmod>2023-03-29T11:49:44+02:00</lastmod>
</url>
-</urlset>
+
+ <url>
+ <loc>https://community.apache.org/gsoc/guide-to-being-a-mentor.html</loc>
+ <lastmod>2023-03-29T19:28:51+01:00</lastmod>
+ </url>
+
+</urlset>
\ No newline at end of file
diff --git a/content/speakers/index.html b/content/speakers/index.html
index cadff4d..75eaeb6 100644
--- a/content/speakers/index.html
+++ b/content/speakers/index.html
@@ -9,7 +9,21 @@
<meta property="og:title" content="Speaking about Apache, our Projects and our Community" />
<meta property="og:description" content="The Community Development project creates and provides tools, processes, and advice to help open-source software projects improve their own community health." />
<meta property="og:type" content="website" />
-<meta property="og:url" content="https://community.apache.org/speakers/" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="og:site_name" content="Apache Community Development" />
+<meta property="og:url" content="https://community.apache.org/speakers/" />
+
+
+
+<meta property="og:updated_time" content="2023-03-29T11:49:44+02:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
<title>Apache Community Development - Speaking about Apache, our Projects and our Community</title>
@@ -182,25 +196,37 @@
<hr>
- <p>If you are looking for speakers for an event, or are a speaker looking for
+
+
+<p>If you are looking for speakers for an event, or are a speaker looking for
materials, this is the place for you.</p>
+
<p>If you are seeking to organise an Apache-branded event, you must ensure your activities
conform to the <a href="https://community.zones.apache.org/">Third Party Event Branding Policy</a>. Once you have verified you are in
conformance, please consider adding your event to the <a href="/calendars/conferences.html">events calendar</a>.</p>
-<h2 id="finding-speakers">Finding speakers <a class="headerlink" title="Permalink" href="#finding-speakers">¶</a></h2>
+
+<h2 id="finding-speakers">Finding speakers</h2>
+
<p>You can use our “<a href="https://community.zones.apache.org/">Find People</a>” application to find speakers willing and able to
talk about The Apache Software Foundation and its projects. A few people have shared <a href="slides.html">Apache related presentations</a> for you.</p>
+
<p><em>NOTE</em> This service is alpha-quality right now, and features only
some of the many volunteer speakers from Apache projects. If you have a problem with
it, or it doesn’t turn up a suitable candidate, feel free to contact us
for help (see below).</p>
-<h3 id="listing-yourself-as-a-potential-speaker">Listing yourself as a potential speaker <a class="headerlink" title="Permalink" href="#listing-yourself-as-a-potential-speaker">¶</a></h3>
+
+<h3 id="listing-yourself-as-a-potential-speaker">Listing yourself as a potential speaker</h3>
+
<p>If you’re an Apache committer, and you’re interested in speaking about Apache Projects, our Communities, or the Apache
Software Foundation as a whole, we encourage you to get involved: list yourself in our speaker application!</p>
+
<p>For more details on how to list yourself as a potential speaker, see the <a href="speakers.html">Apache Speakers WebApp</a> page.</p>
-<h2 id="speaker-support-materials">Speaker support materials <a class="headerlink" title="Permalink" href="#speaker-support-materials">¶</a></h2>
+
+<h2 id="speaker-support-materials">Speaker support materials</h2>
+
<p>If you are creating your own slides, you will find the <a href="https://www.apache.org/foundation/press/kit/">ASF Press Kit</a> useful. It contains logos in various formats.
We also have <a href="themes">sample themes</a> available.</p>
+
<p>We aim to collect a set of slide decks about the Apache
Software Foundation for reuse in presentations. So far
A few people have shared <a href="slides.html">Apache related presentations</a>
diff --git a/content/speakers/index.xml b/content/speakers/index.xml
index 02f22c7..862b1a7 100644
--- a/content/speakers/index.xml
+++ b/content/speakers/index.xml
@@ -1,11 +1,16 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Speaking about Apache, our Projects and our Community on Apache Comdev</title>
<link>https://community.apache.org/speakers/</link>
<description>Recent content in Speaking about Apache, our Projects and our Community on Apache Comdev</description>
<generator>Hugo -- gohugo.io</generator>
- <language>en</language><atom:link href="https://community.apache.org/speakers/index.xml" rel="self" type="application/rss+xml" />
+ <language>en</language>
+ <lastBuildDate>Wed, 29 Mar 2023 11:49:44 +0200</lastBuildDate>
+
+ <atom:link href="https://community.apache.org/speakers/index.xml" rel="self" type="application/rss+xml" />
+
+
<item>
<title>Apache-related slides, videos and presentations</title>
<link>https://community.apache.org/speakers/slides.html</link>
@@ -24,9 +29,9 @@ Many Apache speakers post their slides to the SlideShare website, and the Feathe
<guid>https://community.apache.org/speakers/speakers.html</guid>
<description>If you&rsquo;re an Apache committer interested in speaking about Apache Technologies, Apache Projects or the Apache Software Foundation as a whole, we encourage you to get involved and list yourself in our speaker application!
-Finding Speakers &para; If you are organising an event and looking for speakers, see the Apache Speakers homepage for details.
-Listing yourself as a potential speaker &para; To list yourself as someone interested in being an Apache speaker, there are two steps.</description>
+Finding Speakers If you are organising an event and looking for speakers, see the Apache Speakers homepage for details.
+Listing yourself as a potential speaker To list yourself as someone interested in being an Apache speaker, there are two steps.</description>
</item>
</channel>
-</rss>
+</rss>
\ No newline at end of file
diff --git a/content/speakers/slides.html b/content/speakers/slides.html
index 16c5ae0..04ce7fe 100644
--- a/content/speakers/slides.html
+++ b/content/speakers/slides.html
@@ -11,9 +11,23 @@
These presentations are available under permissive licenses; please see each individual presentation for license details.
Many Apache speakers post their slides to the SlideShare website, and the FeatherCast podcast offers audio recordings of many talks and interviews." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/speakers/slides.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="speakers" />
+<meta property="og:url" content="https://community.apache.org/speakers/slides.html" />
+
+
+
+
+<meta property="article:modified_time" content="2023-03-17T10:04:48-04:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2023-03-17T10:04:48-04:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Apache-related slides, videos and presentations</title>
@@ -189,32 +203,42 @@ Many Apache speakers post their slides to the SlideShare website, and the Feathe
<hr>
- <p>This page contains links to presentations and other key papers about the ASF and how
+
+
+<p>This page contains links to presentations and other key papers about the ASF and how
Apache projects work that you may find useful. Many of these have
been presented at <a href="https://events.apache.org">ApacheCon conferences</a> or
other open source conferences.</p>
+
<p>These presentations are available under permissive licenses; please see
each individual presentation for license details.</p>
+
<p>Many Apache speakers post their slides to the <a href="//www.slideshare.net/search/slideshow?searchfrom=header&q=apache+software">SlideShare website</a>,
and the <a href="//feathercast.apache.org/">FeatherCast podcast offers audio recordings</a> of many talks and interviews.</p>
-<p>For those who prefer videos, our many volunteers have posted</p>
-<ul>
-<li><a href="https://www.youtube.com/user/TheApacheFoundation/playlists">full videos of all ApacheCon NA 2013 presentations</a>, and</li>
-<li><a href="https://www.youtube.com/playlist?list=PLU2OcwpQkYCzvGxZgVOunTs-3iEao6YJc">select ApacheCon NA 2014 presentations</a>.</li>
-<li><a href="https://www.youtube.com/channel/UCLDJ_V9KUOdOFSbDvPfGBxw">Sessions from ApacheCon 2019 and 2020</a></li>
-</ul>
+
+<p>For those who prefer videos, our many volunteers have posted
+ - <a href="https://www.youtube.com/user/TheApacheFoundation/playlists">full videos of all ApacheCon NA 2013 presentations</a>, and
+ - <a href="https://www.youtube.com/playlist?list=PLU2OcwpQkYCzvGxZgVOunTs-3iEao6YJc">select ApacheCon NA 2014 presentations</a>.
+ - <a href="https://www.youtube.com/channel/UCLDJ_V9KUOdOFSbDvPfGBxw">Sessions from ApacheCon 2019 and 2020</a></p>
+
<p>Additional slides, videos and audio recordings can also be found through the
<a href="https://wiki.apache.org/apachecon/Past_Conference_Resources">ApacheCon Past Conference Resources page</a>.</p>
-<h1 id="asf-postings">ASF Postings <a class="headerlink" title="Permalink" href="#asf-postings">¶</a></h1>
+
+<h1 id="asf-postings">ASF Postings</h1>
+
<ul>
<li><a href="https://www.apache.org/theapacheway/index.html">Briefing: The Apache Way</a> (paper)</li>
<li><a href="https://blogs.apache.org/foundation/entry/the-apache-way-to-sustainable">The Apache Way to Sustainable Open Source Success</a> (paper)</li>
</ul>
-<h1 id="isabel-drost">Isabel Drost <a class="headerlink" title="Permalink" href="#isabel-drost">¶</a></h1>
+
+<h1 id="isabel-drost">Isabel Drost</h1>
+
<ul>
<li><a href="http://isabel-drost.de/hadoop/slides/christoph.pdf">Open Source development for students</a></li>
</ul>
-<h1 id="justin-erenkrantz">Justin Erenkrantz <a class="headerlink" title="Permalink" href="#justin-erenkrantz">¶</a></h1>
+
+<h1 id="justin-erenkrantz">Justin Erenkrantz</h1>
+
<ul>
<li><a href="https://www.erenkrantz.com/apachecon/TransferSummit%20-%20Open%20Innovation.pdf">Open Innovation in The Apache Software Foundation</a></li>
<li><a href="https://www.erenkrantz.com/apachecon/OSBC%20-%20No%20Jerks%20Allowed.pdf">Writing and Distributing Software “The Apache Way”</a></li>
@@ -222,20 +246,28 @@ and the <a href="//feathercast.apache.org/">FeatherCast podcast offers audio rec
<li><a href="https://www.erenkrantz.com/apachecon/Apache%20Roadshow%20Asia%202009.pdf">Putting It Together</a></li>
<li><a href="https://www.erenkrantz.com/apachecon/SAP%20Apache%20Intro.pdf">An Overview of The Apache Software Foundation</a></li>
</ul>
-<h1 id="ross-gardler">Ross Gardler <a class="headerlink" title="Permalink" href="#ross-gardler">¶</a></h1>
+
+<h1 id="ross-gardler">Ross Gardler</h1>
+
<ul>
<li><a href="https://www.slideshare.net/bosc2010/gardler-bosc2010-communitydevelopmentattheasf">Community Development at the ASF</a></li>
<li><a href="https://www.slideshare.net/rgardler/the-apache-way-and-openofficeorg">The Apache Way and OpenOffice.org</a></li>
</ul>
-<h1 id="jim-jagielski">Jim Jagielski <a class="headerlink" title="Permalink" href="#jim-jagielski">¶</a></h1>
+
+<h1 id="jim-jagielski">Jim Jagielski</h1>
+
<ul>
<li><a href="https://people.apache.org/~jim/presos/IOOS2011/Creating_Community.pdf">Communities and Collaboration</a></li>
<li><a href="https://people.apache.org/~jim/presos/OR2011/Open_Source_NotJust.pdf">Open Source: It’s just not for IT anymore</a></li>
<li>More of Jims presentations <a href="https://people.apache.org/~jim/presos/">here</a> and <a href="https://www.slideshare.net/jimjag/">here</a></li>
</ul>
-<h1 id="bertrand-delacretaz">Bertrand Delacretaz <a class="headerlink" title="Permalink" href="#bertrand-delacretaz">¶</a></h1>
+
+<h1 id="bertrand-delacretaz">Bertrand Delacretaz</h1>
+
<p>Slides and talk recordings are linked from my <a href="https://pinboard.in/u:bdelacretaz/t:pressbook/">Pressbook</a>.</p>
-<h1 id="shane-curcuru">Shane Curcuru <a class="headerlink" title="Permalink" href="#shane-curcuru">¶</a></h1>
+
+<h1 id="shane-curcuru">Shane Curcuru</h1>
+
<ul>
<li><a href="http://shaneslides.com/2017/04/History-Of-The-Apache-Way/">History and Overview of Various Apache Way Presentations</a> (annotated list, pre-2017)</li>
<li><a href="http://shaneslides.com/apachecon/TheApacheWay-Intro-ApacheConNA2017.html">Apache Way: Effective Open Source Project Management</a> ApacheCon 2017 (<a href="https://www.youtube.com/watch?v=hpAv54KIgK8">video</a>)</li>
@@ -246,45 +278,66 @@ and the <a href="//feathercast.apache.org/">FeatherCast podcast offers audio rec
<li><a href="https://www.slideshare.net/shanecurcuru/successfully-profiting-from-apache-brands">Successfully Profiting From Apache Projects</a></li>
<li><a href="https://www.slideshare.net/shanecurcuru/practical-trademark-law-for-foss-projects">Practical Trademark Law For FOSS Projects</a></li>
</ul>
-<h1 id="nick-burch">Nick Burch <a class="headerlink" title="Permalink" href="#nick-burch">¶</a></h1>
+
+<h1 id="nick-burch">Nick Burch</h1>
+
<ul>
<li><a href="https://home.apache.org/~nick/Talks/ApacheConNA15/TheApacheWay15.pdf">The Apache Way (ApacheCon North America 2015 version)</a></li>
<li><a href="https://home.apache.org/~nick/Talks/ApacheConNA16/ButWereAlreadyOpen.pdf">But we’re already open source? Why would we want to bring our project to the ASF?</a></li>
</ul>
-<h1 id="andrea-pescetti">Andrea Pescetti <a class="headerlink" title="Permalink" href="#andrea-pescetti">¶</a></h1>
+
+<h1 id="andrea-pescetti">Andrea Pescetti</h1>
+
<ul>
<li><a href="https://www.slideshare.net/pescetti/bending-the-rules-community-over-code-over-policy-apachecon-2014">Bending the rules: Community over Code over Policy</a></li>
</ul>
-<h1 id="daniel-ruggeri">Daniel Ruggeri <a class="headerlink" title="Permalink" href="#daniel-ruggeri">¶</a></h1>
+
+<h1 id="daniel-ruggeri">Daniel Ruggeri</h1>
+
<ul>
<li><a href="https://people.apache.org/~druggeri/presentations/TheApacheWay.odp">The Apache Way - amalgamation of many other decks</a> - presented at University of Missouri 2015. Attempt to get everything in one deck.</li>
</ul>
-<h1 id="j-aaron-farr">J Aaron Farr <a class="headerlink" title="Permalink" href="#j-aaron-farr">¶</a></h1>
+
+<h1 id="j-aaron-farr">J Aaron Farr</h1>
+
<ul>
<li><a href="https://www.slideshare.net/jaaronfarr/presentations">Several older Apache Way and related slide decks</a></li>
</ul>
-<h1 id="alan-gates">Alan Gates <a class="headerlink" title="Permalink" href="#alan-gates">¶</a></h1>
+
+<h1 id="alan-gates">Alan Gates</h1>
+
<ul>
<li><a href="https://www.slideshare.net/alanfgates/keynote-apache-bdeunov2016">Training Our Team in the Apache Way</a> Keynote slides from Apache Big Data EU 2016</li>
<li><a href="https://www.slideshare.net/alanfgates/hortonworks-apache-training">Hortonworks Engineering Apache Training</a> Training material described in keynote above</li>
</ul>
-<h1 id="brett-porter">Brett Porter <a class="headerlink" title="Permalink" href="#brett-porter">¶</a></h1>
+
+<h1 id="brett-porter">Brett Porter</h1>
+
<ul>
<li><a href="https://www.slideshare.net/brettporter/the-apache-way-dataworks-summit-2017">The Apache Way - based on J Aaron Farr’s earlier versions</a></li>
</ul>
-<h1 id="ismaël-mejía">Ismaël Mejía <a class="headerlink" title="Permalink" href="#isma%c3%abl-mej%c3%ada">¶</a></h1>
+
+<h1 id="ismaël-mejía">Ismaël Mejía</h1>
+
<ul>
<li><a href="https://iemejia.github.io/slides/201806-Construyendo%20software%20y%20comunidades%20a%20la%20manera%20de%20Apache.pdf">Construyendo software y comunidades a la manera de Apache (spanish)</a></li>
</ul>
-<h1 id="piergiorgio-lucidi">Piergiorgio Lucidi <a class="headerlink" title="Permalink" href="#piergiorgio-lucidi">¶</a></h1>
+
+<h1 id="piergiorgio-lucidi">Piergiorgio Lucidi</h1>
+
<ul>
<li><a href="https://www.slideshare.net/PiergiorgioLucidi/the-journey-of-apache-manifoldcf-learning-from-asfs-successes-81289363">The Journey of Apache ManifoldCF: Learning from ASF’s Successes (Open Source Summit 2017)</a></li>
</ul>
+
<p>And more at his <a href="https://www.slideshare.net/PiergiorgioLucidi">slideshare profile</a></p>
-<h2 id="committers---please-add-to-this-page">Committers - please add to this page! <a class="headerlink" title="Permalink" href="#committers---please-add-to-this-page">¶</a></h2>
+
+<h2 id="committers-please-add-to-this-page">Committers - please add to this page!</h2>
+
<p>If you are an Apache committer and have presented slides on community topics
around Apache, please add a link to your information here!</p>
-<h3 id="slide-templates">Slide templates <a class="headerlink" title="Permalink" href="#slide-templates">¶</a></h3>
+
+<h3 id="slide-templates">Slide templates</h3>
+
<p>If you want to prepare a new presentation about any Apache project, feel free to start using <a href="https://svn.apache.org/repos/asf/comdev/slide-templates/">Apache slide templates</a>.</p>
diff --git a/content/speakers/speakers.html b/content/speakers/speakers.html
index c713484..2e1476f 100644
--- a/content/speakers/speakers.html
+++ b/content/speakers/speakers.html
@@ -8,12 +8,26 @@
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="Listing yourself as a Potential Speaker" />
<meta property="og:description" content="If you’re an Apache committer interested in speaking about Apache Technologies, Apache Projects or the Apache Software Foundation as a whole, we encourage you to get involved and list yourself in our speaker application!
-Finding Speakers ¶ If you are organising an event and looking for speakers, see the Apache Speakers homepage for details.
-Listing yourself as a potential speaker ¶ To list yourself as someone interested in being an Apache speaker, there are two steps." />
+Finding Speakers If you are organising an event and looking for speakers, see the Apache Speakers homepage for details.
+Listing yourself as a potential speaker To list yourself as someone interested in being an Apache speaker, there are two steps." />
<meta property="og:type" content="article" />
-<meta property="og:url" content="https://community.apache.org/speakers/speakers.html" /><meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/><meta property="article:section" content="speakers" />
+<meta property="og:url" content="https://community.apache.org/speakers/speakers.html" />
+
+
+
+
+<meta property="article:modified_time" content="2021-07-05T14:07:56-03:00"/>
+
+<meta property="og:site_name" content="Apache Community Development" />
+
+
+
+
+
+
+
+
-<meta property="article:modified_time" content="2021-07-05T14:07:56-03:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Listing yourself as a Potential Speaker</title>
@@ -189,24 +203,34 @@ Listing yourself as a potential speaker ¶ To list yourself as someone inter
<hr>
- <p>If you’re an Apache committer interested in speaking about Apache
+
+
+<p>If you’re an Apache committer interested in speaking about Apache
Technologies, Apache Projects or the Apache Software Foundation as a whole,
we encourage you to get involved and list yourself in our speaker
application!</p>
-<h2 id="finding-speakers">Finding Speakers <a class="headerlink" title="Permalink" href="#finding-speakers">¶</a></h2>
+
+<h2 id="finding-speakers">Finding Speakers</h2>
+
<p>If you are organising an event and looking for speakers, see
<a href="/speakers/">the Apache Speakers homepage</a> for details.</p>
-<h2 id="listing-yourself-as-a-potential-speaker">Listing yourself as a potential speaker <a class="headerlink" title="Permalink" href="#listing-yourself-as-a-potential-speaker">¶</a></h2>
+
+<h2 id="listing-yourself-as-a-potential-speaker">Listing yourself as a potential speaker</h2>
+
<p>To list yourself as someone interested in being an Apache speaker, there are
two steps. The first is to create a FOAF (“friend of a friend”) file for yourself that includes
a couple of key pieces of information. The second is to list yourself in the
speaking DOAP (“description of a project”) file.</p>
-<h3 id="creating-your-foaf-file">Creating your FOAF file <a class="headerlink" title="Permalink" href="#creating-your-foaf-file">¶</a></h3>
+
+<h3 id="creating-your-foaf-file">Creating your FOAF file</h3>
+
<p>If you do not already have a FOAF file for yourself, creating one is very easy. Details on how to create a FOAF file, along with a
handy wizard to guide you through the process, are available at
<a href="https://people.apache.org/foaf/">https://people.apache.org/foaf/</a>.</p>
+
<p>Since you are a potential speaker we do require you
to include a few key bits of information in the FOAF file. These are:</p>
+
<ul>
<li>Your location</li>
<li>The projects you are involved in (include foundation-wide ones, too, if you’re
@@ -214,26 +238,38 @@ happy to talk about these)</li>
<li>Your Twitter ID (so we can point people at your speaking history on
<a href="http://lanyrd.com/">Lanyrd</a>)</li>
</ul>
-<h3 id="listing-yourself-in-the-speakers-doap-file">Listing yourself in the Speakers DOAP file <a class="headerlink" title="Permalink" href="#listing-yourself-in-the-speakers-doap-file">¶</a></h3>
+
+<h3 id="listing-yourself-in-the-speakers-doap-file">Listing yourself in the Speakers DOAP file</h3>
+
<p>If you haven’t already done so, check out the committers directory from
svn:</p>
-<pre tabindex="0"><code>svn co https://svn.apache.org/repos/private/committers/
-</code></pre><p>Edit <code>local-outreach/ApacheSpeakers.rdf</code> and add yourself in as a
+
+<pre><code>svn co https://svn.apache.org/repos/private/committers/
+</code></pre>
+
+<p>Edit <code>local-outreach/ApacheSpeakers.rdf</code> and add yourself in as a
helper. If your FOAF file is in svn and showing up on people.apache.org,
add in:</p>
-<pre tabindex="0"><code><helper>
- <foaf:Person rdf:resource="urn:org:apache:[your username].rdf" />
+
+<pre><code><helper>
+ <foaf:Person rdf:resource="urn:org:apache:[your username].rdf" />
</helper>
-</code></pre><p>If you have your FOAF file externally hosted, the <strong>rdf:resource</strong>
+</code></pre>
+
+<p>If you have your FOAF file externally hosted, the <strong>rdf:resource</strong>
should point to the URL of the file.</p>
+
<p>For an apache committer with username “foo”, your entry would be one of:</p>
-<pre tabindex="0"><code><helper>
- <foaf:Person rdf:resource="urn:org:apache:foo.rdf" />
+
+<pre><code><helper>
+ <foaf:Person rdf:resource="urn:org:apache:foo.rdf" />
</helper>
<helper>
- <foaf:Person rdf:resource="https://www.example.com/foaf/foo.rdf" />
+ <foaf:Person rdf:resource="https://www.example.com/foaf/foo.rdf" />
</helper>
-</code></pre><p>Within 24 hours of committing your addition to
+</code></pre>
+
+<p>Within 24 hours of committing your addition to
<em>local-outreach/ApacheSpeakers.rdf</em>, you should appear in the web
application as a potential speaker! Head over to
<a href="https://community.zones.apache.org/">https://community.zones.apache.org/</a>