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

Information

• Qiskit Terra version: master
• Python version:
• Operating system:

What is the current behavior?

As pointed out by @HwajungKang, it is a bit tricky to figure out that the color wheels are more or less rotated by pi.

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

Describe the bug

After typing @, typing a letter or pressing Ctrl+Space shows completions for all identifiers and keywords, not just attribute names.

To Reproduce

Steps to reproduce the behavior:

1. Open a Q# file in Visual Studio Code.

2. Type @r in a namespace:

   namespace Example {
       @r
   }

3. Code completion shows identifiers that

Now, there's no unit test.

Is your feature request related to a problem? Please describe.
Many of the unit tests in the Q# standard and domain-specific libraries predate the existence of the new @Test() attribute, and should be updated. The legacy method of discovering tests (namely, functions and operations in allow-listed names

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.

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.

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

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