COmanage News and Announcements

[Laura Paglione <>]

View in a browser

NEWSLETTER

ISSUE #5 | February 28, 2022

Reset

Well, we may not be resetting the whole world as this image from Lisbon suggests, but occasionally it is helpful to take a step back and re-orient yourself with the basics. This month we are thinking about the fundamentals in the form of learning how to use Registry and how COmanage versions are handled.

Open Office Hours - Mar 4

Do you have a question on deploying or configuring Registry or Match? Want to get some input on a solution architecture design? Want to hear how your colleagues in the community are solving problems similar to yours? Each month you can bring your topics for discussion to the call. No need to register or spin up a presentation (but feel free if it suits you!), just show up! Each session is kicked off by a short conversation starter to help get the discussion started.

Friday, March 4 at 12:00 PM (America/New York) (no registration necessary)
https://illinois.zoom.us/j/84190579924?pwd=a1R6Q3VjWi92SHRETlVDMEthZVJYZz09

IN YOUR TIMEZONE & link for your calendar

February’s Topic Aperitif: COmanage Training Perspectives

In 2019, we created the first COmanage Registry training program. Since then, we have taught the class 5 times, enhancing it each time. For this month’s “‘topic aperitif” we will share perspectives about COmanage training, and give a peek into what is taught and how. Already taken it? Share what you thought, and give us feedback on what was missing. Taking the workshop this March? Share what you hope to get out of it. We will follow this 15 min chat with topics of your choosing. Bring your questions, comments, and suggestions about any topic to office hours with the COmanage project team.

The Versions of COmanage

COmanage manages changes to its open-source code in a Github Repository and uses a git-flow style branch management strategy to fuel new releases.*  The current release or release candidate is always on the “main” branch. This release is always documented on the Release History page.

The software team develops features on their own branches named after the feature. Once these features are ready to be shared, they are added to the “develop” branch where they remain until they are ready to be included in the next release. Occasionally there are bugs that need to be addressed in between releases. These are stored on the “hotfix” branch until they are added to a release.

Organizations that are using COmanage have the flexibility to incorporate fixes or features before they are part of the official release. This advanced feature is only recommended for teams that would be able to manage potential conflicts that could happen with this approach. As always, feel free to reach out with questions! 

* Not a software developer? New to Github? May we suggest this Git and Github for Poets tutorial series from The Coding Train for a very accessible orientation of the tool.

COmanage News

This newsletter section is designed to provide additional transparency on the day-to-day workings of COmanage. We’re starting small with a high-level update from the development team. We are looking forward to hearing your ideas on what other information we can include.

COmanage Training week

The next class will be the week of March 7! - there’s still time to sign up.

Registry 4.0.2 release

COmanage Registry v4.0.2 was released on Thursday, Feb 24. We recommend all deployments upgrade to this release. A Security Advisory is being posted along with this release. While this Advisory is not expected to apply to most deployments, all deployments should review the Advisory to determine if any action is warranted. Further details are posted to the COmanage Registry Security Advisories page.

You can find more details about this release on the COmanage wiki.

Match 1.0.0

We held back this release to address a few things found in our last round of detailed testing. We will announce when it is read through a notification to the comanage-announce mailing list.

MOMENT OF ZEN
What difference does a capital letter make?

Turns out, a lot - at least if you're talking about COmanage. We were curious about what all of those other comanages were about....

• comanage (Merriam-Webster) - transitive verb, to manage (someone or something) with one or more other people

• coManage (comanage.com) - a full-featured property management software-as-a-service.

• CoManage (comanage.me) - Met onze handige bedrijfssoftware regel je online administratie, facturatie, klantenbeheer, voorraadbeheer, offertes én projectbeheer. (We'll let you translate that one if necessary!)

That’s it for this month’s newsletter; keep an eye out for our next one scheduled for late March. We hope to see you at our Open Office Hours on March 4th!

---

About The COmanage Project

COmanage is an Open Source Project that is focused on streamlining digital lifecycle management for your populations. It consists of two tools: Registry and Match. 

COmanage Registry is an identity registry with flexible enrollment and lifecycle management capabilities that helps you meet your identity management objectives using standardized tools and approaches. It can be used as a central person registry, a guest management system, or a collaboration hub for scholarly collaborations.

COmanage Match performs identity de-duplication in order to help minimize the creation of duplicate accounts for the same individual. It provides a heuristic-based system for matching identity records across multiple authoritative systems of record. Match can be used with Registry or as a standalone product complementary to your other tools.

Learn more about the project and its supporters at https://incommon.org/software/comanage/.

---

Q: Why did I get this awesome email? 

A: Because you have subscribed to one of the COmanage mailing lists!
See the COmanage Email Lists wiki page for more details.