Skip navigation
All Places > Alfresco Content Services (ECM) > Blog > Author: davidcognite

I’m excited to announce that we’ve completed the move of Share’s entire codebase to GitHub.


The observant amongst you will notice that a couple of months back we moved the old Share GitHub mirror and stopped updating it - that’s because we’ve been transitioning both the code and our internal development processes to GitHub natively.


As of today, the new repositories are now public. The Share codebase is split across four repositories:



Surf Web Scripts:

Aikau: (this project has always been openly developed)


What this means for everyone who uses or develops against Share is that you’ve now got a much greater level of transparency over how we’re working, earlier visibility of what we’re doing and an increased opportunity to have input to that process. It makes it significantly easier for us to accept contributions as pull requests and for those of you who want to apply custom patches to your own forks. These benefits apply whether your Community or Enterprise users, as the codebase is exactly the same across the two versions.


We’ve written contribution guidelines to help, so please take a look at those:


Those of you who are coming to DevCon, I look forward to discussing this there and maybe even working with you on some Share PRs at the Hack-a-thon.


RM Pull Request Process

Posted by davidcognite Nov 14, 2016

Alfresco Records Management is now able to accept Pull Requests to our GitHub project. Following the success that Dave Draper and the Aikau project has had in receiving community contributions, the RM team was keen to get the process sorted out to enable us to accept pull requests from our GitHub mirror. We accepted our first pull request from the community last week: Fix for Dynamic Extensions by cetra3 · Pull Request #2 · Alfresco/records-management · GitHub  - thanks to Aussie partner Parashift for sending that one in.


As explained previously, we use a mirror script to create a public copy of our community code base. This script now pushes any PRs made in GitHub back to our internal Git server and creates a bamboo branch for us to review the code from.


As part of this change, our scrum master Christine Thompson has opened up the RM JIRA project so that we can create issues that are publicly readable without an account, which we feel better matches the openness of working with Community members on pull requests.


So, if you find an issue you'd like to fix:

1) Raise a JIRA when you discover the issue (it'll be invisible after you create it as RM tickets default to "Internal" access only, but we'll open up the access when we triage it).

2) Send us a Pull Request.

3) Our build servers will pick up the change and run our automated tests on it.

4) We'll try to review the code as quickly as possible (how long that takes depends on the size of the change, severity of the bug and balancing it with other priorities), but will keep JIRA and the PR discussion updated.


If you're planning on starting work on any significant code submission, it might be worth checking the approach with us first to avoid disappointment - we may already be working on a fix or have a refactor of that area of the code planned. It's likely that we'll also need to get a contributor agreement signed.


I'm eagerly awaiting the next PR; if you could change any code in the RM module, what would it be and why?

For the last few months, the Information Governance team at Alfresco has been heads-down getting Records Management 2.5 released. Since then we've been tidying things up on our community code base.


New Community Release

Alongside our Enterprise RM 2.5 release, we’ve got a shiny new RM Community release too: RM 2.5.a. This version has been tested against the latest 5.1.g (201605-EA) and 5.2.a (201609-EA) Alfresco One Community releases, so although the pom specifies 5.1 as a dependency, we don’t expect any issues when running against 5.2. Please let us know if you find anything.


Download the zip:

Check out the docs:

and see below for details of the code.


Community code now back on Github!

As I said in a previous post on my blog, we moved the RM code from SVN to our internal Git server recently (actually, it was about a year ago!) and since then, the SVN -> GitHub community mirror hasn’t been doing much.


We had a few issues getting the mirror set up due to the way we’d structured the new project, rm-community and rm-enterprise are both in the same repo which makes it much easier for us internally when we’re working on code that crosses projects, but with some creative python code from Tom Page, we were able to extract only the commits that make sense for the community and push them to our GitHub repo: - please take a look at the latest code. We’re keen to receive pull requests, so if there are any bugs you find and want to submit a PR for, please do (and raise a JIRA:


Community Versions tagged

If you’re looking for the code for a specific RM Community version, then Tom's hackathon project will please you no end. He’s fixed the tags in GitHub, so you can go to the releases page for our new repo to see community tags for 2.3, 2.4 and 2.5 releases. If you really want to see versions older than that, you’ll need to go to our old repo and look at the tags there, but try to stick with the new stuff if at all possible - it’s much more fun to work with!


What’s next for RM Community?

Following news that version 3.0 of the Alfresco SDK is on its way, we’ve got an on-going development task to upgrade the RM project to use it. It’s still a work in-progress and we’re keeping Ole Hejlskov and Martin Bergljung in the loop as we have feature requests/bugs. The theory is that we (Alfresco Engineers) should be using the SDK for our own projects, so it makes sense to ensure that the RM module works with version 3.0. I’ll post back here once we’ve got more news on that.

Filter Blog

By date: By tag: