For filing tickets with the Sysadmin team.
Progress report :)
Thu, Dec 12
@gladhorn any update?
Tue, Dec 10
Thank you, I will chat with Ben. pns nameservers are ready now for qtcon.org
PNS which @bcooksley said yesterday they should be
Exactly which 31-34 did you spread, pns31-34, dns31-34 or gns31-34 ?
Discussion with who? Did you prepare those nameservers or check if they are answering? I'll set them up in half an hour or so, but I would like to know who said this was ok to email.
There was discussion on irc, I then emailed the details of the new DNS servers 31-34 which freql then passed on
Sorry to interrupt, but what exactly is 'sent'?
Hi, please send me an email with instructions, I'll forward it to Qt Company IT. Reach me at email@example.com.
Mon, Dec 9
Sun, Dec 8
@ochurlaud: I was under the impression that KApiDox is already a framework, since it is listed along the Tier 1 frameworks... Anyways, I would be great to have it providing a more general scope than just KDE specific API documentation, but I think for now it is OK to just focus on our needs and maybe during the KF6 branching phase re-evaluate if one can make it also useful for others.
Sat, Dec 7
Apologies for going ahead with landing a version of this prior to you updating the review.
removed </ br> tag
Fri, Dec 6
Thu, Dec 5
The CI system can provide the Dependency Diagram information easily enough for this - we provide it already for the existing builds (not sure if it is used though)
If we want to generate the doc of the libs one by one, it means that we need to have the order of generation.
The proper fix would be to wrap the string in a Yii class that indicates to it that the content is already escaped, but the name of it escapes me at this time and it isn't hugely important in any case as few people should hit this.
Could you clarify what needs working on here?
Wed, Dec 4
The code is not valid PHP. I think you can just remove the <br /> tag. It's not like it is important anyway.
what if i pass "\n" in the string? . can you help me in running this locally so i can find a solution and test it too.
okay . understood this change is not gonna work. didn't tested this as i don't know how to run it locally. but i am interested in solving this . how can i?
Unfortunately we can't reuse the metadata that the CI system and kdesrc-build use, as some Frameworks have two libraries in them - with one often not having the GUI components in it (and thus having a much smaller dependency graph). We also don't record any information about anything external to KDE (like Qt).
The tag is broken in all likelihood because Yii will be performing escaping on the text passed to it (to prevent injections).
The change in question doesn't look like it is valid PHP - has this been tested?
Tue, Dec 3
Another idea about the issue raised for "tweaking the csss/html" :
Very interesting ideas!
- If the compilation is broken, we have bigger issues as projects should never fail to build from source (for long anyway)
- That would be required under this approach yes. (a rebuild of all projects that have API Documentation anyway, i'd like to see this limited to those projects that support and request this be enabled, as use of kapidox does require some setup work in the project itself)
With regards to the data needed for the Dependency Diagrams, this is why the CI system currently exports that information as part of it's builds. It's currently only available on the machine that runs api.kde.org, but we could probably make it publicly accessible - which we somewhat decouple the CI system and the API Documentation Generation.
About your very first point: for information, lxr.kde.org also relies on kdesrc-build to check out all the relevant sources. This has been working rather well for many years, I don't see that as "unwanted coupling of tools".
But OK, the rest of your email makes that point moot anyway :-)
In order to gain some more insights, I created a first proof of concept container (based in the OpenSuse13 CI container) to check where I will find problems in this approach. What I understood so far:
Mon, Dec 2
Given this isn't too sensitive, I see no reason not to make this public.
I've now added KDE Promo as requested.
Sun, Dec 1
@ognarb - Thanks for working on this! Maybe for the next step...how hard is it going to be to get a version of it going on a KDE server? Once we get it semi-working on a KDE server, people might be able to provide better feedback too if they can start playing around with a dev site. It sounds like you already have a lot of things set up like 2FA.
Can we subscribe the KDE Promo group to this secret task? ;)
Sat, Nov 30
Okido, thanks a lot. Will do that in a separate ticket.
speak to fregl probably as a good way in
Ok, then we will have to contact them.
old sysadmin Ticket ID #WHQ-9986 (10/2/16) discussed setting nameservers but i haven't found if anything happened after that
It was originally registered by someone else (maybe TQtC?), and we then had it point its dns servers to us so we could manage it
That is a good question.