Timeline for Help set Q&A (TeamDAG) product development priorities [closed]
Current License: CC BY-SA 3.0
Post Revisions
62 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 30, 2024 at 11:25 | history | closed |
Jonathan Leffler cottontail bad_coder CPlus Dave |
Not suitable for this site | |
| Aug 30, 2024 at 1:35 | review | Close votes | |||
| Aug 30, 2024 at 11:25 | |||||
| Sep 28, 2017 at 0:28 | history | edited | Joe FriendStaffMod | CC BY-SA 3.0 |
added link to update on current work
|
| Aug 11, 2017 at 23:06 | answer | added | Clement Cherlin | timeline score: -11 | |
| Aug 11, 2017 at 20:34 | history | edited | TylerH | CC BY-SA 3.0 |
Replacing imgur link with stack's imgur sub-domain to prevent linkrot
|
| Aug 11, 2017 at 19:56 | history | edited | Joe FriendStaffMod |
removed Featured tag
|
|
| Aug 9, 2017 at 21:23 | comment | added | Joe Friend StaffMod | @DForck42 working on something like that right now. It will be a "new feature/major feature improvement" notification. | |
| Aug 9, 2017 at 21:20 | comment | added | DForck42 | @JoeFriend was discussing with someone in chat. it'd be awesome if there was a developer blog where big changes were announced that could then be fed into the sidebar like the podcasts | |
| Aug 9, 2017 at 21:15 | comment | added | Joe Friend StaffMod | @DForck42 I hear you loud and clear. The DAG team is working on the right way to do just what you're asking. | |
| Aug 9, 2017 at 21:11 | comment | added | DForck42 | @JoeFriend ok. it'd be amazing if there was more visibility and communication into what's actually being worked on. IE a Trello board that y'all use to track where different things are at that we can look at. One of my biggest gripes as of late is that things either just get ignored, or get plopped on us without any prior notice (e.g. top nav on SO and flagging). OR, when things get declined there's usually no reason given or a very short reason, no real explanation. | |
| Aug 9, 2017 at 21:00 | comment | added | Joe Friend StaffMod | @DForck42 We are definitely working on improvements for the whole network and we consider the needs of all the sites. See my comment above. | |
| Aug 9, 2017 at 20:56 | comment | added | DForck42 | it'd be nice if network wide changes (a la flagging) were actually announced in a way that ALL sites on the network can see that it's happened, or is happening. or, y'know, some love got sent to the littler sites every once in a while rather than ONLY focusing on SO. I know it's the biggest site, but it's not the only one and hasn't been for a VERY long time | |
| Aug 9, 2017 at 19:18 | history | edited | Joe FriendStaffMod | CC BY-SA 3.0 |
added 661 characters in body
|
| Aug 9, 2017 at 18:11 | answer | added | pnuts | timeline score: 5 | |
| Aug 9, 2017 at 15:22 | comment | added | VonC | meta.stackexchange.com/q/286057/6309 would be nice too. | |
| Aug 9, 2017 at 8:46 | answer | added | Pro Q | timeline score: 3 | |
| Aug 9, 2017 at 5:52 | comment | added | polkovnikov.ph | Please, add to that list "hire someone who knows CSS". | |
| Aug 8, 2017 at 19:10 | answer | added | Ian Ringrose | timeline score: -22 | |
| Aug 8, 2017 at 19:03 | answer | added | Ian Ringrose | timeline score: 4 | |
| Aug 7, 2017 at 17:11 | answer | added | anon | timeline score: 7 | |
| Aug 5, 2017 at 12:19 | comment | added | user1803551 | @JoeFriend I'm confused as to how applying the search filter to the list of questions is related to the navigation bar. The behavior hasn't changed with the New Nav. | |
| Aug 4, 2017 at 17:13 | history | edited | Peter Mortensen | CC BY-SA 3.0 |
Active reading.
|
| Aug 4, 2017 at 13:57 | comment | added | Joe Friend StaffMod | @Makyen Totally agree. We will ultimately do some work across these themes when it is low hanging fruit. The goal of this exercise is to figure out where to focus our attention in general. Also, it's important to realize that we want to make changes that have an impact. So we will run experiments and not push things out to the entire site unless they have the impact we are hoping for. That way we don't pile up lots of changes without confirm that they actually address the problem. | |
| Aug 4, 2017 at 13:53 | comment | added | Joe Friend StaffMod | @user1803551 I added it to the Experienced user workflows theme since it is related to the New Nav. | |
| Aug 4, 2017 at 13:52 | history | edited | Joe FriendStaffMod | CC BY-SA 3.0 |
Added additional links to relevant SO/SE posts
|
| Aug 3, 2017 at 22:43 | comment | added | user1803551 | Can we add this to the "SO works for me" theme? | |
| Aug 3, 2017 at 17:50 | history | edited | MachavityMod | CC BY-SA 3.0 |
Clarified which review problem was being linked
|
| Aug 2, 2017 at 18:14 | comment | added | Makyen Mod | Organizing RFEs by what they affect is needed/beneficial, but they should also be grouped by their effort required to implement (& expected user experience impact). As it is, some requests have existed for years that are very low-effort to improve (e.g. change the text descriptions for action buttons in review queues to reflect consensus/audits of how they should be used). Before starting long, difficult projects, take a few days to pick off the low hanging fruit. Developer time is a limited resource, you should first do what provides the best return on investing that limited resource. | |
| Aug 2, 2017 at 7:44 | answer | added | l4mpi | timeline score: 24 | |
| Aug 2, 2017 at 6:27 | comment | added | Makyen Mod | @MonicaCellio, Just FYI: While there was feedback provided on MSO regarding the new top-nav, it was also largely presented as a fait accompli to SO (or at least as a "this is happening whether you like it or not"). There were some changes made based on the feedback, but it certainly wasn't something that was made to fit a requests by users on SO/MSO. The reception of the new top-nav was quite mixed, with several of us developing user scripts to largely change it back to what it used to be (with, perhaps, some of the new features added in). | |
| Aug 2, 2017 at 5:14 | answer | added | Karan Desai | timeline score: 12 | |
| Aug 1, 2017 at 19:05 | comment | added | Monica Cellio | @JoeFriend I agree that MSO is a right place to bring these things up. It's just that as a "citizen" of the broader network, I sometimes feel like we don't get a chance to have our input, questions, & concerns heard unless we happen to stumble on posts like this. For example, the new topbar was developed with SO-specific needs in mind, and a lot of us elsewhere on the network have real problems with parts of its design. How do we get those addressed before being given a fait accompli? Improving Q&A (like this post) helps all of us; let's find a way to get broad input too. Thanks. | |
| Aug 1, 2017 at 18:52 | comment | added | Joe Friend StaffMod | @MonicaCellio Great question. Yes, DAG serves the entire network. In fact, we are currently working on updating the header and footer across the networks (should roll out this month). However, in reviewing the outstanding asks, many of the features and the themes that seem most critical are massive-scale problems that affect SO much more than almost all other sites, so meta.so seemed to be the right location for the post. | |
| Aug 1, 2017 at 18:15 | comment | added | Monica Cellio | Does DAG serve only Stack Overflow? If not, shouldn't this question be on MSE, where lots of highly-committed users who just don't happen to use SO congregate? | |
| Aug 1, 2017 at 16:41 | comment | added | Joe Friend StaffMod | @Rubén I considered that approach but I wanted the community to have more flexibility in giving feedback. | |
| Aug 1, 2017 at 16:39 | comment | added | Wicket | Am I the only one that think that the OP should post a answer for each theme ? Right now, this Q&A has three answers about Question Quality... | |
| Aug 1, 2017 at 15:03 | history | edited | Joe FriendStaffMod | CC BY-SA 3.0 |
clarified title
|
| Aug 1, 2017 at 14:37 | comment | added | John Y | Come on, people! We're programmers, we use Git (or similar), right? The obvious meaning for DAG (particularly in all caps like that) is directed acyclic graph! Amirite? | |
| Aug 1, 2017 at 13:58 | answer | added | MachavityMod | timeline score: 23 | |
| Aug 1, 2017 at 9:03 | comment | added | Tieson T. | @AndrasDeak Like this feature request? | |
| Aug 1, 2017 at 6:53 | answer | added | Frank Schmitt | timeline score: 32 | |
| Aug 1, 2017 at 0:04 | answer | added | Suragch | timeline score: 31 | |
| Jul 31, 2017 at 23:35 | comment | added | Kevin Workman | @AndrasDeak I think that's part of the problem. New users have no incentive to fix their posts because nobody will see it anyway, and experienced users have no incentive to go back and look at old questions because they're almost never updated. Fixing both of these would go a long way towards overall question quality, imho. The point is not to force anybody to do anything, but to make it what they naturally want to do. | |
| Jul 31, 2017 at 23:25 | comment | added | Andras Deak -- Слава Україні | @KevinWorkman don't forget that there's no way for downvoters to be notified if a question has been fixed up, so even if someone fixes their post, most of the downvotes are bound to stay. I'm sure there's a corresponding feature-request around...but if users complained about seeing their own rep loss, surely they'd revolt if they got notifications about "this question you downvoted has gone through a major edit"... | |
| Jul 31, 2017 at 22:55 | comment | added | Kevin Workman | The second half of the question quality theme user story should be something like: "If my questions does get downvoted or closed, the best way for me to get answers is by editing my post to fix the problems. Downvotes feel like a tool instead of a peronal attack." As of now, users have zero incentive to fixing posts instead of just posting more bad questions. | |
| Jul 31, 2017 at 19:50 | comment | added | Joe Friend StaffMod | @NathanOliver That's a good one. I had a search category and had example posts like that one in it. I decided to narrow the choices down to just three and dropped search since I think SO will have to improve there for Channels to succeed. That said, the dupe scenario needs search improvements to really shine. | |
| Jul 31, 2017 at 18:56 | comment | added | NathanOliver | This is somewhat different than the dupe improvement in the question but I think it complements it. The dupe search should be more flexible and use synonyms to help the OP find a dupe before they even post a question. | |
| Jul 31, 2017 at 17:45 | answer | added | AndyMod | timeline score: 105 | |
| Jul 31, 2017 at 16:40 | history | edited | TarynStaffMod |
edited tags
|
|
| Jul 31, 2017 at 16:33 | comment | added | Joe Friend StaffMod | @JonClements We definitely work closely with the community team on our backlog. They not only set priorities for the community request but have a voice into our overall plan for improvements. Wouldn't have it any other way. As far as the team charter, DAG can work on anything within the context of Q&A as well as site-wide features like sign up/sign in, user messaging and on boarding, and the navigation/chrome. So our scope is fairly broad. The purpose of this post is to narrow that down for the near term. | |
| Jul 31, 2017 at 16:29 | comment | added | Joe Friend StaffMod | @gnat I added those links to the relevant parts of the post. | |
| Jul 31, 2017 at 16:29 | history | edited | Joe FriendStaffMod | CC BY-SA 3.0 |
Added additional links to relevant SO/SE posts
|
| Jul 31, 2017 at 14:59 | comment | added | Jon Clements Mod | @Joe I'm still slightly unclear how much resides within the team's remit. Just picking something ottomh - let's say weighting close votes based on badges and possibly extending the gold badge beyond duplicate closure etc... I imagine the amount of "development" work there would be less than the analysis for what impact it would have had, other considerations it may have to the network, maybe do trial runs, etc...I imagine concerns from the CM team is going to sway what actually gets/can get worked on here... | |
| Jul 31, 2017 at 14:52 | comment | added | gnat | I see, thanks. Consider editing in reference to that post to help other readers see. Another thing I would like to understand better - speaking of "Improved duplicate question discovery/prominence", does this feature request fit under this investment or it should be considered separately: Could: “Possible duplicate of..” be given prominence for answering users? | |
| Jul 31, 2017 at 14:49 | comment | added | Joe Friend StaffMod | @gnat Definitely NOT ignoring the post you linked to. As you can see, most of the feature areas above come directly from meta posts. Happy to have you and others point out others for the team to mine for good ideas. | |
| Jul 31, 2017 at 14:46 | answer | added | Makoto | timeline score: 0 | |
| Jul 31, 2017 at 14:45 | comment | added | gnat | there was somewhat similar feedback request at MSE: Let's Plan the Second Iteration of the Stack Exchange Quality Project! - did you consider picking suggestions from there or it can be assumed to be ignored for DAG purposes? | |
| Jul 31, 2017 at 14:26 | comment | added | Joe Friend StaffMod | @ryanyuyu Voting on the theme. The individual features are just examples of what we could work on. | |
| Jul 31, 2017 at 14:24 | comment | added | ryanyuyu | So we're voting on which bucket/theme we want to see worked first? Or voting on specific tasks/features within those buckets? | |
| Jul 31, 2017 at 14:21 | answer | added | enderland | timeline score: 193 | |
| Jul 31, 2017 at 14:10 | comment | added | I haz kode | Users come and go, whether new or old. Quality content is the anchor and one is what one focuses on. New users need to get with it. (runs away) | |
| Jul 31, 2017 at 13:59 | history | asked | Joe FriendStaffMod | CC BY-SA 3.0 |