The Support Forums will be in read-only mode for a scheduled maintenance window on 01 September 2016 14:00 UTC - 20:00 UTC. More information.

Ideas Forum/Communication Channels (55 posts)

  1. Jen
    Community Organizer
    Posted 7 years ago #

    @demetris: Your post just proves the point that communication is an issue. I would not say that WP lacks a clear direction, I would say that it simply hasn't been communicated properly.

    @Kwebble: A published roadmap against which suggestions can be weighed is a great idea.

    @aaron_guitar: In the Ideas forum, right under the rating and tags it will say the idea is -under consideration, -addressed by a plugin, or -it has been implemented.

    @mark8barnes: re WordPress.com affecting WP development, I haven't really seen that since I started at Automattic. Different developers work on .com full-time, so they write their own stuff as needed. Also? If I'd been thinking about .com when I worked on the 2.7 redesign, a few things definitely would have been different. :)

    @jeffr0: I agree that using BuddyPress as a base would open up a lot of possibilities.

    @bsutcliffe: I should have mentioned the wp-testers mailing list in the original post, too. Thousands of people test the alpha/beta versions and submit bug reports, so we'd need to make sure any system allowed them quick and easy bug reporting.

    @JohnMyr: Derek's article did not inspire this discussion, as the dev blog post is based on a talk I gave at WordCamp Denver in February, but his article does make some good points. If you look back at the icon design contest, I think we followed a process similar to that which he recommends.

  2. Lars Koudal
    Posted 7 years ago #

    I would like to second the notion about too many ways of communication.

    I cannot comment on which approach would be the best, I leave that up to the core developers/leaders of the WordPress community, but I do agree a more streamlined approach and "housecleaning" of the hundreds(thousands?) of discussions, ideas and tickets currently submitted.

    Reorganize, streamline and focus your developers skills towards what they do best, develop.

    p.s. Thank you (all of you) for making WordPress as strong and flexible as it is.

  3. Ben Sutcliffe
    Posted 7 years ago #

    @janeforshort Then the UserVoice system (customized to suit) would be a good idea.

    Any chance you could forum sticky this so it's easier to find :)

    Posted 7 years ago #

    Hi Jane !

    Too lazy to read all the comments already posted.. i think this is all about development process and feedback.

    so a little powerpoint is better than a long comment, here is my contribution to the points raised in your post "Contributing to WordPress, Part IV: Ideas, Opinions, Feedback" :


    My major concern about wordpress today is : what is the global picture ?

    How will be organize the settings panes that should be reviewed in 2.9 ?

    What WordPress 3.0 will look like ?

    When will WordPress stop PHP4 support and have a more object oriented code ?

    Once i heard or read Matt speaking of wp as a platform, and that he was thinking of having a unique technical layer shared by wp, wpmu, bbpress and maybe Buddypress. When will that come ?

    How can we help on all these subjects ?

  5. Jen
    Community Organizer
    Posted 7 years ago #

    @lkoudal: You make a good point about letting developers develop. A lot of the complaints have been about the core devs not getting involved in forum threads (here, or in Ideas), but the reason for that is that they're using their time to develop WordPress. So what's the optimal solution that will create more two-way communication without turning the core developers into forum mods?

    @bsutcliffe: Forum is now sticky. (See, we listen! :) )

    @arena: From your diagram it looks like you're suggesting we keep all the channels we have now, but set it up so they all create trac tickets by default? I think that would be problematic in a number of ways.

  6. I think using BuddyPress somewhere other than BuddyPress.org is a great idea, but as a mod on those forums I'm probably a little biased. :)

    Jane, I think that what you're doing is probably a much needed breath of fresh air.

    Public relations, getting down in the trenches, getting the feedback and reporting the news back is essential. I also think that the recent discussions over the past 2 months or so show a new initiative and a fresh outlook on the open source development style that WP is founded on, and ultimately relies upon to keep its core audience.

    WordPress is a culture now for a lot of us. I wear the t-shirt and have the pencil, and stuck the stickers on as many little random things as I could. I wake up in the morning, and goto work, and get paid to make websites using *Press. I come home from work, and maintain my personal sites, using *Press. I goto sleep at night, thinking about how to improve *Press.

    It's super cool to know that even copious amounts of feedback are embraced, and I wanted to say that you're doing a fantastic job. :)

    Go BuddyPress! :)

  7. mrmist
    Forum Janitor
    Posted 7 years ago #

    My opinion? Trac needs a pruning. Currently the number of active tickets is so vast that the core devs have little chance of catching up with active bugs. One major issue is that tickets continually get punted.

    There are, currently, 53 active tickets marked with commit that aren't commited, 211 tickets marked with has-patch, and 312 marked with needs-patch. 302 tickets are marked for a "future release", which probably means we won't see traction on them for some time. (4 of them were marked as tested and 19 as has-patch, so they really should have gone into 2.8)

    Clearly that's not great. It's demoralising to patch writers, and it must be hell for the devs, too, to have to sift so many tickets.

    Possible solutions -

    1. Auto-close anything with no traction for longer than x days.
    2. Auto-close anything punted for more than x releases.
    3. Seperate the trac into two distinct tracs, one for enhancements and one for bugs (this may not be possible given one source base, I don't know how trac works.)
    4. Allow more (trusted) people to commit patches.
    5. Establish a team of testers to test patches, and
    5.1 Ensure patches that they mark as tested get commited

    Realistically only getting tickets closed off is going to help, anything else is just firefighting. Of course, you could limit access to raise tickets, but I'd see that as counter-productive in terms of reporting actual bugs. So there's possibly

    6. Make the public trac for defects only, and re-vamp the idea forum. Make the idea forum actually produce an output. Have regular (publicised) votes on the best ideas, the output being that a trac ticket (enhancement) is created for that idea. Allocate a certain number of ideas per core-dev per release cycle. Only core devs or the idea forum can then generate enhancements.

    Of course, 6 might stem the flow of ideas into code, and there's the possibility of great easy-win ideas falling by the wayside. So you'd probably need some way of introducing "easy-win" enhancements on top of that.

  8. Denis de Bernardy
    Posted 7 years ago #

    @Jane: I'm 100% with Demetris on this. This whole things' governance is dismal. It has been ever since I've first used WP, and it has only *mildly* improved since. I congratulate you for your efforts in trying to counsel it all, but until I see things moving, allow me to remain very skeptical.

    So, where do we currently stand?

    Community input is ignored outright or treated as intellectual property by Automattic. I vaguely remember a poll I answered, towards Christmas, about what should make it into 2.8. Its results were supposed to be released early January. Best I'm aware (and I'll be happy to learn I was wrong), they never showed up in my Dashboard.

    Ideas is cluttered with junk to the point where it's no longer useful except as a place to look for plugin ideas. Nobody's maintaining it. Or then whoever is, either isn't doing a good job, or lacks the clout to get things done on the dev side.

    wp-hackers is in a sorry state. It's mostly noise, geek-speak, and ranting. I haven't been subscribed to it for 2 years, but I still scan the archives every now and then. There is even less signal now than then.

    Codex is cluttered with obsolete stuff to the point of uselessness. One cannot blame the community for it, either. Leaving aside that contributing docs is boring, docs quickly go out of date when the release cycle is too fast (see below).

    Then, there is trac. A couple of weeks ago, it was cluttered with well over a thousand tickets. That's just insane. I didn't show up on it a few weeks back because I was suddenly craving to contribute patches and get 500 tickets closed. Rather, I did because I end up maintaining plugins (yes, plugins!) to work around WP bugs with every new release, and I felt I'd be better off, given the sheer number of bugs this time, with things patched in WP instead. (I read all tickets since, btw, and a lot of what's in 2.9/Future is either trivial to patch, or ticket clutter.)

    The most stunning aspect, however, is how contributors are treated. By contributors, I'm not meaning end-users who whine their wish list in Ideas, wp-hackers, or the forum. I'm meaning people who, like myself, can actually code these ideas and get the job done.

    In case you're thinking I just feel like trolling and ranting, here are three trac threads to chew on:




    They're typical of what has put me and others off in the first place.

    In the first one, you've a valid patch, tested and ready to go, that gets dumped, for no reason other than "we're trying to meet an artificial deadline". The fact that a similar patch was nearly committable 3 months earlier but never received any feedback makes absolutely no difference.

    In the second one, you've an interesting idea, one that was discussed in wp-hackers, whose patch arguably has a few weaknesses. It awaits some kind of core dev feedback or 2nd opinion. The patch gets refreshed, again and again, to a point where the person who is maintaining it loses interest and decides to do something else. Unless it gets some kind of attention quickly, this ticket will rot for years in trac.

    In the third one, you've someone who has nothing to do with WP, who shows up in trac, highlights an issue, highlights how to fix it, contributes a patch, refreshes it FOUR times based on feedback, asks what else might be needed to get this fixed and working... only to see his patch get ignored -- because we were then in feature freeze. He left in disgust, presumably never to be seen again.

    And then there are several tickets in the current commit list who will get punted to Future, for the same reason as the first ticket -- in spite of the fact that they break nothing and that their contributor will stand behind his patch and fix it because he needs it for a plugin.

    And that is not to mention the genuine -- but yet to be patched -- bugs that got punted to Future in spite of the fact that they affected users who reported them in a very real manner. You can be certain that their reporters won't necessarily report them in the future.

    Now, let's look at the cold facts. You're wondering how you can improve communication and the feedback loop. My answer to that is: put people in front.

    This is supposed to be a community, for heaven's sake. It's not about a company. Especially not about Automattic. It has everything to do with WordPress. This is an Open Source Software. It seems this has been forgotten at some point.

    Nevermind that Automattic is paying Ryan, Andrew, Jane, and quite a few others. There are other people out there (I certainly count myself among them) who make a living on WordPress, who have been doing so for years, and who would be quite willing to spend more time contributing if they thought it was worth their time.

    Currently, it is not. You can try as hard as you want to fit a square into a circle. It just won't. The development cycle is too short, and WP is severely understaffed. The two combined results in potential contributors getting put off outright.

    3 months is too fast. You end up relying on who gets a hold of a committer to get things into trunk. Change that to 6 months (say, Feb 1st and Aug 1st as release dates, so that people such as myself don't end up working on Christmas or New Years Eve) and there suddenly is plenty of time to go through the weirder patches. WP could then have time for a real QA process as a bonus.

    As for staffing, consider how we got to over a thousand trac tickets by contrasting WP with an OSS project that gets *everything* right: PostgreSQL. PG has a bugs mailing list, and no ticketing system. And no bugs, I'd add. *Every* ticket that is reported gets an immediate response by a core dev. Bugs are fixed on the spot instead of rotting for years into a ticketing system. 48h bug-to-fix is common.

    With a half dozen extra committers (try the trac regulars if you need names) you could achieve the same thing in WP, render Ideas obsolete on the spot, and put WP back on track. It doesn't matter if a bug gets committed into WP every now and then. If things *do* get committed in the first place, and fast, those who have bothered to contribute their piece of code into WP will be happy to contribute a fix to what broke on the spot. And with a dozen committers as opposed to two and two eights, you'd get several people who are actively reviewing what gets committed anyway.

    My $.02. See you on IRC later today.

  9. Denis de Bernardy
    Posted 7 years ago #

    @Jane: Oh, a quick separate note on the way trac is organized.

    First, notice that all of the wordpress.org tickets have been rotting for ages. (One is even assigned to you, btw.)

    One of its tickets, in particular, relates to setting up a template for bug reports so as to improve their quality. It should have been taken care of long ago.

    Then, there is the way things are organized. There are a few components that are missing. (Query and Charset, in particular, come to mind. wpautop and wptexturize might be worth doing as well. And scanning through the Administration tickets would reveal quite a few more.)

    Dropping the Severity field would be good imo. Something Severe should be fixed on the spot as a rule of thumb. So Severity is really redundant for Priority. Severity should be dropped.

  10. elfin

    Posted 7 years ago #

    One thing that has always bugged me is the [resolved] tag for these forums. many plugin authors do respond to bug reports (and many don't) but they don't have the ability to mark such threads as resolved, when they obviously are.

    This would also be useful for weeding out resolved posts about WordPress itself, though for that to work you would need more 'official' people to have a presence on the forums.

    I don't like these forums, they aren't as fully featured as is the norm, and it makes finding things that much more difficult. Was it ever really designed for the scale and scope of a support forum this large?

    The communication, especially from yourself Jane, has been good of late. Giving us mere users a chance to vote on certain aspects makes us feel more involved in the direction that WP is taking. But as another poster pointed out, there are occasions when things aren't followed up. This doesn't help things.

    Ideas are mooted in various places, and I think some of the better or more important ones may be getting missed because of the wide diversity that has grown over time. Take the WP hackers list for example - what is it for? I've been on the list for some time and I'm not entirely sure, is it for improvements to WP, or helping plugin authors? A recent suggestion for a list about improving the accessibility side of WordPress appears to have been shelved, even though Matt does have an interest in it.

    A complete overhaul and re-evaluation of all the current lists/forums etc should be in order. Especially the direction that some of them have taken.

  11. islamegy
    Posted 7 years ago #

    #1: Bulk text replacement:

    Sometimes there is a need to replace a certain text in many posts and/or pages in one shot instead of editing each of them one by one. This might happen when there a broken link or video which needs to be replaced in all posts/pages that refer to it.

    #2: Private pages not listed in the Parent dropdown menu

    It should be allowed to build a hierarchy of private pages as in the older versions

  12. islamegy
    Posted 7 years ago #

    I apologize for my previous post!!! I posted it here by mistake and I couldn't delete it

  13. Ben Dunkle
    Posted 7 years ago #

    Regarding the insert media icons above the post box... It's weird to click them and think you're inserting a video, but it says "Insert Media". Of course, it says insert video above that, but it's in really small lettering and easily missed. And one of them looks like a star...I guess that is everything besides images video and sound, but maybe it should be for documents... Also, it doesn't work-you need to install plugins to get video/audio embedded in your posts. So I don't see the purpose of them anyway.

  14. Andrew Stephens
    Posted 7 years ago #

    What I really don't like about the ideas forum is the fact that it's the same highest rated ideas and then the newest ideas. If it's more than a few days old, there is no way to access it, as far as I know, and it just gets lost in space. Nobody can comment on it, rate it higher, or have any say on its future. I think the Ideas forum should be a full-featured bbPress, where you can browse ideas by type, and be able to view ALL of them, old and new. Then there's Kvetch, where some of the things that pop up are complaints from older versions of WordPress that were fixed/updated quite a while ago. I say throw that out completely.

    What I think would get more people involved is a few pages on the site (not necessarily in the codex) that explain HOW to get involved. I have wanted to help in the WordPress project for a few months now, since I understand PHP for the most part, but I don't really understand things like the 'Hackers Mailing List.' Trac was hard enough to figure out. If you just wrote out some more instructions, more people like me would probably be a bit more motivated to join the project.

    The UserVoice idea sounds good if it could be implemented.

  15. Joen Asmussen
    Posted 7 years ago #

    I wrote what basically amounts to a wishlist:

    10 changes to WordPress that would make it a Killer CMS

    Here's the list:

    1. Multi language support
    2. Better custom fields
    3. A way to easily refresh image cache
    4. WYSIWYG in textwidgets and optionally in custom fields
    5. A widgets overhaul
    6. A better way to change page sort order
    7. A simple way to hide page items without having to write a long "exclude" list in the templates
    8. Better media insertion dialogs
    9. Ability to upload images to, and edit custom fields on tags and categories
    10. Better user role management

  16. elfin

    Posted 7 years ago #

    perhaps a good example of not enough moderation on the forums, sorry Joen.

    Jane said in her original post:

    This forum thread is for discussion of how to improve the feedback loop and communication among the WordPress open source community

  17. perthmetro
    Posted 7 years ago #

    Here is what I'd like to see... batch/bulk editing of password protected posts from within the 'quickedit' mode.

    As it is now we can change an individual password protected post form within the 'quickedit' mode. Wouldn't it be great if we could choose which posts we want to password protect with the same password and then do it in quickedit bilk edit mode. This would allow for very easy and convenient protection of groups/categories of posts.

    thanks for listening

  18. gcaleval
    Posted 7 years ago #

    I am not a developer but I do work with developers and I do a lot of searching for answers to specific questions in the various WP venues.

    The challenge is that there are tens of thousands of WP publishers and at least many hundreds of people actively writing code against the WP engines (themes, plugins and some unique stuff that falls in neither or both like Carrington).

    In that world, a "regular" or even intermediate publisher frequently does not know if an issue they bump into is a bug, third-party code problem or plain inexperience on their own part. Distinguishing what content addresses their need and does not is a major communications challenge, that, without being trite, comes down to search results.

    When I use wordpress local searches I rarely if ever get as good results as if I search from Google or Yahoo. What is really odd is that the most useful results are often in one of the wordpress venues, just not returned by wordpresses own search.

    There are a number of small things that might help with this challenge and it seems to be vaguely described in a number of previous posts to varying degrees. Really I think people are trying to get at yet-another-taxonomy. There is an attempt to address this with the idea of "Resolved" markers or the explanation, I believe Jane provided, for "-under consideration, -addressed by a plugin, or -it has been implemented."

    But for a great many needs, these tags do not go far enough. Might there be some sense in a post, in whatever venue is finally settled on, to include markers that identify it as one of the broad categories of Bugs, Feature Requests, Publisher Support and, if Publisher Support REQUIRE a flag that the post is Question, Answer, Comment; if a Feature Request, then include the under consideration, -addressed by a plugin, -has been implemented and if a Bug Report, similar tags as ticketing systems.

    What use would this be? For me, I could then search the venues for posts for Questions with Answers and exclude all the Comments, Feature Requests and Bug Reports for my initial effort at getting an answer. For me and many others this would make sense because often our issue is not really about a bug at all but some aspect of usage.

    As maligned as the Codex has been, it has been my primary source for answers, but frequently has left me in a position of knowing what the correct syntax should be, but not quite understanding how to implement that syntax to solve whatever problem I have. So I struggle with trial and error for days and frequently discover much later that somewhere else in the WP universe the exact scripting example I needed was hiding from me the whole time.

    I think people have to have reasonable expectations about exactly how much something as immense as the wordpress universe can be made to function as a predictable, tidy organization. The use of the word "community" is well taken in this context. A community is not going to magically fall into line with a systematic, hierarchical communications, education, evaluation and implementation system. "Governance" per se is an elusive proposition.

    But there are some things that can be done, and some, like the fairly passionate plea to empower more committers, should relieve some burden from the current crew while significantly improving the entire development process.

    At the same time, I believe that Automatic or whoever is going to lead this process, should appropriately challenge those of us who have complaints or needs to become part of a documentation effort. What I mean by this is not the ebb and flow of responding to questions and bug reports, but a structured effort with volunteers to build up the codex or some other version of a living documentation system. Many forum posts could and should be cleaned up and inserted into an appropriate spot in a table of contents with indexed entries. maybe a wiki, I don't know.

    But it seems to me that an enormous amount of effort and thousands of person-years are contained in all the various forums and mailing lists and so on. This information represents an asset to the community that privately valued would be in the many millions of dollars. Perhaps those of us who cannot code could become copy editors and technical writers?

  19. Mike Schinkel
    Posted 7 years ago #

    @Jane: Glad to see your post on the subject. Yes, the state of WordPress is rather abysmal WRT direction and community communcation.

    There is no forum for first discussing what should be done and how it should be done. The regulars on wp-hackers seem to be online simply to challenge the validity of any use-cases discussed by anyone who hasn't been contributing for 5+ years. They all say "submit a patch to Trac" expecting people to go off in a vaccuum, create a patch, and then submit it to Trac where the active devs play Whack-a-mole rather than addressing the use-case or issue that precipitated the patch. So progress is rarely except for what the four (4) main devs are working on only one of which occassionally participates in the discussion.

    How to solve it? Minially we need a list or forum whose goal is to discuss use-cases and how best to solve them with an eye towards updating the core if need be. This list or forum needs a moderator that can step in when people who have been involved for years bully the newcomers otherwise it will become like the wp-hackers list where most people realize it's just not worth the pain to post anything.

    I for one would like to see the WordPress community get rid of the "not invented here" mindset and get proper forum software such as phpBB or even Google Groups. I know there is BBPress, but it is nowhere near as good for facilitating discussion as some of these others.

  20. Elpie
    Posted 7 years ago #

    A good example of how messed up the communications channels are exists right in this forum thread. Just following the comments is hard when there are off-topic posts and spam amongst some very worthwhile feedback.

    The barriers to contributing here are huge. The core team may know what they want to do and what they are working on next, but for anyone trying to find that information its like asking how long is a piece of string. There appears to be no reasoning given as to why some tickets on trac languish for years, and again no reasoning behind new functionality that gets thrown in without use cases or any discussion that end-users can contribute to. If any actual planning goes into development its certainly not obvious.

    It is not practical for anyone wanting to contribute to have to watch trac, the development blog, the official wpdevel blog, mailing lists and the forum just to try to work out what is happening.

    I am in agreement with Denis, Demetris and MikeSchinkel so won't bother repeating their comments. However, I want to emphasise two - a roadmap so that everyone knows where development is heading and what new features are planned, and a slower development cycle.

    Thanks for initiating this discussion. I hope it doesn't end up like development discussions or trac tickets - going nowhere and wasting people's time.

  21. enailor
    Posted 7 years ago #

    Having read this, there are 2 points that I would like to agree with and chime in on...

    1. Development Cycles
    It does seem that the next version of WordPress comes out way too quickly after that last one. Its one thing if you find a major security issue, but for those of use that make some changes to the core, this gets frustrating. I know, core changes are highly discouraged, but in many cases needed. I am looking for beefed up security as well as a real CMS powered by WP. This leads me to point #2.
    2. Direction of WP
    You mentioned that the direction is clear but obviously not communicated... and still not communicated within the response! Not a dig, but just something that should be noted.
    In my humble opinion, WP has matured well beyond just a blogging platform and is just a few real tweaks from being a major player in the CMS world. Sure the WP.com side is focused on blogs, but us .org users tend to lean towards more of the CMS side and I for one would love to see this direction embraced. But all I have read and found on my own indicates a major resistance to the idea of WP as a CMS at its core.

    So how do we change the communication? That is a great question... one I do not have a real solution for. However, I would ask that whatever is used would allow a user to quickly identify what version of WP the information applies to. Maybe even allow us to search based on the WP version we are using... this could even apply to the Plugins section, where some of the plugins are no longer supported but you have to weed through so many to find ones that work for a specific version.

    Regardless of all this, WP is my first choice for any website I am developing. Second choice would also be WordPress, so little chance of my leaving to another! I love you guys and this program.

  22. Ben Sutcliffe
    Posted 7 years ago #

    @enailor - so true on the issue of core mods. Could WP release patch files alongside updates, so if after 2.8 we have 2.8.1 like with 2.7 then the security updates could be release as patches. Also, I agree that there seems to be some sort of rush - as soon as 2.7 came out there was word of 2.8, and dare I say it, 3.0. If we get to the end of 2009 and 3.0 is on it's way then something is seriously wrong - updates either need to be grouped or they need to be illustrated as patches - so 2.7.1 would have come out as Maybe the patches could become a system whereby a patch is released on the 1st of every month but never more often.

    Secondly, continuing @Elpie's point, what is the roadmap for WordPress, bbPress and buddyPress? With WP we are seeing a stream of updates, on bbPress we're still waiting for 1.0. How about Automattic publishes a roadmap (like Apple do with iPhone) to show devs what will and won't happen by this time next year, and then have a concerted effort to bring the Press family to the same level (common admin UIs, similar/common functions, same levels of support & documentation)? That way, I wouldn't be jumping from slightly bloated WP with funky admin UI to slimline bbPress and having to reinvent the wheel when I want to make things look similar. At the same time, I don't have a resource for checking bbPress functions like the WP codex and nor do they follow the same naming logic or parameter logic.

    This isn't to say that I don't love WordPress. I agree that it's the best platform out there. But I do feel like I don't know what's happening with the development, which means I question wether or not I should develop my installations if that might just get deprecated. Further, for open-source, Automattic seem to try and keep things quite quiet. I know it's a competitive industry, but that's the choice the Press family faces. From an industry where a new release will earn the firm a few million we don't keep it all secret even though our competitors are there. We quite happily jump up and down telling customers about what's coming next month, next year and down the pipeline.

    What would be nice? Well, let's see a Wave style presentation of what's going to happen to the entire Press family with the advent of 3.0 - whenever that may come.

  23. Wow how time flies. This thread has reached an age of 8 months. I think it's time to provide some updates as to how far any of the ideas discussed have progressed.

  24. jimisaacs
    Posted 6 years ago #

    Organize this site into "Publishing" and "Contributing" bubbles. I believe it would solve many of the hurdles in communication. It would make a clear distinction between the platform's usability issues, and the platform's development structure. If there was a question where a development mission statement would go, this would answer it. People who use WordPress versus develop for it both have valid contributions to make to the whole of the project. What they don't have is a coherent place to live in the same forum. It would solve many issues in the organization of current pages and content. It would also allow content to be targeted, and hence more easily found by curious prowlers.

    Interactive direction and the development of those functionalities of course have a lot to do with each other. Unfortunately, they should not influence each other in an open medium, otherwise one is always trying to appease the other.

  25. kerryhilton
    Posted 6 years ago #

    Hi, this is Kerry and I'm glad to be here. I agree with UserVoice, because it works really well for a forum where users can post feature requests and bugs/problems with app. Using the UserVoice's free plan will might be a good idea for testing then if it did well it's the time to upgrade to paid plan. UserVoice offers the single sign-on feature in their $89/month plan.
    The one really big feature that's missing from the free plan is the single sign-on feature. This enables a user that is logged into webapp to remain logged in after they click on the Feedback tab and go to the UserVoice support forum. The problem I am seeing is that users click on the Feedback tab, go to UserVoice, and post feature requests as Anonymous. This is problematic because there is no way for you to tell which user posted the feature request, and there is no way for that user to see your reply (unless they go back to the UV forum to check, which they probably will not do). If you know who posted the feature request, you'll also have the option to contact that person via email and have a back-and-forth conversation about his/her feature request.
    cheap car insurance for young drivers

Topic Closed

This topic has been closed to new replies.

About this Topic