Bugzilla – Full Text Bug Listing
| Summary: | [pmi] Add the Marketplace Client Drag-To-Install button to projects pages | ||
|---|---|---|---|
| Product: | Community | Reporter: | Wayne Beaton <wayne.beaton> |
| Component: | Project Management & Portal | Assignee: | Christopher Guindon <chris.guindon> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | chris.guindon, nathan |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | stalebug | ||
| Bug Depends on: | 365667 | ||
| Bug Blocks: | |||
|
Description
Wayne Beaton
Each MPC listing is built using two pieces of information, the update site which I believe we're already tracking, and a multi value field of Feature IDs. Building this into the project feature on the project management interface should be a fairly simple task. Do we want to automagically create a Marketplace Client installable drag source based on project-provided information? i.e. if the project specifies an update site and other information as a natural part of the release record, can we just generate the necessary information? Does something have to actually be in the Marketplace to work with the client? Or is it more meaningful to facilitate a project providing a link to an Eclipse Marketplace link that they've established? I think we provide an automagic solution for the project but let them tinker with it if they so wish. Also I think were more talking about adding a Drag-To-Install button rather then a listing inside MPC. (Changing the title of this bug as a result) From my past life as the Marketplace Admin, we really didnt want projects having a separate listing on MP as it would just be another thing they have to update. 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. 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. I prefer not to add more functionality to the PMI at this time. Feel free to reopen if you feel strongly that this is important. |