Feedback - Community tool

[Sealjay]

Hi folks, @FergusKidd , if you get a chance, could you add this to the backlog please?

GitHub Management

• When a repository is requested, both the user requesting the repository, and the user added as co-owner should be invited to the repository

  

• We need to check that all repositories in github.com/avanade and github.com/ava-innersource are indexed - is it worth having an endpoint we can ping weekly with a logic app to check this?

• We need to make sure that users are only invited if they are organization members, and that they are not added as external collaborators

• Outside collaborators must be removed; only users that have accepted an invite to the organization should be part of the GitHub

• When a user signs into their GitHub account, the community tool should check they have been invited to both the github.com/avanade and github.com/ava-innersource organisations

• When a user has left Avanade, we need to remove them from github.com/avanade and github.com/ava-innersource

  • @FergusKidd we'll need to ask Richard Nielsen for guidance on this

Activities

• Contribution areas should be configurable
• When a user asks for help, an email should be copied to the OSPO email address

Notifications

• We should use the Avanade Notify functionality when a repository is requested, or requested to move public - link for new notifications
  • Notification to the owner, and co-owner of the new repository URL - asking them to install the GitHub app if they haven't already - https://avanade.sharepoint.com/sites/OpenSource/SitePages/GitHub-for-Microsoft-Teams-has-launched-at-Avanade.aspx
  • Notification to tell a user they need to accept the github invitation to both github.com/avanade and github.com/ava-innersource
  • Notification when an invitation to github expires
  • Notification when approval is sent to legal
  • Notification when everyone has provided approval
  • Notification every 7 days for repositories awaiting approval, to approver
  • Notification when someone asks for help on the activities page, including an email to ospo team
  • When employees have left the business, and a repository is left without two owners (1 owner + 1 or more co-owners) then a notification needs to be sent to the remaining owners to nominate a new owner, and an email to the ospo@avanade.com team

Repositories

• The owners of the repository and added users should be shown in search listing

Domain names

• The site needs to support multiple domain names - so if someone were to open https://innersource.avanade.com or any other incorrect URL they would be redirected to https://community.avanade.com

Reporting

• Reporting
  • We need a report of activities, broken down by employee, community, and activity type
  • We need a report of all activities where someone has asked for help
  • We need a powerbi report of current employees, current repositories, and then how we measure engagement
    • Could this be active commits? Active pull requests?
    • Could we measure our employee engagement in other repositories? We have their github ID, so we could query the repositories they are working on outside Avanade with the GitHub API.
  • @AoifePower1234 might be able to help design the repository, but not make it - @ferguskidd is there anyone benched in analytics that could help? they might also be able to do the design

Approvals

• Approval tool - approver should be able to re-assign approval to another person
• Would be good to be able to delete an approval type when unused, or archive it

Tool UI

• External links should be configurable

Bugs in community tool

• Errors in community tool
  • When I update an approver email, it doesn't reflect in the tool
  • Approvers are set for the community tool, but the button is disabled
  • When How to Join instructions are blank, or unset, the button should be hidden - currently it errors out

Bugs in approval tool

• Errors in approval tool
  • Some requests show invalid date

Directory integration

• It would be good to have the option of 'internal', 'external', and 'teams' community - and then provide a teams ID as the community site URL, and programatically check if a user is part of the community, checking O365.

[Sealjay]

One additional item - we have a bug on live @iibuan Constantly redirecting to logout

[Sealjay]

@iibuan is there a ticket for this one?

[iibuan]

Hi @Sealjay, yes. That's the issue 465. We created a endpoint that can be triggered by a logic app.

[iibuan]

Hi @Sealjay, we have these 2 items on notifications. I'm thinking if the first one is already covered on the 2nd item? We'll send a notification to the approvers upon user request to make a repo public, and then every 7 days until the request has been responded. Is that right? Notification when approval is sent to legal Notification every 7 days for repositories awaiting approval, to approver

[Sealjay]

Yes, that sounds right to me, thanks @iibuan

[iibuan]

Hi @Sealjay, can you give more details on this? Thanks! The owners of the repository and added users should be shown in search listing

[Sealjay]

@iibuan when I look at projects on the search listing on community.avanade.com, I can’t see the users that own the project, or the users that have been added. Owners (Admins) should be able to invite other collaborators via the interface. The co-owners should display, so that we know who in the company (name, avanade email, and GitHub ID) is responsible for a project, or if a project is missing a co-owner. Admins should be able to update the co-owners, and the users. Co-owners should be able to update other co-owners, and the users.

So it’s:

• Display owners in the search and repository listing UI
• Display non-owners but users added by GitHub ID to the project (GitHub as source of truth)
• Ability for co-owners to be updated by co-owners and admins
• Ability for users with repo edit permissions to be updated by co-owners and admins

[iibuan]

Hi @Sealjay, can you give more details on this? Thanks! It would be good to have the option of 'internal', 'external', and 'teams' community - and then provide a teams ID as the community site URL, and programatically check if a user is part of the community, checking O365.

[Sealjay]

Like this @iibuan

[iibuan]

So if it is a teams community, we'll pull the list of members from O365, then all community portal users who are members of the teams channel will automatically marked as members of that community on the database. Did I understand this correctly? @Sealjay

[Sealjay]

Yes please @iibuan I also get an Excel export of all GSF members, which is the second box (and then need a way to insert employee emails)