Wine 1.7.36 Released

The Wine development release 1.7.36 is now available.
What’s new in this release:

Some preliminary 64-bit support for Mac OS X.
Support for configuring speakers in Winecfg.
Improved support for M…

GNOME: Outreach Program to Join Conservancy from GNOME; Program Renames to Outreachy

Software Freedom Conservancy and the GNOME Foundation together announce that the Free and Open Source Software Outreach Program is moving from GNOME to Conservancy. As Karen Sandler, Executive Director of Conservancy and co-organizer of the Outreach Program, announced in her keynote at FOSDEM this weekend, the program will be rebranding as part of the transition under the new name “Outreachy”.

Outreachy helps people from groups underrepresented in free and open source software get involved by providing a supportive community for newcomers to contribute to throughout the year, and by offering focused internship opportunities twice a year with many free software organizations. To date, the program has had 214 interns with 35 different free software organizations, including the Linux Kernel, Wikimedia, GNOME, Mozilla, Twisted (a Conservancy member project), and OpenStack. Marina Zhurakhinskaya, Community Engagement Lead at Red Hat and co-organizer of the program said, “It’s amazing that the program we started four years ago with eight GNOME interns has grown to enable hundreds of women become established free software contributors across a broad spectrum of projects. I vividly remember the call in which Karen proposed the idea of inviting other organizations to participate, and I’m excited to continue working closely with her in growing the reach of the program.”

The GNOME Foundation, previous nonprofit home of the program, remains a core partner of Outreachy, providing infrastructure support. “The GNOME board is unified in its enthusiasm for Outreach to join Conservancy,” said Jean-François Fortin Tam, President of the GNOME Foundation. “We’re proud to have launched the program and seen it grow beyond our wildest expectations. We look forward to remaining a partner, supporting and participating in the program in its new home as it continues to grow.”

Over the next few months, Outreachy will complete its transition to Conservancy, the non-profit home of over 30 free and open source software projects. “Outreachy is a natural fit for Conservancy,” said Sandler. “Conservancy is organized to support many free software projects — and to promote software freedom in general. This program has become an essential way for free software projects to improve their communities. I am honored to keep working with Marina, Sarah Sharp and all of the other volunteers who keep Outreachy going.”

The next round of Outreachy internships will have an application deadline on March 24, 2015, and internship dates from May 25 to August 25. Coding, design, documentation and other projects will be available. Applicants will be asked to select a project with one of the participating organizations and collaborate with a mentor listed for that project to make a relevant contribution to the project during the application process. Accepted participants will work remotely, while being guided by their mentor, and will receive a $5,500 stipend.

About Outreachy

Outreachy is the successor of the Outreach Program for Women (OPW). OPW was inspired by Google Summer of Code and by how few women applied for it. The GNOME Foundation first started OPW with one round in 2006, and then resumed the effort in 2010 with rounds organized twice a year. In the May 2012 round, Software Freedom Conservancy joined OPW with one internship with the Twisted project. In the January 2013 round, many other free and open source organizations joined the program. For the May 2015 round, the program was renamed to Outreachy with the goal of expanding to engage people from various underrepresented groups and is transitioning to Conservancy as its organizational home.

This program is a welcoming link that connects talented and passionate newcomers with people working in free and open source software and guides them through their first contribution. Through Outreachy, participants learn how exciting and valuable work on software freedom can be, while helping us to build a more inclusive community. The organizational partners of the program are the GNOME Foundation, Red Hat and Software Freedom Conservancy.

About the GNOME Foundation

GNOME was started in 1997 by two then-university students, Miguel de Icaza and Federico Mena Quintero. Their aim: to produce a free (as in freedom) desktop environment. Since then, GNOME has grown into a hugely successful enterprise. Used by millions of people around the world, it is one of the most popular environments for GNU/Linux and UNIX-type operating systems. GNOME’s software has been utilized in successful, large-scale enterprise and public deployments.

The GNOME community is made up of hundreds of contributors from all over the world, many of whom are volunteers. This community is supported by the GNOME Foundation, an independent non-profit organization that provides financial, organizational and legal assistance. The Foundation is a democratic institution that is directed by its members, who are all active GNOME contributors. GNOME and its Foundation work to promote software freedom through the creation of innovative, accessible, and beautiful user experiences.

About Software Freedom Conservancy

Software Freedom Conservancy is a public charity that promotes, improves, develops and defends Free, Libre and Open Source software projects. Conservancy is home more than thirty software projects — including Git, Inkscape, Samba, Wine, Selenium, the Linux Compliance project, PyPy, and Sugar Labs — each supported by a dedicated community of volunteers, developers and users. Conservancy’s projects include some of the most widely used software systems in the world across many application areas, including educational software deployed in schools around the globe, embedded software systems deployed in most consumer electronic devices, distributed version control developer tools, integrated library services systems, and widely used graphics and art programs. A full list of Conservancy’s member projects is available. Conservancy provides these projects with the necessary infrastructure and not-for-profit support services to enable each project’s communities to focus on what they do best: creating innovative software and advancing computing for the public’s benefit.

Docker-Rocket Conflict is a Good Sign

2014 saw the rise of Docker, and ended with appropriately inflated hype and hysteria around a related container technology: Rocket. Immediately, discussions of uncertainty and doubt, and the familiar fear of forking unfolded. Was it only a matter of time before some developers or organizations splintered off from the Docker community with their own container technology?

Community Spotlight: Paul Johnson (pdjohnson)

It’s time for another community spotlight, and this month, we’re highlighting a community member who has made huge contributions to the success of the Drupal project and of DrupalCon — and not only through code.

Paul Johnson at DrupalCon AmsterdamPaul Johnson (pdjohnson) of Manchester is currently the Drupal Director of CTI Digital, and is the social media lead for most DrupalCons. He also maintains the @Drupal Twitter account. Paul has grown the DrupalCon social media program from a small following on twitter to a set of huge, engaged channels. (Image credit to Frank Crijns on Flickr. Thanks, Frank!)

The Drupal Association sat down with Paul in late January to talk about some of his accomplishments and passions.

DA: How did you get involved with Drupal and volunteering with DrupalCon?

Paul: I got involved in 2005 or 2006 by accident when I found it on Google, though I don’t really remember the exact moment. The company I worked for at the time wanted to move from their own homegrown CMS to something else, so I was looking for other solutions. While doing research I came across Drupal, and before I knew it I’d gone to DrupalCon Barcelona [in 2007].

Not long after that, I got really in to twitter. I was going to DrupalCon London in 2011 and I was fiercely excited about going, and I was expressing it on Twitter. Out of the blue, Isabel Schulz — a nice woman who worked for the Drupal Association at the time — reached out to me. She said, “it sounds like you want to get more involved.” It was like lighting a touch paper. Before I knew it they’d given me the username and password to the DrupalCon account and said “right, get on with it.”

DA: That’s a big responsibility!

Paul: At that time social media wasn’t so prevalent, and I don’t think anyone in the Drupal community realised how it could make a big contribution to the success of the conference— how it could reach a wider audience and get help in executing the conference.

I had no rules, and I made mistakes… I was really quite daunted by the prospect. Looking back, I might have destroyed my reputation with Drupal but thankfully I didn’t! I grew and learned, and then in Portland the social media aspect started to grow more quickly. I began writing formal processes to help myself, but it became apparent that as DrupalCon was growing, the success of the social media was perhaps leading towards other people getting involved.

I suppose I’m an unusual person — I find it difficult to find my place in the Drupal community. There are a lot of people out there who are better developers than I am, and I have this thing in my head that held me back from getting involved. I suppose it was quite a long time before I realised I had something valuable to contribute to the community. There has been this idea that contributing modules or contributing to core is cool, but there are lots of us who fall outside that immediate group of people, and who have– until recently– felt orphaned from contribution.

I’ve always thought about when the Association reached out to me. It was a small bit of recognition, but it felt very empowering. It had a big influence on me, and because of it, I’ve always tried to shout for these people who have enthusiasm, and try to ignite it.

DA: Do you have any good examples of that?

Paul: Sure. DrupalCon Portland took place at the same time as that awful Oklahoma tornado. Before it happened, I had always wanted to use social media to watch out for these kinds of things, because… with a very large audience, we can do things and help people very quickly by using the broadcast mechanism.

When the tornado hit, I saw guys in our coder lounge hacking together a solution to help people on the ground, and I used social media to draw attention to it. It snowballed, and before we knew it, FEMA was involved, and that sends shivers down my spine. I love it when social media translates from something that’s just a conversation on the internet to something with a positive, real-world impact.

DA: Switching tracks a little bit, can you tell us about some of the challenges you’ve faced when working on the DrupalCon social media?

Paul: I’ve grown up with the Drupal Association and the project, but in many respects, the biggest attraction is also one of the biggest challenges. The diversity of the Drupal community is… well, in being responsible for representing the Drupal Association and the project and the community, you have to be quite careful. You’re an ambassador, and you have to have to have the highest level of conduct. You can’t always speak your mind.

Sometimes I’ve gotten upset. It’s a big part of my life, Drupal, and people will say things to the official accounts that are upsetting, and you have to rise above that. And sometimes, people will say things from within or without the community that can be quite cutting, and I suppose that’s one of the hardest things. But, ultimately you can draw many positives from that because it becomes a question of, how do you work towards enhancing the minds of people who think like that.

Another challenge was that, in the early days, nobody knew it was me behind the accounts. It does take a reasonable amount of my time — a half an hour or more a day every day, oftentimes more. I didn’t mind [not being known] necessarily, but it’s really nice to get recognition — and, if anyone writes anything valuable I try to give them credit on social media, to encourage and celebrate people who make the effort, and put them on a pedestal so that it spurs others to do the same.

Along those lines, I so often hear, “I don’t go to local meet-ups,” or “I’m not good enough,” or “people will think I’m not clever enough or that my contribution isn’t sufficient.” I think it’s really important that people appreciate that, no matter where you are in your Drupal journey, you know more than the person who just started. You don’t have to be chx or morten or webchick– they all started at nothing, too, but they started a long time ago.

DA: What’s your favorite thing about the Drupal community?

Paul: When our community gets behind an idea, stuff really happens, and it happens really fast. Whether that’s code, or whether it would be to crowd source some funding for a blind man who lives in Italy and wants to go to DrupalCon Portland, it is just magnificent how fast things can happen if the will of the community is drawn.

And, you know, the Drupal community gives me the opportunity to meet or converse with people I would never imagine having the chance to do so with otherwise. It makes my life so much richer. It’s not about the code, Drupal is providing me with the most unimaginable opportunities. It has allowed me — in my career and my personal life — to take on challenges that would never have been available to me before.

Drupal has allowed me to be brave and to take a few risks, like interviewing Dries at the end of his keynote. I like to hide behind social media.. but then I’m projecting it onto a stage. And another thing about the community is, rarely do you meet someone who’s not nice.

DA: What’s your favorite thing about volunteering?

Paul: The thing that I enjoy the very most of volunteering is making a difference. There have been a few things where, I don’t know, I’ve seen a small smoldering fire and I’ve been able to ignite it into a bigger thing.

I was given the keys to DrupalCon, and then in the last few years I’ve taken ownership of the Drupal twitter account. Previously, it had become an abandoned channel, but under my stewardship it has gone from 30k followers to over 55k. And, you know, there are lots of people in media who are watching Drupal and who might be loosely interested. The Drupal twitter has so much opportunity to reach a wider audience with big achievements. So I love to use social media to show that Drupal is more than just America, more than just Europe — there’s a lot going on in India and in Africa and elsewhere.

I welcome anyone to approach me with news of things that they are doing in their local community that we can celebrate on official channels. I love to help grow something that’s a great idea into something that’s really big, because I think we’ve succeeded in growing the community in the USA and Australia and Europe. For me, the next big thing is to support the community in those regions that are about to flourish. How can we help them to make things happen more quickly?

DA: Who are you when you aren’t online?

Paul: I do seek solitude, and I really have a strong appreciation of wilderness. I’m a dad, and I love kids, and I suppose most of my time is spent cycling with my family. We go to The Lake District quite often in the UK, which is a beautiful and mountainous area.

I am passionately into road cycling on my bike, and mountaineering too. I like challenging myself — in everything I do, I always like to push myself. I’m always trying to climb higher or go faster. I’m no happier than when I’m in a mountaintop in the snow, even — especially — if it’s in a blizzard. I love being in a hostile environment where perhaps other people wouldn’t be able to cope. I love to explore places and trek the untrodden path. So even if I go back to the same place, I’ll take a different road.

DA: Do you have any final thoughts to share with us today?

Paul: With Drupal 8 on the way, I started a twitter account called @drupal8iscoming. It’s starting to grow and grow and grow now: it celebrates all things Drupal 8 on the internet — you know, articles, tutorials, events, and also how to help to get the word out to organisations about Drupal. Please check it out!

Joomla! 3.4 Beta 2 Released

The Joomla! Project is pleased to announce the availability of Joomla! 3.4 Beta 2. Community members are asked to download and install the package in order to provide quality assurance for the forthcoming 3.4 release.
Joomla! 3 is the latest major rele…

GNOME Foundation: Minutes of the Board Meeting of January, 23th, 2015

= Minutes for Friday, January 23th, 2015, 17:00 UTC =

Next meeting due on February 6th, 2015 at 17:00 UTC

== Attending ==
 * Ekaterina Gerasimova
 * Rosanna Yuen
 * Marina Zhurakhinskaya
 * Jeff Fortin
 * Andrea Veri
 * Karen Sandler
 * Tobias Mueller
 * Sriram Ramkrishna

== Regrets ==

== Missing ==

== Board meeting ==

 * Adboard meeting at FOSDEM 2015
   * Unfortunately was not organized yet, so possibility of piggybacking on the SFC dinner event with a "GNOME table"? ($40 in advance/euro 40 at the door per attendee)
   * People can go on an individual basis, but the general feeling among board members seems to be "we're probably not setting this up as an official event"; maybe just sending an informal invitation email to the adboard list to let them know they can join us there
   * ACTION: Sri to send an informal invitation mail to the adboard for the event

 * Next steps for the Outreach Program
  * Marina sent an e-mail to board-list with all the planned next steps for the OP
   * This is a follow-up to a discussion we started during the GUADEC 2014 board meeting about the growth & requirements for the Outreach Program
   * GNOME has been a good home to launch and grow the project so far, but the program has somewhat outgrown the capabilities of GNOME. Preparations are being made to create an environment where the OP can grow over time without creating too much burden to the GNOME Foundation (in terms of workload on the Board, Rosanna's time handling the payments and invoices)
   * OP is being renamed to "Outreachy"
   * OP would be joining the SFC; GNOME would still be providing its infrastructure, for the time of the transition
  * When this round will end (around March) funds (general OP and travel funds) will have to be transferred from the GNOME Foundation to the SFC
   * Obligations (reimbursements etc.) will be then moved to the SFC itself
   * Rosanna will still be required to help out OP with invoicing / reimbursement till the end of March
   * Travel allowances will still have to be approved by the Board for this (round that ends in March) and previous rounds
  * VOTE: The board agrees to move of OP to the SF Conservancy to further the growth of the program. GNOME will continue to be the infrastructure partner for the time being. Details on the transfering of funds and any other information and the exact timetable will be established in due course, upon consulation with counsel.
    * The GNOME Foundation would not be bound by the contract of the SFC. The primary reason for this vote is that SFC wants to make sure that "GNOME is okay with this move"
    * +1 from Jeff, Tobi, Sri, Kat, Andrea - Karen & Marina abstain
  * ACTION: Karen & Marina should provide a more detailed plan as things are being figured out (timeframe, next steps)

 * 500$ materials sponsorship request for GNOME Peru Fest 2015
  * VOTE: approve the 500$ materials sponsorship: +1 unanimous

 * Next board meeting: our backlog is huge. We could have an extra meeting right after FOSDEM, intsead of waiting 2 weeks.
   * ACTION: Tobi/Sri to evaluate the situation while at FOSDEM and request an extra meeting if needed

Deferred:
 * Responding to a phone press inquiry asking to reach Stormy Peters
  * Comment from Stormy: "There is a press mailing list to deal with press inquiries. And if they are looking for me, they should be able to find me but you are welcome to point them my way."
  * ACTION: maybe Rosanna can check with the caller to see what he wants and see if we need to get back to him by press contact, or if he really wanted to reach Stormy in particular?
 * Sysadmin sponsorship: should we have a guadec-style sponsors' brochure to help with that?
 * WHS
 * OEM Linux distribution including GNOME - any action required wrt Narcis Garcia's email?
 * Review action items in kanban board, for completeness and status
 * ED search

 * Deferred until further mailing list discussion occurs from other board members (or missing info):
   * Reviewing and harmonizing our logos & trademark guidelines wrt ®, ™, etc.
   * Discuss plans for reviewing salaries/hourly rates of employees/contractors
   * Trademark defense campaign has ended and been a success: start evaluating the use of funds to wrap up the matter and to make GNOME better
   * GNOME Privacy project: what to do with the gathered funds? (hackfest? internships? more ideas?)
   * NDA for sysadmins (for the privacy policy)

== Discussed on the mailing list ==
 * Midpoint payments to Outreach interns

== Completed Actions ==
 * Edward Swartz's "philantropist donation": Sri to email him to thank, say we're getting a gift together, ask about reasons motivating his great donation, maybe offer an interview? And verify his mailing address.

== Pending action items ==
 * GNOME's CoC: Board to follow up in the upcoming meetings and prepare a version of the CoC to be finally considered final over all the GNOME yearly events
 * Kat to create a private wiki page on the web services accounts holders and passwords
  * Allan and Kat decided to go for a private git account instead for security reasons
 * Kat to draft a proposal for a privacy policy for review
 * Kat to draft a contract template for future use organizations for which we handle money
 * Karen to write the Privacy policy for GNOME services
 * Karen will look at gnome-software privacy issues from a legal standpoint
 * Karen to draft a proposal for the photography policy at GNOME conferences to discuss on foundation-list
 * Tobi to continue pursuing the fund collection in Europe
 * Tobi to talk to Andrea to move the PayPal data extraction scripts over to the GNOME infrastructure
 * Sri to investigate better uses of adsense/adwords on the GNOME websites
 * Sri to communicate to Rosanna and work on the donation for the West Coast hackfest
 * Sri, Marina, Kat to work on establishing criteria for drafting for the hiring committee for the ED role
 * Sri to investigate the GNOME gifts situation


Nominations Open for Drupal Association At Large Director

It’s a great time to be part of the Drupal Association. We’ve done some amazing work in the last few years, and we’re in a great position to work with the community to continue to improve and grow fully into our mission. As a Drupal Association At-Large Director, you’d be in the center of the action. The At-large Director position is specifically designed to ensure community representation on the Drupal Association board and we strongly encourage anyone with an interest to nominate themselves today.

Nominate Yourself Today

The Board of Directors of the Drupal Association are responsible for financial oversight and setting the strategic direction of the Drupal Association. New board members will contribute to the strategic direction of the Drupal Association. Board members are advised of, but not responsible for matters related to the day to day operations of the Drupal Association, including program execution, staffing, etc. You can learn more about what’s expected of a board member in this post and presentation.

Directors are expected to contribute around five hours per month and attend three in-person meetings per year (financial assistance is available if required). All board members agree to meet the minimum requirements documented in the board member agreement.

Today we are opening the self-nomination form that allows you to throw your hat in the ring. We’re looking to elect one candidate this year to serve a two-year term.

Log in first and…

To nominate yourself, you should be prepared to answer a few questions:

  • About Me: Tell us about yourself! Your background, how you got into Drupal, etc.
  • Motivation: Why are you applying for a board position? What initiatives do you hope to help drive, or what perspectives are you going to try and represent?
  • Experience: What Drupal community contributions have you taken part in (code, camps, etc.)? Do you have experience in financial oversight, developing business strategies, or organization governance?
  • Availability: I am able to travel to three in-person board meetings per year (either self-funded, or with financial sponsorship)
  • IRC Handle
  • Twitter Handle

We will also need to know that you are available for the next step in the process, meet the candidate sessions. We are hosting 2 sessions: 

Session One

  • Tuesday, 24 February 2015 at:
  • 8 AM PST in the US and Canada
  • 11 AM EST in the US and Canada
  • 1 PM in Sao Paulo Brasil
  • 4 PM in London
  • 12 AM Wednesday, 25 February in Beijing
  • 3 AM Wednesday, 25 February Sydney Australia

Session Two

  • Wednesday 25 February 2015 at:
  • 4 PM PST in the US and Canada
  • 7 PM EST in the US and Canada
  • 9 PM in Sao Paulo Brasil
  • 1 AM Thursday, 26 February in London
  • 8 AM Thursday, 26 February in Beijing
  • 10 AM Thursday, 26 February in Sydney Australia

Session Three

  • Thursday 26 February 2015 at:
  • 12:30 PM PST in the US and Canada
  • 3:30 PM EST in the US and Canada
  • 5:30 PM in Sao Paulo Brasil
  • 8:30 AM Friday, 27 February in London
  • 4:30 AM Friday, 27 February in Beijing
  • 7:30 AM Friday, 27 February in Sydney Australia

The nomination form will be open February 1, 2015 through February 20, 2015 at midnight UTC. For a thorough review of the process, please see our announcement blog post.

If you have any questions, please contact Holly Ross, Drupal Association Executive Director.

Flickr photo: Kodak Views

Front page news: 

Open Source at the Front of the Class

Open source is sitting at the head of the class in a growing number of schools with all levels of education. Its no-cost starting point and use-it-your-way flexibility gives open source technology an advantage over proprietary solutions with its no-license and no-fee lesson plan. Don’t think so? LinuxInsider spoke with several technology administrators around the country who gave their open source experiences a solid A+.

World Wine News Issue 384

WWN Issue 384 was released today.

Wine64 on OS X
Weekly AppDB/Bugzilla Status Changes

LibreOffice 4.4, the most beautiful LibreOffice ever

The user interface has been improved in a significant way Interoperability with OOXML file formats has been extended Improved source code quality based on Coverity Scan analysis Berlin, January 29, 2015 – The Document Foundation is pleased to announce LibreOffice 4.4, the ninth major release of the free office suite, with a significant number of […]

There’s a GHOST in Linux’s Library

Patches for GHOST, a critical vulnerability in glibc, the Linux GNU C Library, now are available through vendor communities for a variety of Linux server and desktop distributions. Qualys earlier this week reported its discovery of GHOST, a vulnerability that allows attackers to remotely take control of an entire system without having any prior knowledge of system credentials.

Meet KDE at FOSDEM this Weekend

KDE will be at Europe’s largest gathering of free software developering this weekend, taking over the city of Brussels for FOSDEM. We start with the traditional beer event on the Friday, sampling 100 flavours of beer while we mingle with old friends …

GNOME: Meet GNOME at FOSDEM

This weekend GNOME will be present at FOSDEM, one of the largest gatherings for Free Software contributors and enthusiasts taking place in Brussels, Belgium January 31 – February 01.

GNOME is hosting a booth where attendees can test the latest GNOME version, get promotion material, talk to contributors and learn more about how to get involved in the community. In addition to the booth GNOME will share the H.1308 (Rolin) devroom with other free desktop environments.

Joomla! 3.4 Beta 1 Released

The Joomla! Project is pleased to announce the availability of Joomla! 3.4 Beta 1. Community members are asked to download and install the package in order to provide quality assurance for the forthcoming 3.4 release.
Joomla! 3 is the latest major rele…

GNOME: Builder fundraiser concludes

Christan Herget’s Builder fundraiser have concluded. The fundraiser surpassed its original goal allowing Christian to dictate extra time to the development of Builder.

gnome-builder logo

Christian stated in a comment “The overwhelming support of the community is both heartwarming and inspiring. I’m excited to get to continue working on a project that I think is critical to the future of our platform.”

Updates about the progress the project are making is frequently posted on the @GNOMEBuilder twitter account. It’s also possible to view git.gnome.org/Builder/log for real-time source updates. As with any GNOME project the project welcomes community contributions.

Christian will present his work with Builder at the South California Linux Fest (SCALE 13x), taking place February 19-22 in LA.

 

 *The builder logo was done by Jakub Steiner 

 

Drupal.org 2015 Advertising Initiatives

I was hired by the Drupal Association in October 2014 to develop a new revenue stream from advertising on Drupal.org. For some time we’ve been trying to diversify revenue streams away from DrupalCon, both to make the Association more sustainable and to ensure that DrupalCons can serve community needs, not just our funding needs. We’ve introduced the Drupal Jobs program already and now, after conversations with the community, we want to put more work into Drupal.org advertising initiatives.

This new revenue stream will help fund various Drupal.org initiatives and improvements including better account creation and login, organization and user profile improvements, a responsive redesign of Drupal.org, issue workflow and Git improvements, making Drupal.org search usable, improving tools to find and select projects, and the Groups migration to Drupal 7.

We spent time interviewing members of the Drupal Association board, representatives of the Drupal Community, Working Groups, Supporting Partners, and Drupal Businesses, both large and small to help develop our strategy and guidelines. Our biggest takeaways are:

  • Advertising should not only appeal to advertisers, but also be helpful to our users and/or our mission.
  • When possible, only monetize users who are logged out and not contributing to the Project. If you’re on Drupal.org to do work and contribute, we don’t want you to see ads.
  • Don’t clutter the site, interfere with navigation or disrupt visitors, especially contributors.
  • Do not put ads on pages where users are coming to work, like the issue queue.
  • Advertising products should be inclusive, with low cost options and tiered pricing. We want to make sure that small businesses without huge marketing budgets have the opportunity to get in front of the Drupal Community.
  • Create high impact opportunities for Partners that already support the Community.
  • Address the industry-wide shift to Programmatic Advertising, which is the automated buying and selling of digital advertising.

There are already advertising banners on Drupal.org, however we need to expand their reach to hit our goals. We’re trying to address challenges for our current advertisers, including a relatively low amount of views on pages with ads, which makes it difficult for them to reach their goals.

We’re also facing industry-wide challenges in Digital Advertising. Advertisers are looking for larger, more intrusive ads that get the users’ attention, or at the very least use standard Interactive Advertising Bureau (IAB) ad sizes, which are larger than the ads we offer on Drupal.org.

We came up with a new line of products that we feel will help us reach our goals, but not disrupt the Drupal.org experience, or the Drupal Association Engineering Team roadmap. We want our Engineering Team to fix search on Drupal.org, not spend time developing and supporting major advertising platforms.

2015 Advertising Initiatives:

  • The ongoing development of curated content with banner ads including resource guides, content by industry and in the future, blog posts.
  • Continued display of banner ads on high profile pages like the Homepage, Marketplace and Case Studies Section.
  • Sponsored listings from Supporting Technology Partners (similar to Hosting Listings).
  • Opt-in email subscriptions with special offers from our Supporters.
  • Audience Extension: a secure, anonymous, non-interruptive way to advertise to Drupal.org visitors. It allows advertisers to programmatically reach the Drupal.org audience while on other websites through Ad Networks and Exchanges.

I wanted to spend most of my time explaining Audience Extension, since its unlike anything we’ve done in the past, and it may prompt questions. This product makes sense because it addresses all of the challenges we’re facing:

  • It’s affordable for small businesses; they can spend as little as $200 on a campaign
  • We don’t need to flood the site with ads and disrupt the user experience.
  • It’s relatively easy to implement – we won’t interrupt the engineering team or their efforts to improve Drupal.org.
  • We will only target anonymous (logged out) users.
  • We will support “Do Not Track” browser requests.
  • This is an industry-wide standard that we’re adopting.
  • Anonymous users will have the option to opt-out.
  • This improves the ad experience on other sites with more relevant, useful ads that also support the community.

How does Audience Extension Work?

We’re partnering with Perfect Audience, a company that specializes in retargeting, and offers a unique audience extension solution called Partner Connect.  We add a Perfect Audience JavaScript tag to the Drupal.org source code. This tag will be loaded on the page to logged out users. The tag places a Perfect Audience cookie in the visitor’s browser that indicates that they recently visited Drupal.org. Once that cookie is in place, an advertiser looking to reach out to the Drupal.org community can advertise to those visitors on Facebook, Google’s ad network, and many other sites that participate in major online ad networks. Advertisers create and manage these campaigns through their Perfect Audience accounts. They pay for the ads through Perfect Audience and we split the revenue with Perfect Audience and the ad networks that serve the ads.

  • The program is anonymous. No personally identifiable information (such as email address, name or date of birth) is gathered or stored.
  • No data is sold or exchanged, this merely gives advertisers the opportunity to buy a banner ad impression within the Perfect Audience platform.
  • It’s easy to opt-out. You can just click over to the Perfect Audience privacy page and click two buttons to opt out of the tracking. Here’s the link.
  • Drupal.org will support “Do Not Track” browser requests and only users who have not logged in (anonymous) will be included in the program.
  • It does not conflict with EU privacy rulings. Advertiser campaigns for Partner Connect can only be geotargeted to the United States and Canada right now.
  • Only high quality, relevant advertisers who have been vetted by an actual human will be able to participate in this program. Some good examples of Perfect Audience advertisers would be companies like New Relic and Heroku.
  • Perfect Audience is actually run by a Drupaler! The first business started by founder Brad Flora back in 2008 was built on Drupal. He spent countless hours in the IRC channel talking Drupal and posting in the forums. He understands how important it is to keep sensitive pages on Drupal.org an ad-free experience and he’s very excited to be able to help make that happen.
  • This program has the potential to generate significant revenue for the Drupal Association and Project over time as more advertisers come on board.

It’s important that we fund Drupal.org improvements, and that we do so in a responsible way that respects the community. We anticipate rolling out these new products throughout the year, starting with Audience Extension on February 5th.  Thanks for taking the time to read about our initiatives, and please tell us your thoughts!

Plasma 5.2 Is Beautiful and Featureful

Today KDE releases Plasma 5.2. This release adds a number of new components, many new features and many more bugfixes.

New Components

KScreen dual monitor setup
This release of Plasma comes with some new components to make your desktop even mor…

The Document Foundation announces the results of the Android Tender

Berlin, January 27, 2015 – Following the successful release of the LibreOffice Viewer (Beta), The Document Foundation announces the results of the Android tender – http://tdf.io/tender – today. The tender aims at developing the technical framework that will ultimately power LibreOffice for Android, including the document editor. This tender is one more step towards a […]

Debian Forked: All for Devuan and Devuan for All?

A group of developers made good on their threats to fork Debian Linux late last year, after the community’s leadership voted to replace sysvinit with systemd, making systemd the default init boot process. The Debian Technical Committee’s decision spurred several key Debian developers and project maintainers to resign. Some of them formed a new community dedicated to forking Debian.

GNOME Foundation: Minutes of the Board Meeting of January, 09th, 2015

= Minutes for Friday, January 09th, 2015, 17:00 UTC =

Next meeting due on January 23th, 2015 at 17:00 UTC

== Attending ==
 * Ekaterina Gerasimova
 * Rosanna Yuen
 * Marina Zhurakhinskaya
 * Jeff Fortin
 * Andrea Veri
 * Karen Sandler
 * Tobias Mueller
 * Sriram Ramkrishna

== Regrets ==

== Missing ==

== Board meeting ==

 * Funding - quick status check on:
  * Ecosystem (re)mapping
  * Adboard outreach
   * Around 20 companies involved in the last 10 years
   * The Board is looking to expand our Advisory Board membership base
    * Karen points out how hard it is to reach out companies asking for funds when there is no existing connection (effort expended versus posible gain is too high). Also the wrong person reaching out on our behalf can also be detrimental
    * Karen also states the fact even without a successful response by a specific company, it's another way to touch base with an external entity and contacts that might be willing to support the GNOME Foundation
   * Discussions with startups reveals that those who are server-intensive are looking for good desktop tooling, it's something GNOME is lacking in and Mac OS X has a lot of traction in.
     * Opportunity to crowdsource outreach, which may turn into fundraising opportunities, to whoever people in our community that attends startup-gatherings types of events all around the world - imagine if we were hundreds doing that
     * At least in Portland, GNOME is a very well recognized brand, 7/10 times it needs no explanation; similar story among developers in some venues in NYC; we have a strong brand
     * A different approach than traditional door-knocking fundraising, more about getting those actors involved and interested in our activities...
     * Idea for a mixed approach where we have a 70% effort on maintaining current adboard relationships at various touch points, and 30% new outreach etc.?
     * Idea to have highly technical and popular "GNOME ambassadors"? Already have a couple of qualified volunteers

  * Sysadmin sponsorship
   * VOTE: Assign 5K of general funds as a buffer to cover sysadmin work for coming months while funding for it is being sorted out
    * +1 from jeff, marina, karen, sri, tobi (andrea abstains)

 * Sitrep on deal with WHS for funds in Europe and countries following the IBAN convention
  * The core issue is the "outgoing payments" (payments they make on our behalf) needing to be included in the file export/report; it would be possible but a lot of work for them?
  * Entering this agreement would create some more work/complexity when it comes to annual reports
  * ACTION: get back to them, explain that the export is necessary, and ask for some form of documention wrt outgoing payments?

 * Review action items in kanban board, for completeness and status
  * See Board of Directors board on https://tasks.gnome.org
  * Access is granted based on the credentials of your GNOME Account
 
 * ED search

 * Deferred until further mailing list discussion occurs from other board members (or missing info):
   * Reviewing and harmonizing our logos & trademark guidelines wrt ®, ™, etc.
   * Discuss plans for reviewing salaries/hourly rates of employees/contractors
   * Trademark defense campaign has ended and been a success: start evaluating the use of funds to wrap up the matter and to make GNOME better
   * GNOME Privacy project (what to do with the remaining funds): hackfest? internships?
   * NDA for sysadmins (for the privacy policy)

== Discussed on the mailing list ==
 * Builder fundraiser launched (http://www.hergert.me/blog/2014/12/29/fundraiser.html)
 
== Completed Actions ==
 * GUADEC 2015 Sponsor Brochure Draft: Jeff to mail Fabiana back with the result of Board's vote

== Pending action items ==
 * GNOME's CoC: Board to follow up in the upcoming meetings and prepare a version of the CoC to be finally considered final over all the GNOME yearly events
 * Edward Swartz's "philantropist donation": Sri to email him to thank, say we're getting a gift together, ask about reasons motivating his great donation, maybe offer an interview? And verify his mailing address.
 * Kat to create a private wiki page on the web services accounts holders and passwords
  * Allan and Kat decided to go for a private git account instead for security reasons
 * Kat to draft a proposal for a privacy policy for review
 * Kat to draft a contract template for future use organizations for which we handle money
 * Karen to write the Privacy policy for GNOME services
 * Karen will look at gnome-software privacy issues from a legal standpoint
 * Karen to draft a proposal for the photography policy at GNOME conferences to discuss on foundation-list
 * Tobi to continue pursuing the fund collection in Europe
 * Tobi to talk to Andrea to move the PayPal data extraction scripts over to the GNOME infrastructure
 * Sri to investigate better uses of adsense/adwords on the GNOME websites
 * Sri to communicate to Rosanna and work on the donation for the West Coast hackfest
 * Sri, Marina, Kat to work on establishing criteria for drafting for the hiring committee for the ED role
 * Sri to investigate the GNOME gifts situation