Project

• What is Drupalfund and what’s the idea behind it?

  • Drupalfund.us is a crowdfunding platform for projects related to Drupal. Think of it as a Kickstarter for Drupal.

  • The problem which Drupalfund is trying to solve is that as we all know - Drupal development is backed by volunteers (individuals and companies) that donate their money or time to contribute to Drupal. However, most of the development (even core development) happens against the developer's personal free time or his paid hours. Because of this many issues, fixes and changes are pushed back and fixed when the developer can steal away some of his time. To be a little more specific I looked at top 25 most installed modules and their issue queues and got some interesting numbers:

  • These most installed or most popular modules have in average over 400 issues. It takes in average 279 days to fix & release the module. I know that the critical or security issues get fixed much faster but it still is a long time.

  • We started to look for a solution to this problem and so we've asked ourselves a question: What everything could be achieved, if we would provide an easy way how how the Drupal community could contribute financially to the Drupal development? Our community is huge. There are nearly 1M registered users on Drupal.org. If only 1% of us would donate 1% of our salary each month, we would be able to rise over $5M/year And that is enough to hire over 65 developers to work on Drupal development full time.

  • With these numbers in your mind - think about how Drupal 8 development, porting modules to Drupal 8 could be accelerated. Think about that missing part of Drupal Commerce or Open Atrium, new features to Drupal.org. Or think about the plans you could have to write a book on Drupal development, or release a training materials. Think about new products and services that could be born out of this. How much could we all as individuals and companies benefit if we together supported the development and not only depend on volunteering time.

  • So we built Drupalfund as our answer to this problem.

• How does Drupalfund work

  • It works as all of the standard crowdfunding websites work:
    1. Submit a project idea
    2. set some rewards
    3. generate buzz around it
    4. get some valuable feedback from the community
    5. raise funds
    6. and deliver your project.

• What kind of projects can it be used to raise money for?

  • Drupalfund can be used to support both coding and non-coding projects
    • Coding projects can be submitted to support existing and new modules, Drupal core initives, Drupal.org infrastructure, or installation profiles or products.
    • A good example of non-coding projects can be a book or curriculum, documentation, art & marketing projects or organising a sprint.

• What plans do you have for Drupalfund

  • We would love to integrate or connect Drupalfund with Drupal.org
    • share user accounts
    • provide badges for activity that could be displayed on D.org account page
    • create an easy way how to turn an project issue into Drupalfund project
    • provide widgets to embed on the module page
    • We would love to become the official platform for Drupal fundraising

• Who is behind Drupalfund

  • Our team consists of two groups:
    • Mogdesign developed and is operating & managing the platform itself
    • we have a team of community advisors. These are very valuable and respected members of our Drupal community and we discuss very closely the future of Drupalfund with them. At this time they are Robert Douglass, Jeffrey McGuire (or Jam) and Kristof Van Tomme.

• Why should anyone use Drupalfund?

  • I have 3 core answers to this
    • We believe that crowdfunding can be a new way to achieve greatness in Drupal development? Drupal has started in
    • Sustanability - as Drupal itself and our community grows and matures, we need to find different ways how we can multiply the amount of people that actively contributing to it. There are many people who would love to contribute to Drupal, but they are not coders, they would love, but simply don't know how they could help. Drupalfund aims to lower this barrier and provide an easy way for this to happen.
    • Giving back - we all got so much by using Drupal on our sites or selling it to our clients and I personally believe that it is time to give back from what we have gained. It does not matter if you are a large company or an individual, Drupalfund wants to help anyone to give back to Drupal.

• Why not just use Kickstarter?

• What should we do if we want to start?

  • If you have an interesting idea go and submit a project. Or if you know about anyone who would benefit from using Drupalfund, point him our way. Go to Drupalfund.us, get in touch with us, we would love to help you setting up the project.

  • First 3 submitted projects will get a $100 credit each:)

  • Also if you come to Drupalcon Prague, we will have a BoF session on Wednesday @1pm in the Club B · Windows Azure room where we will be to discuss Drupalfund, answer any questions or help with setting up projects. Looking forward to meet you.

Omega 4.x

• Omega 3 vs. Omega 4
  • No Layout Builder UI
  • No predefined breakpoints
  • No dependency on Omega Tools or need for Delta.
• Sass, Compass & SMACSS
• How does this work with Panels?
• Will this be the route going forward for D8?
• BEM class naming Syntax
• Core CSS Cleanup
  • Easier to override
  • Split up stylesheets
• Omega Layouts
• Development tools (Guard / Grunt, LiveReload, etc.)
• Manage assets (exclude CSS/JS, move JS to footer)
• Manage browser compatibility (Chrome Frame, conditional classes, etc.)
• Split up preprocess, process and theme functions
• Drush Integration
  • drush help --filter="omega"
• Ohm

Use Cases

• What prompted the major overhaul?
  • This reminds me of the conversation going on around D8 right now.
  • How long can people keep using 3.x?
• What does this mean for site-builders?
• What does it mean for themers?
• How does Omega 4.x compare to other base themes like AdaptiveTheme and Aurora?
• When should we expect a stable release?

Questions from Twitter

• Dirk Bazuin (@dbazuin): #MUP076 will there be templates made with singularity.gs?
• Kendall Totten (@KendallTotten): Is there a timeline for when we can expect all the Panels integration to be wrapped up in Omega 4.x? It sounds fantastic :) #MUP076

Sprints

• What are sprints?
• When are they?
• How did they get started?
• Who can participate in the sprints?

Track

• What is the theme of the track?

I tried to make the theme consistent with the overall DrupalCon Prague theme of “One to many”.
Leveraging new paradigms in Drupal 8: improving your projects and workflows
Drupal as an application platform
Integrating Drupal’s API with other systems and libraries

So we really want to present Drupal as a unifying platform, that can consolidate many technologies.

Part of that is what Alex is going to talk about in his featured session - removing some of the Drupalisms that we have all gotten used to in favour of incorporating best-of-breed open source components from outside the community. I think Symfony’s components are the most obvious example there, but there are a lot of other components too (like Guzzle, Doctrine).

Another element is the general move to OO, PSR-0, and the adoption of modern design patterns which bring us up to date with other major PHP projects. The plumbing is there now to integrate with other frameworks - and we’re doing that.

I’ve kind of been talking about low level code integrations, But theres also a lot that can and has been achieved with Drupal as it is today, by incorporating integrations with outside systems via web services, or supplying services to other systems. So I would like some of our presentations to cover how Drupal integrates, and maybe in ways you hopefully haven’t thought of.

Session

• What is the name of your session, and what is it going to be about?