As currently configured, a taskotron deployment will have the apache test page as its' root (https://taskotron-stg.fedoraproject.org is an example)
This should have some a much mroe user-frendly, relevant and pretty landing page - preferrably in some form of plain html or rendered markup.
This should use the css from https://bitbucket.org/fedoraqa/baseweb
I've written out a draft for this located here: http://roshi.fedorapeople.org/taskotron/
It's just html and rendered CSS from baseweb. A couple links are broken, but they'll be updated through ansible variables when pushed (according to tflink).
@roshi: Looks good.
As long as we don't have a landing page for Phab, it might be better to link to https://fedoraproject.org/wiki/QA/Phabricator rather than to https://phab.qadevel.cloud.fedoraproject.org/ in the "Issue Tracker" button.
Where will the page source code live, inside our libtaskotron docs/ directory or will we create a separate git repo for it?
I'll update the link. I didn't realize the phab page went to a generic login page :-/
I'm not sure where it's going to live specifically, but @tflink knows.
I'd argue that https://phab.qadevel.cloud.fedoraproject.org/maniphest/ would be a better choice than the wiki page
Where will the page source code live
https://bitbucket.org/fedoraqa/ansible-playbooks
I've updated the link for the issue tracker. I think the maniphest page is the best place to link to (kinda wondering why I didn't do that to begin with). I also updated the documentation link to point to our code on http://libtaskotron.readthedocs.org/en/latest/.
The file is attached, it merely relies on baseweb/static for its styles. If there isn't anything else I'll close this since those seemed to be the only issues...
File is here: {F2143} (it's also updated online here: http://roshi.fedorapeople.org/taskotron/ )
The landing page has been added to the ansible playbooks and deployed to taskotron-stg
https://bitbucket.org/fedoraqa/ansible-playbooks/commits/ce8a3f58e85c332e7eea1754546c9df4edc9f5d9