[jira] [Commented] (COMDEV-382) Prepare a proposal for Policy for Helm Charts and Container images ASF policies
[ https://issues.apache.org/jira/browse/COMDEV-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17468975#comment-17468975 ] Nick Nezis commented on COMDEV-382: --- What ever happened to this? No movement? I'm also very interested in the distinction of compiled vs packaged artifacts. For Apache Heron we release a Java framework and it would be nice to release convenience Docker images with OpenJDK. Currently we are told that we can't install JDK in the Dockerfile, but it has to be already included in the parent image referenced in the FROM line. This seems like an odd distinction to make. Could someone shed some light on this proposal's status and how other teams are handling the issue I mention above? > Prepare a proposal for Policy for Helm Charts and Container images ASF > policies > --- > > Key: COMDEV-382 > URL: https://issues.apache.org/jira/browse/COMDEV-382 > Project: Community Development > Issue Type: Proposal > Components: Comdev >Reporter: Jarek Potiuk >Priority: Major > > There is a discussion started in the comdev mailing list about release > policies related to release "Convenience Packages" relevant for the modern > way of releasing "cloud" projects - Container Images and Helm Charts. Seems > that the current policies are not fully answering the questions of projects > trying to release those, and there is likely a need to provide an ASF > "approved" way how to make the images and Helm Charts available to users. > [https://lists.apache.org/thread.html/rcb608739206d788785081073a0deb417ffa9981634975fc5525dc769%40%3Cdev.community.apache.org%3E] > > > The issue is created to keep track on the progress of the proposal that > should become an official policy for the ASF projects on how to approach this. > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [apache/comdev-site] [Improved] Added ASF logo as the comdev site logo (#69)
It’s just three approvals of PRs and not really a contribution. Call them random non-binding +1. Sent from my iPhone > On Jan 4, 2022, at 7:57 AM, Rodent of Unusual Size wrote: > > Consider as well the current spotlight on FOSS provenance tracking since > log4j. Allowing anonymous contributions/approvals into anything > 'customer-facing' seems contraindicated. > > -- > Ken Coar (📱) > Software developer, author, opinionist > Sanagendamgagwedweinini - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[GitHub] [comdev-fosdem-content] Shahen20 commented on pull request #5: Minor commit to keep website active for FOSDEM 2022
Shahen20 commented on pull request #5: URL: https://github.com/apache/comdev-fosdem-content/pull/5#issuecomment-1004976857 I use this site support my android mobile phone -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [apache/comdev-site] [Improved] Added ASF logo as the comdev site logo (#69)
Consider as well the current spotlight on FOSS provenance tracking since log4j. Allowing anonymous contributions/approvals into anything 'customer-facing' seems contraindicated. -- Ken Coar (📱) Software developer, author, opinionist Sanagendamgagwedweinini
Re: [apache/comdev-site] [Improved] Added ASF logo as the comdev site logo (#69)
On 1/3/22 04:47, Pierre Smits wrote: There is little wrong with the contribution. Shane has described what is wrong with the contribution. Yes, one may question whether where it originated (the PR) is the wrong place. Or whether it should have been raised without the required aspect being in play (the desired mailing list). But classifying it as 'unwanted' at this stage is premature. Nor does it seem appropriate to question the validity of a contribution because the contributor (garcYj-fybgeg-8nebqu) is not list of 'approved' contributors. This contributor can give his +1 via a process the community implemented. Not everybody wants to be known as the privileged would like it to be. Which makes it impossible to get in touch with them for clarification, or to give them credit for their contribution (which is, I believe, something that you have strong opinions about). - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
