Project

General

Profile

Actions

Feature #1519

closed

allow to enter feedback to the extensions; public or only for authors

Added by Dennis Roczek over 8 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Category:
Plone
Target version:
-
Start date:
Due date:
% Done:

100%

Tags:

Description

bug ticket moved from https://bugs.documentfoundation.org/show_bug.cgi?id=63299

Petr Mladek 2013-04-09 08:09:51 UTC
Some extensions can't be supported by TDF easily because they are hard to build, use, or are too language specific. These should be supported by the author.

We need an easy way how to contact the author. It can be partly solved by the enhancement bug #58423. But some authors does not have its own bugzilla. We need to contact them another way.

One possibility would be to make the authors E-mail address easily accessible from the extensions web site. Would be possible to add a button that would open E-mail client and prefill the address?

Another solution would be to allow adding comments for each extension and send them automatically to the authors.

The second solution has the advantage that other users will see the feedback. They could share hints and suggestions. They could be prepared for potential problems even before installing the extension. IMHO, this is the best way how to handle support for 3rd party extensions that are not supported by TDF.
Actions #1

Updated by Andreas Mantke over 4 years ago

The latest versions of the Plone add-ons already habe such feedback form for extension and template projects. But I'm afraid this versions will never reach TDFs Servers, because nobody in the infra team is able vor willing to run buildout.

Actions #2

Updated by Guilhem Moulin over 4 years ago

Andreas Mantke wrote:

But I'm afraid this versions will never reach TDFs Servers, because nobody in the infra team is able vor willing to run buildout.

Wow. FWIW, while this message only came to my eyes a few minutes ago, I believe a buildout was run pretty much at the same time you posted it. And was followed with a fair amount of time chasing regressions. Please understand the reasoning behind the infra's time conservative policy and don't misinterpret that for malice or incompetence, especially during migration periods. Thankyouverymuch.

Actions #3

Updated by Guilhem Moulin over 4 years ago

And to put the “already” into perspective for this 4 years old bug bug, my understanding from reading the changelog is that the feature was added to 0.31 released on 2019-05-12. Thank you for taking care of updating the addon until last autumn, but the infra team has too much on their shoulder right now to follow up on every single release.

Actions #4

Updated by Andreas Mantke over 4 years ago

Maybe there are too few ressources spent for infra, but too much on other topics with no messurable output for the project.
I think we could close this feature request with status solved.

Actions #5

Updated by Andreas Mantke over 4 years ago

  • % Done changed from 0 to 100

Solved

Actions #6

Updated by Andreas Mantke over 4 years ago

  • Status changed from New to Resolved
Actions #7

Updated by Andreas Mantke over 4 years ago

  • Status changed from Resolved to Closed
Actions #8

Updated by Florian Effenberger over 4 years ago

Maybe there are too few ressources spent for infra, but too much on
other topics with no messurable output for the project.

This is a ticketing system. If you have complaints about the project's
direction, there are other platforms to discuss this with the community.

Actions #9

Updated by Andreas Mantke over 4 years ago

Ai, ai, captain!

Have fun with the feedback form and the new features and improvements

Actions

Also available in: Atom PDF