Updating issue template and missing docs

.github/ISSUE_TEMPLATE/documentation_request.md

@@ -7,29 +7,15 @@ assignees: ''
 
 ---
 
-## Report incorrect documentation
+## Report incorrect or missing documentation
 
-**Location of incorrect documentation**
+**Location of documentation**
 Provide links and line numbers if applicable.
 
 **Describe the problems or issues found in the documentation**
 A clear and concise description of what you found to be incorrect.
 
-**Steps taken to verify documentation is incorrect**
-List any steps you have taken:
-
 **Suggested fix for documentation**
 Detail proposed changes to fix the documentation if you have any.
 
----
-
-## Report needed documentation
-
-**Report needed documentation**
-A clear and concise description of what documentation you believe it is needed and why.
-
-**Describe the documentation you'd like**
-A clear and concise description of what you want to happen.
 
-**Steps taken to search for needed documentation**
-List any steps you have taken:

.github/ISSUE_TEMPLATE/feature_request.md

@@ -7,14 +7,22 @@ assignees: ''
 
 ---
 
-**Is your feature request related to a problem? Please describe.**
-A clear and concise description of what the problem is. Ex. I wish I could use cuGraph to do  [...]
 
-**Describe the solution you'd like**
-A clear and concise description of what you want to happen.
+**Describe the solution you'd like and any additional context**
 
-**Describe alternatives you've considered**
-A clear and concise description of any alternative solutions or features you've considered.
 
-**Additional context**
-Add any other context, code examples, or references to existing implementations about the feature request here.
+
+
+
+---
+_For Developers below this line_
+
+  - [] Code passes CI
+  - [] Code uses Graph Primitives
+  - [] Code in C++/CUDA layer
+  - [] Code in C layer
+  - [] Code in pylibcugraph Python layer
+  - [] Code in cugraph Python layer
+  - [] Documentation
+  - [] Test cases at each layer (for MG tests, a note in the PR description indicating the new/existing MG tests were run and passed)
+

.github/ISSUE_TEMPLATE/question.md

@@ -7,4 +7,4 @@ assignees: ''
 
 ---
 
-Ask a question that could be converted into a feature or enhancement
+Ask a question

docs/cugraph/source/api_docs/sampling.rst

@@ -11,3 +11,5 @@ Random Walks
    :toctree: api/
 
    cugraph.random_walks
+   cugraph.ego_graph
+   cugraph.experimental.dask.uniform_neighborhood_sampling

docs/cugraph/source/basics/cugraph_ref.rst

@@ -28,6 +28,13 @@ Betweenness Centrality
 
 Katz
 
+- Katz, L. (1953). *A new status index derived from sociometric analysis*. Psychometrika, 18(1), 39-43.
+- Foster, K.C., Muth, S.Q., Potterat, J.J. et al. *A faster Katz status score algorithm*. Computational & Mathematical Organization Theory (2001) 7: 275.
+
+
+
+K-Truss
+
 - J. Cohen, *Trusses: Cohesive subgraphs for social network analysis* National security agency technical report, 2008
 - O. Green, J. Fox, E. Kim, F. Busato, et al. *Quickly Finding a Truss in a Haystack* IEEE High Performance Extreme Computing Conference (HPEC), 2017 https://doi.org/10.1109/HPEC.2017.8091038
 - O. Green, P. Yalamanchili, L.M. Munguia, *Fast Triangle Counting on GPU* Irregular Applications: Architectures and Algorithms (IA3), 2014
@@ -36,6 +43,18 @@ Hungarian Algorithm
 
 - Date, K., & Nagi, R. (2016). GPU-accelerated Hungarian algorithms for the Linear Assignment Problem. Parallel Computing, 57, 52-72.
 
+
+Leiden
+
+- Traag, V. A., Waltman, L., & Van Eck, N. J. (2019). *From Louvain to Leiden: guaranteeing well-connected communities*. Scientific reports, 9(1), 1-12.
+
+Louvain
+
+- VD Blondel, J-L Guillaume, R Lambiotte and E Lefebvre.  *Fast unfolding of community hierarchies in large networks*. J Stat Mech P10008 (2008)
+
+
+
+
 | 
 
 |