adding licensed tree

[craigsteffen]

This branch is instantiating the licensed software tree in the main index so that it can be populated, integrated, and tested against everything else.

[craigsteffen]

@rmokos I accidentally left this behind.

I have several branches that I need to revive, get composed, reviewed, and then rolled into the main branch. Do you have any other software that should be added in the next few weeks? I guess Matlab, now that we have a site license? Anything else?

[craigsteffen]

@greghbauer @rmokos
I'm sweeping up a bunch of documentation efforts that got assigned to me but then I left behind. This is probably the oldest one.

I have branch with an instantiated page for "licensed software". It's here on this branch:
https://docs.ncsa.illinois.edu/en/set_up_licensed/software/index.html

Currently it has one page instantiated for Gurobi optimizer. That just has one sentence in it.

It has single-sentence boilerplate pages for ansys, abaqus, fluent, and matlab (they're named as .txt files; you'll have to look in the repo, they're not on the page. We can instantiate and flesh out any or all of those, or leave them out.

Let me know if there's a minimum viable set of descriptions that you'd like to have on that page before we roll it into the proposed_changes and then out into the public main.

Craig

[pmenstrom]

I'm not sure what licenses should be listed but it might be nice if there were at least a few listed to start with.
The first line seemed a bit terse, maybe change it to "Listed below are packaged Third-party software available on NCSA computing resources."
In the Gurobi section, should there be an explanation on how to get/use the license?

[craigsteffen]

@pmenstrom
Yes to all of this. There are five placeholder pages in there (four of them named with .txt instead of .rst files so they don't show up in the built page) all of which have single-line boilerplate descriptions. I suspect generated by Lillian.

I'm pinging Ryan (and maybe Greg) to get a feel for which things they'd like to have actually listed and at what level of detail, so that we can target that threshold before bringing this into the main documentation pages.