Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request: Asset audit report #249

Closed
jasnell opened this issue Apr 17, 2017 · 12 comments
Closed

Request: Asset audit report #249

jasnell opened this issue Apr 17, 2017 · 12 comments

Comments

@jasnell
Copy link
Member

jasnell commented Apr 17, 2017

@nodejs/build @nodejs/tsc @nodejs/ctc @nodejs/benchmarking @nodejs/jenkins-admins

One thing that we seem to be missing overall is a clear listing of all hardware/software assets (owned or donated) that core and related projects currently depend on. This is something that the TSC and CTC really should have better visibility into given the potential risks should any resources no longer be available for whatever reason.

I would like to request that an audit report be put together to help catalog the various assets, along with information about who has access to those, who the primary points of contact are, where the secrets live with regard to access, who has access to those secrets, where those are located, whether they are physical or virtual assets, and where they are used. The report should also include service and hosting providers that we are relying on (paid or donated).

Obviously, this report could contain some sensitive information so distribution of the audit report would be limited to CTC and TSC members (and any delegates necessary to help pull the information together). If it would be helpful to pull the report together, I can ask one of our nearForm interns to help.

@Trott
Copy link
Member

Trott commented Apr 17, 2017

If it would be helpful to pull the report together, I can ask one of our nearForm interns to help.

@jasnell Are you volunteering to lead this? Not trolling, honest question. If not, then step 1 is probably find someone willing to own it and push it forward. Barring that, figure an appropriate WG or other body to delegate it to?

If you are up for at least organizing it and keeping it on track (both distinct from doing the actual work), then awesome! This would be a great thing to have.

@jasnell
Copy link
Member Author

jasnell commented Apr 17, 2017

Yes, I'm volunteering to lead the effort. Obviously, however, I would need participation from the various WGs to pull everything together.

@rvagg
Copy link
Member

rvagg commented Apr 19, 2017

@nodejs/build maintains a private spreadsheet of its assets, including incoming small donation payments and purchases using those monies. We can extract just the asset list from that pretty easily if you have a place in mind for it to live?

@jasnell
Copy link
Member Author

jasnell commented Apr 20, 2017

@rvagg ... a shared google doc that is accessible only to current TSC members and anyone from the build WG that would be helping to compile the list would work and would be a great place to start.

@indutny
Copy link
Member

indutny commented Apr 20, 2017

@jasnell I can't really see any link anywhere in my inbox. Was I added?

@jasnell
Copy link
Member Author

jasnell commented Apr 20, 2017

I have not yet created the shared doc :-)

@rvagg
Copy link
Member

rvagg commented Apr 20, 2017

@jasnell I've shared the Build spreadsheet with you, perhaps it's an appropriate starting point for this stuff. My only concern is that it contains some details about donations that some folks have made they didn't do publicly and I want to respect their confidentiality. We can talk 1:1 about the details of this doc if you want more context.

@indutny
Copy link
Member

indutny commented Apr 20, 2017

@jasnell oh gosh, for some reason I thought that you mentioned it. Sorry!

@jasnell
Copy link
Member Author

jasnell commented Apr 20, 2017

@rvagg ... Thank you. It's a great starting point. re: confidentiality, the audit report itself will be limited strictly to voting TSC members. If there are specific details that should not even be shared at that level, then we should identify those. I'm not planning for the report to include actual $ figures. It's really just making sure we have a handle on what assets we actually have available and who is responsible for those.

@mhdawson
Copy link
Member

@jasnell @rvagg in terms of the softlayer assets should I send that info to you ?

@jasnell
Copy link
Member Author

jasnell commented Apr 25, 2017 via email

@mhdawson
Copy link
Member

Ok shared with @jasnell and @rvagg, I think $ amounts should likely be keep private but included in spreadsheet to give the monthly spend at list prices.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants