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

Move org.yaml from test-infra to evolution repository #274

Closed
wants to merge 77 commits into from

Conversation

maxgio92
Copy link
Member

What type of PR is this?

/kind feature

Any specific area of the project related to this PR?

/area utils

What this PR does / why we need it:

As the evolution repository is now the central point for the evolution of the project, 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 here.

Moreover, this PR adds the Prow job needed for the automation that reconciles the desired source of truth with the actual one.

Which issue(s) this PR fixes:

Fixes #176

Supersedes #204

/cc @leogr

@poiana
Copy link
Contributor

poiana commented May 26, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: maxgio92

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@maxgio92
Copy link
Member Author

I think we finally have a clean history @leogr.

There was history related to the source repository test-infra to a directory wrongly named "distrubution" under config.

@maxgio92
Copy link
Member Author

@leogr I think we're ready to unhold this and consequently update related pipelines. WDYT?

zuc and others added 20 commits June 20, 2023 18:05
Signed-off-by: Michele Zuccala <michele@zuccala.com>
He deserves it :)

Signed-off-by: Mark Stemm <mark.stemm@gmail.com>
Signed-off-by: Leonardo Grasso <me@leonardograsso.com>
Co-authored-by: Federico Di Pierro <nierro92@gmail.com>
Signed-off-by: Leonardo Grasso <me@leonardograsso.com>
Signed-off-by: Leonardo Grasso <me@leonardograsso.com>
Signed-off-by: Leonardo Grasso <me@leonardograsso.com>
Signed-off-by: Massimiliano Giovagnoli <me@maxgio.it>
Signed-off-by: Leonardo Grasso <me@leonardograsso.com>
This is an emergency commit. The peribolos job is failing because the missing user "danpopnyc" (he has left the org :( )

Signed-off-by: Leonardo Grasso <me@leonardograsso.com>
Signed-off-by: Issif <issif+github@gadz.org>
Signed-off-by: Leonardo Grasso <me@leonardograsso.com>
Signed-off-by: Leonardo Grasso <me@leonardograsso.com>
Signed-off-by: Leonardo Grasso <me@leonardograsso.com>
Signed-off-by: Leonardo Grasso <me@leonardograsso.com>
…ners lists.

Signed-off-by: Federico Di Pierro <nierro92@gmail.com>
Signed-off-by: Leonardo Grasso <me@leonardograsso.com>
So we can add him as a reviewer. See falcosecurity/falco#2137

Signed-off-by: Leonardo Grasso <me@leonardograsso.com>
The maintainer expressed willingness to be removed from all repositories and the organization. See falcosecurity/falco#2122

Signed-off-by: Leonardo Grasso <me@leonardograsso.com>
EXONER4TED and others added 5 commits June 20, 2023 18:05
Signed-off-by: Logan Bond <lbond@secureworks.com>
Signed-off-by: Melissa Kilby <melissa.kilby.oss@gmail.com>
Signed-off-by: Massimiliano Giovagnoli <me@maxgio.it>
Co-authored-by: Leonardo Grasso <me@leonardograsso.com>
Signed-off-by: maxgio92 <me@maxgio.it>
Co-authored-by: Federico Di Pierro <nierro92@gmail.com>
Signed-off-by: maxgio92 <me@maxgio.it>
@maxgio92
Copy link
Member Author

The org.yaml and related history has been updated.

… team

Signed-off-by: Jason Dellaluce <jasondellaluce@gmail.com>
@maxgio92
Copy link
Member Author

maxgio92 commented Jul 22, 2023

@falcosecurity/evolution-maintainers this is up to date and ready to be reviewed.

@poiana
Copy link
Contributor

poiana commented Oct 20, 2023

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
Copy link
Member Author

/remove-lifecycle stale

@maxgio92
Copy link
Member Author

maxgio92 commented Dec 1, 2023

@falcosecurity/evolution-maintainers is there something I can do here?

@leogr
Copy link
Member

leogr commented Dec 1, 2023

@falcosecurity/evolution-maintainers is there something I can do here?

Hey @maxgio92

I lost track of this sorry. Is anything else needed to make this work ready yet?
If yes, we should just schedule when. I would not say this is super urgent, but this issue has been open for too long, so I would address it.

@FedeDP @LucaGuerra could you help with this?

@poiana
Copy link
Contributor

poiana commented Feb 29, 2024

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
Copy link
Member

leogr commented Mar 1, 2024

/remove-lifecycle stale
/assign

@poiana
Copy link
Contributor

poiana commented May 30, 2024

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
Copy link
Contributor

poiana commented Jun 29, 2024

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
Copy link
Contributor

poiana commented Jul 29, 2024

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 closed this Jul 29, 2024
@poiana
Copy link
Contributor

poiana commented Jul 29, 2024

@poiana: Closed this PR.

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-sigs/prow repository.

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

Successfully merging this pull request may close these issues.

Move org.yaml here