(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.
Keywords: (none) => Atelier
OK on whiteboard, cause assignee assigned to himself
CC: (none) => marja11
(In reply to comment #1) > OK on whiteboard, cause assignee assigned to himself now really :/
Whiteboard: (none) => OK
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
added in cauldron.
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.
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?
Test code in this page: https://wiki.mageia.org/en/Atelier_Work_in_Progress
(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 => rdalvernyComponent: New RPM package request => wiki.mageia.orgCC: (none) => dmorganec, oliver.bgrSummary: Package mediawiki-bugzilla for our own usage => Add mediawiki-bugzilla to our wikiProduct: Mageia => WebsitesVersion: Cauldron => trunk
- 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 => dmorganecURL: https://github.com/LegNeato/mediawiki-bugzilla => https://github.com/mozilla/mediawiki-bugzilla
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
(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 => enhancementAssignee: dmorganec => sysadmin-bugsKeywords: Atelier => (none)