Andre Klapper <> changed:

           What    |Removed                     |Added
           Priority|Unprioritized               |Normal
            Summary|Disable new bug posting for |Disable new bug posting for
                   |some extensions             |some semantic extensions
                   |                            |(moving to GitHub)

--- Comment #2 from Andre Klapper <> ---
(In reply to Jeroen De Dauw from comment #0)
> I'd like to have new bug reports disabled for the following extensions:

That's possible. :)

> * Semantic Extra Special Properties

Does not seem to exist in

> I'd also like to have their descriptions updated to "The bugs for this
> extension are now tracked at $1

Note that
will not offer (and display) components that are disabled for new bug entry.
The only place where the descriptions would be still visible will be

Hence it's important to inform reporters also in other places where they are
expected to go.
Will you update the Extension homepages (e.g. ) to clearly say where to file
bug reports and enhancement requests?

What should happen with the existing open tickets in

Out of curiosity, what's the code location plan for vs
Github? Mirroring?

And just to mention it explicitly (but I guess you're aware of it), as other
semantic components (Semantic Glossary, SemanticBundle,
SemanticCompoundQueries, SemanticDrilldown, SemanticForms, SemanticFormsInputs,
SemanticSignup) would stay in Bugzilla, moving a ticket from one semantic
component to another will become harder if the other component is in a
different bugtracking system. Just saying, as I have no idea how often tickets
are moved (or initiallymis-filed) among semantic components.

(In reply to Jeroen De Dauw from comment #1)
> And Wikibase Database:

That's currently watched (default assignee) by wikidata-bugs@ so I assume it
requires clarification how to make sure that ticket notifications in GitHub are
still send to the Wikidata crew.

You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
Wikibugs-l mailing list

Reply via email to