Last week we were at our historical minimum of 36 open issues only! We did fix some and did open some more since then. Current count is 49 open issues, 70% of which are issues discovered via our BDD test runs.Personal blog tags: week notes
Hassan Bawab is the Founder and CEO of Magic Logix, an interactive digital marketing agency in Dallas, TX. Magic Logix combines dynamic website development, professional website design, Social Media, SEO and integrated online marketing to drive new leads with high conversion.Personal blog tags: Drupal 8
32 days to go until DrupalCon Prague. And... we need 25 more mentors. Can you mentor? Maybe. If you have experience working in the issue queue, understand how d.o works, and can support people as you find answers to their questions together, then you can mentor. Even our experienced mentors do not know all the answers, but we know how to start looking for the answers. Sign up to mentor!
Want an idea of what mentoring is like before you sign up? Checkout:
- 2 minute DrupalCon Sprint Day video
- Modules Unraveled Audio Podcast about Sprints at DrupalCon
- Mentoring Mentors video'd conversation with @ZenDoodles at the Nerdery
- recorded Running Coaches Wanted mentoring session from DrupalCon Portland by @add1sun, @xjmdrupal, @ZenDoodles and me @YesCT
- one of the irc mentoring sessions, reminders tweeted by @drupalmentoring
- blog Contribution Sprints: Something for everyone
See the list of people currently signed up to mentor, including notes on who is coming on scholarship, grant and free mentor tickets. We have 2 more free mentor ticket codes for those willing to put some extra work.
If you are not mentoring, be sure to stay for the Friday Sprint either to participate with a mentor, or sprint in the general sprint. And... remember the extended sprints when you are planning your travel.
The second alpha release of CiviCRM 4.4 is now available for downloading AND you can try it out on the 4.4 sandbox site!We Need You to Try it Out!
Excited to try the new features in this release? Please do! Great software requires great testers, and you can help. You don't need to be super technical to participate in this way, but your participation will make a huge difference.
- Download it and either do a fresh install or (better yet) upgrade a test copy of your existing database. Note that this is alpha software and should not be used on production servers.
- Try to break it! Do all the things you normally do with CiviCRM, try out as much as you can think of.
- If anything doesn't seem right, please let us know on the Release Testing Forum.
- Faster searching - a real timesaver when working with searches and smart groups, especially with large databases.
- Soft credits - improve soft credit tracking and include soft credit data in key contribution reports
- Flexible event name badges - design and print cool name badges for event participants including logos, custom data, QR and bar codes
- Visual selection of "credit card type" on contribute/event forms - improves the user experience when giving to your organization
- ShortCode Support for Petitions - a great new feature for CiviPetition users on Wordpress
- Better campaign tracking - campaign column and filters added to membership, participant and addtional contribution reports
Not all the good stuff in CiviCRM comes in the main package. There are also many extensions you can install. Here are some exciting new and updated extensions for CiviCRM 4.4. (Note that some of these extensions are not yet published on the extensions directory but will be available as part of the stable 4.4 release.)
- CiviHR - A fully-featured Human-Resources management application for charities and non-profits.
- CiviVolunteer - Recruit and manage a variety of volunteers for your events.
- Webform Payments - The popular Webform Integration module now integrates with CiviContribute, CiviMember, and paid CiviEvents.
- SEPA Direct Debit Payments - Allows CiviCRM users to setup an SDD compliant payment process for recurring and one-off direct debits.
- CiviBooking - Now organisations can manage a group of resources (i.e. rooms, equipment, etc.) offering these to constituents for a fee.
CiviCRM is free, open source software made possible through contributions from people like you. If your organization benefits from using CiviCRM and from the great new features in this release, please consider making a recurring contribution to support the project.Compatibility
CiviCRM 4.4 is compatible with:
- Drupal 7
- Drupal 6 (community supported)
- Joomla 2.5 & 3.0
- Wordpress 3.4 and higher
If you are installing CiviCRM 4.4 from scratch, please use the corresponding automated installer instructions:
If your site is highly customized with special code or theming for CiviCRM you will want to upgrade a test copy first and test your customizations. For everyone else, follow these simple steps to get yourself up and running with 4.4.
Community support and engagement is the force that sustains and drives CiviCRM forward. This release would not have been possible without the incredible contributions of these people and organizations:
AGH Strategies - Andrew Hunt; Backoffice Thinking; Chris Burgess; Circle Interactive - Andrew Walker, Dave Moreton; CiviDesk - Nicolas Ganivet; CiviHosting - Hershel Robinson; Community Builders; Compucorp - Jamie Novick, Erawat Chamanont; Confluence - Frank Gomez, Michael Daryabeygi; Dave D; CiviCoop - Erik Hommel; Drupal Association - Neil Drumm; Electronic Frontier Foundation - Micah Lee, Kellie Brownell; Emphanos - Allen Shaw; Fuzion NZ - Eileen McNaughton, Peter Davis, Torrance Hodgeson; Giant Rabbit- Anna Heath; Jim Meehan; JMA Consulting - Joe Murray; Keith Morgan; Ken West; Korlon - Stuart Gaston; Koumbit - Samuel Vanhove; Lighthouse Consulting and Design - Brian Shaughnessy; Mathieu Lutfy; National Democratic Institute - Chris Doten; New York State Senate - Ken Zalewski; NfP Services (MTL Software Group) - Jag Kandasamy, Rajesh Sundararajan; Niro Solutions; Noah Miller; Orgis - Hans Idink; Palante Technology Cooperative - Jon Goldberg; Progressive Tech Project - Alice Aguilar, Jamie McClelland; Paul Delbar; Registered Nurses Association of Ontario; San Francisco Baykeeper - Eliet Henderson; Tadpole - Dana Skall; Tallyfox; Tech to the People - Xavier Dutoit; Third Sector Design; Veda Consulting - Parvez Saleh; Web Access - Pradeep Nayak; Wikimedia Foundation - Adam Wight; Zing - Simon West, Andrew Tombs.
Unfortunately the 1.x version of Badbot only supported protecting the user registration form, and was not compatible with the dozens of other, equally vulnerable forms available for anonymous "consumption."
Because of Federico Jaramillo's efforts in the issue queue, last night I was able to release Badbot 1.1, which adds support for any and all forms on a Drupal site (obviously including the much-desired comments form). This is a great example of a community contribution to an existing project, making big headway towards a cleaner, spam-free experience.Tagsdrupal planetcaptchaspamdrupal
Since we discovered Drupal, our content management system of choice, we've never looked back. We've built upon our business, grown our team (19 and counting!), and are involved in some pretty impressive projects including some of Germany's most important publishers. Drupal has taken us across continents, put us in touch with some amazing people who share our enthusiasm for Drupal and open source, and taught us so much. The Drupal community is more than a bunch of nerds building a big piece of software: it's a source of help and assistance, inspiration, ideas, friendship and fun.
So as a business, it's safe to say that Drupal is one of the major factors in comm-press' success. One way that we can put something back is to sponsor events where the Drupal community can meet up, socialise, and work together. In the past, we've sponsored several events, including Drupal Con London, Drupal Con Munich, and Drupal Dev Days in Dublin. We also take a lead in organising and financing Drupal Camping, and we love to contribute our code too. (Not least because it helps us improve our code thanks to Drupal's stringent quality control.)
This year, we are Gold Sponsors of Drupal Con in Prague. This will be a very important event because the release date for Drupal 8 is coming ever nearer and there's lots of work to be done. Five members of our team will be making the journey to Prague and we will be taking part in the sprints as well as manning a stand and reporting on our experiences. We are already hatching plans for some fun with the video camera too!
We can't wait until Prague and are very pleased to do what we can to make sure that Drupal events large and small get the support they deserve.
Shockingly enough, I disagree.
At the most basic level, the output of different Special Interest Groups is not all equal. We've had issues over the past few releases where various spins have shipped in a broken state, because the SIG responsible for producing them doesn't have the resources to actually test them. We're potentially going to end up shipping F20 with old Bluetooth code because the smaller desktops aren't able to port to the new API in time. Promoting these equally implies that they're equal, and doing so when we know it isn't the case is a disservice to our users.
But it's not just about our users. Before I joined the Fedora project, I'd worked on both Debian and Ubuntu. Debian is broadly similar to the current state of Fedora - no strong idea about what is actually being produced, and a desire among many developers to cater to every user's requirements. Ubuntu's pretty much the direct opposite, with a strongly defined goal and a willingness to sacrifice some use cases in order to achieve that goal.
This leads to an interestingly different social dynamic. Ubuntu contributors know what they're working on. If a change furthers the well-defined aim of the project, that change happens. Moving from Ubuntu to Fedora was a shock to me - there were several rough edges in Fedora that simply couldn't be smoothed out because fixing them for one use case would compromise another use case, and nobody could decide which was more important. It's basically unthinkable that such a situation could arise in Ubuntu, not just because there was a self appointed dictator but because there was an explicit goal and people could prioritise based on that.
Bluntly, if you have a well-defined goal, people are more likely to either work towards that goal or go and do something else. If you don't, people will just do whatever they want. The risk of defining that goal is that you'll lose some of your existing contributors, but the benefit is that the existing contributors will be more likely to work together rather than heading off in several different directions.
But perhaps more importantly, having a goal can attract people. Ubuntu's Bug #1 was a solid statement of intent. Being freer than Microsoft wasn't enough. Ubuntu had to be better than Microsoft products on every axis, and joining Ubuntu meant that you were going to be part of that. Now it's been closed and Ubuntu's wandered off into convergence land, and signing up to spend your free time on producing something to help someone sell phones is much less compelling than doing it to produce a product you can give to your friends.
Fedora should be the obvious replacement, but it's not because it's unclear to a casual observer what Fedora actually is. The website proudly leads with a description of Fedora as a fast, stable and powerful operating system, but it's obvious that many of the community don't think of Fedora that way - instead it's a playground to produce a range of niche derivatives, with little consideration as to whether contributing to Fedora in that way benefits the project as a whole. Codifying that would actively harm our ability to produce a compelling product, and in turn reduce our ability to attract new contributors even further.
Which is why I think the current proposal to produce three first-class products is exciting. Offering several different desktops on the download page is confusing. Offering distinct desktop, server and cloud products isn't. It makes it clear to our users what we care about, and in turn that makes it easier for users to be excited about contributing to Fedora. Let's not make the mistake of trying to be all things to all people.
 Although clearly in this case the absence of a stable ABI in BlueZ despite it having had a dbus interface for the best part of a decade is a pretty fundamental problem.
 See the multi-year argument over default firewall rules and the resulting lack of working SMB browsing or mDNS resolving
 To be fair, one of the reasons I was happy to jump ship was because of the increasingly autocratic way Ubuntu was being run. By the end of my involvement, significant technical decisions were being made in internal IRC channels - despite being on the project's Technical Board, I had no idea how or why some significant technical changes were being made. I don't think this is a fundamental outcome of having a well-defined goal, though. A goal defined by the community (or their elected representatives) should function just as well.
In this episode, Addi is joined by Bill Liao, co-founder of CoderDojo, and Drupalers and CoderDojo volunteers Heather James (heather) and Mike King (emkay). At a CoderDojo, young people learn how to code, develop websites, apps, programs, games and more. Dojos are set up, run by, and taught at by volunteers.Teaching kids about tech for free
I’ve just tried to paste a link to video material from DebConf13 on my Facebook wall and I got this warning:
Could someone tell me what privacy settings are set on materials from DebConf?
Or maybe the more applicable question is what is the license of these materials?