Commons on D7 : Define a Minimally Viable Product (MVP)

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
marc.obrien@acquia.com's picture

We are interviewing Commons communities and doing research on successful Commons and social business communities. We are specifically looking for community feedback on what constitutes an MVP for Commons. This will help define an initial release of Commons on D7 and allow early, continual feedback in shaping the future of Commons!

Comments

Commons MVP wishlist

penguino's picture

Getting through a development phase should be a high priority. If Commons could be brought up with Dev Desktop and worked well (with templates) with NetBeans that would be a plus.

It would also be useful to have a Commons distro that would work on a shared server. That might mean a reduced set of modules that addressed a minimal set of user features.

Community Dev support

tahoeob's picture

One of the goals with Commons on D7 will in fact be to enhance the ability for partners to work with the distribution. We have heard this should be a priority. It would be great if you can continue to give feedback as we make progress!

To my mind almost any minimum

Soul88's picture

To my mind almost any minimum functionality will do. Cause for now if one wants to build a community site he'll need to start it from scratch and it'll be harder to switch/integrate with Commons later.

So being a Drupal developer and having a wish to port my own community to Drupal (I'll do it in my spare time) I'm thinking hard whether I should wait until first release of Commons or should I develop it from 0. The one thing I'm pretty sure about is that D6 version won't work for me.

So in my personal usecase I'd be glad to see almost any release for D7 with a clear roadmap of what is supposed to be done later. So I'd develop only my-site specific features or something I'll need to have from the first minute the site is deployed.

But anyway, thanks for the work you do. And I do realize that you have much more users with their own needs.
Thanks again.

Good feedback... in line with the MVP concept

marc.obrien@acquia.com's picture

Hello Konstantin,

Thank you for the feedback! I do agree that getting an MVP out into the community is very important. We will focus on the core needs of community and that will be a big benefit. We are also looking for community contributions for the MVP delivery and roadmap discussions.....

Dev copy?

hexag's picture

Hi guys,

Got a community website here in Holland to build & would love to start with a Drupal 7 copy of Commons, of particular interest to me would be doing documentation for setting up & installing, as I think that is where my skills could be of most use to the community. So is there a dev copy anywhere I could start playing with? Offering feedback, etc? The sooner I get my grubby little mits on a copy, the sooner I can start :)

Cheers,
hx

great idea

unleash's picture

hello dear hexag this is a great idea - starting with a developer-copy.

this would be a great thing - and besides of early adopting the new stuff - the development would benefit from the cycles of feedback .....

i also would love to see a developer-release.

Above all: i really love and appreciate this thread great ideas were shared. .- fruitful discussion here

Greetings
unleash

Good to hear...

tahoeob's picture

That would be terrific, we are currently still defining what the MVP will "be".... it would be great assistance to utilize your expertise as we progress!

Hi, I'm new to Drupal,

marjorum's picture

Hi, I'm new to Drupal. I've looked at Drupal in the past but the learning curve was far too steep. D7 is much more accessible and I'm looking forward to getting started on a commons based website. However given my previous comments it would seem daft to start with the D6 products at this stage of the game. So I can only echo the sentiments above by saying,give me something, anything, so I can get started. A development copy with minimal functionality would be fine; just give me some sort of roadmap so I know what's missing and I can plan round that. As is, I'm left twiddling my thumbs. I really cannot believe I am the only one in this situation.

Apologies if this seems a bit strident; I'm just keen to get started.

unleash's picture

Hi, I'm also very very new to Drupal.

i second the statement! My take is D7 is much more accessible, than all the previous versions.

I really really am looking forward to getting started on a commons based website. I eagerly wait to get the first site up and running! With D6 or D7!
If we talk about the feature-set: Well i am very very interested in a D7 version of Commons with basic OG functionality that is also extendable. This is somewhat the base install would include Groups, Blogs, Wikis, Documents, Discussions, Polls, Events and Notices.
Above all: I also can only echo great statements above by saying and arguing the same way. Please pleaese give me something, anything, so I can get started. Thanks for all you do - keep up the great project it rocks!!! youve got friends allover the planet! Hundreds and Hundreds...

greetings
unleash

D7 feedback

tahoeob's picture

It is great to get the feedback. Do you feel wikis and documents create an overload of content types ? If both are there we will need to design it so there is a clear deliniation....

D7 Commons with basic OG functionality that is extendable

rj.seward's picture

My request would be for a D7 version of Commons with basic OG functionality that is also extendable.

The base install would include Groups, Blogs, Wikis, Documents, Discussions, Polls, Events and Notices. In addition to this I would add a Chat module wherein different groups could open a group-specific chat room embedded into the website and then share that chat room with other groups if so desired. If we can do video-conferencing (embedded in the website) somewhere down the road, that would be most awesome. The setup required for video-conferencing is a little daunting so don't put this on the must-have list just yet.

I need the ability to install new themes and modules without breaking the existing Commons setup. Perhaps a list of "approved & compatible" modules & themes would be good.
A very big wish on the list is the ability to upgrade using Drush, or a Commons-specific port of Drush. Right now, Commons + Drush = Disaster.

Essentially, I need a base Commons which I can build, extend, & customize without messing up the basic Commons core. And the ability to manage the upgrades with Drush would be fantastic.

Extensibility and customization of Commons

tahoeob's picture

I agree and hear that often from partners.... we have discussed and a more accessible Commons for extending and customizing is an important consideration.

UX, flexibilitiy and MVP

mariomaric's picture

Hi Marc!

Thanks for the oportunity to participate in the making of the new version of Commons distro. :)

Althoug it may be offtopic, I'll feel free to draw bigger picture and present what IMHO is important for Commons:

1) Excellent out of the box UX

One of the points of the distributions is to speed up development / site building proccess - with out of the box (via themes and extra modules) excellent UX experience you can start using site right away with no trouble at all. Example issue: As a Commons user, it seems unnecessary to confirm when I want to join a group.
Commons 6.x-2.5 made great (and big) step to address UX issues and that is really great! ;)

2) Flexibility to build upon Commons distribution

AFAIK this is really crucial to all Drupal distributions - to be able to make changes without losing upgrade path.
This task would be probably easier with having:

3) MVP

Content types:

  • Discussion (feature request: merge it with Facebook-style Statuses to avoid confusion what to use for communication)
  • Wiki
  • Event management (feature request: add any kind of sing-up functionality
  • Q&A
  • Poll

Features:

  • OG
  • Subscription options and mail messaging of notifications
  • RealName option by default
  • Better login / registration mechanism:
  1. Locally (e.g. via Realname registration and LoginToboggan module combo - to avoid using usernames at all when using also RealName module)
  2. Remotely (e.g. via FB Connect, Twitter or Google account)
  • Profiles (via Profile 2 module maybe?)
  • User points
  • There are probably some more stuff, but it's too late and I can't think any of.

    The point is that I think that it would be great to be able to use Commons for building community sites in the same way as Acquia is using Drupal (core and contrib) to build Commons.

    My use case is web site for CSA groups in my country. Idea is to make Apps / features that can transform Commons in CSA specific site in no time..

    I suppose I could open some issues / feature request @ Commons d.o issue queue based on above text, but I would definitively appreciate some feedback from your side..

    Cheers!

    Better non-English support

    mariomaric's picture

    Aha, one more important thing / feature that I forgot - better support for non-English / multilingual sites!

    unleash's picture

    good evening hello dear mariomaric -

    dear buddy - wholeheartedly agreed - you point out what s wanted and needed! especially the OG-things are important.

    besides OG I agree with almost all your points!

    I look forward to the next steps of the sustainable development of Commons and D7

    greetings unleash

    backward compatibility

    John_B's picture

    One of the key reasons I discourage newcomers from using my favourite CMS is that a Drupal site with a lot of contrib modules and with certain themes can create huge problems when it is EOL and a major upgrade is required. People may build fairly sophisticated sites before they discover this aspect of Drupal work. I was one of them: my first Drupal site was an online store, with Ubercart, Views, and a Fusion theme dependent on skinr. The difficulty of the upgrade process comes as a shock. It involved a lot of debugging requiring direct editing of the database.

    Therefore, the target market for MVP will only be well served if it is panned in such a way that it is likely to have reasonably reliable 'one click' upgrade path. Otherwise users are being led into a sort of trap, where they can build a complex Drupal site with a relatively low skill level, but cannot upgrade it when it ceases to have security fixes.

    Thefore, when considering including OG for example, the question has to be asked, 'will it have an upgrade path to a reasonably stable release when Core does?'

    The other question is whether the installation should be limited to a size which has a good chance of working reliably on shared hosting, since many people starting with Drupal use shared hosting, and this does cause problems sometimes. OG is quite resource-hungry. Alternatively, MVP could could be released with a clear warning that is not suitable for many shared hosting plans.

    unleash's picture

    good evening dear John_B

    thx for the answer - and your interesting ideas: well vialid points - good thoughts - thx for your great contribution!

    I am very very new to Drupal. But i think that OG is a must have for my use-case. I need id. All your other ideas, suggestions and concearns i agree.

    Above all - i love this fruitful discussion here. It shows how many friends are there
    Drupal Commons has to friends all over the planet. And i am pretty sure that lots of them look forward to the next step in
    sustainable development!

    greetings unleash

    Survey to help shape D7 version of Commons

    lisarex's picture

    Great feedback so far! It's good that we're hearing the developer's perspective on Commons. We'd love your participation in our survey at http://commons.acquia.com/content/help-shape-commons-drupal-7-survey.

    Lisa Rex
    Commons User Experience Design Team

    ==================================
    http://about.me/lisarex

    Contributed modules

    ebieymjunior's picture

    I personally would like to have some more contributed modules, although I understand that it'd be difficult to have on shared hosting, but as John_B wrote, a solution might be to warn people about that (his point about having Commons update easier is also worth noting).

    1. SEO and RDF

    I think Commons could use some good SEO and RDF modules.

    Drupal SEO Tools does a good work on SEO and analyzing content on Drupal.

    Schema.org is a nice way to enhance RDF with modules that extend it like Microdata and RDF Extensions (along with SPARQL). OpenCalais might also be considered.

    2. Features

    Some features that I'd like to have are written down by mariomaric.

    Profile 2 with Organic groups profiles for OG, Profile2 Registration Path for profile registrations and Profile Privacy for private profile settings.

    • The above stated solution by mariomaric for logging in and registering locally with RealName, Realname registration and LoginToboggan, and additionally Ajax Login/Register for a better user interaction.
    Remotely could also be possible with Google Authenticator login, Twitter and Drupal for Facebook.

    • Other Facebook integrations like Facebook Events and Facebook Photo Sync could be nice.

    • Mailing and messaging could be enhanced with Mail Comment, Privatemsg (along with Private Message Growl) and possibly User Notifications which is still in the development phase for Drupal 6 and of which the maintainer is welcoming patches.

    • Other features such as Advanced Forum (and Advanced Forum More Styles), Blog API and Radioactivity would be embraced well. The BeautyTips would also be a helpful module for users.

    Open Atrium has some nice collaboration features. Maybe some of them could be used in Commons.

    • I'm not really a big fan of the User Points module but I'm sure a lot of people use it.

    3. Search & Media

    Last but not least it'd be nice to have more search capabilities with Custom Search that enables a lot of integrations like Apache Solr. Apache Solr Media would do well for websites which work with media. It works with the Media module.

    Other modules that extent the Media module are FileField Sources, which is helpful to reuse already uploaded files instead of uploading them again, Media Mover to store media elsewhere and Remote stream wrapper, which uses external files without saving them to your local files directory. There are much more modules which extend the Media module, and that is why it's the best in handling media for the moment.

    These are just some suggestions that I'd like to have on a Commons profile. The main features I'd be looking for would be to be able to collaborate on projects like music and photography and to be able to showcase all those projects so that the community could be able to see and give feedback, talk about them and so on.

    Not MVP

    ebieymjunior's picture

    Note that this is not for the MVP but for a full release.

    Mail Comment

    dugnap's picture

    I realize this is not an MVP request, but not having the ability to email into a discussion was the reason we are looking into other solutions. I would love to see this feature in Commons.

    Already in 6.x-2.4

    mariomaric's picture

    Are you talking about this maybe: http://drupal.org/node/1348912 ?

    :)

    Thanks!!

    dugnap's picture

    Thanks for letting me know. It has been several months since I tested Commons.

    Andrea C

    Andrea C's picture

    For stuff concerning themes see http://groups.drupal.org/node/210838#comment-694588

    I write here what already written in Lisa Rex survey.

    Question: What are the biggest usability problems you see/anticipate in Commons? :

    • Security: We need to be sure that only authorized people read content and documents. But we must use old IE (7 and 8). So we need to use the optimize CSS to solve the 31 css limit, but to use css optimization you cannot set file system to private. To face this problem can be usefull to inteface an external DMS like Alfresco.
    • For security I use Solr search without Acquia Search, but now I'm not able to get the facet search
    • As the content grows, some of this content need to be organized to be quickly found, like a tree but where each document can be a leaf of different branches of the tree.
    • We need Single sign-on and at least LDAP integration (we use the contrib module for this)
    • It's a must: username must be hidden and profile and posts must show an alias (like using the Realname module)

    Question: Any other ideas or suggestions for the team?: (this is not MVP but for a full realese)

    • Will be usefull a simple project management feature where to assign task and monitor progress
    • Will be nice have a chat
    • Will be nice to have video
    • Some colleagues ask for a popup that open automatically when subscribed content is submited

    a great pleasure

    unleash's picture

    hello ebieymjunior, hello Andrea C hello all!!

    It's great to see this out. Congratulations to all the people who made this happen!

    Well - it is a great pleasure to see commons on D7 comming to the community. Fantastic job to everyone that contributed to the release. You guys are amazing. This is going to be a great boon to the Commons-community, and it really goes to show how far we've come. I can't wait to see what else 2012 holds for Commons on Drupal.

    You guys are what makes working in this community great. Thank you.

    greetings unleash

    What about Commons

    pinkonomy's picture

    What about Commons internationalization?Could this be included in the Commons core(D7)?

    og-features - important

    unleash's picture

    overwehlming feedback so far. i see that this is

    on a sidenote: Drupal is a synonym for a globalwork: Bridging Distance, Culture & Time! The spirit of the drupal-community is one of the most impressive things i ever experienced! The Drupal group is stronger than ever before: .
    It is very impressive to see how many developers and users come here and communicate & share your questions, knowledge on every Drupal-commons-matter:

    as MarioMaric stated above - the OG-Features are pretty important. I regard them also as very important - at least to my use-case.

    see what Mario has written:
    OG
    Subscription options and mail messaging of notifications
    RealName option by default
    Better login / registration mechanism:
    Locally (e.g. via Realname registration and LoginToboggan module combo - to avoid using usernames at all when using also RealName module)
    Remotely (e.g. via FB Connect, Twitter or Google account)
    Profiles (via Profile 2 module maybe?)
    User points

    making Drupal installation run smoothly

    John_B's picture

    As someone who has written many posts helping out beginners, the top things which help could people get going with Drupal are:
    1. A script which can auto-set file permissions and ownership for a Drupal run as document owner (or as Apache owner if php is being run as Apache module) (permissions on all files and folders including document root folder); and permissions to write files/; or output clear instructions if the script has insufficient permissions to run. Also creation of a writable temporary directory, preferably above doc root, but other than server /tmp (which if mounted as no-exec may be unable to unzip modules being installed, regardless of permissions). (I would actually like to disable private file system for new users...).
    2. A script which checks users have copied a working Drupal .htaccess to their doc root. This often gets missed in filezilla uploads or using cp or mv commands etc.
    3. A WYSIWYG with the js code included (many users clean ignore the message sending them to download the code from an external site).
    4. Some kind of prompt to get people to clear caches when moving a Drupal site.
    This would cure 80% (OK a that's a guess) of installation problems which can waste hours for beginners.
    5. Nice to have, a ready made settings.php and a script setting permissions on it.

    It would be also a good idea

    pinkonomy's picture

    It would be also a good idea if D7 Commons ,as it is a community platform,to include on its core the semantic FOAF vocabulary or People from the Schema.org modules.This would do D7 Commons a first class community platform.
    Thanks

    great idea

    unleash's picture

    hello dear pinkonomy

    this is an outstanding great idea! You deserve a monster congrats for bringing up this idea. I think this is pretty important.

    many many greetings
    unleash

    +1

    isellakuria's picture

    I subscribe to this feature. It would great if Commons could take advantage of Drupal 7's semantic capabilities.

    Any estimated release date

    unleash's picture

    Any estimated release date for Commons running on Drupal 7!?
    Look forward to hear from you

    greetings
    unleash

    btw: Drupal gains new friends each day. In the last months many have joined us from all over the world who share our interests and ideas.
    The Drupal landscape is constantly changing and has a strong community of both users, supporters and contributors. The future is very bright

    Good question. I'm also

    Soul88's picture

    Good question. I'm also interested very much about the possible estimations.

    MVP is not the right approach

    escapesequence's picture

    Get a D7 version ASAP. MVP doesn't matter. 7.x-1.x should be eventually consistent with D6 to allow for D6 upgrades. Most contrib modules are already there. It seems like a two-week effort from multiple people would get you to alpha1 (beta = D6 functionality is replicated). Then start on a dual-track (1.x and 2.x). Ideally, you'd have a 1.x-beta and 2.x-alpha by June and a upgrade path (6.x-1x --> 7.x-1.x --> 7.x-2.x) by the end of the year.

    Note: Many module developers have done such a phased upgrade; closely replicating functionality in 1.x and using D7 functionality for new functionality in a 2.x version. An example is Amitaibu's Organic Groups.

    The 7.x-1.x branch doesn't even need to get "polished" to the point of a release as it would essentially serve as 1) a means of quickly getting new sites on D7, and 2) a stepping stone from 6.x-1.x to 7.x-2.x (by the end of the year seems reasonable).

    I agree, sooner the better

    js's picture

    MVP is only one point of view.

    Another is for development work extending Commons with additional Drupal functionality. Custom work in D6 and them moving it to D7 a few months later is silly. Limiting dev work with D6 modules and not embracing D7 modules is equally silly.

    ANY crippled working version of Commons in D7 is a much better place to work from. Much of the customizations will be, in my case, around modules that Commons elect to support. Examples could be activity (status), notifications, and translations.

    Or Commerce. Why would someone who could use the Commerce features customize Ubercart these days?

    Also, getting something out now would get Commons into the hands of developers who can contribute back now.

    Commons in D7 is late, because there are so many advances in Drupal 7.

    MVP not my priority...need *something*

    crimsondryad's picture

    I agree. BTW, was there a code sprint at Drupalcon? We were there w 2 devs ready to work but there wasn't an official sprint. We ended up working on the ladder instead.

    I've needed this since last summer and if we get an alpha in D7 I can commit my folks to contrib patches. But my company isn't going to devote scarce resources to an MVP that might drop by June and we aren't going to cowboy multiple module upgrades. Give us something real to work with and we will help.

    We're planning a new build, so for me an upgrade path is moot. End of year for an upgrade path seems reasonable as at least those sites are functioning.

    as js mentioned

    unleash's picture

    hello dear buddies, hello dear friends

    i am brandnew to Drupal and to commons too.

    but i can second the statements - i think that we should focus on d7 now ... js says:

    ANY crippled working version of Commons in D7 is a much better place to work from. Much of the customizations will be, in my case, around modules that Commons elect to support. Examples could be activity (status), notifications, and translations.

    http://www.lullabot.com/articles/organic-groups-drupal-7

    Organic Groups (OG) for Drupal 6 is a powerful and widely used module for creating websites that enable group collaboration or to create 'mini sites' within a bigger Drupal site. The Drupal 7 version of Organic Groups is a total rewrite, taking advantage of many new Drupal 7 features, in particular the new APIs for entities and fields.

    http://www.lullabot.com/articles/organic-groups-drupal-7

    One of the big differences between the Drupal 6 and Drupal 7 versions is an expansion of the concept of what a 'group' is. In D6, a group is a node, and other nodes can be assigned to it as the content of the group. In D7, any type of entity can be a group and any type of entity can belong to a group.

    and as js mentioned: ANY crippled working version of Commons in D7 is a much better place to work from.

    The sooner the better!!!

    what do you say!? I look forward to a fruitful discussion

    above all - keep up the great project it rocks