In my company (as probably in many) we are struggling to share the knowledge. This goes from product-specific knowledge (which would not fit on Stack Overflow) to more broad knowledge like the one related to libraries or Eclipse bugs (to name a few possibilities).
Once somebody finds a solution to a problem, usually they share it. But it may happen that they forget, or that they way they share it (an email, link on the wiki) is not good enough as users may no check it once the stumble upon the same problem. Probably most of them will just type the error on Google or Stack overflow.
Knowing most developers just go to Stack Overflow to check for the issues, it would be worth to leverage this adding a system that facilitated the spread of knowledge in the company. I think it would be handy a system that would allow us to:
- Create a list of questions (a private list as public lists are the same as tags) to which a given set of users can contribute adding existing or new questions, where we could search for issues in that list. Tags won't work as questions have a limit on the number of tags and it would pollute the questions with one tag per list, although the idea would be similar (private tags?). That way users have a place to check first of all.
- Notify members of the lists of new items (an RSS feed would work)
- Prioritize results on that list when searching
My questions are:
- Do you have any suggestion on how to implement this given the currently available options on Stack Overflow?
- If it's not feasible, there is any way we can code a solution and contribute it back to Stack Overflow? (I suspect no as I've not seen the source anywhere, but I may have not looked at the proper place)
- If neither of both would work, how can we suggest this feature for future releases of Stack Overflow? This message is enough?
EDIT: My main point is that tags can be somehow limiting if you have a cross-tag interest. Maybe you can filter all queries with all the tags involved, but doing so will give back results that you may not want (due to quality or not being completely related) and it may be that your interest can't be expressed properly by grouping tags.
Also, you may want to keep a set of questions that fit a specific theme relevant to you grouped and easily available. That could be done with the favorite flag. But you may want other people to see that list and contribute to it questions that fit the theme. That you can't.
For example, let's say me and my group are interested on issue that include: Struts 2, Spring Framework 2.5, Hibernate 3.0, CSS, jQuery, HTML5 and Tomcat. We may find handy to have a list to store relevant questions (project gives error XYZ, why? check there) as it becomes part of a tool you use daily (Stack Overflow). Also, filtering by tags all these concerns would return an empty list, but we want to keep the relation somehow.