summaryrefslogtreecommitdiff
path: root/generator
AgeCommit message (Collapse)Author
2023-02-08Update issue template for annual reportsChristoph Blecker
2023-02-08Fix formatting in GitHub issue generationChristoph Blecker
2023-02-08Fix KEP generation and formattingChristoph Blecker
2023-01-22Add automatic labelling for annual reports and charter changesChristoph Blecker
2023-01-21auto generate list of subprojects & working-groups from annual report yearPriyanka Saggu
2023-01-16auto generate list of KEPs in annual-report/sig_report go templatePriyanka Saggu
2022-05-26Write generate errors to stderrJordan Liggitt
2022-05-12Fix `make test`Yuki Okushi
2022-01-27Link to working groups from SIG readmesJordan Liggitt
2022-01-27Link to sigs from WG readmesJordan Liggitt
2022-01-25Add annual report templates for 2021Christoph Blecker
2022-01-24Update generator README with AR detailsChristoph Blecker
2022-01-24Add notes to AR template that the generation will happen in the futureChristoph Blecker
2022-01-24Add link to the AR tempate that was generatedChristoph Blecker
2022-01-24Fix AR dates to match governance docsChristoph Blecker
2022-01-22Add generation function for annual reportChristoph Blecker
2022-01-21Merge pull request #6355 from parispittman/liaisonupdateKubernetes Prow Robot
adding liaison expectations
2022-01-21vi is busted lolParis Pittman
2022-01-17add links for labels in sig-list.mdDavanum Srinivas
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
2021-12-02Add note about calendar invites to templatesEddie Zaneski
Signed-off-by: Eddie Zaneski <eddiezane@gmail.com>
2021-06-21Update app.goBoleyn Su
fix a typo
2021-03-09generator: make subproject owners links usefulAaron Crickenberger
reduce the visual noise, and make the links go to githubs UI so: https://raw.githubusercontent.com/org/repo/branch/path/to/OWNERS becomes: - link text: org/repo/path/to - link target: https://github.com/org/repo/blob/branch/path/to/ORWNERS note: this does assume/imply we don't need to model the complexity of subprojects owning different branches... but, we haven't found a reason to do so in 5 years, seems a safe assumption
2021-03-09generator: allow github and raw urls in sigs.yamlAaron Crickenberger
2021-03-09generator: add githubURL, orgRepoPath funcsAaron Crickenberger
2021-03-09generator: add validation of subprojectsAaron Crickenberger
specifically: - only sigs+committees can have subprojects - subprojects need at least one owners entry - owners should be raw github links I think the last one could/should change, but: - I'm about to auto-generate links assuming this format, so I want to verify I can assume all owners are in this format - I am not quite sure if we should treat sigs.yaml as public api and give notice/deprecation for field changes
2021-03-09generator: "make test" passes againAaron Crickenberger
there's a lot of boilerplate that is now expected in sigs.yaml
2021-01-20generator: support liaisons in sigs.yamlNikhita Raghunath
2020-12-21Replace master list with community group name in sig-list templateBob Killen
2020-12-21Add hugo metadata to SIG list so we can index it on k8s.dev (#5066)Jorge O. Castro
* Add hugo metadata to SIG list so we can index it on k8s.dev Signed-off-by: Jorge O. Castro <jorgec@vmware.com> * Run make generate to generate the proper file Signed-off-by: Jorge O. Castro <jorgec@vmware.com> * Move hugo block above the template header Signed-off-by: Jorge O. Castro <jorgec@vmware.com> * Update generator/list.tmpl Co-authored-by: Bob Killen <killen.bob@gmail.com> * Run make to generate final page Signed-off-by: Jorge O. Castro <jorgec@vmware.com> Co-authored-by: Bob Killen <killen.bob@gmail.com>
2020-01-23generator: update OWNERS to current list of reviewersNikhita Raghunath
2020-01-23generator/app: add means for sorted and de-duped OWNERS_ALIASESLubomir I. Ivanov
- Add LeadershipGroup#Owners() which returns a sorted and de-duped list of owners ([]Person) for this LeadershipGroup by combining Chairs and TechnicalLeads - The function is used in generator/aliases.tmpl - Update OWNERS_ALIASES with the new results
2019-10-05generator: remove company for emeritus_leads from templatesNikhita Raghunath
2019-10-05generator: don't specify company for emeritus_leadsNikhita Raghunath
If we end up specifying the company for emeritus leads, we could end up stale information. Moreover, we don't gain any specific value from company info of emeritus leads.
2019-08-08Make subprojects linkable, move github teams under contactsAaron Crickenberger
This commit only contains the generator changes for easier review The bulleted list of subprojects makes it impossible to link someone to specific info for a given subproject. Now, instead of linking someone to sig-testing#subprojects and asking them to scroll, I link them directly to sig-testing#kind. While I was at this, I made the main SIG/WG/UG/Committee contact info format match what is used for subprojects, specifically: - display the slack channel name - list github teams as part of contact info instead of in a table - use - instead of * for bullets I also removed subproject rendering from WGs, since WGs cannot own code, and added a link to the governance definition of what a subproject is.
2019-07-30generator: enable validation for sigs.yamlNikhita Raghunath
2019-07-25generator: add emeritus leads to WG and UG templateNikhita Raghunath
2019-05-06Validate same github id has same name/compayAaron Crickenberger
2019-05-03Prototype validation of sigs.yamlAaron Crickenberger
Demonstrating this could be done, not going to enforce it for now. There are also a number of these conventions that could probably just be auto-generated.
2019-05-03Update generator to reformat sigs.yamlAaron Crickenberger
The following formatting is enforced: - Consistent identation of 2 spaces - Keys are sorted by order of struct fields - Lists are sorted by struct-dependent keys - Comments are stripped I had hopes of using yaml.Node to preserve comments, but found no obvious way to marshal from struct to Node, meaning all data manipulation had to be done against Nodes. This loses us all of the benefits of using a struct: types, known fields, field order. Given that there aren't many comments in sigs.yaml to begin with, I'm erring on the side of dropping support for them.
2019-05-03Upgrade to gopkg.in/yaml.v3Aaron Crickenberger
This gives us access to the yaml.Node type, which can be used to preserve more formatting than v2 supported during round tripping of YAML
2019-04-09Display label for user groups in the SIG listNikhita Raghunath
2019-03-20Update generator OWNERSAaron Crickenberger
I reviewed PRs over the last year: - nikhita has done consistent review on almost every change that touches this code, added a number of substantive changes herself, and is a contribex tech lead - pruning grodrigues3 due to lack of activity in the past year
2019-03-20Merge pull request #3466 from nikhita/committee-subprojectKubernetes Prow Robot
Add subprojects for committees
2019-03-20Make subproject contacts optional, nest in displayAaron Crickenberger
2019-03-20Add contact (slack, mailing_list, teams) to subprojectsAaron Crickenberger
Demonstrate by adding slack channels for sig-testing subprojects that already have their own slack channels Add a GitHub team related to conformance to sig-arch's conformance definition subproject GitHub teams as implemented now are very kubernetes-org centric, I'm not trying to change that here, would suggest a followup change to allow for the use of github teams in other orgs (like kubernetes-sigs)
2019-03-19generator: add subprojects for committeesNikhita Raghunath
2019-03-15generator: add support for committeesNikhita Raghunath
Since committees can have private mailing lists, this commit also adds a new field for specifying private mailing lists in the "Contacts" section.
2019-03-14Merge pull request #3359 from nikhita/ug-owners-aliasesKubernetes Prow Robot
Automatically update OWNERS_ALIASES for UGs
2019-03-14fix link to weekly meetingDaniel Holbach
Signed-off-by: Daniel Holbach <daniel@weave.works>
2019-03-12Fix links to sig creation/lifecycle docNikhita Raghunath
generated by cgit v1.2.3 (git 2.25.1) at 2026-02-12 14:55:20 +0000