https://bugzilla.wikimedia.org/show_bug.cgi?id=69603
Andre Klapper <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|Unprioritized |High --- Comment #8 from Andre Klapper <[email protected]> --- (In reply to C. Scott Ananian from comment #7) > Andre: we need to get this done before Wednesday Alright, let's see. Sorry, this got off the radar. > I think it would actually be best to create a new top-level component, > called "Offline content service". (Unfortunately this won't help much with > discoverability for those who want to file bugs against "Download as PDF", > but at least it's technically accurate.) > > Underneath this top-level component would be the components, "PDF renderer", > "ZIM renderer", "ePUB renderer", "Bundler", and "Service". I assume that reflects the code architecture? Is there some scheme so a non-developer could in theory understand how things are supposed to work? Regarding ZIM renderer, there is already an openZIM product: https://bugzilla.wikimedia.org/describecomponents.cgi?product=openZIM - how does this differentiate? What would be component descriptions? I have no idea what "Bundler" and "Service" do and how I could tell... In general, see https://www.mediawiki.org/wiki/Bug_management/Project_Maintainers#To_add_a_project_or_component for required info. We might also > have a "mwlib" component, although my understanding is that there is a > non-WMF bugtracker which is better suited. Any mwlib-specific bugs should > be transferred to the external bugtracker and closed. Currently the description for "Collection" at https://bugzilla.wikimedia.org/describecomponents.cgi?product=MediaWiki%20extensions says: Page collection extension for PDF/EPUB/ODT/OpenZIM/Okawix generation via PediaPress's mwlib backend (Homepage). Primarily for the Special:Book frontend. Note: There is an upstream bug tracker at http://pediapress.com/code/ maintained by PediaPress folks separately. ...which boils down to https://github.com/pediapress > But I'd be willing to > add a "mwlib" component for these issues if it would aid transition. I'd prefer to point people to https://github.com/pediapress instead and explain how they can realize that they should go there (proposals?). > The existing "Collection" component under extensions would be used only for > issues related to the extension itself (which communicates with the OCG > service, or with an external mwlib service), as Marcin wants. -- 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 [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
