{"issue":{"user":{"id":1240282,"login":"jsamuel","url":"https://api.github.com/users/jsamuel","avatar_url":"https://secure.gravatar.com/avatar/bc1d195cedb959a3946572b08ce9e7c7?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"bc1d195cedb959a3946572b08ce9e7c7"},"title":"make initial setup window whitelisting less confusing","milestone":null,"created_at":"2011-12-22T05:17:27Z","labels":[{"name":"extension","url":"https://api.github.com/repos/RequestPolicy/requestpolicy/labels/extension","color":"ededed"}],"state":"open","updated_at":"2011-12-22T05:17:28Z","id":2633776,"closed_at":null,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"html_url":"https://github.com/RequestPolicy/requestpolicy/issues/15","body":"The initial setup window can be confusing by prompting users to choose regions that have corresponding pre-defined origin-to-destination whitelist items. It needs to be clearer to understand the impact that selecting regions has (sometimes it doesn't appear to change the box showing the items to be whitelisted), as well as which ones a user should select. An entirely new approach is not a bad idea.","number":15,"url":"https://api.github.com/repos/RequestPolicy/requestpolicy/issues/15","comments":1,"assignee":null},"comment":{"user":{"id":1240282,"login":"jsamuel","url":"https://api.github.com/users/jsamuel","avatar_url":"https://secure.gravatar.com/avatar/bc1d195cedb959a3946572b08ce9e7c7?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"bc1d195cedb959a3946572b08ce9e7c7"},"created_at":"2011-12-22T05:17:28Z","updated_at":"2011-12-22T05:17:28Z","id":3244853,"body":"[justin] Comments by email from Vitorio Okio (thanks Vito!):\r\n\r\n...\r\n2. Initial Setup window:\r\n   \r\n    2.1. It is my understanding that this window presents a user with a choice of Complementary Default Whitelists, one of which (International) is selected by default. However it is not clear to the user right away. I get the idea only after I asked you and you kindly explained it.\r\n\r\nPlease, note that I called them Complementary Default Whitelists to make a distinction between any of the lists selected in Initial Setup window and future created/defined User Whitelist.  The names surely could be shorten to Default Whitelists vs. Personal Whitelist.\r\n\r\nThere are additional questions that this window raises:\r\n\r\n- Isn't International whitelist \"international\" enough to cover all of the World?\r\n- Why one would want to add some of others if any? A little explanation here would be helpful.\r\n- What is the actual difference between these lists? When the user adds an additional whitelist where can he see and evaluate the need and the results of such addition? Currently the text box below is just a huge dump where everything goes. One cannot easily trace his additions to the default International list.\r\n\r\nSuggestions (IMHO):\r\n\r\na) It would be not a bad idea to make Initial Setup window a tabbed window. \r\n\r\nThe main/general tab would provide the user with concise introduction of the idea behind Complementary Default Whitelists, how and why to use them, and short explanation of the difference between Complementary Default Whitelists and the User Defined Whitelist, etc. \r\n\r\nEach of available new Complementary Default Whitelists then would be presented by its own tab, all similar to what the user sees now. Thus selecting a check box on a particular tab the user would see in a text box below only items that belong to this particular list.\r\n\r\nb) It would be good to give some more control to the user on each of these lists as well. E.g. \"Remove item\" button for each list.\r\n\r\nc) !RequestPolicy Preference window according with the suggestions above should make a clear distinction between User Defined Whitelist and Complementary Default Whitelists by either providing 2 different tabs or by providing a tab to the User Defined Whitelist only and either a link to Initial Setup Window, or a suggestion on how to access/review Complementary Default Whitelists, or both. \r\n\r\nHere I'm not clear on the best solution, since quite a number of options are available. E.g. the existing Whitelist button can launch a new tabbed window with the access to Users Defined Whitelist as well as Complementary Default Whitelists.\r\n\r\nd) Currently whitelist contains 2 fields \"Origin\" and \"Destination\" and sorted by \"Origin\". It would be very helpful to be able to re-sort by \"Destination\" as well, if need arises.\r\n\r\n2.2. There currently 6 whitelists presented for a user's choice.\r\n\r\n- The criteria upon which these lists are divided is a mixture of Part of the World and Country names. That introduces a bit of confusion. E.g. Americas vs. \"US and Canada\".\r\n\r\nOr \"Europe and Russia\"...  While politically Russia does not participate in ES, geographically however it is Part of European continent.\r\n\r\nOne may say that most of the Russian territory is located in Asia. Well, while it is true, it is also true that:\r\na) Russia always positioned itself as an European country;\r\nb) The European part of Russia occupies territory larger then all European countries together.\r\n\r\nWhen selecting a criteria base for whitelist categories, it seems better to stick either to Country names (a crazy choice IMHO) or to Part of the World names (way better and logical choice IMHO):\r\n\r\n- North America (instead of US and Canada)\r\n- Central and South America\r\n- Europe (this includes Russia, as per my note above)\r\n- Asia\r\n- Oceania\r\n\r\nIn case in the future you would deiced to add more granularity this gives actually quite a bit of flexibility. E.g. you can always split Asia to Middle East and Asia. Or you can always split Central and South America to 2 separate entities, etc.","url":"https://api.github.com/repos/RequestPolicy/requestpolicy/issues/comments/3244853"},"action":"created"}