Here are some examples:

• Root README is missing machine learning category of samples
• README in algorithms is missing repeat-until-success and sudoku-grover
• [README in diagnostics](https://github.com/microsoft/Quantum/blob/main/samples/diagnostics/RE

It would be good to update ParameterExpression.__eq__ to accept comparing a bound expression to a fixed value, but this can be a separate issue.

Originally posted by @kdk in Qiskit/qiskit-terra#5192 (comment)

Include a script that can generate weekly status reports to dev's leadership. The report should have enough buzzwords to make leadership feel as if progress is being made without providing any specific detail that defines said progress.

Running travis lint gives a bunch of warning. Like for instance, sudo : required is no longer needed, and Travis migrated to a new architecture. So the travis.yml file needs to be updated.

https://blog.travis-ci.com/2018-10-04-combining-linux-infrastructures

It would be nice to allow users to set a custom value for the tensorflow dtype if they are really pushing their simulations (and aware of the memory tradeoffs). This would be a very straightforward feature to add, most likely by adjusting backend_options to accept a dtype argument or something similar

See, e.g., the discussion below:

You could change this line https://github.com/XanaduAI

Most documentation comments in the compiler only use the <summary> tag. For short comments, this is fine, but in many cases the summary is several paragraphs long and would be easier to read if it used standard documentation tags to structure the information. This is especially important for exceptions - exceptions mentioned in the <summary> tag are easy to miss, whereas the special `<exceptio

Now, there's no unit test.

Describe the bug
If I provide Partitioned an array of length N and partition sizes of total length N, the return contains an extra partition of length 0 in the end. This makes it inconvenient to use: if I want to split an array into K parts of equal length ([example](https://github.com/microsoft/Quantum

It would be helpful to add a tutorial explaining how to run things in parallel (mpirun etc). There are some users who are not familiar with mpi (see #173 ) and it is useful to explain the basic steps to do this.

See attached files. The Python call accepts 0 and 1 as input qubit result types (putting them as Result.Zero and Result.One in Q#), but also accepts decimals and negative numbers without throwing an error. It appears that it rounds to whichever is closer, 0 or 1. So, when the argument is anything >0.5, it goes to Result.One, and anything =<0.5 is put to Result.Zero.

Side note: wildcard import

We need to create a Q.History documentation page that is similar in nature to the existing Q class documentation pages. See Q-ComplexNumber.html as an example.

Whenever a slide has minted code, like so:

\begin{frame}[fragile]{Example minted}
	\begin{minted}{python}
		from qiskit_aqua import run_algorithm

		print(run_algorithm(params)['result'])
	\end{minted}
\end{frame}

One is unable to add the \pagenumber before \end{frame} as it gets left aligned instead of right aligned:
![image](https://user-images.githubusercontent.com/1