Modules Interviews - Anonymized

	A	B	C	D	E	F	G	H	I	J	K	L	M	N	O	P	Q	R	S	T	U	V	W
1	Participant number	P1	P2	P3	P4	P5	P6	P7	P8	P9	P10	P11	P12	P13	P14	P15	P16	P17	P18	P19	P20	P21	P22

2	Background Questions (2 min)
3	Can you tell me something more about your background?	All drupal company - spend my every moment of work with Drupal	Technically speaking - hobbyist. I touch upon a lot of Drupal concepts in Sales.	Client advisory, Drupal Support, used to do freelancing	Site building since dawn of time, do a lot of support right now - including maintainence. Work on technical editing around D7	Content creator/ amateur site builidng - HTML, CSS, modify slightly templates. Regularly evolved in the modules evaluation ...	Most of my day is managing clients from newbies to experts and guide them for project, problems. I have a different background was an engineer and switched to Drupal	Come from web middleware environment, 3 years started working with Drupal 6 - primarily a web architect, I have built sites using Drupal interface, enable modules, but wasn't coding to it - would work with designers and programmers for changes. Now, in support	Intranet, personal sites	Started Drupal in 2009. Site Building. Contributed and maintain a module and patch for D7.	Experienced in module & theme development as well as managing the entire application stack (linux, memcache, varnish, apache, mysql).	I have a software development background I'm new to Drupal and teaching myself. It's been an interesting experience. Haven't got live yet; probably soon. I'm the only tech person.	Site builder, limited php, work on client facing sites	Developing modules and functionality for the site admins that use our sites.	I consider myself a beginner. I know HTML & CSS and a bit of AJAX & JS. In Drupal I only know how to do SIte Admin tasks using the GUI	Project management and development of Drupal projects, using D6/7	I am a brand new user of Drupal. I'm just beginning to figure out how to make websites	I have used Visual Basic, Java, Javascript, ASP, Foxpro, Clipper. So program 20 years now.	The most important is that I build Joomla for 6 years now.		I am working in webdesign for 10 years. I have learned it myself.	Drupal dev since 2006, tech savvy, site building, enable and disable modules. I now use Drush but when want to see dependencies and browse the modules page.	Flash developer, but also doing more web development. Themed my own site and build a very tiny module.
4	Can you tell me what you do with Drupal?										D7	Avoided doing stuff under the hood, mostly been selecting appropriate modules and theming based on Zen. Using a couple dozen modules.		Mostly backend development	Built 2 sites in Drupal. Mainly installing and configuring modules and themes.	Anything from modules, to views, building elements for display suite, theme creation and module assessment	So far I just use the most basic functionality.	I do module development, build websites and developing a hosting platform.	With Drupal I build my first site now. and investigate if I want to use Drupal next to Joomla.	experience in configuration, theming and of developing custom modules.	I build websites, iphone module apps and interactive installations. I do design, install, configurations, and sometimes an small module.		Maintain a personal website, and projects where you are part of a community, where you need a few more functionality that normal. A particular functionality is for example, permissions.Maintain a website for a non-profit artist organisation.
5	Which version(s) of Drupal do you use for projects now?	D5,6,7 (mostly 7)	Two in D6 and just playing with D7 and DG site	4.7 to 7	4 something onwards, mostly working on 6 and 7 now.	5,6, 7	Drupal 6 and 7	D6 and D7	Drupal – Since 2007 – D7	mostly use D6	Starting using Drupal for CMS needs around D4.7.	Started withed D6 but quickly migrated to D7.	6 and 7	D6 primarily	D6	D6 and D7	D7	I use Drupal 5, 6, 7, and I have a Drupal 8 patch.	I only use Drupal 7.	Started with Drupal 5.	Sinds Drupal 5	6 mostly but also 7	Drupal 6 and Drupal 7
6	How long have you been using Drupal?	3 years	since 3 years - not continuously everyday	5 years	8.5 years	6 years	Since 2003. More involved from 2007.	3 years	Since 2007			About a year	2 years	4-5 years	4 months	4-5 years	A couple of weeks	Six years.	For 3 weeks now.	5 years of Drupal	6 years		4 years
7	Current Usage (10 min)										See each module's status, version, and interdependencies. Alter module status: enable, disable, and uninstall.
8	Can you describe what are the things you do with the module page?	lot of scrolling, enable/ disable, uninstall (really stupid - it is called unistalling but it is deleting from db... you would expect it to disappear.. but I can reinstall) Have problem with "uninstall" and the functionality - both. configure, set permissions, often read about the module - description	The page needs to remember the collapsable pointers - where I left it the last time. How to configure,enable/ disable, check dependencies	enable/ disable, check which are enabled and uninstalled modules	Less now than before (using the moduels page). I use Drush now but it is not good in telling to the dependencies are... more often I do the most go to the page to see what is installed and how things are set up... because it is a lot to do with support... enabling and disabling module.	Download a module / sometimes I usually drush module/ and sometimes I try to fix the permissions/ sometimes I forget to configure/ read me is not usually helpful.	I would install modules-sita modules it allows me to complete search at a glance. Search box is very helpful. Find quickly the dependencies of the modules. Really interested in seeing the colors (As of now). Running update script	Will talk about D7 - enable a module, browse through available module, disable, very often look for configuration links, install new modules now I dont do that anymore. Verify the version of the module. I used to click through the permissions of the module. Uninstall a module. These days 20% of the time, I use on this page and the rest of the times I use Drush.	- Enable Modules - Browse Modules	enable and disable a module, use it when I clone a site, often enable and disable a collection of dependencies module. disabling is painful and have to refresh them. debug a problem without going to debugging them and tracing the error and what module is implementing the hook that bothers the site. Use Drush. I dont use the modules page a lot anymore, it is usually drush. Depends on what is easy.	Fair to Poor	Upgrade from one realease to another, though I've learned about Drush. I'll use the admin UI and drush interchangeably. I link to configuration options/permissions.	Turn on and off, look at versions,	Enable and disable modules. I will also come o the page to check if updates are available.	Enable and disable modules. Use the "permissions" and "configure" links.	Turn modules on and off, in D7 the links to settings, to check wither a module is installed or not	Use checkboxes to turn on and off functionality on my site. I also use the information listed to see what is required.	In Drupal 7 I sometimes click on the settings links, I'm happy with that, sometimes it's a lot of search to find de settings page of the module. That's a good addition in D7. Since I use Drush I hardly use the modules page. Drush enable, download, uninstall from the commandline. I use the configure and the permission link.	I have tried to install and configure wysiwyg editor and changed a few settings of the filter module. And I have looked at the update manager.	With the module page is turning module on and off. Settings and persssion with the old method. Sometimes I use the links, its handy, but not common practice. So mainly on and off.	In Drupal 6 I only used the module page for enable and disable. In Drupal 7 I don't use the installation option. In Drupoal 7 I don't use the link to the configurations page.	seeing the dependencies (mostly), search the modules. Ctlrl - F -> it is not great, list as dependencies is difficult.	Try to find the version number of a module, for specific problems. And in some cases enable and disable to troubleshoot modules.Use CNTRL-F to find a module. After install, to enable.Sometimes to find the setting pages.
9	How has this experience been so far?	Horrible - Modules named poorly Description are verbose The biggest pain point I have is - mod and sub modules and you want to disable a module, it could be multiple level of scrolling Enable a module to understand what the module does Description - A B C D E (dependent B-D, C-E). You should be able to disable a parent if the children are enabled.	The biggest problem is that too much scrolling. I find myself collapsing the groups to find what I want. THis is a page that I dont want to mess with. There is just too much scrolling. I wish I could collapse the CORE and let it be collapsed the next time i come here.	I usually use drush. It's faster. Modules page loads faster.	It is a pain in the ass. On multi site, large code bases, sharing code base, you have to scroll ... find with overlay... and depends on the browser... sometimes it is inconsistent on the browser... how it interacts. There are bugs on the page (like if you have chain of dependency, module X on Y, but confusing when Y on Z.... May be its fixed right now. I dnt know.	The modules page is fine. SLOW. Hate going to that page because it takes too long to load. does good to job of dependiences. What is less obvious is to disable ... it does not tell what else I need to disable. Disable in two steps. How would you expect? Probably faster, AJAZ< Check box solution, I expect Drupal to know the dependencies. Tell me before I make the decisions. INFORM ME.	A lot of time doing search, and doing ctrl F, I am trying to type and beginning the name of the module -> but there would be like 200/300 modules... collapsing the field set ... Page is not handy so we use Drush.		o The core modules are clumped together that is useful, others are not organized in the right groups. DG has core, contrib. – that is good. The sub-modules are confusing	Sometimes it is really slow for sites that have a lot of modules. sometimes there are people are cautious to add a module.	Everything on one page; since D7 including links to permissions & configuration	Better with D7 than D6. The the upgrade the release of a particular module in the UI is a nice feature.	I don;t like it, difficult to search, categories - dont map, enabled/ required - is nice to have... use ctrl + F... I hit all the others places that a module (Dependent)... A giant page...Names on the D.O. are different from the files that are on the modules .. may be I wrong...	Needs some improvement.	D7 is better than D6.	Getting better with every release; it's good but somethings could be done with fewer clicks	There is a lot of information on this page, but its easy to understand.		My experience with installing the wysiwyg is that it is not clear. Most of the documentation is for Drupal 6 and how to set up is not very clear. With the module page I think it will become unclear when a lot of modules are there. There is a no differentiation between the functions within core. I have only used Core. On the configuration page, there is a grouping, on the module page there is not. If it is grouped by function I can skip some. On a long list it will be a lot of scrolling.	Turning off is difficult, with deeper laying modules where other modules depend upon, need to turn of 4 times. Turning on is easyer if the moduels are on the server. Sometimes it is difficult to find a module, especially if you have more modules. It would be handy if the desciption would contain the module systemname, if I want to go to drupal.org. Now I need to do inspect element to find the name. A better integration with drupal.org would be handy. It is not always clear in which category I can expect a module. Sometimes in other, not very clear. The reason for enabling modules on this page is that I had two occasions by which I enabled module via Drush, but I had some strange unwanted behaviour. Finding disabled modules, I do no the module page, in the file system a module is avaible, find the modules on the page that, they are not checked.	Enabling is easy, but when building a large site I loose overview, I scroll and don't collapse fieldgroups. Is would be handing if it remembers the fieldset collapse/expand status. I usually use the status module, but opening the modules pages sometimes takes very long because it checks in the background if new releases are available. That is annoying I use the page often to check which version of the module is on the site. Sometimes I start the update script from the module page.	search is not effective.	In general difficulty with just the overview.
10	Is there anything that you like?	Easy to enable multiple modules at a time Helpful to provide the version of the module Like to branch off and config and permissions after I have enabled a module.	Visually appealing - no concerns of set up - the layout Like how they group.	Shows dependencies. Getting better in D7... external requirements are shown. Intermodule dependencies is good.	Not particularly		I like - configure link next to the module ... and the colors are different for the dependent modules		o Modules like page – link to the config on the modules page. And help is good too. BUT config is great	Pretty good information on dependencies once you know how to use it.	Layout & grouping can be esoteric. Lots of scrolling. Unsortable. Historically poor page-load time. If I check or uncheck something there's nothing to indicate that the state has changed before I click submit (e.g. on a site I'm unfamiliar with and everything blends together when there are 350 modules enabled).			I like the groups and I like that I can see dependencies. In D7 I really like the "operations"	I like that one I enable I can imediately click a "configure" link. It helps figure out where to go next. Same for permissions link. Also likes the "help" link.	There's nothing that stands out as awesome or amazng; it's functional. i like the fact that it categorizes	The groups are helpful. Also, the zebra stripping makes it easier to use.		The description and what is enabled and disables are good.				Nothing in particular, maybe the setting links
11	Is there anything you dislike?	Use of groups (field sets) is jargon - the average user does not care about. The avg. cares about the task. Core or contrib. Some users may use it. Do not use Drush	want it to be easier to scan. Once I enable a module, I dont want to see them again. Once I enable a module, I dont want to see the desc. Its all the space Save is all the way down... but there is so much scrolling	It's slow. There is a contrib modules that people use with vertical tabs and search elements - but I hate it.	Inconsistency how things are grouped. Because it is dependent on the module maintainer... it is not easy to tell where to find that module. HOw Do you find a module? It is hunt and peck. If I have multiple version of module in the code base - it is difficult to find which one is active and drupal is paying attention to it.		Ctrl F to search, have a hard time to find, I dont have the time to find a module,	Design, Groupings don't make sense, Browsing is tedious and there is no filter - tags associated (community agreed terms), name of the modules, what needs to be updated, I would expect to update the modules from here than the status page. Want CSV export to download and no ability to take a snapshot and recreate that. Revision history is missing - that is destructive.			Mostly use this page to find details about interdependencies. While it's important to have the actions on this page, I'm more likely to use Drush to actually perform the actions, because the page load time is so terrible (providing that I have access to the filesystem).	It would be helpful to also have on the same page what the current recommended release is.		Dependencies are "unweidy"; "Not easy to search; you need to know what bundle/group something is in; Difficult to "browser search" on a term because it may be a dependency and therefore listed over and over.		Someimtes there's inconsistencies, like settings are there or not, the fact that you have to navigate away to get to the settings (should be same time), [check recording]	There are no instructions at the top of the page .. that might be helpful.	I would like to have to have an operation to disable and uninstall modules in one go. Sometimes I am annoyed by the categorisation of modules. I do like to search on a category. for example I search for a module related to Views, do I search under 'Views', but some module place themselves under 'Other', that annoyes me. A better broader classification would be better. I don't know how. An other thing I don't like, some modules have a long list of modules it depends upon, it is a cascading dependency, it is too much. Not only its immediate dependencies, but also the dependecies of the dependencies are listed. I think for an ordinary user this will be difficult.	The requirements are long list, and it may be hidden under a mouse over. I don't need it immediately.			stuff that i mention, the fieldset could be bigger, dependencies hidden by default	Difficulty with oversight, I always start with closing things that don’t matter. Untill I find the interesting candidate, when I don’t know the name. Always close the general ones, Media, Core – always look trough Other. Cntrl-f use when I know the name. Bad experience with module permissions.
12	For you, what are the important tasks on the module page that you do? The tasks could be based on their critically or frequency.		Now, I have started using Drush. So, I don't enabling a module. The only reason I use Drush is to download, install and also because partially of the page.	I use Ctrl + F								Check what version of module I have installed, it provides link to available updates		Enabling/disabling modules.	Enabling/disabling modules.		Enable/disable modules.	For me the operations are most important, help, permissions, configuration. Sometimes I read the module description, after I downloaded and want to see what the module does.	Important activities is searching for modules, where I can configure a module.				Install, is really the most important one. Lookup version number. For posting an issue.
13	Now, I am going to show you a list of tasks related to the modules page. Please let me know which ones are important to you (critical or you do normally). Do note this alphabetically sorted list and is not exhaustive. Please feel free to add others that you deem important. Refer to the issue summary on http://drupal.org/node/538904 for more information about how we got to this list										Critical part of UI when Drush is not available
14	Enable / Disable / Uninstall module			P2 (I would separate "Uninstall a module" as a separate category)	P3. They colorized the text for enable/disable - they should be links and it should be able to click that text.	1	2 -A great PITA is not being able to disable a module as long as the dependencies won't be disabled first. I know it's for security for there should be something implemented to trigger this		1		I typically use browser-based search to find a module on this page. So it is important that something is not hidden (though I would accept the ability to filter the list based on status).	Critical	P1	Critical	Critical	Critical	Critical					Critical	Critical
15	Find a module			P2	P3	2	1 -Modules filter to take advantage of the autocomplete searchbox and left sidebar to order by category		1		Viewing available updates would be nice, without having to visit a seperate page. If by "update module" you mean run hook_update_N for a particular module, that would be nice. If you mean "download the updated version of the module and apply the update to your docroot" I would say that causes many headaches for websites with deployment restrictions (such as Acquia Cloud).	Critical	P1	Important (for those installed)	I look on D.o. to find modules	Very important (for those installed) / Nice to have (if not installed, to search within Drupal.org)	Critical						Critical
16	View available updates / update module			P2	Nice to see but depends on the case.	4	6 -Only when being lazy and not taking the time to check on drupal.org first				Critical	Critical	P1	Critical	Important	Very important	Good to have					I use admin/reports/updates for this - It's nice having a dedicated report for this purpose.	Not important
17	View current module versions			P2		5	5 -Mostly for sanity check				Critical	Critical	P1	Dont use	Don't use	Very important	Unimportant					Critical	Critical
18	View list of disabled modules					6	Not implemented - We can only see that while scrolling down the page. A tab regrouping all disabled modules could be interesting				Nice but not critical	Critical	this is silly	Dont use	Important	Important	Important					Critical	Not important
19	View list of modules by functional set (e.g. Views)					7	Not implemented -Would love it				Nice but not critical, sometimes confusing.	Critical	Nice but currently messy	Minor	Important	Very important	Important					Critical	Nice to have
20	View list of modules of specific category (e.g. Core modules, administrative modules, media management modules)				Handy if it worked and if it was consistent. "Core" is not a meaningful distinction. It is about functionality.	9	4 -When Modules Filter is not installed, allows for quicker search among many modules/categories				Not just "recent" - it is critical to see information about the date/time a module was enabled or updated. Especially useful for tracking down performance issues and functionality issues.	Critical		Important	Would be helpful	Very important	Very Important						Critical
21	View list of recently installed modules					8	Not implemented - Would help to understand why a site reports buggy after a certain date				Nice to have	Nice to have	Would be AWESOME	Would be awesome	Would be really great!	Nice to have	Critical					Nice to Have	Nice to have
22	View module description to orientate what the module is about				Want hover	10	7 - Usually you'll already know about them and/or browse the drupal.org project page				Critical	Critical	No	Very important	Is very important as a beginner	Important, toggle-able would be cool	Critical					Critical	Not important
23	View which modules are required to be able to enable, disable or uninstall a module					3	3 - The colors are great and we could always use more visual understanding of things				Ideally this page should show an overview of the site architecture.	Critical	No	Not so important	Important	Critical	Important					Critical	Critical
24	So tell us more about your rationale for choosing these tasks?					Frequency of use, time of use.			1	5	220 enabled modules on the typical site we encounter in support	If they weren't there, it would be a serious loss of functionality and usability for me	I think it is hard to find modules in this giant list. On an average have 40-60 modules on a site.									30	I only really use the module page to install modules and to troubleshoot when I think a certain version is causing trouble.
25	On an average, how many modules do you usually deal with on a site?	I can't answer that.	40 (including core)	100 is not abnormal		100-150	150, a little less than 100 for smaller sites	For my site, I keep 50-60. For customers, avg. 100	guessing 50	10		Couple doze	40-60	50	20		20					15	20-40
26	So you gave me a quick rundown on each of the tasks, that are important to you. If you where to sort these, could you split 100 points giving more points to the tasks what find most important, how would split those points?									10	15
27	Enable / Disable / Uninstall module	20 (Uninstall - 10)	13	(Enable/Disable) 40 + (Disable a module as a separate category and give 10 points)		100	25	15	25	10	5		50	30	20		30		30	60	30	10	40
28	Find a module	10 This has to happen. Not sure why it's here, but since it is, i have to rank it high since other tasks can't occur without this one	15	30	20	20	25	13	40	5	5		20	10	10		30	10	20	10		10	10
29	View available updates / update module	10	5	10	20	15	5	5		10	13		5	20	8		10				20	8	30
30	View current module versions	1	2	10	20	12	6	10		10	15		5		5					15
31	View list of disabled modules	10	15			15	2	5		15	5	5			6					5	20	5
32	View list of modules by functional set (e.g. Views)		15		5	6	5	5		5	10				10							8
33	View list of modules of specific category (e.g. Core modules, administrative modules, media management modules)	9	15		15	3	5	4		10	14			10	9							14	10
34	View list of recently installed modules	5	0			5	5	12		10	5	0	20	20	10		15		10		30
35	View module description to orientate what the module is about	20	10		20	8	2	1			13			5	10			10	40	10
36	View which modules are required to be able to enable, disable or uninstall a module	5	10			1	20	9 (Other: module configuration sites -> 13, export/import module sets -> 8)			Ctrl-F (browser search), or some combination of drush pml and grep on the command-line.			5	12		15						10
37	Additional tasks																	Operations (help, permissions, config): 80 points
38	Based on your need and usage, how do you currently find a module? (Try to understand if they use groupings, name, status, description, etc.)	Look for the module name. Scroll. Sometimes I use Ctrl F	Modules page > Ctrl - F > Scrolling sucks	Ctrl F, half way problem with is that you want to check Views but that could have 50-60 results and you have to go through all of them. Search by the name of the module.	Mostly because I need to do when I am working on my site and finding a module and view the description may not be so much for me but for the customers. A lot of times they don't have the modules that would do what they need to do. and being enable/disbale and whats going on the site.	15	Described earlier.	Ctrl F, Sometimes it is successful and sometimes it is not. You have to know what you are looking for - that is usually not the case (for someone new coming in to the site)	35	I often use the text search - Ctrl F - the group does not make sense sometimes - ctrl F works pretty well. usually search by the name of the module -	drush en -y module; or via the UI, just following the prompts to install dependencies.	I do Google searches, the Drupal review website, view usage statistics, description, if it's available for D7, is it dev or stable, leery of anything in developement	Ctrl + F > I don;t know the name of the module (because name on the module is different from DO) also because I have to go through all the different required/enabled/missing	Uses contrib module "module filter"	browser search	Drupal.org, starting with having a problem or a need, searching for a proposed solution, and if there is go, thru a test process: does it meet the need, is it activly maintained, etc. Look for whether maintained, meets version necessary, meets functional requirement on the site	Scroll ... sometimes I use browser search, but its annoying that searching for "views" may give me lots of results before i get to the actual module	I use Control-F to find a module, if I know the name. I collapse core, I often collapse the fieldsets, it know it's somewhere there. I search for the module name. I if I don't find it I will scroll the page, scanning for the group name and then the module name and description. For example searching Five Star, I use Control-F, then search for something like rating, and I then find it under voting. To use a module name using Drush I use drush pml. The technical module name I know by hart.	Is there an other way than via the module page? Scan and scroll. The name and then the description. Perhaps if it is enabled, but it depends on what I want to do.	Sometimes I know the name, i search directly the module name. If I know it hase something to do whith ..., I search on the description. I use the grouping much less, unless I know it has to do with Views I search under Views.	Categorization is handy. If I know which module I'm looking for and can search under a category.	Search the page by grouping is helpful. All should not be expanded by default. I dont have any concerns with groupings	Only when specific, I use CNTRL-F or just sporadic to find the names. I usually just go down the list, closing unrelated categories. I know what it does, but just not the name. I look at category titles, and then try to find a relating name. Never read the descriptions.
39	When enabling a module, requires another module to be enabled - how do you usually go about doing that?	Depends on the situation. If a module requires another module, download it, stick it and follow that pocess	Lately Drush does it automatically. Usually I plan on a module and dependiences and then go about doing it. I plan it.	I usually enable the main one and then I know it is going to prompt to other modules. so it takes care of it. You could not disable a module a dependent module - but it should be able to tell me to prompt you and if I want to continue to enable/disable.		Two parts - dependencies - It would be nice to have the option to download the module that I need , an additional module - That works ok. as long it tells what is the dependency.	I use Drush. or I check the dependencies, enabling the dependency and the main module list enabled is last. The version column is also paid attention to.	Save a lot of dependency - it should auto enable and if it does not work, i will individually go and enable them. This process is fine. Saving a module clears all the cache and that is not clear and this could get catastrophic effects on a production site. (Clear caching ?)	o Enabling a module – process? I find it and and enable it. That is no problem. I know Drupal enough that I have to go to configuration – but with expereicne I know how I troubleshooting.	usually I would just after I have ionstalled module, search for the name of the module. I have gottent o searching more by experience. and the normal stuff.	Some themes use vertical tabs to make these more navigable; but doesn't always make sense. Esp with D6 image-related modules, which are scattered in a handful of packages.	I just go to the other module and install it, through drush usually		I enable the primary module and let Drupal tell me what's missing	I enable both at the same time based on prior knowledge from drupal.org	Usually when I enable it, it tells me and you can either say OK or not.	I check each one listed as required before I click the "save config" button	Depencies are handled by 'drush en'.	Dependicies I have not used it yet.	Upload with drush. I look on module on the page and it tells me which other modules are required. I use the dependency list for this. If there are a few dependencies is just install the module. If there are many dependencies, I do it in a few steps.	I do dependencies on trial en error. I wait for drupal to tell me which ones are misinig, unless I know which are required. Dependencies. When I enable a module, where drupal tells me to enable a module, I dont' want a confirmation if the file is on the server. If not available, I want a list of modules, with link to the page on drupal.org. For less experienced this might be different.	Most of the time I do it through drush - years ago moved to drush.	Usually its mentioned that modules are missing or disabled, I go to drupal modules.com – find and install it. When its missing, I usually CNTRL-F till I find the missing module – usually going past a whole lot of positive negatives.
40	Have you used the groupings (core, views, media) in the past? If yes, how? Is it important or not?	have used before. it is artificial. I need some category to understand what they are. Some categorization is needed but on the flip side it is architectural problem inflicted on teh suers to understand all these sub modules. It is abused too badly. It is lame to have views and views interface. We should rely on the 80% use case.	Groupings work fine.	Generally we have a site that has more 300 modules, there is something to worry about. 100 is not abnormal. Do not use the groups, found them to be arbitarily.	Groups are inconsistent. I don;t have choice but I have to use them.	Yes, I use them. What is most important is it in core or not. there is not a distinction what is core and what is not. Sometimes I don;t know what the groupings are ... and they are not consistent.	I have used them in the past, I almost everytime collapse the core fieldset so I could see the contrib fieldset. SOmetimes modules are put in inconsistent categories like Ctools in Other category.	Yes, I have used groups to browse but it is inconsistent.				I look at it but don't pay a lot of attneiton to it	Views, Ubert Cart, Core, -> When you download them you dont know it is going to land up	Yes. I use them for searching what I've got	Nope	Yes	not really, but that sounds great!	I have used grouping, and it helps. But it is annoying that I have to collapse all fields, it's a lot of scrolling.	Categories, I have not used, User Interface group was there. I have expected wysiwyg on the botton, alphabetically. When installing there is only one group. I did not expect a group.				To get an idea what’s in there.
41	Searching (1 min)										Typically browser search
42	Do you currently use some kind of searching on the module page, in browser or through a module?	Ctrl - F works but it is a cruch. We should make it better. To have things like field, comment, node is available to user is non sensical. What drupal package is and hide them from the user and focus on the add-ons Then I have to scroll and find so much. Likewise, the visual display of the module is not pretty. It is not enticing.	Ctrl _ F. Yes - There is a module does auto complete by module name , recently modules, updates, dependencies. It is called Modules_Filter	I am okay with the search filter but not the vertical tabs.	Currently using groups. Would be nice to have a filter and dynamic filter for things that match. It would be based on description, easy tags to quantify (security updates, checkboxes) but mostly the description ... e.g. youtube, twitter and I would see modules add this and share to login using twitter	Type ahead based on module name. I always know the name of the module, i have installed it so I know the name of the module.	Yes, I would be interested in using the search filter. It is the way we interact (google). Search by module name. By category - it requires me to go to that section which is down at the bottom.	Filter - search by custom notes, module name, version, available update, modules I have customized.	o Search – Ctrl – F, Scan – Not good, scroll, miss things – not great Yes, would want to search by description, name of the module. May be some of the higher level like media,photos, text editor, etc. For beginners, it would be useful if I could know that a particular module is in use or not. o Expectation – search – sometimes I don’t know the name of the module, usually I do but sometimes I don’t. Want alpha order with core and , search on the page would be useful, search by description,	search filter - i would be interested. the browser search works well. searches by module name.	ctrl-f to search for a sequence of letters, then spam repeating search until I've seen the whole page.		Ctrl - F	module filter	no	no, but it would be welcome. Yes I use the browser for search.	no	Control F in the browser	No browser search, only scrolling and scanning	I search with the browser, not with a contrib module. I use categories only when searching.	I use the browser search function, Command F	Yes. Primarily by module name, Secondarily by dependencies and desc.	Just CNTRL-F, used module filter once – good idea, but it was bugged once.
43	If yes, how do you use it?												Name of the module (Would use search),	I just type the first few chars and let the module do the rest									-
44	Desired usage (2 min)										Sortable table, with sorts on: Name, Date installed, Date updated, Package. See: https://skitch.com/webbj74/gt9p2/modules-wireframe
45	How would the ideal experience of the module page be?		Auto complete, check boxes,	being able to disable/ enable - dependency - pop up/ check box toggle to show or not show the dependencies/ description. I need to see the description/ dependencies only sometimes.. I only want to status.name of the module. version. (more often than not, when you know what is on the site)	How would you want to find a module? Does not have to clutter the page.. but a little hover and get more information about this module would be good. Want an info link like the help info. Ideal expereince has to be nibble, find things readily, should not be SLOW, and need not to fear that I am not going to blow up my site when I hit SUBMIT, I always want to have a VIEW ONLY mode for the page.	Should you list all the modules and just have the search box. or fieldset. This was improve efficiency.	Be able to find a module in 5 seconds and ideally, find and enable a module in 5 seconds.	Should be as a view and finding it and it should go to search view that instead of all that causes it to become SLOW. The perfect landing page like advanced google search. Most of the times you don't need to look at everything you are looking for something particular./specific.	More data around the module. I want to know what is the uber cart, when did I install it, when did i update it. Search filters. Link to the config page. More of a functional dashboard. It is the heart of the site but it is lame.	I guess I would have be if it was quickly, Find the module that I just installed so that I could enable it. Easier to disable with a lot dependencies.	A directed graph of dependencies, using graphviz. Information about hooks implemented by a module.	Documentation is a	Enabling a module works for fine right now but it is redundant. Why it can be automatically turn on?	One-click install directly from D.O.	There is a ton of information on this page. I would hide some of the info.	Quickly find modules that are active or inactive, to be able to sort between those that need updating, identifying risk (no longer actively maintained), to be able to have control without clicking away and having to come back, [check recording]	I would rather see a list of all modules ordered alphabetically without the groups and without hiding any of them	Ideally enabling a module I would use drush.		Ideal for module installation is with Drush enable. Ideal searching is on Drupal.org, it returns iwth a list, I click to select and drupal installes. But onestly I will not use it, prefer to use drush to set modules on the server. Ideally anly level of dependencies are handled by drupal correctly.		easy to see what module is enabled and what could be enabled. What sub=modules come with a package.	Install it through FTP, when I get to the module page I now have to search again – with all the positive negatives. Ideally it would just bubble up to the top or that green notification thing.
46	Is there currently something missing on the module page, you’d wish it had?										"Install a new module" causes much pain for customers, since the docroot is vcs-managed. Useful for people who have rudimentary websites, or dev environments, but shouldn't be used in tiered hosting or manged hosting environments.	Documentation		filter by name, dependencies; allow user to search by descriptions maybe	no	Filtering and searching, display modules in different ways (eg a simple list) like a file browser for usefulness	I find icons helpful	I would like to have a filter or soundex (sounds like) filter. Quickly go to a module. An uninstall immediately after disabling a module. But perhaps that is only for experienced users. The uninstall does not look good, I expect the page to expand and not go to another page. And when I go to that page I have to enter an URL. I just want to enter a name. An autocomplete should help me there. I would like to see the help link of disabled modules. That is now hidden when the module is disabled. I would like to remove the indirect dependencies. The button Save configuration should always be in the window. That I can aways see it.	A filter on types of module would be helpfull. Types like management, rendering, functionalities. Want to have More idea of which category a module is in, before I install a module. Filter the modules that can not be disabled, make them occupy less space. I need them for the link to the configuration page. Sort om modules with a configuration link, to group all configurable modules together. The same for enabled modules Filter modules that can not be disabled, the checkbox is gray, take in too much space. The help links take too much space, visually. Add an indication if a module is up to date. Make clear what a module does, text filter, functies in the body of the output, block functions. Add an uninstall link. But perhaps that is because I did not disable a module yet.	I would like to have an integration with drupal.org, the knowledge available there should be available on my site, direct access to it. And rating information for a module, how stable is this module. I search but in the past month 150 problems are reportd but not handled. That kind for information is handy. When disabling, for example if I disable Blocks, I want drupal to ask me to disable Domain Blocks, are you shure? And there it goes.	Add to remember the collapse/expand status. Add a search function. Most recently added and most recently installed module. A search function to search on d.o from the modules page. And check the status of the issue-list.		Maybe something like module filter, but then actually working. That would fix my problem with required modules. Missing modules are not clickable. Filtering my categories, the ones that I find interesting. When I don’t know the name, and I have some idea what category to find it in.
47	Is there currently something on the module page, you wish it didn’t have?	Would search filter be helpful? No. But that is extreme case. It is a serious example of a website and A.com uses 25 modules. There are solutions to the problems without requiring search.		Could be faster! Would be nice to have filter out modules based on their status.. modules with unmet dependencies ... If I could hide the desc and dependencies, I would be okay to use CTRL F		If we are thinking at fantasy why version update would be nice to have. Not sure if I want to download button there..depends on the use case (small sites or large sites) It would be nice to have the statistics - divide them in core or stats - will help me think about performance, am I installing too many things? (Thinking about) A portion for better would be that "Read me" is consistent and useful. - Better practices for Read me on the module. Novice drupalists would be touching the modules page - optimize the page for novice user. Worklow- When I enable a module, it should show me a subset of roles and permissions and let me pick me the permissions right away. It should take me to configuration and then subset of roles and permissions. I regularly forget to assign configuration or permissions. (THAT IS THE MOST IMPORTANT THING TO ME _ I WOULD GIVE 50 points to this one)							Want a drop down for the modules and see the description.	list of dependencies that screws up browser search; maybe just show only frst-level dependenceis for each moule?	Just less information over all... overwhelming especially to someone new	can't think of anything	nothing really	No	no	Nothing to remove.	All the listed depencies could be removed or not shown directly. To make the list shorter. No confirmation of required module to be enabled. The link to permissions can be removed. Not so important.		Permissions feels a bit useless, because it doesn’t work. Don’t really use descriptions. Perhaps useful, when you do a lot of projects or so.