Maintenance of api.kde.org

[Jeremy Whiting]

Alex,

Last time I checked api.kde.org was generated by scripts in the
websites/quality-kde-org git repository. It includes instructions for
installing it locally, though the instructions are a bit outdated. I
think perl's setup scripts have changed since it was written since I
needed to tweak the install script to get it to install here (when I
was looking into it about 8 months ago or so). Poke me if you hit the
same issues and I can put a patch up on reviewboard if it's still
around my hard drive here somewhere...

thanks,
Jeremy

On Thu, Nov 5, 2015 at 4:58 PM, Alex Merry <alex.merry at kde.org> wrote:
> On 2015-11-05 09:22, Ben Cooksley wrote:
>>
>> Hi all,
>>
>> For some time it has been apparent that api.kde.org is experiencing
>> some issues with maintenance. It doesn't really fall into sysadmin's
>> domain, but developers often lack the knowledge on how to get Doxygen
>> working as needed to build projects API documentation. This isn't
>> helped by the setup not being simple for easy local testing.
>>
>> Any volunteers to look into it, fix some issues and generally make it
>> easier to work with for the future?
>
>
> This is my domain really, as maintainer of kapidox - kapidox was intended to
> make this simpler and easier, but currently it's only run on frameworks. I
> don't really know much about the automation on api.kde.org itself, though,
> and we need to figure out how to choose whether to run kapidox, kdelibs4's
> apidox generation scripts, or no apidox generation at all for a given
> project.
>
> I'm willing to put some time into this, but I'd need to be able to at least
> mirror api.kde.org's setup locally to try tweaking and testing things -
> going through Allen Winter every time I want to test something out (and then
> waiting for the cron jobs or whatever to run) is just too slow of a feedback
> cycle.
>
> Alex