-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
infopages and licenses for neurohub resolves #1010, #1233 #1234
base: dev
Are you sure you want to change the base?
Conversation
Maybe we should rename the :
To match the other |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
@MontrealSergiy never mind I put the license in the right place but forgot to setup with the interface. |
This comment was marked as outdated.
This comment was marked as outdated.
@natacha-beck pull the latest code for these issues |
Just a quick question, not sure it is the way it should be. If you have a |
for _info page no special checkbox logic is foreseen I just do not see need, because it is info page, the less red tape the better. |
Not sure. The *.html file that is used for the |
I see notion of info page a contradictory to elaborated checks. Checkbox checks seems utterly useless at the moment, without any use case. I would go with Yagni approach until situation. Generally specking, the form on info page is likely have check-boxes unrelated to CBRAIN but another website, such as a maillist server, so I would like avoid any risk here. Personally, I would not even require to click 'continue', though it would diverge from Pierre original suggestion. So I guess my aversion to checkbox checks is as I expect stakeholders eventually ask to relax even Continue box logic. Yet, checking check-boxes might makes code slightly simple, so if you insist I could do it, just confirm. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My review is not finish but I want to send out this first batch of comments.
@MontrealSergiy and @bryancaron is it still needed ? I think we have what was needed for the Newsletter ? Not sure if this PR add something else we need ? |
@natacha-beck I'm going to review this. |
@MontrealSergiy Can you please rebase this PR? It's conflicting with the current |
dbfd05e
to
20f5b26
Compare
rebased |
I found many bugs. I'll document them one by one in separate post. First, I'll describe here my testing setup:
File:
File:
File:
This last line with four ruby statements I keep around, ready to zap the user's state just by doing up arrow and return.
I will document the bugs now in new posts. |
BUG-1The first license shown can be agreed to by clicking any of the two checkboxes (the one in the license text or the one provided by the NH interface). The two checkboxes don't even have the same |
BUG-3I can agree on the second license ( |
BUG-4I can find no way for a user to review the licenses they have signed. There are no links back to read them again. If I try to manually go to |
BUG-5In fact, going to |
BUG-6The url |
BUG-8In the controller code, there is no validation at all that the value
Please change the routing system to return to the standard single token matching in the routes ( |
I will post more comments in the code now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See comments
I have two more general changes to request: Request-1Change the convention for neurohub licenses to be prefixed with "neurohub/" and to be in a subdirectory called "public/licences/neurohub". Instead, the NH licences should simply start with "nh_". E.g. Request-2The license input box in the portal's SHOW/EDIT page should have some information for the administrator about the license conventions. |
Request-3All code returned to the original state before the pull request state should stay identical (no changes in white space, blank lines etc). The DIFF page here in the pull request should only show the minimal amount of changes necessary to implement the function of the PR. |
well, due reiterating requests to refactor something I can factor few lines of sign license action to code a User model, and perhaps, checkbox number checking into a protected method, what do you think?
|
@prioux I am trying to rebase to fix conflicts of the new version. Is there a recommended way to handle or regenerate cbrain_file_revisions.csv file ? |
03210d8
to
98fa023
Compare
Problems and requests addressed, I think I did however a minor a straightforward refactoring, hope it is fine but easy to roll back if you dislike it. |
I also fixed a project license styling issue reffered at #1318 but can put it in a separate PR if needed |
@bryancaron Current flow - license, info-subscription page that starts with nh- prefix, and for info/subscription _info suffix are shown to user Users see that subscription/infobox/license when
If you want to add user during NeuroHub signup and (perhaps after email validation), it is best to resuscitate March 2022 API version, https://github.com/MontrealSergiy/cbrain/tree/email, especially if you like to avoid duplicate email validation for the account and for mailing list subscription UPDATE: as per discussion at NeuroHub meeting April 12, no need for API, at the least as the first step form-based registration is ok. |
Newsletter licence to agree by the user |
A gentle reminder that the requested changes and problems had been addressed a while ago. As discussed, license folder is flat while neurohub licenses are marked with nh- prefix (using hyphen rather than underscore) The verbiage on Envoke list is changes though slightly differently from what Mai asked |
see #1010, #1233
this work is motivated by request to add a newsletter subscription form, the form is from envoke.com mail campaign server.
current motivation is to add Envoke subscription form, tell me, Bryan or James if need Envoke access, but be careful with it, it has no test environment.
Example html of info page can be provided on request, or downloaded from https://mcgill-my.sharepoint.com/:u:/g/personal/sergiy_boroday_mcgill_ca/ERTHRklcJHpEg_TNA5Y7UfQBKCMSESCyAKoHIINuwTdKpQ?e=Drrcv0
The old wiki on licenses is https://github.com/aces/cbrain/wiki/Custom-Licenses
Probably to be modified after the feature is deployed
Note, when replacing new licenses with old on a resource, the information about user signing old licenses might be deleted (I did not remember all quirks of that feature)