Page History

Planning/Brainstorming doc for community.apache.org website.  We have some newfound energy to improve the website, so it can be a truly useful resource to any kind of newcomer to the ASF or our projects.

• TODO Purge ancient/outdated content
  • Mentoring - we do not (currently) have a mentoring program
    • Perhaps note that some projects/other areas might have mentoring programs?
    • Delete content around a mentoring program
    • Move stuff that's actually about GSoC under GSoC
  • Remove mentions of 'helpwanted' service (Done)
  • Remove references to speaker program (Unless someone wants to make that actually a thing)
  • Remove references to community.zones.apache.org
    • Find out what that is (is it a VM?) and drop it.  (Note: it still technically works with the map, but isn't useful, so agreed to decomission)
  • About half of the files at the top-level of the site
    • comdevboardreports.md
    • newsletter (Two editions, back in 2017. Seemed like a good idea at the time, but didn't last.)
    • calendars/ (This content is a duplicate of events.apache.org) (links to it removed; still need to clean content)

Top level content should help lead anyone - newcomers to the ASF, or committers at ASF projects looking for best practices - to the best place to find information about how the ASF operates.

Key navigation links to include - focus on newcomers

• Overview topics explaining high-level ASF concepts, what ComDev does, and pointing tech questions to ASF projects themselves
• Best practices (for specific audiences)   (question: do we have energy to make different versions of contributor ladder? Developers, testers, designers, writers, etc. each have different interests and paths)
  
  • Beginner
  • Contributor
    • See the Contributor Ladder concept at https://github.com/cncf/project-template/blob/main/CONTRIBUTOR_LADDER.md
  • Committer
  • PMC
    • Understanding the role of the Chair
    • Reporting tips/guidelines (Examples of good reports!)and official PMC Board Reporting Guide
    • How/When/Why to promote committers, PMC members
• Some sort of general pointer to projects.a.o or other information reminding newcomers how many separate projects we have
• Links to other conceptual best practices (these are important on the larger scale)
  • ComDev Mailing list page (with brief intro of "here's how to ask questions - use this list")
  • Project Independence https://community.apache.org/projectIndependence.html
  • Maturity Model https://community.apache.org/apache-way/apache-project-maturity-model.html

Other important navigation links - focus on ComDev as a project & our activities

• Links to various "What is the ASF Way" and orgchart kinds of information to help explain how the ASF relates to all ASF projects (like ComDev)
• Event participation
• GSoC
• ALC
• Required links to Apache.org pages (see ASF policy requirement)
• Tools
  • COMDEV JIRA instance
  • Projects.apache.org
    • Helpful info about updating DOAP
    • Should we actively reach out to projects with wrong/old/missing DOAP?  (yes, but how do we do it effectively?)
  • Reporter.apache.orgorg  - Also links to PMC Board Reporting Guide
  • Link to "how to make PRs for this website" page: https://github.com/apache/comdev-site#how-to-publish-the-website
    • Note: linking to GitHub helps people understand they can make PRs, but doesn't actually help non-git people understand "how do I fix this typo". so we should figure out how to explain the "very simple process for suggesting a change" somewhere too.  See also FAQ: https://community.apache.org/newbiefaq.html#websitecms

...