Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
======Google Season of Docs 2021: OpenPrinting project======

[[:gsoc:google-season-of-docs-2021|Main GSoD Linux Foundation page: How to apply, deadlines, other workgroups, ...]]
=====Contact=====

**Important:** We protect the e-mail addresses of our mentors and mailing lists against spam bots. Please replace all occurrences of " at " and " dot " by "@" and "." resp.

Mailing list: [[http://lists.linux-foundation.org/mailman/listinfo/printing-architecture|printing-architecture at lists dot linux-foundation dot org]]

IRC: #openprinting on Freenode

[[https://github.com/OpenPrinting|OpenPrinting GitHub]]

Code License: See project descriptions

=====Organization Administrators=====

The participation of the Linux Foundation and OpenPrinting in the Google Season of Docs is organized by Till Kamppeter (till at linux dot com) and Aveek Basu (basu dot aveek at gmail dot com).

======Project======

=====User and Developer Documentation for cups-filters=====
We need to create the detailed documentation on usage details of all the library functions, CUPS filters, backends, and utilities in the cups-filters project and how to build them. This should especially help developers for printer drivers, Printer and Scanner Applications, and other printing-related software.

Especially changes and new features of [[https://github.com/OpenPrinting/cups-filters|cups-filters]] 2.x (filter functions, libppd, …) should be taken into account.

Current documentation is put together from all the different sources from where the filters and other components came originally, before the cups-filters project got started. Some documentation is in the README file other in man pages, … This should be replaced by a structured documentation covering all at one place, to make using cups-filters easy.

The writer should both put the existing documentation together and improve it and also go through the API functions's C code, perhaps use auto-documentation tools (add comments to each API function's code and generate documentation, as GNOME for example does), and also give instructions for common tasks. It should be easy to update the documentation for feature additions in the future.

Mentors: Till Kamppeter, Project Leader OpenPrinting (till at linux dot com), TBD

License: Apache 2.0 + (L)GPL2 exception
Wiki

User Tools

Site Tools

Page Tools
