Hi All PTL's :) As you are aware of, here at LF we are striving to improve our support work, which of course means that we are improving our various tools continously. The latest versions of our tools, starts to require that each repository has it's own INFO.yaml file, and that it contains up to date and valid data.
This would enable the community, a bit further down the track, to have self serve committer additions and removals for instance. So, we would like the PTL to add an INFO.yaml file to the top of each repository. This file, and more importantly, and its contents are rather crucial for LF's various tools to function as they should. There is a wiki page [1] with more information regarding the INFO.yaml file, as well as a sample INFO.yaml file [2] for your reference The key areas to consider (apart from the obvious other parts) with the INFO.yaml file is 1) The list of Committer people has to be correct and current. 2) Added or Removed committers has to be specified, and a link to TSC approved information about this provided. Observe, this link should go to a official MoM, or Email stating approval of this persons addition or removal. 3) Provide the proper and approved TIMEZONE format, use https://time.is/ to lookup timezone. 4) There should only be one repository listed under Repository, since there is one (1) INFO.yaml file per repository. In addition to the above key points for the actual INFO.yaml file, you should also take advantage of the automatic global-jjb info.yaml file checker [3]. If you need assistance with what the current list of committers looks like, please raise a ticket (support.linuxfoundation.org), and specify which repo you would like to have the list of committers for. /Bengt INFO file Overview ================== The INFO.yaml file is a normal yaml file, which can be roughly divided into 3 main parts. Top part -------- This is the overview of the project, for instance * project name * Creation date * State * Project Lead Middle part ----------- The middle part is all about contact information, for instance * Primary Contact person * Issue Tracking * Mailing list * Meetings Last part --------- And the last part is all about the repository, for instance * Repository (Only one (1) repository, since each repository should have its own INFO file) * Committers (Actual current list of committers) * TSC Approval link for every Added or Removed Committer. References [1] Wiki page with more generic information https://wiki.onap.org/display/DW/INFO.yaml+Guidelines [2] Sample INFO.yaml file https://github.com/onap/sdc-sdc-pubsub/blob/master/INFO.yaml [3] Adding the ci-management job entry to verify INFO.yaml files: https://github.com/onap/ci-management/blob/master/jjb/sdc/sdc-sdc-pubsub.yaml#L3 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#18525): https://lists.onap.org/g/onap-discuss/message/18525 Mute This Topic: https://lists.onap.org/mt/32848540/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
