|
⇤ ← Revision 1 as of 2017-11-09 15:28:34
Size: 1673
Comment:
|
Size: 2679
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| # Milestones | = Milestones = |
| Line 3: | Line 3: |
| ## 1 - Login username/password flow (DONE) ## 2 - Present settings in settings view |
== 1 - Login username/password flow (DONE) == == 2 - Present settings in settings view == |
| Line 22: | Line 22: |
| ## 3 - Change settings in settings view | == 3 - Change settings in settings view == |
| Line 25: | Line 25: |
| ## 4 - Account registration When this milestone is complete, it's possible to sign up to make a one time or regular donation or create a new volunteer account via the http://my.fsfe.org/ website. The flow for this needs to be mapped out a bit more in detail.. |
== 4 - Account registration == When this milestone is complete, it's possible to sign up to make a one time or regular donation or create a new volunteer account via the http://my.fsfe.org/ website. The forms are largely there already. but the processes will look a bit different: * When signing up as a volunteer, the form is in register/volunteer.html (but please REMOVE any mention of local groups or teams to join here. let's keep it simple). * When signing up as a supporter (financial contributor, even one time or regular), the form is in supporter/form (here too, remove local groups and teams). When a form is processed, it should call fsfe-cd with the data provided, and fsfe-cd in turn should wrap this in a JSON structure and call an executable (which I'll provide). The API calls in fsfe-cd need to be adapted for this. When creating an account, it's vital to check if an account with that email already exists! If it does, the user should be given a notice about this and be asked to login using email. This doesn't apply to one time donors though; if an entry exist for one time donations, we should simply call the executable with the new information and the executable will deal with matching this to the existing account. |
Milestones
1 - Login username/password flow (DONE)
2 - Present settings in settings view
When this work is completed, someone can login to https://my.fsfe.org/ and see their current settings, address, etc, retrieved from the fellowship database. This requires implementing an API call from ams-front to http://fsfe-cd/api/fellows/ to get the information relevant, and fsfe-cd needs to be passed appropriate authentication parameters with it (taken from the User object of the logged in user, specifically the access code and id token).
The parameters which should be published and be able to be viewed in this pane include:
- Backup email
- Title
- Full name
- Street address
- Post code
- City
- Country (select box)
- Language
- Birth date
- Opt-in to communication from the FSFE (checkbox)
3 - Change settings in settings view
When work on this milestone is completed, it's possible to not only view the information in the settings page, but also change it. The same settings as those in milestone 2 should be changeable. This requires implementing a new view in fsfe-cd to handle changing data. When an API call to change information is received, the entire data object should be wrapped in a json structure and an executable called with this information on stdin. That executable is then responsible for actually doing the change in the database.
4 - Account registration
When this milestone is complete, it's possible to sign up to make a one time or regular donation or create a new volunteer account via the http://my.fsfe.org/ website. The forms are largely there already. but the processes will look a bit different:
- When signing up as a volunteer, the form is in register/volunteer.html (but please REMOVE any mention of local groups or teams to join here. let's keep it simple).
- When signing up as a supporter (financial contributor, even one time or regular), the form is in supporter/form (here too, remove local groups and teams).
When a form is processed, it should call fsfe-cd with the data provided, and fsfe-cd in turn should wrap this in a JSON structure and call an executable (which I'll provide). The API calls in fsfe-cd need to be adapted for this.
When creating an account, it's vital to check if an account with that email already exists! If it does, the user should be given a notice about this and be asked to login using email. This doesn't apply to one time donors though; if an entry exist for one time donations, we should simply call the executable with the new information and the executable will deal with matching this to the existing account.