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.

Sign up for GitHub

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

Jump to bottom

Move org.yaml here #176

Open
leogr opened this issue Aug 30, 2022 · 18 comments · May be fixed by #274
Open

Move org.yaml here #176

leogr opened this issue Aug 30, 2022 · 18 comments · May be fixed by #274
Assignees
@leogr
Labels
kind/feature New feature or request

Comments

@leogr
Copy link
Member

leogr commented Aug 30, 2022

Motivation

It would simplify the CI and all organization-related processes which are currently initiated from this repository.

Feature

  • move org.yaml
    from test-infra to evolution.
  • configure prow accordingly

Alternatives

Additional context
cc @falcosecurity/test-infra-maintainers
@leogr leogr added the kind/feature New feature or request label Aug 30, 2022
This was referenced Sep 6, 2022
Open
Closed
Closed
@zuc zuc mentioned this issue Sep 8, 2022
Open
@Issif
Copy link
Member

Issif commented Sep 8, 2022

This is maybe a silly question, why are we moving configs in evolution and not in a dedicated repo with all configs useful across repos?

@zuc
Copy link
Member

zuc commented Sep 8, 2022

Because

  1. evolution already contains some assets that we want to leverage from an automation perspective (eg. maintainers list)
  2. org management is tightly connected with how the project evolves, so we think evolution is the right place
  3. peribolos works with a centralized config, so it wouldn't be useful across repos

@maxgio92 maxgio92 mentioned this issue Sep 22, 2022
Closed
@poiana
Copy link
Contributor

poiana commented Dec 7, 2022

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

maxgio92 commented Dec 7, 2022

/remove-lifecycle stale

@poiana
Copy link
Contributor

poiana commented Mar 7, 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

@jasondellaluce
Copy link
Contributor

/remove-lifecycle stale

@maxgio92 maxgio92 linked a pull request May 26, 2023 that will close this issue
Open
@poiana
Copy link
Contributor

poiana commented Jun 6, 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

maxgio92 commented Jun 7, 2023

/remove-lifecycle stale

@poiana
Copy link
Contributor

poiana commented Sep 5, 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

@leogr
Copy link
Member Author

leogr commented Sep 11, 2023

We still want this. I guess the best time window for this is immediately after the release.

@maxgio92 do you agree?

/remove-lifecycle stale

@maxgio92
Copy link
Member

Of course @leogr! :)

@leogr
Copy link
Member Author

leogr commented Sep 21, 2023

Of course @leogr! :)

The release is coming next week. I'll likely be a bit busy the first week of October, but should be available the week after.
Are you available?
@FedeDP can you help us with this?

@FedeDP
Copy link
Contributor

FedeDP commented Sep 21, 2023

You have my sword!

@poiana
Copy link
Contributor

poiana commented Dec 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

@leogr
Copy link
Member Author

leogr commented Dec 20, 2023

/remove-lifecycle stale

@leogr
Copy link
Member Author

leogr commented Dec 20, 2023

/assign

@poiana
Copy link
Contributor

poiana commented Mar 19, 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

@FedeDP
Copy link
Contributor

FedeDP commented Mar 20, 2024

/remove-lifecycle stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@leogr leogr

Labels
kind/feature New feature or request
Projects
None yet
Milestone
No milestone
7 participants
@leogr @Issif @FedeDP @maxgio92 @zuc @jasondellaluce @poiana