Skip to content

Creating a guideline for design decisions. #42

@satyamjay-iitd

Description

@satyamjay-iitd

We must create some guiding principal like zen of python.

This will make making the design decision easier for us (by making it objective). For example we can say we don't like this design because this violates this guideline. Ofcourse the guideline itself is subject to modification but a strong argument must be made. Note that it is not necessary that current state of the framework adheres to the guideline in which case efforts will be made to make it adhere to the guideline.
While creating the guideline we should not be biased towards what we are, instead the guideline should dictate what we should be.

Following is the proposal draft. Feel free to add/modify:- sheet

After the discussion the guideline should be frozen with the following properties:-

  1. All new feature must not violate the guideline.
  2. All modification must the drive the framework closer to the guideline.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions