Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

August 31 2020 Community Meeting #360

Closed
adambkaplan opened this issue Aug 25, 2020 · 9 comments
Closed

August 31 2020 Community Meeting #360

adambkaplan opened this issue Aug 25, 2020 · 9 comments

Comments

@adambkaplan
Copy link
Member

  • Please add a topic in this thread and add a link to the Github issue associated with the topic.\
  • Please make sure you give folks enough time to review/discuss the topic offline on Github before coming into the meeting :)
  • (optional) Paste the image of an animal :)
@zhangtbj
Copy link
Contributor

  • Performance tuning summary

@adambkaplan
Copy link
Member Author

  • Governance roles
    • Infrastructure ownership (Github, quay, etc.)
    • Code of Conduct reporting

@qu1queee
Copy link
Contributor

s

@SaschaSchwarze0
Copy link
Member

SaschaSchwarze0 commented Aug 31, 2020

ox_640

@adambkaplan
Copy link
Member Author

Update on copyright: #336

@zhangtbj
Copy link
Contributor

The first release note: #357 (comment)

@qu1queee
Copy link
Contributor

qu1queee commented Aug 31, 2020

Action Items:

  • Based on the performance we ran from our side, we should document most of the key findings in github. This should include:

    • bottlenecks we find and how to address them
    • dependencies to tekton etc, and issues we open to them
  • Probably have more sessions on how we run performance tests and what could we donate/share to the open-source.

  • We might like to run performance tests in shipwright at some point, this will imply to have robust infrastructure. @qu1queee might have a future proposal for this.

  • Presenting Build and the Build performance findings in the Tekton community sessions.

  • @adambkaplan to provide a PR for the copyright text we need to have in the source code.

  • we discuss on the importance on deciding governance roles and layout the code of conduct.

  • we discuss on getting more feedback in Organize samples #366 and Build controller handling of service account can lead to failing build runs and other artifacts #337

  • we discuss on prometheus metrics and if we are fine to remove some namespace labels in the current metrics, see Reduce prometheus metric count #367

@adambkaplan
Copy link
Member Author

/close

@openshift-ci-robot
Copy link

@adambkaplan: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants