Bugzilla – Full Text Bug Listing
| Summary: | [pmi] Inform project members when the project home page is the standard about page. | ||
|---|---|---|---|
| Product: | Community | Reporter: | Benjamin Bentmann <bentmann> |
| Component: | Project Management & Portal | Assignee: | Portal Bugzilla Dummy Inbox <portal-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | david_williams, ed, jasonweathersby, paul, wayne.beaton |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | stalebug | ||
| Bug Depends on: | 375997 | ||
| Bug Blocks: | |||
|
Description
Benjamin Bentmann
The BIRT project is also experiencing the same problem. We do have the correct URL on our home page. We've had a lot of trouble trying to get this check right over the years. I'm inclined to just turn off checking for this. Thoughts? Disabling this check is fine with the BIRT team. (In reply to comment #2) > We've had a lot of trouble trying to get this check right over the years. > > I'm inclined to just turn off checking for this. Thoughts? Got so far and now giving up ;-) ? But sure, disabling is fine if the maintenance doesn't justify the benefit. I would start by turning it off ... maybe leave behind a bug to fix it someday? But, the way it is now, when there are "false alarm" messages it tends to cause all such messages to be ignored ... well, by some people ... so I hear. :) (In reply to comment #4) > (In reply to comment #2) > > We've had a lot of trouble trying to get this check right over the years. > > > > I'm inclined to just turn off checking for this. Thoughts? > > Got so far and now giving up ;-) ? > I've been in a "less is more" sort of phase. I think that the project summary pages have a lot of benefit for projects. I think that a better approach is to show projects what they need to do to reap the benefit and leave it up to them to decide if they want to take advantage. (In reply to comment #5) > But, the way it is now, when there are "false alarm" messages it tends to cause > all such messages to be ignored ... well, by some people ... so I hear. :) Agreed. I know that I tend to ignore them ;-) I kind of ignore the messages since I get 12 of them, at most two actually relevant to me. For MDT/OCL, the message is particularly odd since the project meta-data points at a page auto-generated by the Foundation. http://www.eclipse.org/projects/project.php?id=modeling.mdt.ocl So either the auto-generator is deficient or the fault report fails to identify the deficient portal meta-data. (In reply to comment #7) > For MDT/OCL, the message is particularly odd since the project meta-data points > at a page auto-generated by the Foundation. It's not particularly odd. It's a direct result of (a) trying to impose too many rules on projects, and (b) the liability inherent in infrastructure developed to enforce those rules. Let's try to do this better with the new project management infrastructure. This is just one bit of information that should be presented to project members on their dashboard and as part of a single email that aggregates the many different issues that need to be dealt with. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. We've been checking for this sort of thing during release reviews. I like this better than sending out (possibly) bogus emails. Turning off the notifications and investigating during a release view is technically a fix, so I'm marking this as FIXED. |