Next gardening love project

[Allen Winter]

On Thursday, March 26, 2015 07:09:27 PM Jeremy Whiting wrote:
> David, Allen, Luigi,
> 
> The KDE gardening team has chosen as it's next target for gardening the
> documentation/api websites. https://community.kde.org/Gardening/docwebsites
> The initial objectives are there on the wiki, but feel free to
> modify/update them if I got anything wrong or something is already in the
> works. The general idea is to improve these sites by getting kf5 based
> applications/libraries apidocs, documentation, and code checks on them.
> Another good objective is to make them work faster/better by not recreating
> everything each day, but only incrementally updating their content somehow
> if possible. And finally I'd like to get bug products/components for each
> of them so if issues are found we can track the issues and fix them as a
> team.
> 
> In looking around bugs.kde.org tonight I saw docs.kde.org has a bug
> component under docs product, but I couldn't find any obvious components or
> products for api.kde.org or ebn itself. Would those make the most sense as
> their own products, or as components under a "websites" product or
> something?
> 
api.kde.org bugs were a component under the sysadmin product.
but then the sysadmin product was moved to https://sysadmin.kde.org/tickets (trellis desk)
so when I do get a api.kde.org bug report it comes from trellis