Enforcing 2FA for all members of the organisation

[TiagoLucas22478]

We're taking steps to further enhance the security of your projects and repositories, as part of our ongoing commitment to cybersecurity.

Following our previous communication on January 14th, shared through the eclipse.org-committers mailing list, and detailed in the associated support ticket, we are now enabling the requirement for two-factor authentication (2FA) across the entire GitHub organisation of your project.

We are pleased to report that your organisation was already in full compliance with this new requirement; all members already have 2FA enabled. Consequently, this policy enforcement will not necessitate any immediate changes on your part. However, it is important to mention that moving forward, all new committers or contributors, will be required to activate 2FA prior to their invitation to join the GitHub organisation.

Should you have any questions or face any challenges with this change, please do not hesitate to open a ticket on the HelpDesk, comment on the ticket tracking this initiative, or just add your comment to this pull request.

Thanks!

/cc @CamilleLetavernier @martin-fleck-at @ndoschek @planger @tortmayr

[github-actions]

Diff for bdb1c53:

Printing local diff:

Actions are indicated with the following symbols:
+   create
!   modify
!   forced update
-   delete

Organization ecd.glsp[id=eclipse-glsp]
  there have been 3 validation infos, enable verbose output with '-v' to to display them.

  
!   settings {
!     two_factor_requirement            = false -> true
!   }
  
  Note: setting 'two_factor_requirement' is read-only, will be skipped.
  
  Plan: 0 to add, 0 to change, 0 to delete.

Canonical Diff for bdb1c53:

Showing canonical diff:

Organization ecd.glsp[id=eclipse-glsp]