09:15 - The Document Foundation - Helping good people make great software

Duration: 10 minutes

Speakers: Charles Shultz (The Document Foundation)

One of the core missions of the Document Foundation is to ensure that the LibreOffice project has the necessary tools and infrastructure to deliver LibreOffice and to work collaboratively. It has chosen since its very beginning to remain largely independent from any third party entity. We will discuss the reasons behind this choice and how the Document Foundation manages to provide the LibreOffice project the answers to its technical needs, in terms of hardware and software resources, tools and collaborative methods.

09:25 - The OpenStack community

Duration: 10 minutes

Speakers: Jeremy Stanley (OpenStack Foundation)

The OpenStack community has been able to handle its dramatic scale and pace of development through automated processes which treat all developers equally, and which keep our project trunks clean through rigorous pre-merge testing. I will briefly outline these tools and solutions, all openly documented and implemented entirely on free software so that anyone can repeat our successes (and learn from our failures)!

09:35 - Xen Project Infrastructure : A tailored approach for our sub-projects

Duration: 10 minutes

Speakers: Lars Kurth (Director, Open Source Solutions, Citrix)

In this session we will give an overview of the different infrastructure approaches sub-projects within the Xen Project take. We have a common set of rules for very basic infrastructure (e.g. mailing lists), but otherwise allow each sub-project to make their own choices for code lines, workflow, bug tracking and other infrastructure items as long as the sub-project takes sysadmin ownership. This works well, but also imposes some complexity for users and community managers.

09:45 - McCommunity?

Duration: 10 minutes

Speakers: Louis Suárez-Potts (Strategist, Age of Peers)

My title refers to MacDonald's. I wanted to write, "MacCommunity," but … perhaps the two are not so dissimilar. The issue here is not the homogenization of open source practice conditioned by common infrastructure. Rather I want to return to a point raised by Dave Neary two years ago: That our usage of online services for community work leads to the diminishment of in-person interaction. This is a loss not only of pleasure but more importantly of all that cannot be communicated online but which is vital for a community. I would extend it and suggest that threat of McCommunity lies as well in losing an important relation to those who are interested in the project but lack the skills to contribute code. I am aware of wikis and the like. But I’m also conscious that the step from a comment posted on a wiki or forum to a solid contribution is a giant leap—and does not seem to have become easier, even as the tools for codework have matured. I identify here reasons for this divide and its cost; and I suggest some resolutions. I also look to parallels in other fields, such as pharma.

09:55 - How open source tools contribute to developing communities and ecosystems?

Duration: 10 minutes

Speakers: Mike Hendrickson (Vice President for Content Strategy, O’Reilly)

How open source tools are enabling OSS communities to build applications, documentation and engagement with their ​members, developers ecosystem and interested parties.

10:05 - Increasing Community Collaboration and Contribution: The Eclipse Experience

Duration: 10 minutes

Speakers: Mike Milinkovich (Executive Director, Eclipse Foundation)

Increasing Community Collaboration and Contribution: The Eclipse Experience

10:15 - The Rise and Fall of the Forge

Duration: 10 minutes

Speakers: Ross Turk (Director, Ceph Community)

SourceForge was the first forge, and for a very long time it was the center of gravity for open source. Any project that mattered (and wasn’t already in a Linux distribution) could be found there, and most open source developers contributed to at least one of them. Academics turned to SourceForge for data when studying open source, and companies regularly received funding (in part) because of their position in its “Top Projects” list.

Times have changed somewhat…but why? Part of the answer lies in Github's rise to prominence, but certainly not all of it. In this quick talk, I plan to share my perspective on this open source giant and show what it can teach us about today’s community infrastructure.

11:00 - The ASF : Community over code : how to fulfil this promise ?

Duration: 10 minutes

Speakers: Emmanuel Lechary (Apache Foundation)

The ASF is quite a big organization (4000+ committers, 400 members, more than 100 projects) but still, it's running smoothly day after day. It's all about the way The ASF operate that makes it easy. We favor collaboration, and 'doers' over anything else. Not that long ago, everything was ran by volunteers, however, in the past few years, the need of a more resilient infrastructure pushed The ASF to start hiring people to manage infrastructure. This is a short description on the tooling we are using, and the philosophy behind the organization, in an attempt to give some clues about the success of The ASF organization and infrastructure.

11:10 - Why should you care about an open infrastructure for your project?

Duration: 10 minutes

Speakers: Karsten Wade (Engineering Manager, CentOS)

In this presentation Karsten will explain how and why it's crucial that your FLOSS project maintain a 100% free/libre and open infrastructure. Hint: because of the scientific method. With the rise of no-cost services such as GitHub and Trello that are useful to FLOSS projects, many projects are choosing to gain the advantage of the tools and the social systems that go along with them. However, there are dangers to the project in using these services. This presentation will briefly cover those dangers, why you should care about them, and how to move your project towards being 100% FLOSS.

11:20 - Upgrading the Community Technical Infrastructure

Duration: 10 minutes

Speakers: Cédric Thomas (CEO, OW2 Consortium)

Since established over ten years ago, OW2's technical infrastructure has evolved from a simple integrated forge into a complex ecosystem of complementary tools. The emergence of state-of-the-art online resources seem to offer appealing alternatives to project development teams. Certain even question the need for our own technical infrastructure. We will share some of the questions we are dealing with as we are considering upgrading some of its key elements of our infrastructure.