Module (and theme) list in vanilla Drupal installation (admin/modules and admin/appearance) lack communication between module maintainers and users (site developers/admins).
I would like to build a module that will enrich module list with links to appropriate issue queues, options to submit new issue (with optional list of enabled modules attached to help problem resolution), documentation etc.
From maintainers perspective, it will be nice to have feedback tools - i.e. ask module users if they want specific feature, or what technical solution they prefer if there is a dilemma, and so on.
Is such "socialization" any good? Or probably there is already something similar? (according to my search, no)
To make it clear: I'm not going to patch update.module, but alter existing form in a separate module
Comments
Sounds interesting, but don't
Sounds interesting, but don't quite see what you're getting at. It would allow me, as a module maintainer, to put links to stuff next to my module's info on the module list, maybe?
Also, this is not Twitter, so please do not put hash signs before your tag names.
The Boise Drupal Guy!
Yes, adding links near
Yes, adding links near module's info is one my suggestions. Another added value: when someone submits a new issue, it would be possible to send enabled modules list with versions, core version etc. - things that module maintainers ask anyway to find a problem.
.
There is an issue to make projects into Organic Groups. If you have the inclination, you might want to put in your effort there. Also, there are issues for cleaning up the module list / update status list as well, though I don't think they include any socialization; just better organization.
Michelle
If you mean
If you mean http://drupal.org/node/1025152, then no, I mean something different.
I don't want to know exact sites that you each modules, but provide some ways of communications between module authors and users
.
No... that's not even close, actually. There is an issue to make projects into Organic Groups. I don't have time to search for that now but having them be groups would do exactly what you're asking.
Michelle
I would appreciate a lot, if
I would appreciate a lot, if there were more ways of feedback for module maintainers.
The usual feedback I get is about things that don't work (if these exist), or asking for a D7 version, etc.
What I miss is positive feedback, usability feedback, people describing their use cases, beta / dev testing and code reviews. Esp, for those of my modules which are in beta, and at around 50 users, and which I only want to officially release as 1.0 when I have some confirmation.
If the suggested "update.module more social" features help with that, they have all my support.
What donquixote said
What donquixote said. I have exactly the same feeling about this.
great, so I feel that there
great, so I feel that there are other people needing this, not only me :)
to the work then! I will publish link to the project as soon as there will be something to show
I think the more important
I think the more important dimension is what happens on drupal.org.
So far, all you can do is send people to the issue queue, or let them create issues, or anything issue-related.
The stuff that I miss would be new channels on d.o. for:
- real-world user stories / use case descriptions (which can involve more than one module)
- code reviews
- general feedback beyond feature requests and bug reports
These things don't need the usual issue workflow of open / needs review / fixed etc. But they could use other fields such as "use case participants" (that would be filled with "anonymous visitor", "the client", "the developer", etc).
Agree. I am going to create
Agree. I am going to create related issue in d.o. webmasters queue and ask for d.o. sandbox to try these things