News for hackers. Stuff that matters.
Re:Code.mil – An experiment in open source at the Department... by conorcleary on Saturday February 25, 2017 @10:49AM (#13732011)
> The system I'm working on has Python as a build dependency. The devs are creating reports using Jupyter notebooks.

Hi, just wondering if someone could explain these points here. I don't know enough about either to know what the implication is or what the OP means.

Re:Code.mil – An experiment in open source at the Department... by stinkytaco on Saturday February 25, 2017 @11:03AM (#13732093)
Not OP, but my assumption is that despite the concerns about open source, they are still using open source tools like Python and still collaborating using non-DOD approved tools like Jupyter (also open source). But correct me if I'm wrong.
Re:Code.mil – An experiment in open source at the Department... by engi_nerd on Saturday February 25, 2017 @12:11PM (#13732496)
OP here. The implication was that the organization cannot deliver consistent guidelines. The devs of the sim I am working on are using Python and Jupyter on their systems, which were accredited and approved in the exact same fashion that I need my corresponding data analysis network approved. However, the IA professionals -- who are the same people who approved the sim dev systems -- are telling me that my request for Python (actually I'm requesting an enterprise license for Anaconda Python distribution) is problematic for the reasons I spelled out in my original post.

Consistency, clarity, and understanding are what I'd like. But, these same IA people also get confused when I mention "highly technical terms" like the size of the SAN I'm planning on using.

Re:Code.mil – An experiment in open source at the Department... by conorcleary on Sunday February 26, 2017 @01:16PM (#13738675)
Thanks for the explanation!

As an aside, I dunno what a SAN is either ;-)