You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This repo is owned by the SunGard-Labs GitHub group, which is associated with FIS (formerly SunGard). Until now, I have been 1 of 2 admins associated with the repo, although the second admin is unknown to me. Additionally, I have not been an employee of SunGard / FIS for a while.
As an admin (and not owner), I have restricted access to maintain the repo itself due to it's ownership by the SunGard-Labs user group. Only the official "owner", in the GitHub sense of the term, is able to associate user groups, approve 3rd party integrations (like Travis, Coveralls, or Slack), and many other common tasks.
As there has been activity in this repo as of late, and the ability to manage the repo is limited, there's a couple options to move forward:
An active employee of FIS can petition the company to add new users to the SunGard-Labs group. At that point I can associate these users as admins and I can remove myself from the SunGard-Labs team. This will still result in limited ability to update the repo due to ownership existing outside of the maintainer's reach.
The repo can be forked under the MIT license it's distributed with and given a much needed update, managed by the active maintainers.
The text was updated successfully, but these errors were encountered:
This repo is owned by the
SunGard-Labs
GitHub group, which is associated with FIS (formerly SunGard). Until now, I have been 1 of 2 admins associated with the repo, although the second admin is unknown to me. Additionally, I have not been an employee of SunGard / FIS for a while.As an admin (and not owner), I have restricted access to maintain the repo itself due to it's ownership by the SunGard-Labs user group. Only the official "owner", in the GitHub sense of the term, is able to associate user groups, approve 3rd party integrations (like Travis, Coveralls, or Slack), and many other common tasks.
As there has been activity in this repo as of late, and the ability to manage the repo is limited, there's a couple options to move forward:
The text was updated successfully, but these errors were encountered: