#296: Fix blocker bug tracker page and replace it with a static HTML page
-----------------------+-----------------------
Reporter: adamwill | Owner: tflink
Type: task | Status: new
Priority: major | Milestone: Fedora 18
Component: Wiki | Version:
Resolution: | Keywords:
Blocked By: | Blocking:
-----------------------+-----------------------
Comment (by johannbg):
Replying to [comment:2 adamwill]:
qa.2012-06-11-15.03.log.html
I don't think anyone said anything about there being a specific reason
for it
to be a wiki page during the meeting. What was the reason?
Yeah I've been to busy to attend or followed up on all the meetings and
will be for a another release cycle or two depending on the progress of
the systemd migration process and the followed up clean up process that
takes place when it's done.
The reason for it was consolidation as in we want(ed) the information for
reporters to use be in the same place.
Mediawiki was the only option at that time with it's limitations as have
been pointed out both in the present and we were aware of in the past.
There is nothing wrong with using some other solution but that means a lot
of work moving things from the wiki into that new thing or coming up with
a front end that keeps tap of all this stuff and presents it to reporters
for easy accessing.
If I can recall correctly the only solution suggested at that time that
held any potential water for success for the community, was the Fedora
community app which at that time was in (very) early stages and which
current status I'm unaware of. ( Reporters would just log in and all
relevant information would be presented to them or within a grasp )
We did look at various testing platforms ( not only for this ) but they as
well fell short one way or another...
--
Ticket URL: <
https://fedorahosted.org/fedora-qa/ticket/296#comment:4>
Fedora QA <
http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance