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

May 24th, 2021 Community Meeting #759

Closed
qu1queee opened this issue May 4, 2021 · 5 comments
Closed

May 24th, 2021 Community Meeting #759

qu1queee opened this issue May 4, 2021 · 5 comments

Comments

@qu1queee
Copy link
Contributor

qu1queee commented May 4, 2021

  • 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 😸
@imjasonh
Copy link
Contributor

imjasonh commented May 10, 2021

@adambkaplan adambkaplan changed the title May 10th, 2021 Community Meeting May 17th, 2021 Community Meeting May 10, 2021
@adambkaplan
Copy link
Member

No agenda items that needed immediate discussion on the 10th, keeping this issue for the next meeting (May 17th)

@qu1queee
Copy link
Contributor Author

qu1queee commented May 11, 2021

  • State of the Runtime feature?
  • Shipwright/Build CI setup, how to avoid blockers?

@qu1queee qu1queee changed the title May 17th, 2021 Community Meeting May 24th, 2021 Community Meeting May 21, 2021
@adambkaplan
Copy link
Member

@adambkaplan
Copy link
Member

Minutes:

  1. SHIP enhancement proposals - community will be the new home. Existing proposals will remain in shipwright-io/build until their respective PRs are merged or closed. @adambkaplan will create a "first" SHIP that links back to the proposals in shipwright-io/build
  2. Runtimes feature - there is consensus that it should be deprecated and removed. "Runtime image" is a specific need for the source-to-image tool, and is not needed for Dockerfile-based build strategies or build packs. Deprecation should be discussed via an enhancement proposal.
  3. CI - @adambkaplan will update permissions so reviewers (as defined in the OWNERS file) have the ability to restart GitHub actions. Unfortunately prow does not have a command that lets us re-run a GitHub action.

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

3 participants