| commit | 4f764bb68b4a628001d50538c12cf237672f3998 | [log] [tgz] |
|---|---|---|
| author | Jarek Potiuk <jarek@potiuk.com> | Wed Jul 17 04:58:50 2024 +0200 |
| committer | GitHub <noreply@github.com> | Wed Jul 17 10:58:50 2024 +0800 |
| tree | 01e43cc77ea1095be9bb42ac0d92079c6f90f7bf | |
| parent | f9264d7698420fc0b23b00a871947801b9e9c0fb [diff] |
Clarify and split new committer / new PMC member templates (#183)
Since we are now reaching out to projects about PMC vs. PMC member,
I looked at the source of some of the templates that are used and
clarified, unified them and fixed a few errors in those templates,
also replaced the link to anchor in www-site about new PMC member
with #newpmcmember instead of #newpmc, which could be confusing
and one of the reasons why people use New PMC rather than New PMC
member.
The problem with those templates were that they did not provide
correct templates for inviting (and following up) in case the
PMC member was invited separately from committer - the templates
required manual modifications of Commiter to "PMC member" and
manually modifying text of the template, which could be onoe of
the reasons why people replaced "Committer" with "PMC member" in
their invitations.
The change splits the process out of inviting PMC member separately
(while leaving the optional process where committer is immediately
a PMC member in the original place).
This PR also unifies the way how links are added to the page, there
was a mixture of `[n]` references and `md` way of inlining links.
Another part of this change is introducing "PMC member" everywhere
where "PMC" could be confused with person. For example the
"PMC candidate" - while technically correct ("candidate to the PMC")
is another reason why people could confuse "PMC" with person.
Replacing it with "PMC member candidate" removes the confusion while
being also techincally correct.
The last part of it that in a few places the documentation was
wrongly referring to "asking the board" when inviting PMC member,
where this process have been changed last year to "notifying the board".
All those places have been corrected.This is the source code for the ASF Community Development PMC website, hosted at community.apache.org
To get in touch with that PMC please use the dev@community.apache.org mailing list.
The events.apache.org website is also managed by the Community Development PMC but managed in the comdev-events-site repository.
Changes to the main or preview/* branches of this repository trigger the comdev-site Jenkins Job, which generates and pushes the website content.
There's currently (April 2020) a lag of about ten minutes for the corresponding Jenkins job to start, if you commit directly to the GitHub repository, but you can also start the job manually if you have the required Jenkins access rights.
For the main branch, the generated content is pushed to the asf-site branch, and the ASF's gitpubsub mechanism then synchronizes that content to the live community.apache.org website, usually within a few seconds.
Branches named preview/<name> are staged automatically, a branch named preview/0421b for example is staged at https://community-0421b.staged.apache.org/ .
More details about the publication process can be found in the ASF Documentation about Project sites. If for some reason this process fails, you can use the self-service page from ASF Infra to trigger a resync of the git repo.
The website uses Hugo as static website generator, see the Hugo website for more information and for how to install and run it if needed.
Other Apache websites that are built with Hugo should be listed by this GitHub query for the ‘hugo’ tag.
You need a recent version of hugo, to find out which one is used to deploy this site look at the Jenkins build output, linked above.
To generate the static website, execute hugo to generate the website under target/content and execute npx -y pagefind --site target/content to index the content for Pagefind (the search bar on the website).
During development, it may be useful to run an incremental build. For this to work, execute hugo server -D -d /tmp/comdev-generated-site to continuously (re)generate and serve the website on localhost:1313 (-D means include draft pages). In another terminal, execute npx -y pagefind --site /tmp/comdev-generated-site to index the site content for Pagefind (the search bar on the website).