Move org.yaml to evolution repo

[maxgio92]

This is the mirror issue of falcosecurity/evolution#176.

Motivation

As the evolution repository is now the central point for the evolution of the project and its ecosystem, and as the falcosecurity organization is formed by the community, and as the point of contact of the contributions are in git (Github), is correct that the source of truth as a declarative configuration of the Github organization is put in the evolution repository.

Feature

• move org.yaml
  from test-infra to evolution. ( Move org.yaml from test-infra to evolution repository evolution#274)
• update Peribolos job repository from test-infra to evolution

Alternatives

Additional context
cc @falcosecurity/evolution-maintainers

[maxgio92]

I propose to adopt in-repo-config, so that the Peribolos ProwJob is configured in the same place the code is in (i.e. the org.yaml Github organization configuration file, in the evolution repository).

Furthermore, this way, we can ensure the job is triggered, both when:

• the org.yaml file changes
• the job config changes.

E.g. the job config could be something like that:

postsubmits:
  falcosecurity/evolution:
    - name: peribolos-post-submit
      branches:
        - ^master$
      decorate: true
      run_if_changed: '^people/org.yaml$|^.prow/peribolos.yaml$'
      ...

/cc @zuc @leogr

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[maxgio92]

/remove-lifecycle stale

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[maxgio92]

/remove-lifecycle stale

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[poiana]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh with /remove-lifecycle rotten.

Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle rotten

[poiana]

Rotten issues close after 30d of inactivity.

Reopen the issue with /reopen.

Mark the issue as fresh with /remove-lifecycle rotten.

Provide feedback via https://github.com/falcosecurity/community.
/close

[poiana]

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue with /reopen.

Mark the issue as fresh with /remove-lifecycle rotten.

Provide feedback via https://github.com/falcosecurity/community.
/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.

[leogr]

/remove-lifecycle rotten

We still want this

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[leogr]

/remove-lifecycle stale