Nested teams are now added on GitHub

GitHub new feature
15 June 2017   1994

Now it is possible to create many levels of nested teams to reflect your company's hierarchy at your GitHub account. It will make your team's structure easier to control.

Continuous integration

Practice of merging all developer working copies to a shared mainline several times a day.

Junior teams inherit their parent's permissions, so repository permissions and mentioning among teams in one nest works from top to bottom. If your team structure, for example, is Teamleads>Project Managers>App. Engineering>QA Testers, granting App. Engineering access for some repository means that QA Testers will receive access too. And if QA Testers team will be mentioned, only they will receive a notifications.

But membership inheritance isn't automatic. If you are a member of App. Engineering team and someone will create a juniour team "Automation", members of App. Engineering aren't automatically the members of Automation. Automation and all other teams created under the App. Engineering will inherit permissions and mentions but nothing else.

Great feature! Now it is possible to create really comfy and clear team structure. It will help big companies to better organize their workflow. At Evrone, we work at few big project simultaneously, and sometimes we got a mishmash instead of good structure. This feature will allow to solve this issue.

 

Dmitry Karpunin
Chief Front-End Developer at Evrone

You can more information in the docs. Start structure your teams now!

Do you find this feature useful?

Nested teams are now added to GitHub. It will allow you to reflect your company’s hierarchy at your GitHub account. Additionally, it will make your team’s structure easier to control. Please, provide us with your opinion about this feature in survey, listed below. Your opinion is very important for us and for the community. Maybe, it will be also interesting for you to see the results of the survey. 

Yes, already using it
75% (3 votes)
Yes, will use it in the future
25% (1 vote)
No, I don't need it
0% (0 votes)
Total votes: 4

Matrix & Riot Hosts Shut Down Due to Hack

Matrix team says that the hacking was done through a vulnerability in an un-upgraded Jenkins continuous integration system
12 April 2019   1033

The developers of the platform for decentralized messaging Matrix have announced an emergency shutdown of the servers Matrix.org and Riot.im (the main client of the Matrix) in connection with the hacking of the project infrastructure. The first shutdown took place last night, after which the servers were restored, and the applications were reassembled from the reference source. But a few minutes ago the servers were compromised a second time.

The attackers placed on the main page of the project detailed information about the server configuration and the data on whether they have a database with hashes of almost five and a half million Matrix users. As evidence, hash password of project leader is in open access. The modified site code is placed in the repository of attackers on GitHub (not in the official matrix repository). Details about the second hack are not yet available.

After the first hacking, the Matrix team published a report stating that the hacking was done through a vulnerability in an un-upgraded Jenkins continuous integration system. After gaining access to the server with Jenkins, the attackers intercepted the SSH keys and were able to access other infrastructure servers. It was stated that the source code and packages were not affected by the attack. The attack also did not affect Modular.im servers. But the attackers gained access to the main DBMS, which also contains unencrypted messages, access tokens and password hashes.

All users were adviced to change passwords. But in the process of changing passwords in the main Riot client, users are faced with the loss of files with backup copies of keys for restore encrypted correspondence and the inability to access message history.