Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] [WARNING] SimRel Headed Off the Tracks

On Wed, Jan 29, 2020 at 2:57 PM Ed Merks <ed.merks@xxxxxxxxx> wrote:
Clearly we digress here.  In any case, this bugzilla is open for
removing invalid marketplace listings:

Many failures are pretty clear.  The host no longer exists so clearly
the listing is completely bogus...

I know the bug and I have commented on it and chased people to drop broken listings and etc. But this is clearly not working thus we need someone from Foundation to either step in or open the management of the marketplace to the community so we can deliver better user experience.

More comments below.

On 29.01.2020 13:34, Aleksandar Kurtakov wrote:
> So who is in charge of marketplace content?

That's unclear.  It's kind of distributed as are most things. The user
create/edits their listing, but until I implemented something to test
it, no one tested it. There is no established process for removal.  I
think only foundation staff can remove listings. And of course, like
everyone else, the foundation staff is overloaded for lack of resource...

> I can't believe we don't have a way to remove non-installable features
> based on these reports. After all each release there is compatibility
> with the latest  simrel added. Who does that? How? Can community
> influence help with that?
> IMHO claimed but not actually supported compatibility should be auto
> removed from the market place entry. Entries with nothing installable
> should be removed.
I agree, but I'd hate for errors in my testing to cause a listing to be
removed for bogus reasons.
> As I would expect something like "Eclipse Foundation doesn't have
> resources to develop that" popping up in the discussion - how can the
> community help?  Any pointers are welcome.
I think the report pretty much does the job, assuming no errors in the
testing process itself.

We have to be 100% sure in the report - yes! But even more importantly it has to be hooked with some automated run, notify (maintainer should be able to point issue in reporting to stop removal or fix the listing), remove if no action cycle and this is not existing AFAIK.
> Wayne, I point to you with these questions as you should at least be
> able to ask the correct person to jump in.
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Alexander Kurtakov
Red Hat Eclipse Team

Back to the top