The oslosphinx library is deprecated, so we don't need to sync
requirements to it any more. If we do need a release for some reason, we
can update the requirements by hand or just leave the minimums as they
are.
Change-Id: I296c212aa342cc022ba026ba29019bb3dae9c1d0
Signed-off-by: Doug Hellmann <doug@doughellmann.com>

- Is the library actively maintained?
It will be maintained by the mistral core team.
- Is the library good code?
It is reasonable, but currently lacking much content. The plan is to
expand the repository to become a "Actions library" for Mistral. We
will follow standard OpenStack development practices.
- Is the library python 3 compatible?
Yes
- Is the library license compatible?
Yes
- Is the library already packaged in the distros we target (Ubuntu
latest / Fedora latest)?
No
- Is the function of this library already covered by other libraries
in ``global-requirements.txt``?
No
- Is the library required for OpenStack project or related dev or
infrastructure setup? (Answer to this should be Yes, of course)
Which?
Yes, Mistral itself will optionally depend on it and TripleO will also
depend on it.
- If the library release is managed by the Openstack release process does
it use the `cycle-with-intermediary` release type?
It is currently `cycle-with-milestones` - I believe we will need to
change this. mistral-extra is currently released with mistral and
mistral-dashboard.
Change-Id: I2973d588901afab88809f2fb4f6d288e842984f7