Revise Github Projects managed by Che teams

mkuznyetsov commented 1 year ago

Is your task related to a problem? Please describe

Some of our projects, especially on Che Incubator side, have inconsistent and/or outdated configurations, like permissions to push branches or merge PRs. Ideally, all projects should have the same configuration, when it comes to those things. Codeowners, who would approve these PRs. Updating all these things would help in future, when someone would have to push to those projects

Describe the solution you'd like

[x] ensure that list https://github.com/eclipse/che/blob/main/.repositories.yaml is up to date.
[x] all eclipse-che/che-incubator repos must have the same configuration:
- main branch protected from direct pushes,
- all che org members must have permissions to push branches to the upstream repo,
- all che org members should be able to merge PRs with at least 1 approved review,
- merge commits not allowed, to keep the git history linear.
[x] every eclipse-che/che-incubator repo should have updated CODEOWNERS file(exact list with repos/owners is TBD).

Describe alternatives you've considered

No response

Additional context

No response

mkuznyetsov commented 1 year ago

as part of this issue, most of che-samples projects should be archived, except those that are currently maintained:

che-samples/apache-camel-k
che-samples/bash
che-samples/cpp-hello-world
che-samples/django-realworld-example-app
che-samples/dotnet-web-simple
che-samples/fuse-rest-http-booster
che-samples/golang-example
che-samples/helloworld-rust
che-samples/java-guestbook
che-samples/java-spring-petclinic
che-samples/lombok-project-sample
che-samples/nodejs-angular
che-samples/nodejs-mongodb-sample
che-samples/nodejs-react-redux
che-samples/php-symfony
che-samples/python-hello-world
che-samples/quarkus-quickstarts
che-samples/react-web-app
che-samples/scala-sbt
che-samples/web-nodejs-sample

mkuznyetsov commented 1 year ago

@l0rd do we want to have CODEOWNERS files in che-samples? if sample is cloned "as-is" to users workspace, will it make sense for him to have .github/CODEOWNERS file in his project, or is this not important?

svor commented 1 year ago

as part of this issue, most of che-samples projects should be archived, except those that are currently maintained:

sounds good to me cc @l0rd

mkuznyetsov commented 1 year ago

updating repositories yaml - https://github.com/eclipse/che/pull/22248 @l0rd this list shoudln't feature product-related prjects like devspaces, correct?

mkuznyetsov commented 1 year ago

all che-incubator repos have now following settings: -added che-incubator team members with write permissions -add protected rule for main branch, with require of at least 1 codereviewer (where codereviewer PR has been merged) -only linear history is allowed on main branch

@l0rd should main branch also require only signed commits? Seems like some of the projects were already doing that, while some won't

l0rd commented 1 year ago

@l0rd should main branch also require only signed commits? Seems like some of the projects were already doing that, while some won't

This would be useful yes.

l0rd commented 1 year ago

@l0rd this list shoudln't feature product-related prjects like devspaces, correct?

Ok with that

l0rd commented 1 year ago

as part of this issue, most of che-samples projects should be archived, except those that are currently maintained

Yes, absolutely.

l0rd commented 1 year ago

@l0rd do we want to have CODEOWNERS files in che-samples? if sample is cloned "as-is" to users workspace, will it make sense for him to have .github/CODEOWNERS file in his project, or is this not important?

We should have CODEOWNERS files. We can avoid including them in the zip file of the devfile registry using a .gitattributes file with export-ignore.

eclipse-che / che