-
Notifications
You must be signed in to change notification settings - Fork 2
/
voters.tex
49 lines (35 loc) · 1.59 KB
/
voters.tex
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
\chapter{Suggestions for Voters}
The following are several suggestions to think about before voting on
an OpenSHMEM proposal.
\begin{enumerate}
\item Actually read the proposal. Take time to think about it.
Socialize it with your colleagues.
\item Is this proposal just ``syntactic sugar'' for something that
could be implemented outside of an OpenSHMEM implementation?
\item Does this proposal represent a ``best practice''?
\item Is this proposal useful on a wide variety of platforms /
architectures, both today and in the conceivable future?
\item Are there applications that will use the functionality from this
proposal?
\item Is the use case for this proposal ephemeral?
\item Implementation issues:
\begin{enumerate}
\item Is there an implementation? Implementations may not be
{\em required}, but should be highly valued, especially for
``non-trivial'' proposals.
\item Does the implementation show a performance or functionality
benefit that could not be implemented outside of an OpenSHMEM
implementation?
\item Is the proposal implementable on a wide variety of platforms /
architectures?
\end{enumerate}
\item Proposal quality issues:
\begin{enumerate}
\item Is the proposal well-written?
\item Is the proposal too young? E.g., does this proposal represent
new work that may not yet have been completely vetted, thought
through, or simply had time to mature?
\item Is the proposal too old? E.g., has there been a significant
time lapse between its reading and/or ballots? (if so, why?)
\end{enumerate}
\end{enumerate}