| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2023-02-08 | Fix formatting in GitHub issue generation | Christoph Blecker | |
| 2023-02-08 | Fix KEP generation and formatting | Christoph Blecker | |
| 2023-01-21 | auto generate list of subprojects & working-groups from annual report year | Priyanka Saggu | |
| 2023-01-16 | auto generate list of KEPs in annual-report/sig_report go template | Priyanka Saggu | |
| 2022-05-26 | Write generate errors to stderr | Jordan Liggitt | |
| 2022-01-27 | Link to working groups from SIG readmes | Jordan Liggitt | |
| 2022-01-27 | Link to sigs from WG readmes | Jordan Liggitt | |
| 2022-01-22 | Add generation function for annual report | Christoph Blecker | |
| 2021-06-21 | Update app.go | Boleyn Su | |
| fix a typo | |||
| 2021-03-09 | generator: make subproject owners links useful | Aaron 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-09 | generator: allow github and raw urls in sigs.yaml | Aaron Crickenberger | |
| 2021-03-09 | generator: add githubURL, orgRepoPath funcs | Aaron Crickenberger | |
| 2021-03-09 | generator: add validation of subprojects | Aaron 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-01-20 | generator: support liaisons in sigs.yaml | Nikhita Raghunath | |
| 2020-01-23 | generator/app: add means for sorted and de-duped OWNERS_ALIASES | Lubomir 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-05 | generator: don't specify company for emeritus_leads | Nikhita 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-07-30 | generator: enable validation for sigs.yaml | Nikhita Raghunath | |
| 2019-05-06 | Validate same github id has same name/compay | Aaron Crickenberger | |
| 2019-05-03 | Prototype validation of sigs.yaml | Aaron 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-03 | Update generator to reformat sigs.yaml | Aaron 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-03 | Upgrade to gopkg.in/yaml.v3 | Aaron 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-03-20 | Make subproject contacts optional, nest in display | Aaron Crickenberger | |
| 2019-03-20 | Add contact (slack, mailing_list, teams) to subprojects | Aaron 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-15 | generator: add support for committees | Nikhita 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-02-26 | Add support for User Groups in sigs.yaml | Nikhita Raghunath | |
| 2019-01-16 | generator: add support for stakeholder SIGs for WGs | Nikhita Raghunath | |
| 2018-11-02 | trim whitespace around sub-project descriptions | Mike Danese | |
| so block descriptions look the same as inline descriptions. | |||
| 2018-06-14 | Add field to define a link to the SIG's charter | Christoph Blecker | |
| 2018-04-04 | fix grammar mistake | mahuihuang | |
| 2018-03-14 | Modify generator to support chairs/tech leads | Christoph Blecker | |
| 2018-02-23 | Add ability to have custom content in OWNERS_ALIASES | Christoph Blecker | |
| 2018-02-09 | Update sig-auth leads | Jordan Liggitt | |
| 2018-02-07 | Add strawman implementation of subprojects | Aaron Crickenberger | |
| A subproject is a one-to-many mapping of a name to a list of OWNERS urls. This allows for a subproject to be a single repo (eg: helm), or a subproject to be a list of multiple subdirectories across one or more repos (eg: workloads api) SIG meetings dedicated to a single subproject moved down to subproject meetings | |||
| 2018-01-24 | Case insensitive slice sort | Christoph Blecker | |
| 2018-01-24 | Generate OWNERS_ALIASES from sigs.yaml | Christoph Blecker | |
| 2018-01-24 | Modify sig docs generator to handle multiple meetings | Christoph Blecker | |
| 2018-01-18 | generator: add google groups for github teams | Nikhita Raghunath | |
| 2017-11-26 | Use teams array to generate Github Team list | Christoph Blecker | |
| 2017-11-06 | Make time zone explicit | Joe Beda | |
| 2017-10-24 | Don't use docker by default for sig docs generator | Christoph Blecker | |
| 2017-10-13 | add labels in sig list | yuexiao-wang | |
| Signed-off-by: yuexiao-wang <wang.yuexiao@zte.com.cn> | |||
| 2017-09-26 | Merge pull request #1127 from cblecker/generator-what | Kubernetes Submit Queue | |
| Automatic merge from submit-queue. . Update generator to use WHAT variable Having to set two different variables is confusing. Changed this to look at the `WHAT` envvar and match on a suffix. Fixes #1126. cc: @jamiehannaford | |||
| 2017-09-26 | Fixed spelling error | Matt Farina | |
| 2017-09-25 | Update generator to use WHAT variable | Christoph Blecker | |
| 2017-08-17 | Add meeting recording links in generator | shashidharatd | |
| 2017-07-14 | Remove duplication | Jamie Hannaford | |
| 2017-06-26 | Add tests | Jamie Hannaford | |
| 2017-06-22 | Remove timestamp from sig file generation | Christoph Blecker | |
| 2017-06-13 | Make resource management working group discoverable | Vishnu Kannan | |
| Signed-off-by: Vishnu Kannan <vishnuk@google.com> | |||
| 2017-06-12 | Create README for new SIGs | Jamie Hannaford | |
