The future of Alfresco’s Community – my thoughts

Update June 14th 2014

It seems that there is quite some interests in the general “Future of Alfresco’s community”-topic. There are already 20 comments here & some more on twitter, linkedIn & Co.

I would be a pity if this is just another discussion that does not lead to any acting. So my proposal:

Let’s do a workshop at the day before London Summit (or even SF if it suit your needs) this year with participations from the Community, Alfresco’s Community Team, Alfresco Engineering & also Alfresco Management if they like to join:

  • Collect Ideas about how to give the Community a boost (like fast-track Contributions, a Aikau widget/plugins system, docs/ guides & tutorials …)
  • Goal is to have a concrete “Community enablement Action Plan” for the next 6 or 12 months


Main post

Jeff Potts recently announced that he is going to leave Alfresco as Chief Community Officer. From my point of view, Jeff was a wonderful “beekeeper” & pushed the Alfresco Community (I’m talking of the Community here & not Alfresco Community Edition!) forward. We had some great Alfresco Devcons that where mainly organized by Jeff – another big “Thank You” from here!

But, the Alfresco company has changed heavily in the last 1 or 2 years. It’s becoming a more & more Sales & Profit (+ IPO-) oriented software vendor like every of their competitors. Already the 1st Alfresco Summit 2013 – as successor of the DevCon –  has shown that the focus has changed al lot.

Don’t get me wrong, It’s perfectly OK that Alfresco as company likes to grow & gain a lot of profit & money, but as a Community member I’m more & more getting the feeling that they forget about their Open (Source) origin. Alfresco should beware of becoming a “sales monster”.

So, as Jeff left Alfresco there is no more a strong & official “Community believer” working for Alfresco. Of course, there are al lot of high talented engineers working for Alfresco in different roles (Engineering, Product Management, PreSales, Support…) that will still push Alfresco to be Open (not only Open Source), but there is an opportunity to setup a “new community network”:

I don’t really like the job title “Evangelist”, but IMHO that’s what Alfresco need to do to work on their Openness:

  • Get some Alfresco community members (should have deep Alfresco knowledge) on their payroll & give them the freedom to work on dedicated community projects (that maybe will be contributed to the core afterwards) – Thing about an approach like share extras + more repository oriented addons like ContentStore encryption, oAuth2-provider, a Dropbox integration (+ prototyping some new ideas like a task board and suchlike)
  • Let them do more tech-driven marketing like
    • Speak on conferences
    • Organize meetups (not Partner-oriented marketing events)
    • Organize Workshops, Hackathons etc.
  • Focus on the local community as things are completely different between US & EMEA or DACH in special
  • These guys should also be able to support Alfresco Consulting or PreSales, but not as their main job

What do you think – is a team of “Alfresco Evangelists” the future of Alfresco’s Community team to strengthen its Openess & technical marketing and visibility?


40 thoughts on “The future of Alfresco’s Community – my thoughts

  1. Hi Jan,

    I for one just kicked off a try establishing a community driven meetup. 🙂

    As for the rest, I have the feeling that Alfresco knows what they are doing and where they want to go. And I guess the fact that Jeff left the company speaks for itself. Looks like 10k+ employee enterprises are driving it … slowly – pretty much like Oracle. I don’t see this change in the near future. Still there is room left to do pretty cool things with cool people.

  2. Hi Jan, I had the same feeling when Jeff left.
    The more concerning part is there is no one following-up on Jeff’s positions (atleast that I know of).

    When Will Abson builded the Share Extra’s it was awesome, but the part is that it hasn’t been growing since a couple of years. You see these kind of things more ate Open Source companies, who start something but don’t finish it. For example the Activity kickstarter project, was a great effort but took too long to finish.

    Let’s see what happens, it’s too short after Jeff’s leave to make anything out of this. Just the fact that Alfresco needs to follow-up pretty soon after this.

  3. Andreas & Tahir, Thanks for your comments.
    As far as I know there won’t be another Chief Community Officer on the short term.
    Yes, I agree that Share Extras was & still is a good starting point. Some extensions made it into the core like Node-Browser & HTML5-Preview, but as several other addons maintenance & a steady investment is the main with such things available for free. Activiti Kickstarter will come back soon.

    Instead of just complaining about the issue I’d like to propose a way out of this dilemma as written in my post. A small bunch of people, locally distributed & familiar with Alfresco coding & projects in general that act as “special forces” to give the community a boost & develop + maintain addons, PoC, tutorials etc.

    I’m not talking about the feature-set of Alfresco Community Edition – Alfresco’s community & the Alfresco Community Edition are two different topics that may have some relations (e.g. Contributions / Pull Requests).

  4. I apologize for being slow to respond to this. I was on vacation until yesterday.

    There are certainly strong “Community believers” at Alfresco. I am disappointed that you forgot about my role on the Alfresco community team. Jeff and I worked together as the Alfresco community team for nearly the entire time he was Chief Community Officer. Alfresco will probably retire the C-level title, but I will be assuming Jeff’s responsibilities. Alfresco has grown and evolved quickly, but don’t expect huge changes in the community in the short term.

    A few thoughts on the rest of the post:

    * As a fast growing company, there is always more to do at Alfresco than there are resources to do it. A lot of what you mention is not a change in attitude so much as the result of limited resources.

    * As Jeff explained during his keynote at the last Alfresco Summit, a lot of the new leadership were unfamiliar with open source when they joined the company. Many of them have come to appreciate the value of open source, and we are working at educating them on how to be responsible members of an open source community. With Jeff’s departure, the leadership reached out to me to confirm their commitment to our community efforts.

    * Share Extras is still moving forward. As the code base has grown, a larger proportion of time spent on that project needs to be maintanence. However, Share Extras is just one portion of the hundreds of add-ons at . Our community members are still contributing lots of useful code.

    * Jeff and I have always seen developer evangelism as a big part of our role. All of the efforts you cite are things we have done in the past, and expect to do in the future. We are a small team at an increasingly large company, and I don’t expect that to change in the near future. But with the help of people like you, and other involved community members, we hope to increase our impact.

    Thank you for the post, and for your enthusiasm for Alfresco. I look forward to working with you on meet-ups, events, blog posts, and other contributions.

    Anyone who wants to reach me can email with thoughts and feedback.

  5. Now honestely: Is the Alfresco community generally perceived as healthy ?

    Is there a demand for changes ?

    If so, are there volunteers willing to make new efforts ?

  6. Richard, the intention of this post was not to say that we need another C-Level Community Manager or that there is a problem regarding the “beekeeper”-job.
    I’m sure that you can cover most of Jeff’s tasks, but from my point of view managing a community as “beekeeper” & having/sponsoring a locally distributed “task force” are two different topics.
    I don’t want to talk about the “beekeeper” topic – It’s all nice there. I want to talk about how the Alfresco Management can give the Community a boost as described in my post.

  7. Andreas, imho there are different views:
    1) There are more than 100 addons available at
    2) Most of this addons are outdated & no maintained
    3) Some regions like DACH don’t have a strong local community, some regions like belgium seem to have a quite large community
    4) I often hear complaints about the quality & feature set of Alfresco Community Edition
    5) I often hear that people would like to have a “pull-request”-style & faster contribution process (to Alfresco core)
    6) Jeff is “the tutorial guy” – who does have to expertise & time to support him here (Ole Hejlskov has recently done a great job with his Aikau-tutorial)

    At least 2, 3 & 6 could be massively improved by creating such a “task force”/ group of evangelists.

  8. Andreas, that’s why I’ve written this post. Make a proposal, start a discussion & watch if sth. gonna change/happen.

  9. Jan, I agree that more volunteer contributions would be helpful and are needed. It is also important to have more of the developers who are paid by our partners and customers contributing back. And Alfresco needs to be better about encouraging and recognizing those contributions. These are all long term initiaves that need to remain our focus.

    But there are already a lot of Alfresco Evangelists in our community who are doing great work (such as yourself). I expect that Jeff will continue many of his efforts. Ole, Boriss, and Martin have been working at better organizing these efforts. My goal is to support your efforts as much as possible.

    Thanks for sharing your ideas, hosting a great discussion, and for your enthusiastic support of Alfresco.

  10. As Richard points out, the list of tasks Jan describes is what Richard and I were responsible for. We worked with the community to organize meetups. We spoke at conferences (particularly when developer outreach was a primary focus). And we supported Sales & Marketing efforts, but not as a primary task. We were (and Richard still is) Alfresco Evangelists.

    There were two differences in what we did versus what you propose:

    1. Local focus. Richard and I are both in the US, so we were unable to focus on Europe as we would have liked to. Frankly, the community is much stronger in Europe than it is in the US, so this was a gap. If I had been given the resources to do so, I would have hired at least one person with the background you described to help me cover Europe.

    2. Dedication to community projects. There is way more work to do internally than a one- or two-person community team can handle. There was not enough bandwidth to allow much time for the community team members to dedicate time to community projects. Even if bandwidth was found, I am doubtful that the current senior management team would support dedicating significant resources to coding on community projects. I don’t think that should be surprising given the givens.

    So I fully support the idea of hiring a teammate for Richard who is based in Europe and I think it would be best if that person was technical and already active in the community. Whether or not that happens is up to Richard and the management team.

    I think it is time for those of us in the community to do what we can to help Richard, to rally the community to continue to innovate and contribute, and to do everything we can in our own worlds to evangelize the platform.


  11. Jeff, Thanks for your comment. I fully agree with statements.
    I’m sure that Alfresco would draw great benefit from from strengthen & distributing the Community team – in terms of recognination of being ‘open’ & more contributions but also in terms of more projects & customers due to a better visibility (let’s call it technical driven marketing.)
    I were involved in lot of ecm platform evaluation processes here in germany where to potential customers often compliant about the following things:
    A) bad & outdated documentation
    B) A weak (local) community
    C) “Strange Web Framework”

    The prospects where searching for a (new) ecm platform & would like to do at least some development on their one. So, they were thinking that a Open Source ECM System would be a better choice than any dinosaur ECM -> The Open Source factor is a big one for such prospects.

    To be fair, Alfresco had invested a lot to solve issue A) ( and also Jeff & his team has done a great job here by providing a lot of tutorials, but there is still room for more tutorials & more current ones.
    As Dave tweeted that is following the discussion: Your SURF blog posts are a big deal, but what if you would put them together in tutorial or guide and keep them sync with current trunk? A lot of work, but it would help a lot of community members and partners!

    Regarding B) That’s why I’m calling for local “evangelists” – Alfresco Management may insert that the local SE should cover this. I don’t think so as they don’t have the time to do so.

    Regarding C) Talking about SURF here…well I like the framework but there is problem with documentation & ownership (Alfresco – Spring – Alfresco). Also Aikau is not self-explanatory. My wishlist to solve this one:
    – more guides & tutorials covering real scenarios
    – A reasonable SURF doc in general
    – + most important: examples as code is still the best guide (a job for the ‘evangelists’ ;-))

  12. Well, I think being a trusted evangelist requires passion. I would call Jeff and Richard passionate, but I do not have the feeling Alfresco as a company embraces passionate people and offers a pleasant environment. How many (seemingly) ignored core code contributions are out there ? Enthusiasm can easily turn into frustration if you feel ignored.

  13. @Jan – I completely agree that there needs to be better documentation for Surf and Aikau. The problem (as always) is “Who’s going to pay for it?”… I do the best I can, but it’s not my (nor anyone else’s) job currently… once we are able to demonstrate how quickly it is to build Alfresco related UI with Aikau (and I’m hoping that post Alfresco 5-0 that will become clear) then the interest and demand might be there for a focus on Aikau specific documentation and tutorials. In the meantime, I’ll continue to do the best I can with my blogs.

    @Andreas – it’s important to realise that code contributions are not quite as simple as you might think…. any code that goes into Alfresco needs continual support and testing forever onwards. I think lots of Community members are willing to contribute code, but not necessarily back that up with the support and testing… it then becomes the responsibility of relatively small Engineering and QA teams to support that contributed code that may only have niche value.

  14. @David : I think I have a pretty good understanding of change impact in general. Take as an example. I would consider this non niche value change with a fairly minimum risk. Whats the big deal here ? I could come up with some more of this kind. Basic l18n – daterange or date format in German: Its and “von … bis …”, not mm/dd/yyyy and “von … an …”.

    Things like ML and Search (when you are not pure ‘en’ which may be niche) are far more difficult and dangerous of course. Still, my perception from looking at JIRA (open contributions) and elsewhere is that these issues are ignored. Maybe you guys should consider offering a fast track version just as the Nuxeo people to. There are people willing to take risk.

  15. @Andreas – I’m not saying that Alfresco shouldn’t take community contributions… just that it’s not just the code that needs to be contributed. Presumably you’d be also be happy to write the automated Selenium tests and fix any bugs that get raised?

    Sure, this example is just a download link (which I completely agree should be part of the product) but not all contributions are so simple. Once again it boils down to the simple fact that if a *paying customer* was desperate for that feature it would have been added a long time ago.

    I’m not saying it’s right, I’m not saying it’s wrong… I’m just trying to clarify *why* contributions aren’t frequently accepted.

    Let’s take a much more complex contribution …. the PDF.js previewer – now that has been accepted into Alfresco and will be part of the next Community release – it’s not true to say that no contributions are accepted.

  16. Hello,

    another Alfresco voice here. This is a fantastic discussion to be having – thanks for the blog Jan.

    Just a couple of things to add to what Dave and Richard have already said: I do personally feel there’s a bit of a disconnect between the community and engineering. Hopefully this is something that can be improved, but if you don’t hear from us, it’s not because we don’t want to be involved, just that we lack time; even keeping up with the forums or IRC can be challenging.

    @Jan We are aware of developer level documentation issues, but are trying to improve that – have you noticed that all the new Aikau widgets come with JSDoc Documentation? I also believe that Richard and Dave and planning a TTL this side of summit.

    @Andreas: any localisation issues should be raised in JIRA: the bis/an issue was raised by a community member and fixed a while back (4.0.2) – if you’re still seeing it, please raise another ticket. With the download link, that’s been built in to the rewritten previewer, so is already available on

    One thing I’d like to see is a community contributed Aikau widget library, perhaps with an in-app interface an admin can use to install them. I know it’s a bit early for that to happen, but long term, they make an ideal extension point for Share. The problem is that Alfresco Engineering is relatively small & we’re just not able to do everything nor can/should everything be included in the core – there’s definitely a place for community owned and managed add-ons.


  17. Then maybe Alfresco should clearly state preconditions for acceptance of contributions and communicate JIRA issue status properly. For most of the open contributions, it is absolutely not clear what the problem is. This frustrates people – believe me.

    And if Alfresco wants engaged, passionate developers they should seriously consider introducing a fast track.

  18. @Andreas – I completely agree – and I think this will happen in due-course, however what isn’t necessarily clear to the external Community is that there is a lot of work going on internally to “get our own house in order” first.

  19. David, I love the idea regarding an Aikau widget library. Someone has to provide an in-app interface first to easily install such widgets/plugins…imho that’s a task for the engineering team as this interfaces must be fully supported.
    Another topic are “webhooks” or web-enabled policies/behaviors 😉

  20. Updated my post & proposed a joint workshop the day before the #Alfresco summit to create a concrete “Community enablement Action Plan” for the next 6 or 12 months.
    What do you think? Who would like to join it?

  21. Jan, thanks for starting this discussion.

    I would be very interested in such a meeting prior to the summit. I’ll be attending in SF.

    I think that meeting face to face to formulate a plan and to discuss who and how this will be coordinated will be invaluable for the community.

  22. Hi Dave & David,

    Just one remark about accepting community contributions. This was spoken at least 2 summits ago and clearly no progress had been made.
    If you really want to engage the community and want our dedication, then you will have to trust us.

    I’m always hearing (also in your post) that the engineering team doesn’t have time for this and that. We consultants fix 80% of the Alfresco bugs raised in Jira & support portal. I’ve literally posted fixes in the support portal and it has never even picked up by engineering, mostly due to lack of time or different focus.

    You don’t want that in a couple of years the Alfresco code gets forked and we work on our own solutions and fixes.

    Let’s at least have a skype/web chat with the engineering team to brainstorm and follow up on that every quarter.


    Tahir Malik

  23. @Jan – hopefully it’ll be easy to add additional widgets into the Aikau framework by virtue of the packaging structure that AMD provides (i.e. you can easily namespace your own code to create separation and then share your own code in the form of drop-in JARs, containing and extension to include your widget package in the AMD loader). There is obviously still work required to not just standardize an approach but to address versioning, etc. – I doubt this will have been standardized by the time 5-0 is released.

    @Tahir – in this discussion about code contributions, I have no power to make any changes – I’m simply trying to provide some clarity and understanding of why every contribution is not readily accepted. I have to admit I find it hard to believe that consultants fix 80% of bugs – and would be interested to know where you get that figure from. Once again though, it comes down to the same thing – if *paying customer* needs a fix then it will be provided (in this context the payment is going towards an Alfresco license) – this is just the way of the world. If people decide to fork and open-source project then there’s not much that anyone can do about it, I strongly doubt that this will happen to Alfresco until done by a large organization with the resources to both support the forked code base and significantly move it in a different direction. Finally, in terms of brainstorming sessions, that isn’t under my control – your best bet would be to work with Richard Esplin to engage the engineering team that way.

    @Andreas – I’m sorry to hear that.

  24. I don’t want to concentrate on the “community contributions”-topic here. I guess, we all agree that the code contributing process(features/changes/patches/fixes …) is currently not as it should be. But I’m sure that the 80% figure is wrong.
    Code contributions is just one thing in the general “future of Alfresco’s Community” discussion.
    @Richard, what do you think about such a pre-summit workshop?

  25. Sorry for spoiling the game, but there are things which require backing of Alfresco (management !) to succeed. And they are not deaf, blind or stupid.

    The code contribution issue is one example. The actions a very small bunch of geeks would like to see happen are pretty clear. I bet Alfresco has discussed it internally long ago. We can see their choice today and we need to respect it. They are still giving away something valuable for free.

    In the end, they need to be profitable on a global scale where a small market (Germany) or a small bunch of geeks does not matter.

  26. Lots of interesting topics. I have a few thoughts directed to the community in general, and not just to the people in this conversation.

    * We should be careful to not be focused on the negative, as it is easy to get caught up on the problems with participating in the Alfresco community. If you look at how the community has matured over the last few years, it is easy to see lots of great improvements. Many of the remaining problems are hard problems that most communities struggle with. We will keep improving, but we should be realistic about what can be done and how fast.

    * Everyone in the community have different priorities, and it is hard to figure out where to invest so as to provide the most useful return for effort. New members of our community have different needs than experienced participants, and records managers want to participate in different ways from UI developers. We have to balance our efforts across the entire community.

    * We have previously discussed how to handle code contributions, and will discuss it again. As has been pointed out, it takes engineering resources to review and accept the contributions. Every organization struggles with the balance between working on prioritized items, and polishing what is already there. We are making progress. I see the GitHub mirror as a big part of the solution. I also hope that many of the ideas we have employed with the Activiti community can be used to improve governance of the Alfresco products.

    * JIRA is the place to submit short patches and bug fixes. It is true that many patches languish, but a lot patches in JIRA do get picked up and added to the product. It is very unlikely that Engineering will see a patch that isn’t in JIRA. Other users also benefit from those patches. Hopefully the GitHub mirror makes this easier since you can submit a pull request there, and reference it in a JIRA issue.

    * I don’t think we need to wait until Summit to have this type of discussion. This sounds like a great conversation for a Google Hangout. It would be good to also meet at Summit, but the US and EMEA communities wouldn’t be able to meet together. Maybe we should plan on lunch together, or have an evening discussion after the hack-a-thon or on the last day. It is going to take more than one session to get anything useful done.

    * Honestly, I appreciate the discussion but I am a bit overwhelmed this week with Summit stuff. I will be distracted with Summit for a few more weeks. I expect thaht in early July we will be able to have a more concrete discussion.

    Keep up the conversation,


  27. I am really trying not to be negative – just realistic.

    Maybe I am missing some signals, but I cannot see a demand for ANY changes backed by more than a handful of people.

  28. Hi All,

    I was away for a week so didn’t see the responses :).

    I’m quite happy with the discussion and the participants. I just had 1 remark about the code contributions, didn’t mean that it’s the most important.

    What I meant by the 80% figure was more pointed to the issues raised by consultants themselves and they fix it before the support engineering team has. I’ve got proof that a lot of calls took more than 3 months to fix and some didn’t get fix at all. But I don’t want to start the support/JIRA thing here, that’s another topic, another time.

    ! The point is that the consultants out there have great knowledge and you see that knowledge spread over Stack, forum, google & the solutions they built. So make use of that knowledge.
    Create a group of Power Alfresco Community specialists run by external consultants. Who at least need the following
    – Have controlled meetings with the Alfresco engineers
    – Have a method of making code contributions easier
    – Arrange meetups locally with the help of Alfresco

    And give these people a title, a special authority, something special and they will do a lot in return.
    This seems like a lot of time of Alfresco is being used, but it isn’t actually and the result will be great.

    I’m not much of a google hangout guy, so if someone can tell me which hangout is created for this and when the first remote meeing can be held, then I’ll be definitely of the party.

  29. All, I have taken way to long to introduce myself and I apologize for that. I’m the CEO of Alfresco and have been here about 18 months at this point. We had a fantastic meeting with Richard regarding all of you and we discuss what’s working and where can we do a better job of interacting with you. We are in the middle of organizing ourselves to do a better job in those areas that you have pointed out above.

    I look forward to Richards leadership of the community and we are committed to continue to support all of you. More details to come as we work through things. I look forward to meeting some of you if you intent to attend the Alfresco Summit. Richard is also setting up office hours for us as well. //Doug

  30. Doug, thanks very much for joining the discussion here. I’ll attend the Alfresco Summit in London and I would be happy to discuss the pros & cons of my “Alfresco Evangelist” idea.
    The DACH region is truly a sleeping giant and I’m convinced that such a role – besides new well skilled sales team members – is needed if you want to wake this giant up.
    Jan (@alfrescian)

  31. Evangelism may help a bit, but seriously, I think Alfresco has more severe business level and usability issues in the DACH region.

    UI localization, Search, DATEV, ZUGFeRD to name a few. You may want to have a look at the competition such as agorum. Besides Germans try to avoid the Cloud at all cost. Nevertheless, the product is still good enough (and even better) than the competition in other areas.

    @Tahir: The hangout will be on Tuesday next week. You may want to have a look at Drop me a line if you want me to pick you up.

  32. Hi guys,

    Wow it’s been a lot of talking here! That’s the simplest way to realize Community still cares us. As you all recall, it’s quite important that we keep the community alive, and it’s something we have to take it very serious.

    My point about Jeff leaving Alfresco (despite the fact is a sensitive drop for the Alfresco team, but it might be good for the Community as he could dispose more spare time to collaborate with the Community, who knows!

    Community in Spain is really active and I try to do my best to keep it alive (actually we have scheduled a Meetup in early September) and I know most of you do the same in your countries. I have to confess I’ve always felt backed up with Alfresco every time we have arranged a meetup and I did not think we would lose it after Jeff’s leaving TBH.

    Anyway, happy to be involved in these discussions during Alfresco Summit or even earlier if we can organize a hangout.


  33. Andreas, “evangelism”/”advocates” or whatever you call it will help a lot more then you’re thinking because it will help to clarify in which functional areas Alfresco is strong & where not. This team gonna build (or help building) extensions to fill the gaps and to encounter new functional areas. I’d expect a direct line between this team & Alfresco engineering.
    Some of you might think, that the Alfresco Pre-Sales team is already covering this tasks, but I don’t think so as most of them don’t have enough time for that.

  34. Hi Jan,
    I like your idea of a pre-summit workshop pretty much. If there is one I’d like to join. I agree that we in the field should organize our independant discussion about a community future, best practices, howtos. Alfresco may join, may agree or not but is allways welcome to join and support. It will help both parties very much if there will be an emancipated community wich is independant, visible, has a vision, an opinion and is not just degraded to a committer or consumer role.
    At the moment I see many people moving from Alfresco to other topics since they are disappointed for any reason.
    There are many topics which could and should be addressed by a living community but may not of interest for Alfresco. So we shouldn’t blame and discuss instead how to act or why not.
    What we all have in common (incl. Alfresco) is that we need to earn money for our work. ECM is not an emotional topic many people have skills in and work in their spare time. So we should also discuss business models, sponsorships etc. to pay the people creating contributions. There is a reason why many of the addons rest in peace…
    Some of my personal interests are how support real and better DMS scenarios (I think Share customisation is much to expensive in comparison to other platforms – so why not integration UI-platforms like ifresco, cara in this discussion), master data management, better identity management, better task management.

    Looking forward to continue this discussion!

  35. Hi Heiko,
    currently the community is forming an independent organization to give the Alfresco Community Edition a boost and to ensure it will be open forever.
    Take a look at
    Sadly, I won’t be present at Alfresco Summit this year. But maybe the Order of the bee is going to organize such a workshop.
    Cheers, Jan

  36. Hi Jan,
    let’s combine both:
    * we arrange a physikal or online meeting with the bee team (strange name – I’ve seen the discussion but I would vote for something like ” ACUG Alfresco Community User Group”)
    * Some bee mebers may discuss specific outcome / suggestions with Alfresco team in London
    greets Heiko

Leave a Reply

Your email address will not be published. Required fields are marked *