COmanage Developers List

[Heather Flanagan <>]

On Oct 5, 2009, at 6:56 AM, Emily Eisbruch wrote:

*Carry Over Action Items*

...

[AI] (Digant and SteveO) will put together a demo video.

[AI] (Digant) will register the Sympa bug in the COmanage JIRA for our reference, and follow up with Sympa developers/maintainers.

Digant, I thought you did this one and just didn't get anywhere?

[AI] (Digant) will verify that Confluence is working with COmanage

Since the appliance is on indefinite hold, this one can come off the AI list.

[AI] (Digant) will incorporate the user dashboard that Steven designed into COmanage.

Since the appliance is on indefinite hold, this one can come off the AI list.

[AI] (Ken) will talk with Lois about Fluid involvement in improving the COmanage GUI, scheduling it for later in the year.

Does anyone know if Lois is still involved in Fluid?

[AI] (Chris) will contact Atlassian and try to obtain a timetable for Jira domestication.

If this wasn't done, Steven, can you do this since you've got a good relationship with Atlassian?  If not, I'll get it.

(Ken) will provide some wording for this communication with Atlassian.

I'm inclined to point them to the upcoming domestication guidelines from Jim and Steve for the message.

[AI] (SteveO) will ask Michael about the ability of a COmanage instance to accept logins from both federated and non-federated sources.

For this one, my $.02 is that with COmanage the shining point of all the federation, group management, and other middleware work that I2 is doing.  Why do we want to enable it for folks who can't/haven't figured out any of that yet?  I'd rather leave the bar higher and drive/encourage institutions to step up and get federation and all that implies to start working.

Heather Flanagan
Director, System Administration