Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Team thoughts on continuous improvement 30
Revision as of 10:50, 26 June 2008 by Unnamed Poltroon (Talk) (New page: = WTP 3.0 Debriefing = == Purpose == Following our WTP 3.0 release, we want to have a short meeting with committers and contributors to discuss things were done well in the 3.0 release t...)
WTP 3.0 Debriefing
Purpose
Following our WTP 3.0 release, we want to have a short meeting with committers and contributors to discuss things were done well in the 3.0 release that we want to continue doing and what our project need to improve on. This can be things you don't like, things you like, things you want changed, improvements you think need to be made, process changes, etc. This feedback will become critical to our success for our next major release
Please use this page to express priorities, make notes, and brainstorm as many ideas as possible. This will serve as a seed list for the meeting on July 10th, 2008.
Seed list for 07/10/2008 discussion
- Newsgroups - Are we giving the proper attention? Should we have a rotation for newsgroup monitoring? There is a great deal of value we may be missing in keeping track of the kinds of problems real users are having. The consensus seems to be to leave it up to each component to ensure there is one team member watching the newsgroups ever week. Everyone should be more diligent about seeing queries without responses and forwarding them to the mailing list for help from the general committer community. (David)
- Perhaps we should do the debriefing more than once a year, maybe twice? (David)