ParSys Sprint - IAM/CoSS Sprint 14 Review

[r_Up2mI1KfXvmSMPkEfhC6eg]

Dear Stakeholders,

here we go with our regular update.

Highlights

• CoSS has a shorter staging URL and there is lots of great draft content on it. For example, see the About Page on Open Source Clubs.
• The CoSS Content Utility now supports multi-site hosting as demonstrated by this prototype site.
  Important: This entire thing (content & domain) is a work in progress. We value transparency and want you to be able to follow our progress.
• User-specific security alerts are coming to the SSO Dashboard.
• We continue to work hard on getting the IAM Q2 OKR into production (i.e. managing Discourse category visibility based on Mozillians.org groups by leveraging the IAM’s stack).

Community contributed Pull Requests

• Looks like no volunteer contributed PR made it to production this sprint.

Release Notes

Mozilla Discourse release 2017-08-22

Most development effort has been focused on IAM and CoSS work which hasn’t made its way to production yet, so not much change since last week: Smaller changes: In Jenkins, automatically pull in our build config from a git repo Got our score back up to B from C- on the Observatory Full upstream changes.

Mozilla Discourse release 2017-08-29

Since last week: Highlight: Further theme iteration: Increased the font size in key areas, including the post body Rearranged the site header to give greater prominence to a topic’s category (see it in action by scrolling down on a long post) Feedback, as always, welcomed below! If things are looking a little off, try a refresh first Smaller changes: Fixed authentication issue with /new-topic Originally non-authenticated users would be redirected to authenticate, and not redirected back …

IAM/CoSS Sprint Review

Video:
https://air.mozilla.org/iam-coss-sprint-14-review/
Slides:

IAM/CoSS Sprint 14 Demo

OKR Confidence Levels

This is our Q3 OKR confidence scoring. It is prefixed in brackets, the scale is 1 to 10.

O1: Share a G Suite document for collaboration with a group as defined by Mozillians.org (e.g. the staff & volunteer body Mozilla Reps Council)

• (1) KR1: Staff profiles are automatically available to Mozillians.org
• (1) KR2: G Suite has visibility of Mozillians.org groups
• (4) KR3: A user login in from a new location triggers an alert in the SSO Dashboard (security enhancement)

O2: CoSS has Utilities that enable content manipulation by admins, users to contact the program, and program-specific discussion groups

• (2) KR1: CMS that has a well designed UX, is secure, and easy to add/edit content without any coding.
• (3) KR2: Roles and permissions are determined from integration with Mozilla’s group management allowing for seamless staff/volunteer management.
• (3) KR3: Discourse’s ability to scale for program-specific discussion groups is proven

O3: Link the contribution of ParSys’ activities and vision to the OI strategic plan

• (1) KR1: The ParSys infrastructure roadmap is aligned with the Open Innovation Strategy
• (2) KR2: All community WordPress sites are decommissioned from ParSys AWS
• (2) KR3: Bitergia’s data, tool and knowledge assets from the Q2 Strategy Project are integrated in our Community Analytics platform