A group for talking about Drupal distribution profile development groups.
Created as an informal response to Dries' blog entry about potential pitfalls in creating Drupal distribution installation profiles, the intent of this group is to provide a forum for discussing the topic on a very broad scope in the interest of promoting collaboration, cooperation and communication among developers.
This group is a good place to: announce new projects and the goals behind them, identify common goals and best practices for distribution profiles as a whole, explore options for collaboration and consolidation where possible, and collaborate with developers working on unrelated installation profiles in order to present their sum as a consistent experience to the end user.
I was somewhat overwhelmed at the amount of people who are trying to use COD, and found out a bit of that first hand this weekend. I'm happy to say beta is coming along very nicely, and we've made some great progress in the past few months...
Thanks to the NYC Camp team for input and showing me how they've used COD for their site, I'm looking forward to integrating their improvements upstream, especially the dashboards. MongoDB was there, Jason working on Ticket Module, and Emilie has written a new base theme for COD based on Omega4.Read more
Is it possible to use two distribution profile in one Drupal installation website. For Example - Suppose I want to use Commerce Kickstart Distribution (https://drupal.org/project/commerce_kickstart) to make an e-commerce site but also I want to use Spark Distribution (https://drupal.org/project/spark) in same website because it has Responsive admin control panel. So is this possible?
If not, is there any alternative way?
We're getting to the point in the Drupal 8 cycle where the UI's are starting to solidify and we have fairly static markup to write interface tours against.
So to facilitate this, we're going to have a weekly scrum to coordinate pain points, progress and participants.
If you're interested in helping write tours for the Drupal 8 UI or identify and resolve any remaining API issues, please come along to this short meeting (Google hangout).Read more
If you're coming to BADcamp, come help make COD for Drupal 7.x better!
We'll be tackling a few issues in the queue, and depending on how much we get done, releasing a new Alpha.
Discuss below which things you want to work on, and maybe with some pre-organization we can make this a really effective sprint. I'll be at BADcamp sprinting on mainly commons, but want to help people get setup if they're interested in improving COD.
1) Moving scheduling from rooms to event CT
2) Getting default (or current events) setup
There seems to be some interest and use case for Drupal-based digital signage. bneil, AndrewGearhart, and btopro had a good conversation in #drupal-edu about some ideas and thought we needed to start collecting our ideas.
Let's use this wiki as a place to start organizing ourselves around what our requirements are and what general functionality we can share between our institutions.
Hopefully we'll end up with a nice list of requirements that we can work together to build a solid base for Drupal digital signage.
Join people from all over the world June 1 and 2, 2013 for a national Hack for Change event.
Click Here to signup for regular updates! http://bit.ly/help4ok_challenge
In conjunction with RHOK Boston - http://hackforchange.org/rhok-boston
and the National Day of Civic Hacking (NDoCH) http://hackforchange.org/, a team of passionate team members will come together and Hack for Good! Join us!
History and Goals
Connect people who need help with people who can give help.
Next week Ezra, Joseph, and Jakob will all be at Drupalcon to further the goals of Commons and COD, two distributions supported by Acquia.
My hopes for COD is to get another update since the Alpha2 release we did at Sandcamp. Its unfortunate that it seems updates only occur after camp, but on the otherhand it just shows how much can get done when we have the community working in the same room as each other!
These are my basic goals:
* Scale the gaps between COD6 and COD7, make a MOSCOW chart to prioritize what needs to be done.
Join us for some distribution sprinting and birds of a feather sessions at DrupalCon Portland!
Maintainers for Commons & COD will be hosting the following BoFs on Tuesday, May 21:
- COD: 2-3pm
- Commons: 3:15-4:15pm.
Locations TBD and will be announced as a comment on this thread.
We'll have maintainers of Commons and COD, and hopefully other distributions as well!Read more
Panopoly provides, by default, an 'editor' role which I find myself using a lot. But using it means I have to guide the site administrator to create a user with the role editor. I thought it could better be handled by providing a form to create that user, next to the form that creates user 1.
And since user 1 usually sees a lot more than the site builder will ever need, I thought I could just finish the installation and log the user as editor.
How do I do that? Also, is it a good idea?
what would you recommend using to provide demo content for a fairly simple distribution. I would liek to include files (images).
I have seen:
Deprecated in favor of UUID, it does have the machine name, that you are throwing under nose to your users even if they don't need it.
Demo content might not be the best use case, seem to be made for deployment not import.
Linuxfest Northwest is coming back for 2013 -- the last weekend in April. After talking to some core maintainers, we thought it'd be a fun idea to do a sprint based around linuxfest northwest.
Sprinters are certainly welcome (and encouraged!) to submit a talk for LFNW, but the main goal is to get some sprinting done on Core in preparation for Drupalcon in May.
I'll also be leading a distros sprint, if people are interested. My main focus is on COD and Commons -- but if there are other distros that would like to host here, feel free.
Why Linuxfest Northwest?Read more
What are your thoughts about the strong points and weaknesses of the distribution? What opportunities or threats are out there? What are the most promising strategies for strengthening the distribution? Please add your ideas, either as comments or directly in the wiki!Read more
What kind of standards is needed to make features as compatible as possible:
- module based
- naming conventions
The usual suspects:
- Text Format
- Content Types
Roles Conflicts comparison :Harmonize app/distro/feature role names
Distro Based Conflict Comparison:Commons 7.x
Related Discussion: Should distro based features be compatible with other distro features?
Standards in features creation process have not been implemented yet.
This post will give you an overview of stoppers within features, ergo not interoperable.
Roles Conflicts comparison :
Harmonize app/distro/feature component names (roles, vocabularies, and so on)
Should distro based features be compatible with other distro features?
Which feature based conflicts could be solved by standards or naming conventions?
I'm looking for web-based software for a community college to use (internally) to schedule it's courses. Even though it's small it needs to support multiple Deans, 100-150 teachers (some full time, some part time, some not currently teaching but still interested in teaching), and several hundred courses each quarter.
I was wondering if there are modules / distributions set up to do this?
After searching I haven't found anything that's quite targeted at this (the "Conference Organizing Distribution" seems close but not quite right).
If you're a new to contributing to distributions, fear not! This is an opportunity to receive some in-person guidance from distribution maintainers and dig in on development!
One focus of the sprint will be on making progress towards updating Drupal Commons and the Conference Organizing Distribution to Drupal 7.
If you're planning to attend, please sign up to this event and leave a comment saying what you plan to work on!
If you'd like to sprint remotely, sign up here and join us on IRC in #drupal-commons and #drupal-cod channels on Freenode.
Sprint Goals/Suggested tasks:Read more
Incompatible component names are a significant barrier to interoperable features. Component types that tend to be shared between multiple features or apps include: roles, taxonomy vocabularies, text formats, and content types.
The Apps compatible module is one initiative to address incompatibilities by providing a set of generic components and methods to share them between apps.Read more