Bug 6703 - Add mediawiki-bugzilla to our wiki
Summary: Add mediawiki-bugzilla to our wiki
Status: NEW
Alias: None
Product: Websites
Classification: Unclassified
Component: wiki.mageia.org (show other bugs)
Version: trunk
Hardware: i586 Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Sysadmin Team
QA Contact:
URL: https://github.com/mozilla/mediawiki-...
Whiteboard: OK
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-05 17:36 CEST by Romain d'Alverny
Modified: 2023-09-25 10:50 CEST (History)
4 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Romain d'Alverny 2012-07-05 17:36:33 CEST
(this is a reminder note for myself at this point)

I'd like us to be able to make Bugzilla reports inside the wiki.

On one end, it needs to be packaged, so sysadmin can install it on our setup.

On the other end, it needs Bugzilla's REST API too - https://wiki.mozilla.org/Bugzilla:REST_API#Your_Own_Installation . It's not packaged either.

Another solution is to add support for xml-rpc or json-rpc in mediawiki-bugzilla; those interfaces are already available.
Romain d'Alverny 2012-07-05 17:36:42 CEST

Keywords: (none) => Atelier

Comment 1 Marja Van Waes 2012-07-06 13:23:24 CEST
OK on whiteboard, cause assignee assigned to himself

CC: (none) => marja11

Comment 2 Marja Van Waes 2012-07-06 13:24:25 CEST
(In reply to comment #1)
> OK on whiteboard, cause assignee assigned to himself

now really :/

Whiteboard: (none) => OK

Comment 3 Romain d'Alverny 2012-07-27 17:40:46 CEST
Sent a patch to upstream to support directly xml-rpc: https://github.com/mozilla/mediawiki-bugzilla/pull/11

I successfully tried it on a local instance of Mediawiki (1.19.1 though - our current prod version is 1.16.5; would be worth a try though) against our current Bugzilla.

Assignee: rdalverny => dmorganec

Comment 4 D Morgan 2012-07-28 02:28:13 CEST
added in cauldron.
Comment 5 Romain d'Alverny 2012-08-03 21:55:54 CEST
Actually, it happens that we're using a PostgreSQL db backend, and the extension currently only supports MySQL... so it won't work with caching right now.

There's a patch waiting for that (https://github.com/mozilla/mediawiki-bugzilla/pull/12) but it's not the only one in row.
Comment 6 Romain d'Alverny 2012-11-12 19:47:44 CET
Not too sure where we are now :-p

The code is moving a bit upstream - and I would like us to use memcache or apc for caching, instead of pgsql. Will be easier (no SQL to manage) and faster.

That makes the following steps:

1. ensuring memcache or apc is available from our wiki server;
2. repackage the extension with the right patches from upstream (master + https://github.com/mozilla/mediawiki-bugzilla/pull/9.diff)
3. find how we can configure the extension (on my dev station, it's done by appending (manually updated) configuration PHP code to LocalSettings.php - how can we map this to our own setup?
Comment 7 Romain d'Alverny 2012-11-12 19:54:50 CET
Test code in this page: https://wiki.mageia.org/en/Atelier_Work_in_Progress
Comment 8 Marja Van Waes 2012-11-12 20:29:41 CET
(In reply to comment #6)
> Not too sure where we are now :-p
> 
> The code is moving a bit upstream - and I would like us to use memcache or apc
> for caching, instead of pgsql. Will be easier (no SQL to manage) and faster.
> 
> That makes the following steps:
> 
> 1. ensuring memcache or apc is available from our wiki server;
> 2. repackage the extension with the right patches from upstream (master +
> https://github.com/mozilla/mediawiki-bugzilla/pull/9.diff)
> 3. find how we can configure the extension (on my dev station, it's done by
> appending (manually updated) configuration PHP code to LocalSettings.php - how
> can we map this to our own setup?

(In reply to comment #7)
> Test code in this page: https://wiki.mageia.org/en/Atelier_Work_in_Progress

cc'ing obgr_seneca because he is working on upgrading our wiki
(see bug 7440, bug 7443, bug 7445),
just in case that makes a difference for this extension

(Something went wrong when I tried to change product to websites, the component doesn't change along with it)

Assignee: dmorganec => rdalverny
Component: New RPM package request => wiki.mageia.org
CC: (none) => dmorganec, oliver.bgr
Summary: Package mediawiki-bugzilla for our own usage => Add mediawiki-bugzilla to our wiki
Product: Mageia => Websites
Version: Cauldron => trunk

Comment 9 Romain d'Alverny 2013-04-15 10:22:37 CEST
 - https://github.com/mozilla/mediawiki-bugzilla master branch is now ready (merged previous PR), can be repackaged.

 - can we push this on the wiki server? (with memcache or pgsql as a backend)?

Assignee: rdalverny => dmorganec
URL: https://github.com/LegNeato/mediawiki-bugzilla => https://github.com/mozilla/mediawiki-bugzilla

Comment 10 Jose Manuel López 2023-09-25 09:18:40 CEST
Are we aware that bugs can be reported from the wiki? or that, according to the last comment, this is finished??

If so, can we close this old bug???

Greetings!!

CC: (none) => joselp

Comment 11 Marja Van Waes 2023-09-25 10:50:55 CEST
(In reply to Jose Manuel López from comment #10)
> Are we aware that bugs can be reported from the wiki? or that, according to
> the last comment, this is finished??
> 
> If so, can we close this old bug???
> 

This was never implemented.

Reassigning to our sysadmin team.

Only the sysadmins have the needed rights to do this, so there is no need for Atelier Team to bother about it.

Lowering "Severity" to enhancement

Severity: normal => enhancement
Assignee: dmorganec => sysadmin-bugs
Keywords: Atelier => (none)


Note You need to log in before you can comment on or make changes to this bug.