mesa / mesa/meps

MEP 2 - Adding a new feature

Open
#1 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

If it is small - it goes straight to PR
If it is medium - open discussion, then PR
If it is complex....
A MEP is required when X

Experiments

If everyone agrees -- then let’s just do it.
If everyone doesn’t -- experiment

How likely you will have to change it in future?
How big will the impact be if you have to change it.

Related: https://github.com/projectmesa/mesa/discussions/1909

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are named. Start by reviewing the MEP process described in this issue and the related discussion at projectmesa/mesa#1909. Done means reaching agreement on when an MEP is required, how experiments are handled, and how the guidance should be documented.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.