EinsteinPy Proposal for Enhancement 1: EPEs and EinsteinPy Governance (EPE1)

EPE stands for EinsteinPy Proposal for Enhancement. An EPE is actually a design document providing important information, details and governance models to the EinsteinPy community, or describing a new feature for EinsteinPy or its affiliated packages. The EPE should provide a concise technical specification of the feature and a rationale for the feature. If the EPE is intended to be regarding a governance specific model, a member meeting should be organized and the EPE must get at least 51% votes to pass.

We intend EPEs to be the primary mechanisms for proposing major new features, for collecting community input on an issue, and for documenting the design decisions that have gone into Python. The EPE author is responsible for building consensus within the community and documenting dissenting opinions. The EPE author is obligated to write a formal email to all@einsteinpy.org for a community meeting.

Because the EPEs are maintained as text files in a versioned repository (indirectly since this wiki is versioned within GitHub), their revision history is the historical record of the feature proposal

The EPE is the beginning of formalism in the future major changes in EinsteinPy. This EPE is meant for understanding what EinsteinPy Enhancement Proposals are, what function they serve, and how they can be implemented.