Atlassian Engage 4 Good Project Application Due January 30!

Looks like January will be a busy month for grant writing!

What is this about?

Engage 4 Good is an Atlassian Foundation program connecting employees with purpose-driven organisations to collaborate on skilled projects, increase their capacity and capability, and leverage digital technologies.

Who : Atlassians have about 5 days of “leave” each year that they can use volunteering on a project. This is a way of connecting Atlassians with organizations who have projects that align with Atlassian’s skills/experience.

How much time? Up to four hours a week or 5 hours for 3-5 meetings/workshops

When would Atlassians work with us? August-November 2022

The application is relatively straightforward - and really focused on communicating a) what problem we’re trying to solve, b) how this project will solve it, and c) the value to our community/beneficiaries of solving this problem.

@burke @grace @ibacher @dkayiwa @cintiadr @permissionerror Trying to remember some of the ideas that were floated around the last spring/summer, when we didn’t have much time or bandwidth to work on this. Anything come to your mind?

More info about Engage 4 Good:

Atlassian Foundation would like to invite non-profits and social enterprises globally to apply for its skilled volunteering program, Engage 4 Good.

Engage 4 Good is an Atlassian Foundation program connecting employees with purpose-driven organisations to collaborate on skilled projects, increase their capacity and capability, and leverage digital technologies.

Our teams across the world have a wide variety of business and technology skills that may be relevant to help you solve the problems that limit your team’s potential.

Download the guide to find out more and apply by completing this short form.

Applications close 11.59pm Pacific Daylight Time on Sunday 30 January 2022 (4.49pm 31 January AEDT).


@jennifer there seems to be a typo in the year within the part of

When would Atlassians work with us? August-November 2021

Hey everyone! This application is due in a little less than week (January 30). Any ideas?

1 Like

Hey @burke @ibacher @dkayiwa - what do you think.

A few suggestions to follow; keeping each separate so folks can :heart: the ones they like.

Some helpful information for us to keep in mind:

  • They’d work on the project from 28 Feb - 20 May. 12 weeks; each volunteer can commit 1-4 hours a week “to collaborate on a solution.”
  • Scope needs to be small. I looked at their past project videos and most were “we helped this group use Trello” or “now they use Jira better”. “For example, we may not be able to build you a new system but could we analyse existing systems, and plan out a technology roadmap for the next year” - I think we want them to work on actual stuff, not just plan work that we’d still need to do later.
  • Example possible Tech skill sets: Back-end software development, Continuous integration / continuous deployment, Systems design and implementation, Website development, Continuous process improvement, Front-end software development, IT strategy, Automation, DevOps, Website design

Idea 1: Migrating from OpenMRS ID to KeyCloak (Large Impact, Large Effort)

The biggest need in my mind is getting on to Atlassian Cloud. But Cintia and Ian and Burke keep saying, that’s not the big lift; the big lift is our Auth service.

@ibacher @burke @dkayiwa do you think migrating from OpenMRS ID to KeyCloak is do-able given the time constraint mentioned above? (i.e. 12-48hrs?)

1 Like

Idea 2: Review of OpenMRS 3 Onboarding by a Frontend Dev (Medium Impact; Medium Effort)

Have a frontend dev go through our 3.x dev onboarding and i.d. where the process and technical documentation needs improvement; make suggestions.

(Why: Presumably their frontend engineers are a decent benchmark for whether our current process/documentation meets the broader industry good practices. Without a comparison like this, it’s hard to know right now which issues 3.x devs are facing are because there’s something generally problematic in our documentation, or whether some problems are specific to our industry because many devs haven’t used JS frameworks before.)

@bistenes what do you think of this?

Idea 3: OpenMRS Website - Fix Google Analytics Sustainably and create SOP for maintaining it; & General Site Improvements (Medium Impact, Medium Effort)

It’s been annoying that our Google Analytics tags keep dying somehow, and Ian and I are the ones who keep catching this and having to fix it. Yet our GA tags keep breaking and this isn’t discovered until I try to find out the impact of our new Product site pages, only to discover that zero traffic has been logged for weeks or even months.

Our website squad is also quite small and doesn’t seem to have bandwidth for all the work and improvements that could be done. We also haven’t received much actionable feedback on the new site. So, ideas:

  • Fix Google Analytics and create SOP for maintaining it
  • General Site Improvements recommendations
  • Improvements to be made to improve Donor awareness/appeal

Idea 4: Jira and Confluence Housekeeping best practices (Medium Impact, Small Effort)

According to past projects, this team has gurus for how to optimize Jira & Confluence, and how to keep them clean.

For Confluence, we don’t have much guidance on how to keep our documentation fresh. Maybe they know of a process similar to our Jira Clean-Up process that we could apply.

For Jira, I’ve documented our Jira Graveyard SOP; they could review this and our Jira and make suggestions for improvement.

@cintiadr mentioned that she was going to put something together for this. Any updates?

1 Like

I like the idea of trying out KeyCloak. Even if we couldn’t fully migrate to KeyCloak, proving its a viable option, working out configuration details, and defining the strategy to migrate would all be valuable.

1 Like

@grace i like all your four ideas. :slightly_smiling_face:

They are critical needs of our community.