Update otterdog config per meeting on 6/24/2024

[lucianovaglienti]

Updated the otterdog config per our meeting to discuss optimal settings...

Also included meeting notes so we have a clear trail of what changes we are making here. :)

[eclipse-otterdog]

This is your friendly self-service bot.

Thank you for raising a pull request to update the configuration of your GitHub organization.
You can manually add reviewers to this PR to eventually enable auto-merging.

The following conditions need to fulfilled for auto-merging to be available:

• valid configuration
• approved by a project lead
• does not require any secrets
• does not update settings only accessible via the GitHub Web UI
• does not remove any resource

Otterdog commands and options

You can trigger otterdog actions by commenting on this PR:

• /otterdog team-info checks the team / org membership for the PR author
• /otterdog validate validates the configuration change
• /otterdog validate info validates the configuration change, printing also validation infos
• /otterdog check-sync checks if the base ref is in sync with live settings
• /otterdog merge merges and applies the changes if the PR is eligible for auto-merging (only accessible for the author)
• /otterdog done notifies the self-service bot that a required manual apply operation has been performed (only accessible for members of the admin team)
• /otterdog apply re-apply a previously failed attempt (only accessible for members of the admin team)

[eclipse-otterdog]

This is your friendly self-service bot.

The author (lucianovaglienti) of this PR is associated with this organization in the role of MEMBER.

Additionally, lucianovaglienti is a member of the following teams:

• technology-osee-committers

[lucianovaglienti]

@mastersonmike do you want me to reflect the same changes on org.eclipse.ote?

[netomi]

while having a reference to the discussion is really useful and helpful, I strongly doubt that this repo is the correct place to put things like meeting notes. The project in general does not have write permissions and there is no guarantee that files in the otterdog directory will be kept. I would suggest to discuss changes somewhere else, e.g. in discussions and then reference the outcome in a PR.

[eclipse-otterdog]

Please find below the validation of the requested configuration changes:

Diff for d061920

Project technology.osee[github_id=eclipse-osee]
  there have been 4 validation infos, enable verbose output to display them.

  
!   repository[name="org.eclipse.osee"] {
!     code_scanning_default_setup_enabled = false -> true
!     dependabot_alerts_enabled           = true -> false
!     has_discussions                     = false -> true
!   }

  
!   branch_protection_rule[pattern="main", repository=org.eclipse.osee] {
!     requires_conversation_resolution = false -> true
!   }
  
  Plan: 0 to add, 4 to change, 0 to delete.

[netomi]

/otterdog check-config