From 544c24ddb11b35655a8c56ad336e45815cdb6ac4 Mon Sep 17 00:00:00 2001 From: John Mertic Date: Fri, 30 Aug 2024 16:50:03 -0400 Subject: [PATCH] Sync templates Signed-off-by: John Mertic --- .github/dependabot.yml | 16 ++--- CODE_OF_CONDUCT.md | 1 - _config.yml | 14 +++- _data/meeting-agenda-items.csv | 56 +++++++-------- _data/projects.csv | 20 +++++- _data/tacmembers.csv | 19 +++++- _includes/projectdetails.html | 9 ++- _includes/tacmembers.html | 4 +- code_of_conduct.md | 11 +++ engagement/README.md | 2 +- index.md | 2 +- meetings/README.md | 1 + meetings/template.md | 105 ++++++++++++++++++++++------- process/README.md | 12 ++-- process/contribution_guidelines.md | 44 ++++++------ process/tsc_faq.md | 90 ++++++++++++++++++++----- programs/README.md | 3 +- programs/infrastructure.md | 1 + programs/infrastructure/plan.md | 1 + programs/license_scanning.md | 70 +++++-------------- tools/mailing_lists.md | 2 +- 21 files changed, 310 insertions(+), 173 deletions(-) delete mode 100644 CODE_OF_CONDUCT.md create mode 100644 code_of_conduct.md diff --git a/.github/dependabot.yml b/.github/dependabot.yml index 5990d9c6..c18cf18a 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -1,11 +1,11 @@ -# To get started with Dependabot version updates, you'll need to specify which -# package ecosystems to update and where the package manifests are located. -# Please see the documentation for all configuration options: -# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file - version: 2 updates: - - package-ecosystem: "" # See documentation for possible values - directory: "/" # Location of package manifests + - package-ecosystem: github-actions + directory: / + schedule: + interval: weekly + + - package-ecosystem: bundler + directory: / schedule: - interval: "weekly" + interval: weekly diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md deleted file mode 100644 index b1ce7fb2..00000000 --- a/CODE_OF_CONDUCT.md +++ /dev/null @@ -1 +0,0 @@ -All participants agree to abide by The Linux Foundation Code of Conduct available at http://events.linuxfoundation.org/code-of-conduct. diff --git a/_config.yml b/_config.yml index eb57b016..1df0fba9 100644 --- a/_config.yml +++ b/_config.yml @@ -26,6 +26,7 @@ gh_edit_repository: "https://github.com/openmainframeproject/tac" # the github U gh_edit_branch: "main" # the branch that your docs is served from gh_edit_view_mode: "tree" +# Various URLs used across the site landscape_url: 'https://landscape.openmainframeproject.org' calendar_url: 'https://calendar.openmainframeproject.org' slack_url: 'https://slack.openmainframeproject.org' @@ -35,11 +36,12 @@ helpdesk_url: "https://servicedesk.openmainframeproject.org" tac_mailing_list_url: "https://lists.openmainframeproject.org/g/omp-technical" website_url: "https://openmainframeproject.org" blog_url: "https://openmainframeproject.org/blog" +lfscanning_repo_url: https://github.com/lfscanning/spdx-omp # Founation Settings -membership_top_tier: 'Platinum' foundation_name: "Open Mainframe Project" clotributor_name: openmainframeproject +membership_top_tier: 'Platinum' aux_links: "Need help or have a question? Contact us here": @@ -56,3 +58,13 @@ kramdown: input: GFM extensions: - autolink + parse_block_html: true + toc_levels: 2..6 + +plugins: + - jekyll-redirect-from + +mermaid: + # Version of mermaid library + # Pick an available version from https://cdn.jsdelivr.net/npm/mermaid/ + version: "10.9.0" diff --git a/_data/meeting-agenda-items.csv b/_data/meeting-agenda-items.csv index 65ac32f1..0a927018 100644 --- a/_data/meeting-agenda-items.csv +++ b/_data/meeting-agenda-items.csv @@ -1,28 +1,28 @@ -title,url,number,status -Ambitus,https://github.com/openmainframeproject/tac/issues/577,577,Next Meeting Agenda Items -TSTerm,https://github.com/openmainframeproject/tac/issues/506,506,Next Meeting Agenda Items -Zorse,https://github.com/openmainframeproject/tac/issues/642,642,Future Meeting Agenda Items -COBOL Programming Course,https://github.com/openmainframeproject/tac/issues/585,585,Future Meeting Agenda Items -Software Discovery Tool,https://github.com/openmainframeproject/tac/issues/580,580,Future Meeting Agenda Items -Feilong,https://github.com/openmainframeproject/tac/issues/579,579,Future Meeting Agenda Items -Mainframe Open Education,https://github.com/openmainframeproject/tac/issues/494,494,Future Meeting Agenda Items -COBOL Check,https://github.com/openmainframeproject/tac/issues/578,578,Upcoming Meeting Agenda Items -Initial policy on TAC Chair/Vice Chair,https://github.com/openmainframeproject/tac/pull/694,694,Upcoming Meeting Agenda Items -Mainframe infrastructure coming online status,https://github.com/openmainframeproject/tac/issues/596,596,Upcoming Meeting Agenda Items -Improve the security posture of our projects,https://github.com/openmainframeproject/tac/issues/541,541,Upcoming Meeting Agenda Items -Looking for Open Mainframe Projects for Western Students,https://github.com/openmainframeproject/tac/issues/690,690,Upcoming Meeting Agenda Items -Reminder on project policies,https://github.com/openmainframeproject/tac/issues/692,692,Upcoming Meeting Agenda Items -GenevaERS,https://github.com/openmainframeproject/tac/issues/575,575,Future Meeting Agenda Items -TerseDecompress,https://github.com/openmainframeproject/tac/issues/576,576,Future Meeting Agenda Items -CBT Tape,https://github.com/openmainframeproject/tac/issues/530,530,Future Meeting Agenda Items -COBOL Working Group,https://github.com/openmainframeproject/tac/issues/581,581,Future Meeting Agenda Items -Tessia,https://github.com/openmainframeproject/tac/issues/531,531,Future Meeting Agenda Items -z/VM Community Tools,https://github.com/openmainframeproject/tac/issues/454,454,Future Meeting Agenda Items -Modernization Working Group,https://github.com/openmainframeproject/tac/issues/529,529,Future Meeting Agenda Items -Linux Distributions Working Group,https://github.com/openmainframeproject/tac/issues/532,532,Future Meeting Agenda Items -Zowe,https://github.com/openmainframeproject/tac/issues/526,526,Future Meeting Agenda Items -Galasa,https://github.com/openmainframeproject/tac/issues/584,584,Future Meeting Agenda Items -CD Foundation Best Practices SIG,https://github.com/openmainframeproject/tac/issues/460,460,On Hold -CLOTributor for Open Mainframe Project,https://github.com/openmainframeproject/tac/issues/620,620,On Hold -z/OS Open Tools,https://github.com/openmainframeproject/tac/issues/625,625,Future Meeting Agenda Items -MainframeGPT,https://github.com/openmainframeproject/tac/issues/644,644,On Hold +title,url,number,scheduled_date,status,meeting_label +Ambitus,https://github.com/openmainframeproject/tac/issues/577,577,2024-09-12,Next Meeting Agenda Items,2-annual-review +TSTerm,https://github.com/openmainframeproject/tac/issues/506,506,2024-09-12,Next Meeting Agenda Items,2-annual-review +Zorse,https://github.com/openmainframeproject/tac/issues/642,642,2025-07-10,Future Meeting Agenda Items,2-annual-review +COBOL Programming Course,https://github.com/openmainframeproject/tac/issues/585,585,2025-04-10,Future Meeting Agenda Items,2-annual-review +Software Discovery Tool,https://github.com/openmainframeproject/tac/issues/580,580,2025-05-22,Future Meeting Agenda Items,2-annual-review +Feilong,https://github.com/openmainframeproject/tac/issues/579,579,2025-07-24,Future Meeting Agenda Items,2-annual-review +Mainframe Open Education,https://github.com/openmainframeproject/tac/issues/494,494,2025-06-26,Future Meeting Agenda Items,2-annual-review +COBOL Check,https://github.com/openmainframeproject/tac/issues/578,578,2024-08-22,Upcoming Meeting Agenda Items,2-annual-review +Initial policy on TAC Chair/Vice Chair,https://github.com/openmainframeproject/tac/pull/694,694,,Upcoming Meeting Agenda Items, +Mainframe infrastructure coming online status,https://github.com/openmainframeproject/tac/issues/596,596,,Upcoming Meeting Agenda Items, +Improve the security posture of our projects,https://github.com/openmainframeproject/tac/issues/541,541,,Upcoming Meeting Agenda Items, +Looking for Open Mainframe Projects for Western Students,https://github.com/openmainframeproject/tac/issues/690,690,,Upcoming Meeting Agenda Items, +Reminder on project policies,https://github.com/openmainframeproject/tac/issues/692,692,,Upcoming Meeting Agenda Items, +GenevaERS,https://github.com/openmainframeproject/tac/issues/575,575,2024-09-26,Future Meeting Agenda Items,2-annual-review +TerseDecompress,https://github.com/openmainframeproject/tac/issues/576,576,2024-10-10,Future Meeting Agenda Items,2-annual-review +CBT Tape,https://github.com/openmainframeproject/tac/issues/530,530,2024-10-10,Future Meeting Agenda Items,2-annual-review +COBOL Working Group,https://github.com/openmainframeproject/tac/issues/581,581,2024-11-14,Future Meeting Agenda Items,2-annual-review +Tessia,https://github.com/openmainframeproject/tac/issues/531,531,2024-10-24,Future Meeting Agenda Items,2-annual-review +z/VM Community Tools,https://github.com/openmainframeproject/tac/issues/454,454,2024-12-12,Future Meeting Agenda Items,2-annual-review +Modernization Working Group,https://github.com/openmainframeproject/tac/issues/529,529,2024-09-26,Future Meeting Agenda Items,2-annual-review +Linux Distributions Working Group,https://github.com/openmainframeproject/tac/issues/532,532,2024-12-12,Future Meeting Agenda Items,2-annual-review +Zowe,https://github.com/openmainframeproject/tac/issues/526,526,2024-11-14,Future Meeting Agenda Items,2-annual-review +Galasa,https://github.com/openmainframeproject/tac/issues/584,584,2025-04-24,Future Meeting Agenda Items,2-annual-review +CD Foundation Best Practices SIG,https://github.com/openmainframeproject/tac/issues/460,460,,On Hold, +CLOTributor for Open Mainframe Project,https://github.com/openmainframeproject/tac/issues/620,620,,On Hold, +z/OS Open Tools,https://github.com/openmainframeproject/tac/issues/625,625,2025-03-13,Future Meeting Agenda Items,2-annual-review +MainframeGPT,https://github.com/openmainframeproject/tac/issues/644,644,,On Hold,1-new-project-wg diff --git a/_data/projects.csv b/_data/projects.csv index 7be98c4c..dfc9f3a6 100644 --- a/_data/projects.csv +++ b/_data/projects.csv @@ -1,2 +1,18 @@ -Name,Level,Logo URL,Slack,Website,Leads,Calendar -OpenTelemetry on Mainframes,third-party-sig,https://opentelemetry.io/img/logos/opentelemetry-horizontal-color.svg,https://cloud-native.slack.com/archives/C05PXDFTCPJ,https://github.com/open-telemetry/community/blob/86aeb7e63cc4dd21337cdb2b45c6bbf0ab6693db/projects/mainframe.md,Ruediger Schulze and Aaron Young,https://calendar.google.com/calendar/u/0/r/eventedit/copy/MzBub3V1dnVodWVxbW5rMDdtdGZuMXMzdTJfMjAyNDAxMTZUMTgwMDAwWiBnb29nbGUuY29tX2I3OWUzZTkwajdiYnNhMm4ycDVhbjVsZjYwQGc +Name,Level,Logo URL,Slug,Categories,Website,Chair,TAC Representative,Documentation,Calendar,Artwork,iCal,LFX Insights URL,Accepted Date,Last Review Date,Next Review Date,Slack,Mailing List,Github Org,Best Practices Badge ID,Primary Github Repo,Contributed By +COBOL Programming Course,active,https://landscape.openmainframeproject.org/logos/cobol-programming-course.svg,cobol-programming-course,"Open Mainframe Project Projects / All,Projects / Learning and Mentoring",https://www.openmainframeproject.org/projects/cobolprogrammingcourse,Sudharsana Srinivasan,,,https://zoom-lfx.platform.linuxfoundation.org/meetings/cobol-programming-course,https://artwork.openmainframeproject.org/projects/cobol-programming-course,https://webcal.prod.itx.linuxfoundation.org/lfx/a092M00001KWrdtQAD,https://insights.lfx.linuxfoundation.org/foundation/open-mainframe-project/overview?project=cobol-programming-course,2021-08-03,2024-04-11,2025-04-10,,,,4770,https://github.com/openmainframeproject/cobol-programming-course, +GenevaERS,active,https://landscape.openmainframeproject.org/logos/geneva-ers.svg,geneva-ers,"Open Mainframe Project Projects / All,Projects / z/OS",https://genevaers.org/,Andrea Orth,,,https://zoom-lfx.platform.linuxfoundation.org/meetings/genevaers,https://artwork.openmainframeproject.org/projects/genevaers,https://webcal.prod.itx.linuxfoundation.org/lfx/a092M00001IkTlvQAF,https://insights.lfx.linuxfoundation.org/foundation/open-mainframe-project/overview?project=genevaers,2021-03-29,2023-08-10,2024-09-26,,https://lists.openmainframeproject.org/g/genevaers-discussion,https://github.com/genevaers,4181,https://github.com/genevaers/Community, +Mainframe Open Education,active,https://landscape.openmainframeproject.org/logos/mainframe-open-education.svg,mainframe-open-education,"Open Mainframe Project Projects / All,Projects / Learning and Mentoring",https://www.openmainframeproject.org/projects/mainframeopeneducation,Lauren Valenti,,,https://zoom-lfx.platform.linuxfoundation.org/meetings/mainframe-open-education,https://artwork.openmainframeproject.org/projects/mainframe-open-education,https://webcal.prod.itx.linuxfoundation.org/lfx/a092M00001IkTlxQAF,https://insights.lfx.linuxfoundation.org/foundation/open-mainframe-project/overview?project=mainframe-open-education,2024-07-16,2024-06-27,2025-06-26,,,,7414,https://github.com/openmainframeproject/omp-education, +Zowe,active,https://landscape.openmainframeproject.org/logos/zowe.svg,zowe,"Open Mainframe Project Projects / All,Projects / z/OS",https://www.zowe.org/,"Jakub Balhar, Sean Grady",,,https://zoom-lfx.platform.linuxfoundation.org/meetings/zowe,https://artwork.openmainframeproject.org/projects/zowe,https://webcal.prod.itx.linuxfoundation.org/lfx/a092M00001IV4KHQA1,https://insights.lfx.linuxfoundation.org/foundation/open-mainframe-project/overview?project=zowe,2021-08-03,2023-10-26,2024-11-14,,https://lists.openmainframeproject.org/g/zowe-dev,https://github.com/zowe,2226,https://github.com/zowe/zac, +Ambitus,incubating,https://landscape.openmainframeproject.org/logos/ambitus.svg,ambitus,"Open Mainframe Project Projects / All,Projects / Other",https://www.openmainframeproject.org/projects/ambitus,Joe Bostian,,,https://zoom-lfx.platform.linuxfoundation.org/meetings/ambitus,https://artwork.openmainframeproject.org/projects/ambitus,https://webcal.prod.itx.linuxfoundation.org/lfx/a092M00001JWqRDQA1,https://insights.lfx.linuxfoundation.org/foundation/open-mainframe-project/overview?project=ambitus,2020-02-24,2023-07-13,2024-09-12,,,,6264,https://github.com/ambitus/ambitus, +CBT Tape,incubating,https://landscape.openmainframeproject.org/logos/cbt-tape.svg,cbt-tape,"Open Mainframe Project Projects / All,Projects / z/OS",https://www.cbttape.org/,Sam Golob,,,https://zoom-lfx.platform.linuxfoundation.org/meetings/cbt-tape,https://artwork.openmainframeproject.org/projects/cbt-tape,https://webcal.prod.itx.linuxfoundation.org/lfx/a092M00001IkTm0QAF,https://insights.lfx.linuxfoundation.org/foundation/open-mainframe-project/overview?project=cbt-tape,2020-09-09,2023-10-12,2024-10-10,,,https://github.com/CBTTape,False,https://github.com/CBTTape/Dicussions, +COBOL Check,incubating,https://landscape.openmainframeproject.org/logos/cobol-check.svg,cobol-check,"Open Mainframe Project Projects / All,Projects / Development Tools",https://github.com/openmainframeproject/cobol-check,Rune Christensen,,,https://zoom-lfx.platform.linuxfoundation.org/meetings/cobol-check,https://artwork.openmainframeproject.org/projects/cobol-check,https://webcal.prod.itx.linuxfoundation.org/lfx/a092M00001KWfljQAD,https://insights.lfx.linuxfoundation.org/foundation/open-mainframe-project/overview?project=cobol-check,2021-02-16,2023-06-08,2024-08-22,,https://lists.openmainframeproject.org/g/cobol-check-discussion,,5559,https://github.com/openmainframeproject/cobol-check, +Feilong,incubating,https://landscape.openmainframeproject.org/logos/feilong.svg,feilong,"Open Mainframe Project Projects / All,Projects / Linux",https://www.openmainframeproject.org/projects/feilong,Mike Friesenegger,,,https://zoom-lfx.platform.linuxfoundation.org/meetings/feilong,https://artwork.openmainframeproject.org/projects/feilong,https://webcal.prod.itx.linuxfoundation.org/lfx/a092M00001IfR9gQAF,https://insights.lfx.linuxfoundation.org/foundation/open-mainframe-project/overview?project=feilong,2019-08-20,2024-07-19,2025-07-24,,https://lists.openmainframeproject.org/g/feilong-discussion,,False,https://github.com/openmainframeproject/feilong, +Galasa,incubating,https://landscape.openmainframeproject.org/logos/galasa.svg,galasa,"Open Mainframe Project Projects / All,Projects / Development Tools",https://galasa.dev/,Louisa Seers,,,https://zoom-lfx.platform.linuxfoundation.org/meetings/galasa,https://artwork.openmainframeproject.org/projects/galasa,https://webcal.prod.itx.linuxfoundation.org/lfx/a092M00001O6R6SQAV,https://insights.lfx.linuxfoundation.org/foundation/open-mainframe-project/overview?project=galasa,2023-07-03,2024-04-25,2025-04-24,,https://lists.openmainframeproject.org/g/galasa-discussion,https://github.com/galasa-dev,9214,https://github.com/galasa-dev/galasa.dev, +Software Discovery Tool,incubating,https://landscape.openmainframeproject.org/logos/software-discovery-tool.svg,software-discovery-tool,"Open Mainframe Project Projects / All,Projects / Other",https://www.openmainframeproject.org/projects/software-discovery-tool,Elizabeth Joseph,,,https://zoom-lfx.platform.linuxfoundation.org/meetings/software-discovery-tool,https://artwork.openmainframeproject.org/projects/software-discovery-tool,https://webcal.prod.itx.linuxfoundation.org/lfx/a092M00001IkTmPQAV,https://insights.lfx.linuxfoundation.org/foundation/open-mainframe-project/overview?project=software-discovery-tool,2020-09-09,2024-06-28,2025-05-22,,,,False,https://github.com/openmainframeproject/software-discovery-tool, +Tessia,incubating,https://landscape.openmainframeproject.org/logos/tessia.svg,tessia,"Open Mainframe Project Projects / All,Projects / Linux",https://www.openmainframeproject.org/projects/tessia,"Deepak Kulkarni, Sanjay Kumar",,,https://zoom-lfx.platform.linuxfoundation.org/meetings/tessia,https://artwork.openmainframeproject.org/projects/tessia,https://webcal.prod.itx.linuxfoundation.org/lfx/a092M00001IkUvgQAF,https://insights.lfx.linuxfoundation.org/foundation/open-mainframe-project/overview?project=tessia,2020-10-23,2023-10-12,2024-10-24,,https://lists.openmainframeproject.org/g/tessia-user,,False,https://github.com/tessia-project/tessia, +TerseDecompress,sandbox,https://landscape.openmainframeproject.org/logos/terse-decompress.svg,terse-decompress,"Open Mainframe Project Projects / All,Projects / Other",https://www.openmainframeproject.org/projects/tersedecompress,Oleksandr Hubanov,,,https://zoom-lfx.platform.linuxfoundation.org/meetings/tersedecompress,https://artwork.openmainframeproject.org/projects/tersedecompress,https://webcal.prod.itx.linuxfoundation.org/lfx/a092M00001IfRAKQA3,https://insights.lfx.linuxfoundation.org/foundation/open-mainframe-project/overview?project=tersedecompress,2019-08-20,2023-08-10,2024-10-10,,,,7734,https://github.com/openmainframeproject/tersedecompress, +TSTerm,sandbox,https://landscape.openmainframeproject.org/logos/ts-term.svg,ts-term,"Open Mainframe Project Projects / All,Projects / z/OS",https://github.com/TSTerminal,Joe Devlin,,,,https://artwork.openmainframeproject.org/projects/tsterm/,,,,2023-09-14,2024-09-12,,https://lists.openmainframeproject.org/g/tsterm-discussion,https://github.com/TSTerminal,False,https://github.com/TSTerminal/TSTerm, +z/VM Community Tools,sandbox,https://landscape.openmainframeproject.org/logos/z-vm-community-tools.svg,z-vm-community-tools,"Open Mainframe Project Projects / All,Projects / z/VM",https://github.com/openmainframeproject/zvm-community-tools,,,,,https://artwork.openmainframeproject.org/projects/zvm-community-tools/,,,,2022-06-09,2024-12-12,,https://lists.openmainframeproject.org/g/zvm-communitytools-discussion,,False,https://github.com/openmainframeproject/zvm-community-tools, +COBOL Working Group,working-group,https://landscape.openmainframeproject.org/logos/cobol-working-group.svg,cobol-working-group,"Open Mainframe Project Projects / All,Projects / Learning and Mentoring",https://www.openmainframeproject.org/projects/cobol-working-group,Cam Seay,,,https://zoom-lfx.platform.linuxfoundation.org/meetings/cobol-working-group,https://artwork.openmainframeproject.org/projects/cobol-working-group,https://webcal.prod.itx.linuxfoundation.org/lfx/a092M00001IkUvlQAF,https://insights.lfx.linuxfoundation.org/foundation/open-mainframe-project/overview?project=cobol-working-group,2020-07-09,2023-08-24,2024-11-14,,,,False,https://github.com/openmainframeproject/wg-cobol, +Linux Distributions Working Group,working-group,https://landscape.openmainframeproject.org/logos/linux-distributions-working-group.svg,linux-distributions-working-group,"Open Mainframe Project Projects / All,Projects / Linux",https://wiki.openmainframeproject.org/display/LinuxDistrosWG/Linux+Distributions+Working+Group,Elizabeth Joseph,,,https://zoom-lfx.platform.linuxfoundation.org/meetings/omp-linux-distributions-wg,https://artwork.openmainframeproject.org/projects/omp-linux-distributions-wg,https://webcal.prod.itx.linuxfoundation.org/lfx/a092M00001MaHzKQAV,https://insights.lfx.linuxfoundation.org/foundation/open-mainframe-project/overview?project=omp-linux-distributions-wg,2021-06-10,2023-10-26,2024-12-12,,https://lists.openmainframeproject.org/g/wg-linux-distros,,False,, +Mainframe Modernization WG,working-group,https://landscape.openmainframeproject.org/logos/mainframe-modernization-wg.svg,mainframe-modernization-wg,"Open Mainframe Project Projects / All,Projects / Other",https://modernization.openmainframeproject.org,Misty Decker,,,https://zoom-lfx.platform.linuxfoundation.org/meetings/mainframe-modernization-wg,https://artwork.openmainframeproject.org/projects/mainframe-modernization-wg,https://webcal.prod.itx.linuxfoundation.org/lfx/a092M00001L1HVVQA3,https://insights.lfx.linuxfoundation.org/foundation/open-mainframe-project/overview?project=mainframe-modernization-wg,2022-09-01,2023-09-14,2024-09-26,,https://lists.openmainframeproject.org/g/wg-modernization,,False,, diff --git a/_data/tacmembers.csv b/_data/tacmembers.csv index 231e08a1..1d5bda56 100644 --- a/_data/tacmembers.csv +++ b/_data/tacmembers.csv @@ -1,10 +1,27 @@ Full Name,Account Name: Account Name,Appointed By,Voting Status,Special Role,Title,HeadshotURL Andrea Orth,State Farm Mutual Automobile Insurance Company,Vote of TSC Committee,Voting Rep,None,Scrum Master,https://avatars0.githubusercontent.com/u/61636929?v=4 +Cam Seay,East Carolina University,Community,Observer,None,Instructor,https://platform-logos-myprofile-api-prod.s3.us-east-2.amazonaws.com/cwseay.png?v=1691004737625 +Claus Bjørno,Bankdata,Vote of TSC Committee,Observer,None,"Product Owner, Mainframe DevX",https://lfx-cdn-prod.s3.amazonaws.com/users/avatar/c.png +Deepak Kulkarni,International Business Machines Corporation,Vote of TSC Committee,Observer,None,,https://lfx-cdn-prod.s3.amazonaws.com/users/avatar/d.png +Derek Britton,DRB B2B Ltd,Community,Observer,None,Global Head of Product Marketing,https://platform-logos-myprofile-api-prod.s3.us-east-2.amazonaws.com/derekbritton.png?v=1721815623263 +Elizabeth Joseph,International Business Machines Corporation,Vote of TSC Committee,Observer,None,"Global Head, Open Source Program Office for IBM zSystems & LinuxONE",https://platform-logos-myprofile-api-prod.s3.us-east-2.amazonaws.com/pleia2.png?v=1695923509387 +Gabriel Gordon-Hall,Individual - No Account,Vote of TSC Committee,Observer,None,,https://avatars.githubusercontent.com/u/24595376?v=4 Giancarlo Frix,Rocket Software,Membership Entitlement,Voting Rep,None,Senior Software Developer,https://platform-logos-myprofile-api-prod.s3.us-east-2.amazonaws.com/gfrix.png?v=1691075442605 -Gregory MacKinnon,Broadcom Corporation,Membership Entitlement,Voting Rep,None,Distinguished Engineer,https://avatars.githubusercontent.com/u/35381000?v=4 +Gregory Mackinnon,Broadcom Corporation,Membership Entitlement,Voting Rep,None,Distinguished Engineer,https://avatars.githubusercontent.com/u/35381000?v=4 +Ingo Adlung,International Business Machines Corporation,,Observer,None,Chief Architect IBM z Systems Virtualization & Linux,https://lfx-cdn-prod.s3.amazonaws.com/users/avatar/i.png Joe Bostian,International Business Machines Corporation,Membership Entitlement,Voting Rep,None,Open Source and Analytics Architect,https://platform-logos-myprofile-api-prod.s3.us-east-2.amazonaws.com/jbostian.png?v=1707847571558 +Joe Devlin,"Zoss Team, LLC",Vote of TSC Committee,Observer,None,Partner,https://platform-logos-myprofile-api-prod.s3.us-east-2.amazonaws.com/joedevlin.1629831030855 +John Mertic,The Linux Foundation,None,Observer,LF Staff,Director of Program Management,https://platform-logos-myprofile-api-prod.s3.us-east-2.amazonaws.com/jmertic.png?v=1709042439248 Lauren Valenti,Broadcom Corporation,Vote of TSC Committee,Voting Rep,None,Head of Mainframe Education and Customer Engagement,https://avatars.githubusercontent.com/u/74365281?v=4 +Louisa Seers,International Business Machines Corporation,Vote of TSC Committee,Observer,None,CICS & Galasa Product Manager,https://platform-logos-myprofile-api-prod.s3.us-east-2.amazonaws.com/louisaseers.png?v=1690192863251 Mike Friesenegger,SUSE Software Solutions Germany GmbH,Membership Entitlement,Voting Rep,None,Solution Architect,https://media.licdn.com/dms/image/C5103AQHEb__yfmKufA/profile-displayphoto-shrink_800_800/0/1516345372562?e=1720656000&v=beta&t=_u25gzbmVpqiOKcuI5qAUhgpYfGfVDZivHpcTFz0-9Y +Misty Decker,Kyndryl,Vote of TSC Committee,Observer,None,Mainframe Modernization Consult Leader,https://platform-logos-myprofile-api-prod.s3.us-east-2.amazonaws.com/mistymvd.png?v=1683742899143 +Oleksandr Hubanov,Rocket Software,Vote of TSC Committee,Observer,None,-,https://platform-logos-myprofile-api-prod.s3.us-east-2.amazonaws.com/alexgubanow.1677964476283 Phil Tully,Citi,Membership Entitlement,Voting Rep,Chair,LinuxONE Engineering Operations Director,https://platform-logos-myprofile-api-prod.s3.us-east-2.amazonaws.com/philiptully.png?v=1655918229871 +Ray Mullins,Individual - No Account,Vote of TSC Committee,Observer,None,,https://lfx-cdn-prod.s3.amazonaws.com/users/avatar/r.png +Sam Golob,CBT Tape,Vote of TSC Committee,Observer,None,Project Head,https://lfx-cdn-prod.s3.amazonaws.com/users/avatar/s.png +Sanjay Kumar,IBM Watson Health,Vote of TSC Committee,Observer,None,,https://lfx-cdn-prod.s3.amazonaws.com/users/avatar/s.png Sean Grady,"Rocket Software, Inc.",Vote of TSC Committee,Voting Rep,None,Senior Software Architect,https://avatars.githubusercontent.com/u/30730276?v=4 +Stephen Hodges,AveriSource,Vote of TSC Committee,Observer,None,,https://lfx-cdn-prod.s3.amazonaws.com/users/avatar/s.png Sudharsana Srinivasan,International Business Machines Corporation,Vote of TSC Committee,Voting Rep,None,IBM Z Influencer Program Manager,https://platform-logos-myprofile-api-prod.s3.us-east-2.amazonaws.com/sudharsana20.png?v=1691074904727 +Tom Slanda,The Linux Foundation,None,Observer,LF Staff,Projects Coordinator,https://platform-logos-myprofile-api-prod.s3.us-east-2.amazonaws.com/tslanda.png?v=1710787259792 diff --git a/_includes/projectdetails.html b/_includes/projectdetails.html index 527945e4..83a43236 100644 --- a/_includes/projectdetails.html +++ b/_includes/projectdetails.html @@ -40,11 +40,14 @@ {%- if project["Documentation"] and project["Documentation"] != 'none' -%} Documentation: {{ project["Documentation"] }}
{%- endif -%} - {%- if project["Leads"] and project["Leads"] != 'none' -%} - Lead(s): {{ project["Leads"] }}
+ {%- if project["Chair"] and project["Chair"] != 'none' -%} + Chair(s): {{ project["Chair"] }}
{%- endif -%} {%- if project["Calendar"] and project["Calendar"] != 'none' -%} - Calendar: {{ project["Calendar"] }}
+ Public Calendar: {{ project["Calendar"] }}
+ {%- endif -%} + {%- if project["iCal"] and project["iCal"] != 'none' -%} + iCal: {{ project["iCal"] }}
{%- endif -%} {%- if project["Best Practices Badge ID"] and project["Best Practices Badge ID"] != 'none' and project["Best Practices Badge ID"] != 'False' -%} diff --git a/_includes/tacmembers.html b/_includes/tacmembers.html index 2a11ffed..9a21d2a7 100644 --- a/_includes/tacmembers.html +++ b/_includes/tacmembers.html @@ -25,9 +25,9 @@ {{ member["Full Name"] }} {%- for project in site.data.projects -%} - {%- if project["TAC Representative"] == member["Full Name"] -%} + {%- if project["TAC Representative"] contains member["Full Name"] -%} {{ project["Name"] }} Representative - {%- elsif project["Leads"] == member["Full Name"] -%} + {%- elsif project["Chair"] contains member["Full Name"] -%} {{ project["Name"] }} Representative {%- endif -%} {%- endfor -%} diff --git a/code_of_conduct.md b/code_of_conduct.md new file mode 100644 index 00000000..d59b8480 --- /dev/null +++ b/code_of_conduct.md @@ -0,0 +1,11 @@ +--- +nav_order: 999 +--- + +# Code of Conduct + +{{ site.foundation_name }} aims to foster a collaborative, inclusive, and safe environment for all participants. {{ site.foundation_name }} and each hosted project have established Codes of Conduct to help provide guidelines on appropriate conduct and how to report violations. + +For all hosted projects, refer to the CODE_OF_CONDUCT.md file in the each code repository that points to policy in use. + +For all other activities and events that are sanctioned by {{ site.foundation_name }}, refer to the [LF Events Code of Conduct](https://events.linuxfoundation.org/about/code-of-conduct/). diff --git a/engagement/README.md b/engagement/README.md index 9980d976..cc2016aa 100644 --- a/engagement/README.md +++ b/engagement/README.md @@ -1,7 +1,7 @@ --- title: Getting Involved has_children: false -nav_order: 2 +nav_order: 10 --- # Getting Involved in Projects diff --git a/index.md b/index.md index 1ae1a56b..e60dbe3d 100644 --- a/index.md +++ b/index.md @@ -32,7 +32,7 @@ Each of the {{ site.foundation_name }} projects are open to participation by any Working groups may be formed by the TAC to focus on specific areas of technical interest or need within {{ site.foundation_name }}. They report to the TAC which remains responsible for any formal decisions or voting matters. -Below are the project and working groups supported by the TAC, listed by [project stage](process/lifecycle) +Below are the projects and working groups supported by the TAC, listed by [project stage](process/lifecycle) {%- include projectlist.html -%} diff --git a/meetings/README.md b/meetings/README.md index debfb2c4..b35a81a3 100644 --- a/meetings/README.md +++ b/meetings/README.md @@ -2,6 +2,7 @@ title: "Meetings" has_children: true child_nav_order: reversed +order: 30 --- # TAC Meetings diff --git a/meetings/template.md b/meetings/template.md index a0545670..d6c339a6 100644 --- a/meetings/template.md +++ b/meetings/template.md @@ -12,54 +12,111 @@ parent: Meetings title: "{{ "now" | date: "%Y-%m-%d" }}" --- -# Open Mainframe Project TAC Meeting - {{ "now" | date: "%B %e, %Y" }} +# {{ site.foundation_name }} Technical Advisory Council (TAC) Meeting - {{ "now" | date: "%B %e, %Y" }} -# Attendance +{%- if site.tac_lfx_meeting_url -%} +Join the meeting at [{{ site.tac_lfx_meeting_url }}]({{ site.tac_lfx_meeting_url }}) +{%- endif -%} -## Voting member attendance +## Voting Representative Attendees -{% for member in site.data.tacmembers %} -{%- if member["Appointed By"] == "Membership Entitlement" -%} +### {{ site.membership_top_tier }} Member Representatives +{% for member in site.data.tacmembers -%} +{% if member["Appointed By"] == "Membership Entitlement" %} - [ ] {{ member["Full Name"] }} - {{ member["Account Name: Account Name"] }} -{%- elsif member["Appointed By"] == "Vote of TSC Committee" -%} +{%- endif -%} +{% endfor %} + +### Project Representatives +{% for member in site.data.tacmembers -%} +{% if member["Appointed By"] == "Vote of TSC Committee" and member['Voting Status'] != 'Observer' %} {%- for project in site.data.projects -%} -{%- if project["TAC Representative"] == member["Full Name"] -%} +{% if project["TAC Representative"] contains member["Full Name"] %} - [ ] {{ member["Full Name"] }} - {{ project["Name"] }} Representative -{%- elsif project["Leads"] == member["Full Name"] -%} +{%- break -%} +{% elsif project["Chair"] contains member["Full Name"] %} - [ ] {{ member["Full Name"] }} - {{ project["Name"] }} Representative +{%- break -%} {%- endif -%} {%- endfor -%} -{% endif %} +{%- endif -%} {% endfor %} -## Other attendees -# Antitrust Policy Notice +{%- if site.vote_of_tac_committee_title -%} +### {{ site.vote_of_tac_committee_title }} +{% for member in site.data.tacmembers -%} +{% if member["Appointed By"] == "Vote of TAC Committee" %} +- [ ] {{ member["Full Name"] }} - {{ member["Account Name: Account Name"] }} +{%- endif -%} +{% endfor %} +{%- endif -%} -Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. +## Non-Voting Attendees -Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at [linuxfoundation.org/antitrust-policy](https://www.linuxfoundation.org/antitrust-policy). If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation. +### Non-Voting Project and Working Group Representatives +{% for member in site.data.tacmembers -%} +{%- if member['Voting Status'] == 'Observer' -%} +{%- for project in site.data.projects -%} +{% if project["TAC Representative"] contains member["Full Name"] %} +- [ ] {{ member["Full Name"] }} - {{ project["Name"] }} Representative +{%- break -%} +{% elsif project["Chair"] contains member["Full Name"] %} +- [ ] {{ member["Full Name"] }} - {{ project["Name"] }} Representative +{%- break -%} +{%- endif -%} +{%- endfor -%} +{%- endif -%} +{% endfor %} -# Meeting Recording +### LF Staff +{% for member in site.data.tacmembers -%} +{% if member["Special Role"] == "LF Staff" %} +- [ ] {{ member["Full Name"] }} - {{ member["Account Name: Account Name"] }} +{%- endif -%} +{% endfor %} -Meeting recording and transcript is [here]() +### Other Attendees -# Agenda -{% assign agendaitems = site.data.meeting-agenda-items | where: "status", "Upcoming Meeting Agenda Items" %} -{%- for agendaitem in agendaitems -%} -- {{ agendaitem.title }} [#{{ agendaitem.number }}]({{ agendaitem.url }}) -{% endfor %} -# Notes +## Antitrust Policy Notice -# Next Meeting Agenda +Linux Foundation meetings involve participation by industry competitors, and it +is the intention of the Linux Foundation to conduct all of its activities in +accordance with applicable antitrust and competition laws. It is therefore +extremely important that attendees adhere to meeting agendas, and be aware of, +and not participate in, any activities that are prohibited under applicable US +state, federal or foreign antitrust and competition laws. -{% assign agendaitems = site.data.meeting-agenda-items | where: "status", "Next Meeting Agenda Items" %} +Examples of types of actions that are prohibited at Linux Foundation meetings +and in connection with Linux Foundation activities are described in the Linux +Foundation Antitrust Policy available at +[linuxfoundation.org/antitrust-policy](https://www.linuxfoundation.org/antitrust-policy). +If you have questions about these matters, please contact your company counsel, +or if you are a member of the Linux Foundation, feel free to contact Andrew +Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to +the Linux Foundation. + +## Agenda + +{% assign agendaitems = site.data.meeting-agenda-items | where: "status", "Upcoming Meeting Agenda Items" | sort: "meeting_label" -%} +- General Updates {%- for agendaitem in agendaitems -%} +{%- if agendaitem.meeting_label == "4-tac-meeting-short" %} + - {{ agendaitem.title }} [#{{ agendaitem.number }}]({{ agendaitem.url }}) +{%- endif -%} +{% endfor %} +{% for agendaitem in agendaitems -%} +{%- if agendaitem.meeting_label != "4-tac-meeting-short" -%} - {{ agendaitem.title }} [#{{ agendaitem.number }}]({{ agendaitem.url }}) +{%- endif %} {% endfor %} +## Notes + + {%- endcapture -%} {{ agenda }} -Create Pull Request | +Create Pull Request | + diff --git a/process/README.md b/process/README.md index 8d7b8cc9..45a7123e 100644 --- a/process/README.md +++ b/process/README.md @@ -1,17 +1,17 @@ --- has_children: true -nav_order: 2 +nav_order: 20 --- # Processes -These are the various processes and policies adopted by the ASWF TAC. Any new proposed policies, or changes to existing policies, should be done via PR and merged only after the TAC has formally approved. +These are the various processes and policies adopted by the {{ site.foundation_name }} TAC. Any new proposed policies, or changes to existing policies, should be done via PR and merged only after the TAC has formally approved. When adding new files in this directory, be sure to add the following metadata at the top of the file... ```jekyll - --- - title: # put the page title here - parent: Processes - --- +--- +title: # put the page title here +parent: Processes +--- ``` diff --git a/process/contribution_guidelines.md b/process/contribution_guidelines.md index ec118ccd..62a614be 100644 --- a/process/contribution_guidelines.md +++ b/process/contribution_guidelines.md @@ -8,13 +8,13 @@ title: Contribution Guidelines * TOC {:toc} -This document captures the general guidelines for contributing to open-source projects hosted by Open Mainframe Project. These guidelines express the provisions in the Intellectual Property Policy within [Open Mainframe Project charter](https://openmainframeproject.org/charter). +This document captures the general guidelines for contributing to open-source projects hosted by {{ site.foundation_name }}. These guidelines express the provisions in the Intellectual Property Policy within [{{ site.foundation_name }} charter]({{ site.directed_fund_charter_url }}). Note that each hosted project may adopt its guidelines, which would supersede these provisions in the case of conflict. -## Two-factor authentication (2FA) +## Two-factor Authentication (2FA) -To enable more robust security for hosted projects, Open Mainframe Project TAC requires all hosted projects to require Two-factor authentication (2FA) for accessing code repositories. Instructions for GitHub are below... +To enable more robust security for hosted projects, {{ site.foundation_name }} TAC requires all hosted projects to require Two-factor authentication (2FA) for accessing code repositories. Instructions for GitHub are below... - [Configuring 2FA for your GitHub account](https://docs.github.com/en/github/authenticating-to-github/configuring-two-factor-authentication) - [Accessing GitHub using 2FA](https://docs.github.com/en/github/authenticating-to-github/accessing-github-using-two-factor-authentication) @@ -22,12 +22,12 @@ To enable more robust security for hosted projects, Open Mainframe Project TAC r ## License specification -All source code must clearly identify the open-source license used. The Open Mainframe Project charter dictates [Apache 2](https://spdx.org/licenses/Apache-2.0.html) by default, except for Linux kernel code which must be [GPLv2](https://spdx.org/licenses/GPL-2.0) unless a specific project charter's intellectual property policy states otherwise. The Project will receive and make all documentation and other non-code assets available under the Creative Commons Attribution 4.0 International License (available at http://creativecommons.org/licenses/by/4.0/). +All source code must clearly identify the open-source license used. {{ site.foundation_name }} hosted projects generally use the [Apache License, Version 2.0](https://spdx.org/licenses/Apache-2.0.html) for all code contributions and the [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0/) for documentation and other non-code assets. Each hosted project maintains their own Intellectual Property policy as part of thier Technical Charter which outlines the specific guidelines. Requirements to ensure license compliance - Each repository must contain a license file. Include the plain-text version of the license as a LICENSE file in the top-level directory of the repository. -- All source files need to include a header to clearly show the license. Open Mainframe Project has standardized on including [SPDX short-form license identifiers](https://spdx.org/ids) and a general copyright statement as shown below ( this example is for Apache 2.0 licensed code ): +- All source files need to include a header to clearly show the license. {{ site.foundation_name }} has standardized on including [SPDX short-form license identifiers](https://spdx.org/ids) and a general copyright statement as shown below ( this example is for Apache 2.0 licensed code ): ```` /** @@ -39,13 +39,13 @@ Requirements to ensure license compliance The license may be omitted for property or configuration files that do not support comments. If comments are supported, the license header should be included. -Contributors may include a copyright statement specifying themselves or their employer (as applicable) as the copyright holder of their contributions, but the Open Mainframe Project does not require or recommend this. +Contributors may include a copyright statement specifying themselves or their employer (as applicable) as the copyright holder of their contributions, but the {{ site.foundation_name }} does not require or recommend this. -Finally, please note that pre-existing third-party license notices and copyright notices *should not be modified or removed* by anyone other than the copyright holder. Any questions on including code under a different license than the project should be discussed with the project lead and Open Mainframe Project Governing Board. +Finally, please note that pre-existing third-party license notices and copyright notices *should not be modified or removed* by anyone other than the copyright holder. Any questions on including code under a different license than the project should be discussed with the project lead and {{ site.foundation_name }} Governing Board. ## Developer Certificate of Origin -Open Mainframe Project requires the Developer’s Certificate of Origin 1.1 (DCO), the same mechanism the [Linux® Kernel](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst#n416) and many other communities use to manage code contributions. The DCO is considered one of the simplest tools for sign-offs from contributors as the representations are meant to be easy to read and indicate signoff is done as a part of the commit message. +{{ site.foundation_name }} requires the Developer’s Certificate of Origin 1.1 (DCO), the same mechanism the [Linux® Kernel](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst#n416) and many other communities use to manage code contributions. The DCO is considered one of the simplest tools for sign-offs from contributors as the representations are meant to be easy to read and indicate signoff is done as a part of the commit message. Here is an example Signed-off-by line, which indicates that the submitter accepts the DCO: @@ -53,9 +53,16 @@ Here is an example Signed-off-by line, which indicates that the submitter accept You can include this automatically when you commit a change to your local git repository using git commit -s. -Additionally, it is possible to use shell scripting to apply signoff automatically. Here is an example for bash to be put into a .bashrc file: +### Make doing DCO signoffs easier -``` +By default, all GitHub repositories have both the [GitHub DCO App][] installed and [commit signoffs enabled][GitHub commit signoff policy]. This ensures anyone contributing via the GitHub web interface will automatically signoff commits. + +For developers working from thier local machines, there are a few options available to automatically signoff commits. + +- DCO command line tool, which lets you do a single signoff for an entire repo ( https://github.com/coderanger/dco ) +- Shell scripting to automatically apply signing. Here is an example for bash, to be put into a .bashrc file: + +```bash git() { if [[ $1 == "commit" ]]; then shift @@ -69,7 +76,7 @@ git() { ### Signoff for commits where the DCO signoff was missed -When bringing in a code repository for the first time or commits done before the DCO checks are enabled, there would be a series of commits that don't include the sign-off statement. You can retroactively signoff commits you've made by making a commit with your DCO signoff that contains a new text file (the suggested name is past_commits.txt ) with the following contents: +When bringing in a code repository for the first time or commits done before the DCO checks are enabled, there would be a series of commits that don't include the sign-off statement. You can retroactively signoff commits you've made by making a commit with your DCO signoff that contains a new text file (the suggested name is `past_commits.txt` ) with the following contents: ```` The following commits were made pursuant to the Developer Certificate of Origin, even though a Signed-off-by: was not included in the commit message. @@ -78,18 +85,13 @@ The following commits were made pursuant to the Developer Certificate of Origin, ... ```` -Each user who has made the past commits should have their Signed-off-by: line in the commit message. +Each user who has made past commits should have their own Signed-off-by: line in the commit message. This process can be automated using the [DCO Org Check script](https://github.com/jmertic/dco-org-check). -### Handling DCO errors using GitHub website commits - -The [Probot: DCO](https://github.com/probot/dco) app requires that the email address and name specified in the DCO Signoff match that of the current information from the user making the commit. Generally, this is handled automatically when using a local git client, but when making contributions from the GitHub website directly, this needs to be aligned manually. - -If you are using one of the recommended [GitHub UI integrations for adding the signoff automatically]( https://github.com/scottrigby/dco-gh-ui), you should ensure that the name and email listed there match that which is in your GitHub profile. - -Examples of the UI elements to match are below. +### Handling DCO errors using GitHub website commits. -GitHub user profile (https://github.com/settings/profile) -![](assets/github-settings-profile.png) +The [Probot: DCO](https://github.com/probot/dco) app requires that the email address and name specified in the DCO Signoff match that of the current information from the user making the commit. Generally, this is handled automatically when using a local git client, but when making contributions from the GitHub website directly, this needs to be aligned manually. +[GitHub commit signoff policy]: https://docs.github.com/en/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization +[GitHub DCO App]: https://github.com/apps/dco diff --git a/process/tsc_faq.md b/process/tsc_faq.md index ebd7edd7..650d501d 100644 --- a/process/tsc_faq.md +++ b/process/tsc_faq.md @@ -1,6 +1,7 @@ --- parent: Project Lifecycle grand_parent: Processes +nav_order: 99 --- # Technical Steering Committee (TSC) FAQ @@ -17,15 +18,26 @@ The Technical Steering Committee (TSC) is the leadership of the project. This co ## Members -Typically the TSC is comprised of the primary committers or maintainers in a project. To start there may be an appointed list, but over time more individuals may join the TSC according to the policies the TSC set for how new members are added. Regardless, TSC meetings are generally open to anyone interested unless there are sensitive issues to discuss which necessitate a private meeting. +Typically, the TSC comprises the primary committers or maintainers in a project. To start, there may be an appointed list, but over time, more individuals may join the TSC according to the policies the TSC set for adding new members. Regardless, TSC meetings are generally open to anyone interested unless there are sensitive issues to discuss, necessitating a private meeting. -[LFX Project Control Center](https://projectadmin.lfx.linuxfoundation.org/) is a tool for managing project committees and roles within a project. Each project will be setup in that tool with a voting committee named 'Technical Steering Committee (TSC)', notating the project chairperson and all of the voting members. Project chairpersons will have access to manage this in addition to the Linux Foundation staff supporting the project. +[LFX Project Control Center] is a tool for managing project committees and roles within a project. Each project will be set up in that tool with a voting committee named 'Technical Steering Committee (TSC)' notating the project chairperson and all voting members. Project chairpersons, in addition to the Linux Foundation staff supporting the project, will have access to manage this. -More details on using LFX Project Control Center for committee management can be found [in the LFX documentation](https://docs.linuxfoundation.org/lfx/project-control-center-pre-release/setup-services-for-a-project/committees-setup-for-a-project). +Additionally, each project has a [GitHub Team][GitHub Teams Docs] set up which will provide ['Maintain' permission]((https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization#permissions-for-each-role)) for each project maintainer. Generally, the LF staff will have this set up for each project; after that, the project is expected to maintain any changes. + +More details on using LFX Project Control Center for committee management can be found [in the LFX documentation][LFX PCC Committee Management Docs]. + +### Adding New Members + +The TSC can add members at any time with a simple majority vote of the current TSC members. The vote can be held during a regular TSC meeting, via email, or as part of a GitHub Issue; either way, it is crucial to have a documented vote for adding the individual with the votes recorded. You should also save this vote in the TSC records for future reference to provide full transparency into TSC member selection. + +Once a TSC member is confirmed, the TSC Chairperson should... + +- Add them to the TSC Committee in [LFX Project Control Center]. +- Update the GitHub repository team to add the TSC member as appropriate. ## Roles -Generally, TSCs have a few roles to facilitate the operations of the TSC. Roles are elected by TSC voting members and term lengths are determined by the TSC. +Generally, TSCs have a few roles in facilitating the operations of the TSC. TSC voting members elect roles, and the TSC determines term lengths. ### Chairperson @@ -33,15 +45,15 @@ The TSC Chairperson is the figurehead of the project. The TSC Chairperson's prim - Lead all meetings of the TSC, setting the agenda with the consultation of other TSC members. - Be the public spokesperson for the project at events and in public communications ( such as PR/AR meetings, articles, and blog posts ) -- Serve as a representative of the project to the TAC and other projects and entities. +- Serve as a project representative to the TAC and other projects and entities. ### Secretary -The Secretary records all meeting notes for TSC members and ensures they are distributed to the project community after the meeting in a timely manner. Often projects have a rotating secretary role instead of a permanent role. +The Secretary records all meeting notes for TSC members and ensures they are distributed to the project community after the meeting in a timely manner. Often, projects have a rotating secretary role instead of a permanent role. ### Additional roles -TSCs often will add additional roles on an as-needed basis to manage different areas or roles within a project. TSCs can come up with the right definitions and scope for these roles, but it's highly advised to document them to ensure expectations are aligned. +TSCs often add additional roles on an as-needed basis to manage different areas or functions within a project. TSCs can develop the correct definitions and scope for these roles, but it's highly advised to document them to ensure expectations are aligned. Roles we've seen in a project include but aren't limited to... @@ -50,34 +62,78 @@ Roles we've seen in a project include but aren't limited to... - Release Manager - Documentation Lead +### Transitioning Roles + +Individuals in project roles change from time to time, and it's important to have both a transparent selection process and ensure all relevant permissions are transitioned to the new role owner. In general, TSCs should follow the following process when transitioning roles: + +1) Define an election or selection process for the role. This should be documented in a GOVERNANCE.md file or similar document. +2) Hold a vote of the TSC to confirm the individual being elected to the role. +3) Update any systems relevant to the role, in particular... + - Add the role for the person on the TSC Committee in [LFX Project Control Center], specifying the date they started the role and, if the role has a set term, the date the role will end. + - [Contact the LF Staff][Service Desk], which will assist in changes to other resources, namely... + - Changing the project's TAC representative if needed. The TAC Chairperson serves as the TAC representative unless the project indicates otherwise. This representative will be added to the [Technical Leads Mailing List], the TAC Committee, and associated mailing lists ( [TAC Mailing List] and [TAC Private Mailing List] ). + - Updating the GitHub repository team to give the TSC Chairperson the ['team maintainer permission'](https://docs.github.com/en/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member) so they can add/remove maintainers and TSC members from the team. Projects may also request additional roles be given that permission as well. + +TSC charters do not dictate the specific terms or election processes for any of the roles within the TSC; it's expected that the TSC develops these as part of its policies and documents them in a GOVERNANCE.md file or similar document. + ## Meetings -TSC meetings are opportunities for the project community to come together to share updates and discuss issues and future plans. All TSC meetings are considered open to the public unless there is a sensitive issue to discuss ( in the case of private meetings, Linux Foundation staff should be present at such meetings ). +TSC meetings allow the project community to share updates and discuss issues and plans. All TSC meetings are considered open to the public unless there is a sensitive issue to discuss ( in the case of private meetings, Linux Foundation staff should be present at such meetings ). -It's recommended to schedule meetings on a regular cadence ( for example, every other week at 2pm US Pacific Time ). Many project communities alternate TSC meeting times if project members are globally dispersed ( for example, one time that is US Eastern/Europe friendly and another that is US Pacific/Asia/Australia friendly ). +It's recommended to schedule meetings on a regular cadence ( for example, every other week at 2:00 pm US Pacific Time ). Many project communities alternate TSC meeting times if project members are globally dispersed ( for example, one time that is US Eastern/Europe friendly and another that is US Pacific/Asia/Australia friendly ). ### Scheduling logistics -Using LFX Project Control Center, you can easily schedule one-off or recurring meetings that automatically send invites to TSC members, allow other interested parties to register for meetings, and record meetings and make them available for others. Additionally, it provides excellent statistics for meeting attendance which can help you assess member engagement. +Using LFX Project Control Center, you can easily schedule one-off or recurring meetings that automatically send invites to TSC members, allow other interested parties to register for meetings, and record and make them available for others. Additionally, it provides excellent statistics for meeting attendance, which can help you assess member engagement. -More details on using LFX Project Control Center for meeting management can be found [in the LFX documentation](https://docs.linuxfoundation.org/lfx/project-control-center-pre-release/it-services-for-a-project/meetings). +More details on using LFX Project Control Center for meeting management can be found [in the LFX documentation][LFX PCC Meeting Management Docs]. -For public meetings, LFX PCC provides a public link for sharing the meeting with non-attendees so they can register for the meeting. It's recommended to make that link available publically. +For public meetings, LFX PCC provides a public link for sharing the meeting with non-attendees so they can register. It's recommended that that link be made available publicly. ### Agenda -The TSC Chairperson should share an agenda at least 24 hours prior to the meeting, if possible, with an ask to share additional agenda items. Projects can share via the public discussion lists or using a pull request on GitHub. +The TSC Chairperson should share an agenda at least 24 hours before the meeting with an ask to share additional agenda items. The agenda should be shared through the public communication/collaboration channels they use ( such as mailing lists, chat channels, GitHub, etc ). ## FAQs about TSCs -### Q: Is a TSC member required to have their employer be a member of the Open Mainframe Project? +### Q: Is a TSC member required to have their employer be a member of the {{ site.foundation_name }}? -A: No - All technical community work, such as projects and working groups, are open to anyone to participate and not bound by membership in the Open Mainframe Project. +A: No - All technical community work, such as projects and working groups, is open to anyone to participate and not bound by membership in the {{ site.foundation_name }}. ### Q: Does a person lose their membership in a TSC if they leave or change employers? -A: No - TSC membership is bound to an individual and not an organization. If the change of employment for a TSC member results in a key contributing organization having a lack of TSC representation, the TSC may choose to invite a new TSC member affiliated with that organization, provided that that person meets any requirements set for TSC membership. +A: No - TSC membership is bound to an individual, not an organization. If a change of employment for a TSC member results in a key contributing organization lacking TSC representation, the TSC may invite a new TSC member affiliated with that organization, provided that person meets any requirements for TSC membership. ### Q: Does an individual serving on the TSC represent themselves, the project, and/or their employer? -A: As TSC members are individuals within the context of a TSC, it's expected that all their actions are for the general good of the project itself. It's not appropriate to use the project for anti-competitive purposes, nor is it appropriate to discuss a TSC member employer's product plans and roadmap in conjunction with the project planning. +A: As TSC members are individuals within the context of a TSC, it's expected that all their actions are for the general good of the project itself. It's not appropriate to use the project for anti-competitive purposes nor to discuss a TSC member employer's product plans and roadmap in conjunction with the project planning. + +### Q: Could a project start working groups or sub-committees within their project? + +Yes, projects can establish working groups or sub-committees ( herein referred to as 'subgroups' ) and do not need to change their Technical Charter to accommodate. + +When thinking about starting a new subgroup, generally, projects tend to follow a few key factors: + +- Is this initiative big enough, with a long enough timeline (6+ months usually, or ongoing is also ok) +- Will this initiative require a level of collaboration and discussion that is not possible in the general TSC meeting? +- Should this initiative involve folks not on the TSC? +- Is this a high priority for the project? + +If the answer to all or most of these questions is yes, a subgroup is a good idea. + +Each project can develop its own specific process around establishing subgroups. Generally, projects should align with the following key points: + +- It's best practice to have a TSC member as either the leader or, at minimum, a defined member of the subgroup. This person is responsible for the group's operation, meetings, and communication with the larger TSC about progress. +- Each subgroup should have a charter. This can be a simple one-pager, outlining the purpose, goals, non-goals, and deliverables of the subgroup. The TSC should approve this charter +Just like TSC Meetings, subgroup meetings must be open to anyone interested in participating. Someone should be tasked with taking notes for each subgroup meeting that capture key discussion points and action items. +- Evaluate the subgroups on a regularly scheduled basis, and try not to keep them around indefinitely. Once their larger goals have been achieved, they can be folded back into normal TSC operations. + + +[TAC Mailing List]: https://lists.aswf.io/g/tac +[TAC Private Mailing List]: https://lists.aswf.io/g/tac-private +[Technical Leads Mailing List]: https://lists.aswf.io/g/technical-project-leads +[LFX Project Control Center]: https://projectadmin.lfx.linuxfoundation.org/ +[Service Desk]: https://servicedesk.aswf.io +[LFX PCC Meeting Management Docs]: https://docs.linuxfoundation.org/lfx/project-control-center-pre-release/it-services-for-a-project/meetings +[LFX PCC Committee Management Docs]: https://docs.linuxfoundation.org/lfx/project-control-center-pre-release/setup-services-for-a-project/committees-setup-for-a-project +[GitHub Teams Docs]: https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams diff --git a/programs/README.md b/programs/README.md index 17d68ef4..bd3c1bc4 100644 --- a/programs/README.md +++ b/programs/README.md @@ -1,6 +1,7 @@ --- title: Programs has_children: true +nav_order: 40 --- -The Open Mainframe Project supports a number of programs that are driven by the requirements and oversight of the TAC and technical communities, with the operational components supported by the project staff. Read more about them below. +The {{ site.foundation_name }} supports a number of programs that are driven by the requirements and oversight of the TAC and technical communities, with the operational components supported by the project staff. Read more about them below. diff --git a/programs/infrastructure.md b/programs/infrastructure.md index ae7a6f0b..ddac4440 100644 --- a/programs/infrastructure.md +++ b/programs/infrastructure.md @@ -1,5 +1,6 @@ --- has_children: true +parent: Programs title: Mainframe Access --- diff --git a/programs/infrastructure/plan.md b/programs/infrastructure/plan.md index 3fc63eb0..238d8b13 100644 --- a/programs/infrastructure/plan.md +++ b/programs/infrastructure/plan.md @@ -1,4 +1,5 @@ --- +grand_parent: Programs parent: Mainframe Access title: Plan --- diff --git a/programs/license_scanning.md b/programs/license_scanning.md index 59d73639..6323a676 100644 --- a/programs/license_scanning.md +++ b/programs/license_scanning.md @@ -1,26 +1,13 @@ --- -parent: Programs title: License Scanning +parent: Programs --- -# The Linux Foundation License Scanning and Analysis Support Program for LF projects - -- [Support plan summary for 2022: Open Mainframe Project](#support-plan-summary-for-2022-open-mainframe-project) - - [Notes](#notes) - - [Dependencies on other LF and project teams](#dependencies-on-other-lf-and-project-teams) - - [Covered projects and schedule of scans](#covered-projects-and-schedule-of-scans) - - [Every Month](#every-month) - - [Cycle 1](#cycle-1) - - [Cycle 2](#cycle-2) - - [Cycle 3](#cycle-3) - - [Exhibits](#exhibits) - - [Exhibit 1](#exhibit-1) - - [Exhibit 2](#exhibit-2) - - [Exhibit 3](#exhibit-3) +# License Scanning and Analysis Support Program -## Support plan summary for 2022: Open Mainframe Project - -Support to be provided by: Jeff Shapiro <> +* TOC +{:toc} +## Support plan summary For the projects described below, the following actions will be performed: @@ -32,8 +19,7 @@ performed: contained in the project codebases 3. Publish SPDX documents with the license conclusions and copyright - statements at (or a similar public - location), for broader community use in their own compliance + statements at <{{ site.lfscanning_repo_url }}>, for broader community use in their own compliance processes 4. Produce summary reports for project leads / maintainers, with @@ -69,8 +55,9 @@ performed: describe the requested exceptions and facilitate approvals under the charter -Stretch goals: will perform where feasible, subject to available -resources and time: +### Stretch goals + +Will perform where feasible, subject to available resources and time: 1. Run “red flag” pre-intake scans, for net new projects: @@ -129,33 +116,6 @@ continued development of the scanning workflow automation. managed by LF IT (none presently anticipated for current projects / scan types) - -## Covered projects and schedule of scans - -### Every Month - -- Zowe - -### TBD - -- Ambitus ( see note below ) - -- CBT Tape ( see note below ) - -### March/June/Sept/Dec - -- All other projects - -Anticipate up to approximately 12 new small-to-medium projects to come -in during 2022. Will perform pre-intake scans and allocate to cycles -based on project sizing. - -- **Ambitus**: to be discussed what to cover in scanning, in light of -Ambitus’s forks of several large pre-existing OSS projects. - -- **CBT Tape**: to be discussed what (if anything) to cover in -scanning, in light of CBT Tape’s historical context. - ## Exhibits 1. Screenshots from example SPDX document @@ -168,8 +128,8 @@ scanning, in light of CBT Tape’s historical context. **Screenshots from example SPDX document** -Graphical user interface, text, application Description automatically generated -Text Description automatically generated +Graphical user interface, text, application Description automatically generated +Text Description automatically generated ### Exhibit 2 @@ -177,18 +137,18 @@ scanning, in light of CBT Tape’s historical context. Key findings and recommended actions: -Graphical user interface, text, application, email Description automatically generated +Graphical user interface, text, application, email Description automatically generated Summary of findings: -A picture containing graphical user interface Description automatically generated +A picture containing graphical user interface Description automatically generated Spreadsheet with detailed findings: -Graphical user interface, table Description automatically generated +Graphical user interface, table Description automatically generated ### Exhibit 3 **Screenshots from example board decks** -Graphical user interface, application Description automatically generated +Graphical user interface, application Description automatically generated diff --git a/tools/mailing_lists.md b/tools/mailing_lists.md index cf7030c9..dffad71e 100644 --- a/tools/mailing_lists.md +++ b/tools/mailing_lists.md @@ -51,4 +51,4 @@ Being a moderator is as much a privilege as it is a duty. As part of volunteerin - Contact the list moderators if there are concerns about the [Code of Conduct][]. [Code of Conduct]: /code_of_conduct -[TAC Mailing List]: {{ site.tac_mailinglist_url }} +[TAC Mailing List]: {{ site.tac_mailing_list_url }}