The PKP sprint at the Heidelberg University Library was fully attended with 40 participants from 14 countries (including one from Bangladesh!) representing university libraries, university presses, national platforms, and commercial and non-commercial publishers. The breadth of attendees demonstrated the strength of the PKP community in Germany and across Europe.

We’ve recently added a Contributor License Agreement (CLA) to our git repositories here at PKP. This requests that open-source contributors sign the CLA as part of the process of contributing to our software. The PKP Technical Committee (which is comprised of PKP team members and community members) has been considering how to start using the latest GNU GPLv3 license for our software instead of our current GPLv2 license.

Gracias de nuevo al arduo trabajo de la traductora María Elena Sánchez Salazar, con el apoyo del equipo editorial del Instituto de Geografía de la Universidad Nacional Autónoma de México (UNAM), tenemos el segundo curso de PKP School en español – Flujo de trabajo editorial en OJS 3. Gracias también a Raúl Marcó del Pont Lalli y Claudio Amescua de la UNAM por apoyar esta traducción.

Created in the spring of 2017, Coalition Publi.ca aims to establish an infrastructure dedicated to the digital production and dissemination of research results in the Canadian humanities and social sciences (HSS). The project is now guided by an advisory committee with representatives from various stakeholders within academia.

In recognition of PKP and SciELO’s twentieth anniversary, the Public Knowledge Project (PKP) and SciELO Program are entering into an agreement to develop a Preprint Server system on the principles that have guided these two organizations over the last two decades.

Ubiquity Press and the Public Knowledge Project (PKP) have entered into an agreement to work more closely together. This agreement is strategically aligned with Ubiquity’s commitment to Open Source Software under its new Customer Charter. Ubiquity has used the Open Journal Systems (OJS) software to manage the editorial process for its journals since inception and OJS will continue to play a role into the future.

Earlier this year, we released the first in our series of new themes for OJS 3 — the Health Science theme. Using the contemporary and humanist typeface, Fira Sans, this theme was designed with cleanliness, simplicity and accessibility in mind. Today, we’d like to share a new style guide we’ve written to help you make the best use of that theme.

Ready to sprint? We’re getting ready for another PKP sprint, this time in fabulous Heidelberg, Germany. The sprint will run from Thursday, September 20 through Friday, September 21, 2018. We are extremely grateful to our local host, the University of Heidelberg and look forward to meeting more friends from the German OJS network and elsewhere. You can read more about their activities here.

At the PKP Code Sprint in 2017, a group of PKP community members/supporters created a report on PKP’s myriad documentation. As our software had grown over ~20 years, so too had our solutions for platform- and task-specific documentation. By the end of the sprint, the group identified redundant and deprecated documentation for outdated versions of software, specific plugins, unique tasks, and information on publishing.

We’re pleased to release our 2017 PKP Annual Report to the Community, providing a brief overview of our major accomplishments over the past year, in all areas of our activities, including software development, services, research, partnerships, finances, and more. We’ll be using the Report as a guide for tomorrow’s PKP Virtual Annual General Meeting, and we hope to see you there.

We’ve recently been asked for advice on how to best plan for upgrading to OJS 3. OJS 3 is a significant upgrade from the old OJS 2.x line, which means you will need to do some careful planning with your editors to ensure a smooth process. In many ways, the changes are more human resources related (i.e., training and visual design) than technical, so you’ll want to build in time for that, as well as clear communications at each stage.