We need onboarding instructions for this repo

[wbadgett]

We need onboarding instructions for this repo. Many people in AD will soon need access to this repository, setting up your initial work area and connection to GitHub are not obvious

[wbadgett]

Might any of the proposed on boarding instructions have any sensitive info?

[crispd]

Agreed. This is the closest that we currently have: https://fermi-ad.github.io/getting-started/initial-setup.html (from https://github.com/fermi-ad/getting-started)

The issue is that any documentation for onboarding instructions related to developing phoebus screens will become its own form of technical debt until we fix issues with how we deploy phoebus-fnal--thus taking time from those efforts, which themselves help more than those focused on display development. What we have so far is general, broad strokes for how one sets up their github account for access, but it is the part of it that I don't expect to change outside of as-required based on specific user feedback.

As I understand it, the guidance for determining sensitive information is fairly vague. Beau stated it the other day as "anything that might help someone map out our controls system". In my mind, a robust onboarding for developing screens would almost certainly include information that would fit that description, but I could be misinterpreting it. If we can improve our build and launch scripts, however, effective guidance within this scope would be much simpler and effective without as much in terms of deployment specifics.

I don't know if this really answers the ticket... in short, I agree that more guidance is needed, but it's unclear to me that it's more important than aligning and stabilizing our Phoebus effort as a whole--until the point at which said work would no longer affect the guidance needed here.

In the meantime, I open myself up as a point of contact to help anyone who needs it. Working with people in a more candid setting could positively influence how this kind of onboarding once made.