Community
Participate
Working Groups
Created attachment 263535 [details] Account, Public profile tab, with annotations At the moment, there is no difference between mandatory and optionnal fields. We need to add a * to the mandatory fields. 1. Tabs "Public Profile", "Settings" and "Notifications The tabs are actually the same forms, split in 3 by topics to make it easy for the user to understand. Maybe the "Save button" at the bottom must be displayed in each tab, or just one time. Do what is possible. 2. Tab "ECA" This tab is a separate form, and so goes at the end. 3. Avatar The avatar is square, the choice of the size is up to the webdevs for performance. If possible, I would like to have an assistant for the upload, like other websites are doing. The user clicks on "Upload a file", the websites open a div on top of the page. It displays to choose an image, and an assistant to crop it and resize it to fit what we need. Not sure if the assistant should run on our server, or if we can use a .js app on the client side for that so we don't use our server to resize. 4. Personal information Nothing special here. Do we need to check that we know the organisation? 5. Display nickname I am pretty sure that for privacy issues or something like that, some users might prefer to display their nickname instead of their real name. This is also very common on other tech communities to use the nickname. So it makes sense to allow user to display it. 6. Location Only country is mandatory at the moment, can we please continue like that? If the province/state and city fields could depend on country, and be checked, that would be great. 7. Information A place where a user could put anything, even ascii art. Not possible to show that on the mockup (Wireframesketcher limitation) but this field should have a monotype font for the information area. This way users can add some fun stuff like ascii art or fake code/commands. No html allowed, no links. 8. Interests A taxonomy, we will have to manage it, there is a Drupal plugin for that (e.g to merge them if necessary.) Can we limit the creation of new interests to a category of users, like the committers, or people who signed the ECA? 9. Social Feel free to change the order (alphabetical, for example) What is better: ask for the entire urls, or just for the nicknames or accounts. So please do what you think it the best with Drupal. If possible, verify that the url exists, or complies with the standard of the websites. 10. Save As stated at the beginning, see if one is enough or if one per tabs is necessary We discussed that in order to save, the form will ask the password again. Technically, Is it better to ask the password when a user start to edit a field? or when he clicks on save? Both are fine for usability, so please choose the best for security. Do we need a cancel button to appear when the user is starting to edit something, but changed his mind? 11. Disclaimer Just a paragraph to tell that some fields are mandatory, why we are asking this information, and what we do with it (including non mandatory fields.) If we already have a page somewhere explaining why we ask so many information, we add the link here. Otherwise we need to write something about it.
(In reply to Antoine THOMAS from comment #0) > Created attachment 263535 [details] > Account, Public profile tab, with annotations > > At the moment, there is no difference between mandatory and optionnal > fields. We need to add a * to the mandatory fields. > > 1. Tabs "Public Profile", "Settings" and "Notifications > The tabs are actually the same forms, split in 3 by topics to make it easy > for the user to understand. > Maybe the "Save button" at the bottom must be displayed in each tab, or just > one time. Do what is possible. > > 2. Tab "ECA" > This tab is a separate form, and so goes at the end. > > 3. Avatar > The avatar is square, the choice of the size is up to the webdevs for > performance. > If possible, I would like to have an assistant for the upload, like other > websites are doing. The user clicks on "Upload a file", the websites open a > div on top of the page. It displays to choose an image, and an assistant to > crop it and resize it to fit what we need. > Not sure if the assistant should run on our server, or if we can use a .js > app on the client side for that so we don't use our server to resize. > > 4. Personal information > Nothing special here. > Do we need to check that we know the organisation? > > 5. Display nickname > I am pretty sure that for privacy issues or something like that, some users > might prefer to display their nickname instead of their real name. This is > also very common on other tech communities to use the nickname. So it makes > sense to allow user to display it. > > 6. Location > Only country is mandatory at the moment, can we please continue like that? > If the province/state and city fields could depend on country, and be > checked, that would be great. > > 7. Information > A place where a user could put anything, even ascii art. > Not possible to show that on the mockup (Wireframesketcher limitation) but > this field should have a monotype font for the information area. This way > users can add some fun stuff like ascii art or fake code/commands. > No html allowed, no links. > > 8. Interests > A taxonomy, we will have to manage it, there is a Drupal plugin for that > (e.g to merge them if necessary.) > Can we limit the creation of new interests to a category of users, like the > committers, or people who signed the ECA? > > 9. Social > Feel free to change the order (alphabetical, for example) > What is better: ask for the entire urls, or just for the nicknames or > accounts. So please do what you think it the best with Drupal. > If possible, verify that the url exists, or complies with the standard of > the websites. > > 10. Save > As stated at the beginning, see if one is enough or if one per tabs is > necessary > We discussed that in order to save, the form will ask the password again. > Technically, Is it better to ask the password when a user start to edit a > field? or when he clicks on save? Both are fine for usability, so please > choose the best for security. > Do we need a cancel button to appear when the user is starting to edit > something, but changed his mind? > > 11. Disclaimer > Just a paragraph to tell that some fields are mandatory, why we are asking > this information, and what we do with it (including non mandatory fields.) > If we already have a page somewhere explaining why we ask so many > information, we add the link here. Otherwise we need to write something > about it. It's now possible for users to edit personal information via https://accounts.eclipse.org/user/edit
