My Future Dev Work

Development
1

Hey all,

Recently, I have been putting in a lot of time into dev work for StashApp. I dropped a lot of work on WPs plate with reviews and I would like to take a smarter approach this time to limit the amount of time he has to spend answering my questions. I would like to get some community feedback on what my next project should be.

My current flow for finding things to do:

  1. Look through the issues list and find something I think is in scope/would be a good idea
  2. Talk to WP to see if it is in scope for the current release/project direction
  3. If yes, work, if no, go back to step 1
  4. PR and wait for feedback
  5. Fix, get it merged, then go back to step one.

Now, I think giving myself a project to complete means that I can go ahead and do various PRs at once without necessarily having to go to WP for every single one. As long as it is in scope for the general project I think I have a good enough idea of what he would consider in scope for core stash to make that decision on if it should be implemented. Of course, the overall plan still needs to be signed off by him to move forward and he will have final say on if/when something gets merged.

What I mean by “Project”:

  • Stash-Box Consistency
  • Revamp/Upgrade the current scrapers infrastructure

What I don’t mean by “Project”

  • Add a filter
  • Fix this bug

I would like some community ideas on what part of the app/flow causes the most friction and could be upgraded or revamped. Mostly what I do with the app works for how it is but I know there are tons of users with different use cases and friction points and I would love to hear it so I know what I could potentially work on. There are currently 2 projects available on Github for both of the examples that I listed above and I think they would be a good starting point for sure.

Please feel free to reply here or ping me on discord for a faster response.

1 Like
2

This isn’t a direct answer, but ideally you’ll choose something that fulfills all three areas:

  • Your strengths. Whether that’s primarily front end, back end, etc. Or something that piques your interest and you want to learn more.
  • Prioritized requests on the project Roadmap/backlog. Some of those already have an estimated task size: Roadmap · GitHub
  • Popular requests the community has. Look at open issues and sort by most “thumbs up”.
3

That is what I am currently doing as described in my current workflow. The roadmap isn’t a “project” its a cluster of random features/issues that WP needs to constantly maintain to be relevant. I’m looking for a project that I can get his go ahead on so he doesn’t need to keep being nagged for every individual feature since they normally have no relevance to each other.

4

GitHub Projects are not really ideal for this as they are managed at organization not repository level.

I think the better approach would be for us to triage the feature requests based on the object, frontend/backend, GraphQL API, plugin API, etc to make it developer agnostic. Then those labels could be used as a project to work on specific codebase instead of jumping from issue to issue.
For new issues we could add a labeler to do this automatically moving forward, but the backlog of issues would need to be dealt with the hard way.

From my point of view the biggest issue that needs solving is the inconsistency.

Scenes are the most developed since that’s what most people use Stash for, but as a result other objects do feel like second class citizens. So if someone wanted a “project” to work on porting scene exclusive features would be my suggestion.

5

That is exactly a recommendation I was looking for.

Thanks

1 Like