Hi,
Is there work going on for Commons based on Drupal 8 alpha release? Please also let me know the road map of commons in terms of new features going to get added, If thats all are the features of commons then we can start for migrating it to Drupal 8.

Thanks and Regards
Amit Tarkar

Comments

amittarkar’s picture

Issue summary: View changes
ezra-g’s picture

Status: Active » Postponed

We don't currently have a release timeline for Commons based on Drupal 8. However as an estimate, it seems likely that this would be released a few months after Drupal 8 core is officially released.

For feature roadmap, we're working on revising our 2014 roadmap and that's something we can share sometime over the next few weeks.

amittarkar’s picture

Does commons based on drupal 8 beta released?

amittarkar’s picture

What te estimated date of commons based on drupal 8?

zhinio’s picture

Hi,
I am also interested in an estimate for D8 based Commons.
I like to know if I should continue with D7 for development of a new site or wait for a D8 version.
Thanks.

jmudshoe’s picture

Same! Beginning to strategize for a Drupal Commons project, and wondering if a D8 version is on a foreseeable horizon, which would be great! Thanks-

amittarkar’s picture

Status: Postponed » Active
giorgio79’s picture

An alternative distro for D8 https://www.drupal.org/project/social

Maybe the Acquia team could join forces with them, and provide an upgrade path to Social.

Also noticed this message on the Social distro page: "Drupal Commons for Drupal 7 used to be a strong competitor, but has lost momentum last year and will be discontinued by the current maintainer Acquia."

I also noticed ezra-g the product owner left Acquia as well.

amittarkar’s picture

But does It have all the features of commons? can we compare the features list?

amittarkar’s picture

Priority: Normal » Major
amittarkar’s picture

Priority: Major » Critical
japerry’s picture

Status: Active » Closed (won't fix)

I think I can safely say that commons will not be ported to Drupal 8. At least, not from Acquia.

I did take a look at open social, it certainly seems to be trying to fill the shoes from commons. I have some architectural questions with it, but the product is not complete, so it might be an option.

amittarkar’s picture

Status: Closed (won't fix) » Active

but still Let the community know it and If possible fix It.

ajayg’s picture

Looks Acquia won't be able to port it.
How about others following this module? Is there any common interest to port this? We can chip away each module in the next several months. Or alternately see if we can come up with a path to D8 Open social.

Either case there are so many base modules outside commons that it depends on (OG is a major one) which need to be ported to D8 first.

slowflyer’s picture

Hi,
I'm heavily using Commons since version 1.
But from my point of view, I would prefer an update path to Open Social instead of porting Commons to D8.
I think we as a community can benefit more from one strong product, we all try to improve instead of maintainig two similiar distributions.

ajayg’s picture

1. Unless there is a way to migrate from OG to groups , commons can't migrate to social.
I am looking at social with a bit of caution. Several times I have seen modules getting momentum because of a few passionate developers and then see it loosing after 12-20 months. The predecessor to commons module statuses, Activity log etc are example.

2. Commons code is small enough to port to 8 first. And then figure out a way to migrate Commons 8 to social 8 perhaps? Because by that time Og8 to groups 8 would have happened ideally. Keep in mind open social is not released yet.

3. OG has a life outside commons (or outside social networking space) with Open Atrium. So it will get ported to 8 , is underway and not going to go away. Groups don't (yet) have a life outside open social.

amittarkar’s picture

@slowflyer:There are some good features in both social and common, Thats why people are still here waiting for commons to get ported in D8. @ajayg: we think of combining good features of both the products, thats Instead of OG we can see whether there is an alternative for OG in social.
I like the events, user wall paper features in social and I am mainly here for the media module.

slowflyer’s picture

Ok, but it's not only a porting of Commons as it is to D8, it needs some modifications and cleanups.

If the upgrade is not supported from Acquia, there is no reason to keep the Acquia modules in like Acquia connector.
Second, Acquia added modules to suppport their partners like Kissmetric and Lingotek. Instead of Lingotek, the Translation Management Tool should be included for multilingual and translations. Its more flexible in case of selecting your prefered translation provider.
Apache Solr Search module will not be ported to D8 and needs to be replaced by the Search API Solr module.

The notifications / follow function needs a more granular configuration. Fe. if a moderator is followed by a user, the user receives a notification when the moderator creates new content, no matter of content type. If it's a newsletter the user is informed before newsletter has been send out.

And I guess there's a lot more ...

ajayg’s picture

Some of these issues will eventually work out. But real need is to get started on 8.x

We need to create 8.x branch and start porting modules, patches etc. I am surprised the maintainers of the modules has not chimed on this yet. Or perhaps they need help. Anyone who has time to submit patches and get in touch with current maintainers and get 8.x branch created?

amittarkar’s picture

@slowflyer:good one!! your earlier point also makes lot of sense " I would prefer an update path to Open Social instead of porting Commons to D8.I think we as a community can benefit more from one strong product"
So I suggest a following work arround /approach based on following points:
1) currently social is highly supported and contributed so those efforts must be fully utilized.
2) media module is already ported in D8
3) commons is not supported by acquia so we are free to remove unwanted modules, Infact we will have lot of freedom (this is most important). I was even thinking of creating separate 'New module' but many people still landup over here searching for commons, so the background and approach should be known.

so based on these points
a) here we should create social as 'baseline' version for drupal 8 and start development from there! all the updates from the social should reflect here as well.
b) We can think integrating of media module to social.
c) the enlist the desired features of commons which are not present in social and we will try to add those here. create the 'feature request issues'

Again I am not saying this that 100% !! I said above approach because we are almost going to develop from scratch so instead of basic D8 I suggested 'social' as making base version. We must not forget our real concern of maintaining the backword compatiblity , that is those users whose sites are already developed in earlier versions commons must be able port there sites into D8! thats the whole point of porting/maintaining this module in D8

amittarkar’s picture

there are following guidelines for migration to Drupal 8 using migrate_upgrade and
migrate_plus
http://www.tanay.co.in/blog/drupal-7-drupal-8-migration-101-and-observat...
https://www.drupal.org/upgrade/migrate
https://drupalize.me/blog/201511/simple-drupal-7-drupal-8-migration

use above guidelines 'using drush' to migrate the exting code to latest 'open social (instead of basic D8) and this step will let us know what are the things in social that can used for commons. this will reduce some efforts.

amittarkar’s picture

@ajayg: I think development version of OG . has been released. Are talking about this Group ? whats your opinion now? I am not very familiar with Social

ajayg’s picture

@amittarkar I was thinking based on OG . OG itself has been stuck in Development for more than 2 years now. I was hoping they would have atleast alpha version out by now.