New Repo: `func` (move from knative-sandbox/kn-plugin-func) about community HOT 15 CLOSED

Just a heads up to the @knative/technical-oversight-committee that we hope to do this move tomorrow, October 6.

from community.

• Send a PR adding entries for this repo in /peribolos/knative-sandbox.yaml. Please mind the alphabetical order when adding to a list.

  • Add the repository and a description.
  • Grant Knative Admin the admin privilege.
    - [ ] Grant the sponsoring WG the write privilege.

Note that for repos moving from knative-sandbox, it is necessary to move these entries from knative-sandbox.yaml to knative.yaml

See: #1170

from community.

I think the missing tasks in the checklist can be done after moving the repo. @evankanderson @psschwei @csantanapr It will be great to get the steering committee's blessing so @lance can move the repository, and we can complete the tasks.

from community.

@salaboy this is a technical topic that is under TOC purview

TOC is already aware of this work, and @lance has the access to move the repo on the admin panel.

from community.

can we close this issue now? and track new problems if they arise in a separate issue?

from community.

+1 for me. I can take on whatever work is needed from the TOC side to do the move, etc.

from community.

👍

I can help with this tomorrow if we agree on it. I think the current progress on func matches the guidelines in [Migration to Core] (https://github.com/knative/community/blob/main/mechanics/MATURITY-LEVELS.md#migration-to-core).

In particular, the abstractions are user-facing, developer-friendly, and the underlying language addition process is pluggable outside the core.

from community.

A stable project may apply to the SC and TOC to be admitted to the Knative core ...

Reading the migration guidelines, does Steering also need to approve? cc @lance

from community.

Reading the migration guidelines, does Steering also need to approve?

As discussed on Steering call today, migration to core was already approve, this is just moving the repo, so disregard the above

from community.

👍

from community.

• (golang) Send a PR to add aliases for knative.dev/$REPONAME import paths (sample).

knative/docs#5257

from community.

• Set up prow for a new repo

This will need to be a modification to the existing prow configuration for knative-sandbox/kn-plugin-func

knative/test-infra#3554

from community.

I've created this PR for knobots. I am trying to figure out what other configuration changes do we need in there: knative-extensions/knobots#240

from community.

Ask to steering to add to EasyCLA in Slack done: https://knative.slack.com/archives/CU9DGL4FM/p1664956526130389

from community.

+1 from me as well, I was off last week

from community.