Project: Analyze and Prioritize Dataverse Backlog

cmbz commented 8 months ago

Overview

To analyze and prioritize the current Dataverse (https://github.com/IQSS/dataverse) issue backlog
Define and implement a process to monitor and triage new Dataverse repo issues

As of Jun 24, 2024 the main dataverse Github repository has 1116 open issues; the oldest is from 2014.
The Dataverse Team does not have a comprehensive strategy or process to address this backlog of issues. In contrast, the team recently developed and implemented an approach for managing the current backlog of Community pull requests
The backlog has proven to be a fruitful source of potential feature and functionality improvements and bug reports from the Community and the core development team.
Designing and implementing a comprehensive approach to analyze and prioritize the backlog and manage future issues would:
- Reduce and ideally clear the current backlog
- Act on Community-identified code defects (275 on Jun 24, 2024)
- Act on Community-identified software improvement contributions aligning with Dataverse Project priorities
- Increase transparency about how Community-submitted Dataverse issues are evaluated and prioritized for action
- Provide the Community with improved GitHub issue and pull request templates

pdurbin commented 8 months ago

Proposal: Analyze Dataverse Backlog

Can we please open this document to the public?

cmbz commented 3 months ago

cmbz commented 2 months ago

cmbz commented 2 months ago

cmbz commented 1 month ago

Announced the project to the community. See Google Groups post.
Inventory of bugs was created for review (task complements the Type: Feature review process)
Dataverse prioritization team began reviewing issues on the Type: Feature list
@sbarbosadataverse began reviewing the Type: Bug list
Issues older than 2020-08-18 and that were not Type: Feature were closed.
- Some closed issues were reopened based on Community feedback.
- Monitoring of Community responses will continue

cmbz commented 1 week ago