#131 development for Inactive Dashboard #132
Conversation
- Add new pyos-packages section with package activity dashboard - Track last commit dates and identify inactive packages (6+ months) - Add sortable tables for all packages and inactive packages - Update existing package dashboard with activity tracking features - Reorganize navigation to group package-related metrics - Remove pyosmetrics dependency to fix Python 3.9 compatibility Closes pyOpenSci#100
- Add comprehensive workflow documentation for package-activity.qmd - Include Nox-based development instructions - Focus on inactive package identification (6+ months) - Provide setup, testing, and troubleshooting guidance - Create docs directory structure with README Related to pyOpenSci#131
| # Nox will handle the rest automatically | ||
| ``` | ||
|
|
||
| ### Alternative: Manual Python Setup |
There was a problem hiding this comment.
If the user uses nox, then they don't actually need to create a venv because nox does that for them so i'm not sure about this section.
we could add a sentence that says "python should be installed". And probably using uv to install Python is ideal but i'd just suggest that people install a current version of python (not 3.9).
There was a problem hiding this comment.
hey @stevenrayhinojosa-gmail-com we won't be able to merge this as is as it needs a good bit of work. I really appreciate your attending our sprint. Do you have time to make some updates or help me understand what your goal is with the docs in this pr?
And also i'd remove the dashboard content and have a docs pr be completely separate for easier review.
| # - Watch for file changes and rebuild automatically | ||
| ``` | ||
|
|
||
| ### Manual Workflow (Alternative) |
There was a problem hiding this comment.
The point of using nox is to avoid this section altogether.
| @@ -14,37 +14,36 @@ execute: | |||
| import ast | |||
There was a problem hiding this comment.
Is the intention to also submit changes to the dashboard through this pr or just documentation? I think this should be two separate pr's.
There was a problem hiding this comment.
Hi, As I remember I was working on the "Inactive Packages" dashboard but then we realized that we also had to lay out the documentation to work on the "Inactive Package" dashboard. I did it backwords and could have provided better direction.
There was a problem hiding this comment.
No worries, @stevenrayhinojosa-gmail-com. I do want to merge this PR, but I think we need to make some enhancements to it first.
I am going to test the dashboard locally. What we might consider doing is pulling the dashboard and its commits out and merging it separately from the docs. As the docs we should consolidate into the readme as it makes sense and avoid overlapping information
I appreciate all of your work on this.
Summary
This pull request improves developer onboarding for the pyos-packages dashboard by adding clear setup instructions, workflow documentation, and a troubleshooting guide. It addresses Issue #131.
What's Included
Environment Setup Instructions
Instructions for using:
Dashboard Structure Overview
Goals
Related Issue