# Summary
Open Atrium is a Drupal Distribution for creating collaboration sites.
# Project URL
https://www.drupal.org/project/openatrium
# Where is the code?
Because Open Atrium is a distribution, see the make file in the 8.x-3.x branch for a list of all specific module code that is used.
# Estimated completion date
Since Open Atrium depends on a large number of contrib modules, it is difficult to estimate its completion date. Work is already underway on several major modules including Panels, Organic Groups, Media, Features.
# Dependencies
List is too long to list here, but will link related project D8 threads to this issue.
# Who's doing the port?
Unknown.
# What help do they need?
Unknown.
# D8 roadmap
More detailed roadmap to come in the future.
# Background and reference information
None for now.
Comments
Comment #2
mpotter CreditAttribution: mpotter commentedComment #3
Niklas.G CreditAttribution: Niklas.G commentedHi Mike,
It has been a long time since the last webinar, blog or twitter about open atrium. Starting to get very curious about how the development of the next version progresses :-)
Best regards
Niklas
Comment #4
druplicate CreditAttribution: druplicate commentedSee this: #2846523: D8 and project status?
Comment #5
Niklas.G CreditAttribution: Niklas.G commentedAny update on the drupal 8 version?
Comment #6
mmjvb CreditAttribution: mmjvb as a volunteer commentedAccording to maintainer too many modules of the eco-system are still missing D8 versions.
Comment #7
mgiffordWhich modules?
Comment #8
Biker93 CreditAttribution: Biker93 as a volunteer commentedWe have several websites running OA as well as Drupal 7 sites. We are deploying new sites with Drupal 8. We need to plan the update of the older sites to D8, even if it is over a few year time frame.
The basic question is: will OA ever be updated to D8 or do we need to explore alternatives?
How many contributed modules still need to be updated?
How many OA custom modules remain?
If there is a roadmap or a time estimate, perhaps we can assist in the upgrade, but we'd need some sense of how large a task this is.
Comment #9
mmjvb CreditAttribution: mmjvb as a volunteer commentedThe purpose of this issue is to provide answers to these kind of questions. They should be asked in the project itself,
Comment #10
delacosta456 CreditAttribution: delacosta456 commentedhi
in past 1 or 2 years i would have also asked for an urgent port to version 8... but l now think that porting OA to version 8 may be time wasting as
d8 will end on 2021 (which is also the same year d7 too will end) .
So i think Discuss should be planned and focus on version 9...
Comment #11
mpp CreditAttribution: mpp commentedWill openatrium for Drupal 8/9 use og or groups?
Comment #12
marty.true CreditAttribution: marty.true commentedIs this happening or not? This appears to be going away. The openatrium.com site is now just redirecting the project page on D.o so is Phase 2 "phasing" this out?
Comment #13
colanIs Open Social a viable alternative for Drupal 8? If so, can we mark this as a duplicate?
Comment #14
imclean CreditAttribution: imclean commented@mpp
Good question. The IS also mentions the Features module. Drupal 8 (9 and beyond) is so fundamentally different from Drupal 7 that it would require a complete rethink on how OA is built rather than trying to replicate previous versions with the exact same set of contrib modules.
What should the distribution do? How can this be achieved with Drupal 8?
We didn't use it past the Drupal 6 version which which we mainly used as a Case Tracker for various clients and projects.
Comment #15
mpotter CreditAttribution: mpotter at Phase2 commented@delacosta456 Any D8 version would work with D9 unless it used deprecated code. There is no reason to "wait for D9" today. See the various D9 roadmaps and discussions (I know your comment on this was old, so you probably already know)
@mpp OG in D8 does not support fundamental Atrium requirements, such as Subgroups. The "groups" module supports Groups within Groups, but obviously migrating from OG to Groups is very difficult.
@colan Open Social is its own distribution and very different from Atrium in many ways (and has a lot of custom code). People are welcome to evaluate it, but it certainly isn't going to make it any easier to move from D7 to D8 for existing Atrium sites. If you have to rewrite for D8 then I advocate more for just building your own site out of modules and don't worry so much using about a "distribution".
In general, there are no plans to port Atrium to D8. If this was ever done, it would be as @imclean mentioned a "complete rewrite" again. We did the rewrite from D6 -> D7 with the intention that the architecture was improved and wouldn't need a "rethink for D8". But that was before it became clear how different D8 was going to be from D7. Now that we've had D8 for a while it's pretty obvious that trying to replicate Atrium with the same modules (or porting it) would be a huge effort and we've had no clients willing to pay for that.
Moving from D7 -> D8/9 is rarely easy for any site, and Atrium sites are no different. Atrium has no magic way of making the D7->8 transition any easier...if anything it is harder because Atrium really embraced using a lot of different contrib modules that have just changed too much in D8 (if they even still exist).
If you are a big organization that depends on Atrium and have the budget to pay a vendor to migrate to D8 and were willing to contribute that work back to the community then definitely let me know. But if you are a smaller organization that can't afford that kind of project then I'd say to just stick with D7 and look into the D7 Extended Support option.
Comment #16
delacosta456 CreditAttribution: delacosta456 commented@mpotter
yes of course and thanks for others explanations.
Comment #17
sastha CreditAttribution: sastha as a volunteer and at TATA Consultancy Services for Johnson & Johnson commentedComment #18
Biker93 CreditAttribution: Biker93 as a volunteer commentedMike, can you give me a rough estimate of the level of effort ( hours and/or dollars ) to do the upgrade to Drupal 8 or 9? We've used it for several projects and MIGHT be able to justify some expenditure if that is less expensive than migrating to a new collaboration platform
Comment #19
enricpera+1 we have also some projects, somebody is already working with?