-
Notifications
You must be signed in to change notification settings - Fork 2
/
todo.txt
113 lines (81 loc) · 5.24 KB
/
todo.txt
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
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
- USE SES
Amazon Ec2 installation:
- yum update
- yum groupinstall "Development Tools" (may not be required)
- yum install libxml2-devel libxslt-devel (for nokogiri)
- gpg2 --keyserver hkp://keys.gnupg.net --recv-keys D39DC0E3 ( trust the rvm guy)
- \curl -sSL https://get.rvm.io | bash -s stable
- source ~/.profile
- rvm install ruby 2.1.2
- rvm alias create default ruby-2.1.2 (set the default ruby)
- sudo yum install nodejs npm --enablerepo=epel (for js-runtime)
- sudo yum install nginx
- bash --login (so that I can use the ruby)
- yum install postgresql-devel
- gem install bundler
- ? install postgresql 93 (yum install postgresql93) ?
- `createuser rulebooktestuser -h unisoftdbmaster.cdotscaeyshe.us-west-2.rds.amazonaws.com -d -P -U robindunlop`
- write these credentials into the database.yml
- then `RAILS_ENV=stage bundle exec rake db:create`
- install redis via script/install_redis.sh
- copy nginx.conf.template to /etc/nginx/nginx.conf
- copy database.yml.template and secrets.yml.template to /home/ec2-user/unicycling-rulebook/shared/config/
- cap prod deploy
- bundle
- rvmsudo bundle exec rails s -p 80 -e production
Allow SuperAdmin:
Known issues:
- Fix that some discussions have no associated committee (but they _do_ have a proposal?...bad migration?)
- Word-counting of Revision text is broken (it always sayss 500 characters remain)
Friday To-Do:
-Brakeman
- Update FAQ to describe that "you do not get e-mails for votes when you have submitted your vote"
- Only Voting members receive e-mail about voting?
- Update "Table" to include a description?
- Create scopes for the "vote_submitted" mailer search lists (like: voting_members, voted_members, etc)
- address some of the rulebook software issues (See Jan23 E-mail)
#####- Add ability for Admin to adjust the admin status of another user.
- Mass mail issue when sending e-mail: "Any new proposals for the rulebook must be submitted by November 27th (that's the day before thanksgiving)"
- Include the Rulebook Name in the "New Committee Applicant" e-mail
- Add ability to "open" a "Closed" discussion.
- Add option to "auto-enroll" people to a given group (include option about whether they are a voting member by default or not)
- Add freeform text box to application
- "Do not send me e-mails"
- "send me e-mail once a week"
- Can I change it so that the system sends e-mails based on the 'read-ability' of objects, instead of the relationship. (thus all super-admin would get ALL e-mails).
- Add interface to allow people to modify these settings for themselves easily.
- Update the e-mails with a footer which talks about how to modify these settings
- Receive e-mails for comments/proposals/votes options
- Remove indication of who-voted-what based on Olaf.
- display "who voted" for admins
- Hide the voting results while voting is in progress.
- Add indication of percentage:
- Add indicators to show whether the proposal will pass/fail based on the quorum rules.
- Display indicators which say that "Your name will not be displayed along with your vote."
- Clean up the redundant code in the tests....really nasty duplication
- Add unit tests for user:is_in_committee/etc methods
- Add Conf table which allows admin to specify the time-delay for many things
- Send an e-mail to the admin whenever a new application is receieved.
- Add Conf table which allows admin to specify that new applications are no longer accepted?
- REVOKE my gmail password, and create a new gmail account for using?
- Ask Olaf which statuses should "PUBLIC" be allowed to see proposals....Passed? Other?
- Ability for public to "read" proposals that have "passed".
- Ability for public to "read" proposals and comments while they are in progress. But not comment. Configurable?
- Learn why self.number_of_votincg_members gives me private/public error
- Write up the usage for the system, and how it can be configured.
- Please allow 30 seconds when you first load the page....it may take a few seconds before it comes up.
- list all committees in the "sign up" form, and allow people to enter their preferences when signing up. (perhaps as freeform text?)
- only display voting info to members
- create a conf table, to configure the instance with the expected names/etc?
- Update the _end_date properly
- permissions to restrict who can do what to what object
- Move proposal logic into the model
- Change to use 'thin' server (as per heroku documentation https://devcenter.heroku.com/articles/rails3)
- If I am not a member of any committees, put a message on the 'new proposal' page to say "e-mail the chairperson"
- Only allow proposal to be view by: admin, owner, (committee-member AND if the proposal IS NOT submitted.)
- From Proposal-view, should be allowed to 'edit' proposal in various ways (Approve, Table, un_table, change-votes,change back to pre-voting, change dates, change committee)
- Mock Time.now, and pass it around, to eliminate 'fuzzy-matching' when checking timestamps.
Instructions:
- Create a Single Committtee
- Q: Should I auto-assign new people to the committee, or require (like now) that the administrator assign them to the committee, and determine if they are a "voting" member.
- Q: Should we restrict the time that the committee is open for new registrants (right now, it has a hard-coded date which disables the sign-up form)