donkirkby / donkirkby/live-py-plugin
Pylint alerts corrections as part of intervention experiment
- Dominant language
- Python
- Stars
- 302
- Forks
- 63
- Avg merge
- 6h 50m
- Merged PRs (30d)
- 2
Description
I'd like to conduct a software engineering experiment regarding the benefit of [Pylint](https://pypi.org/project/pylint/) alerts removal.
The experiment is described [here](https://github.com/evidencebp/pylint-intervention/).
In the experiments, Pylint is used with some specific alerts, files are selected for intervention and control.
After the interventions are done, one can wait and examine the results.
I'm asking for your approval for conducting an intervention in your repository.
See examples of interventions in [stanford-oval/storm](https://github.com/stanford-oval/storm/pull/181), [gabfl/vault](https://github.com/gabfl/vault/pull/82), and [coreruleset/coreruleset](https://github.com/coreruleset/coreruleset/pull/3837).
You can see the [pland interventions](https://github.com/evidencebp/pylint-intervention/tree/main/interventions/candidates/donkirkby_live-py-plugin_interventions_October_06_2024.csv)
@donkirkby , may I do the interventions?
Contributor guide
Research direction
Read the linked pylint-intervention experiment and its candidate interventions CSV first. The issue does not name repository files, tests, specific alerts, or a concrete completion condition; it requests approval to conduct interventions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100