RFC

SOCI RFC

RFC (Request For Comment) is an informal process to drive SOCI development forward. It is recommended to use RFC to:

• request big and significant changes in current code base
• propose big new features especially, those with potential of breaking backward compatibility in SOCI.

SOCI RFC Rationale

RFC is a simple yet useful procedure that helps to record source and rationale of important decisions regarding design and implementation of made on the course of SOCI development (where things come from). Such knowledge may be very important for new developers and maintainers in future. RFC is by no means supposed to work and feel like a straitjacket put on SOCI developers. RFC is not a requirement, but a recommendation. In fact, only few decisions would be made based on RFC.

RFC process has proved useful in many successful FOSS projects, regardless of size of their communities. For example, GDAL, MapServer, FDO.

SOCI RFC documents

• RFC1 - Complete support for C++ integer types

SOCI RFC Metadata

• Author: name and e-mail
• Date: data of completing and proposing
• Version: version for which adoption of submitted RFC is planned
• Status:
  • Proposed: RFC is complete, and open for voting.
  • Development: RFC is being written/revised/discussed.
  • Adopted: RFC is approved (and presumably implemented)
  • Withdrawn: RFC is unapproved, and not being pursued further.