24i GitHub Organisation Changes & Updates #1
ghost
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
📣 📣 Announcement: : 24i GitHub Organisation Up & Coming Changes 📣 📣
As part of our ongoing efforts to increase security and better align our 24i GitHub Organisation, the 24i @devops team will be introducing a number of important changes, updates and best practises rolling out from the
1st October
. This announcement is to make you aware of these changes in preparation to take action and open up dialog with us should you need to better understand whats happening.User Changes:
Two Factor Authentification - Should be enabled for all 24i GH users. We recommend activating this as soon as possible, check here to see if you already have it enabled. If not follow the instructions here to enable it, LastPass Authenticator seems the logical solution. Download -> Apple | Android
Enablement: 1st October
Ownership Privileges - Anyone who previously had ownership privileges and who is not a member of the @devops team will be downgraded to a member. A mail has already been sent to those people making them aware of this.
Enablement: 1st October
Revising Team / Role Structure - We are currently rethinking about how best we can reorganise the team/role structure within 24i GH Org.
Enablement: Oct / Nov
Inactive Users - There are a number of inactive users who are presently not using using our 24i GH Org for whatever reason, we will be contacting those people individually and revising their access.
Enablement: 1st October
Update User Details - For security and auditing purposes there are many missing names and corresponding 24i email addresses that allow us to identify you. We would like for you to update your GH user settings, adding your full name and 24i email address as a secondary mail if you are using a personal GH account.
Enablement: Oct/Nov
Organisation Changes:
24i GH Org Base Permission - Presently default permission is set to
Write
for all repositories, we intend to change this toRead
which is standard practise in most GH Organisations.Enablement: 1st October
Revise All Repos - Analysis of our 24i GH Organisation shows us that we have around 1755 repos, ideally if any of those are no longer in use and can be archived this is the perfect opportunity. We will be digging deeper on this topic and touching base with all teams to see how we can achieve this over the coming weeks. If you have any insight into this we would like to hear from you please contact us in our #cloudops channel @devops
Enablement: Oct/Nov
Security Concerns over Public Repos - We currently have 230 public repos in our 24i GH Org which are obviously cause for concern, we would like to revise these to have a better understanding of their nature and whether they can be removed/archived. If you have any information pertaining to these then you can leave a comment in the Confluence page or contact at #cloudops channel @devops
Enablement: Oct/Nov
We hope you like this new format of communication with you, it has many possibilities to enhance our GH organisational space. Please let us know your ideas and how best we can move forward to improve this community for everyone.
🚀 24i DevOps Team
Beta Was this translation helpful? Give feedback.
All reactions