Investigate alternatives to github for mechanical part process

[mmroden]

There are two basic pain points for using github as the integration and issue tracking portal for the mechanical teams.

1. This is not how they are used to working
2. Those of us without Fusion360 licenses are in the dark wrt stl/step files

The particular pain points as per point 1 above:

• identifying assignee

• creating issue

• task dependencies

• SOP for part design (i.e., testing procedure needed to get to the assembly)

• delivery schedule (i.e., gantt chart)

[mmroden]

More painpoints:

1. Should have a single assignee per task, not multiples.
2. Should have different stages for a current task's completion
3. Should have a due date for the current task (ie, review, part print, part delivery, etc)
4. Should have a due date for the overall task (the entire part is complete and published as a step file in the git repo) that may or may not match step 3 above.
5. Want a list of current tasks by person logged in (ie, I want to see what's been assigned to me across all three projects). Should not require a bookmark.

[capsulecorplab]

Looking into setting up redmine instance for managing hardware testing-related issues, assignees, and tasks & dependencies. Plugin considerations include github commits (see also https://redmine.org/projects/redmine/wiki/redminerepositories#Git-repository). Considering mermaid.js gantt charts for facilitating delivery schedule.

[capsulecorplab]

It's worth noting this is a product lifecycle management (PLM) issue, not necessarily a source control issue