Ticket #1664 (closed enhancement: fixed)

Opened 5 years ago

Last modified 5 years ago

request of "Test_Results" name space

Reported by: liam Owned by: mmcgrath
Priority: major Milestone:
Component: General Version:
Severity: Normal Keywords:
Cc: jlaska, ianweller, nigelj, spot, pfrields Blocked By:
Blocking: Sensitive:

Description

problem

We already have the Test_Day namespace ,so the test day's wiki page can be edited by anonymous users, but to other tests,such as installation test, we can not get anonymous feedback in wiki.

enhancement recommendation

we need to create a "Test_Results" namespace which would be generic for any non-test day collaboration. This will be convenient to help us collect test results of non-test day from anonymous users.

Change History

comment:1 Changed 5 years ago by pfrields

  • Cc pfrields added; pfrields@… removed

comment:2 follow-up: ↓ 3 Changed 5 years ago by mmcgrath

Give me an example of a test result.

comment:3 in reply to: ↑ 2 Changed 5 years ago by pfrields

Replying to mmcgrath:

Give me an example of a test result.

Any results from organized testing, such as seen here: https://fedoraproject.org/wiki/Test_Day:2009-09-09_Radeon#Results

(You could substitute any Test Day page in there and get similar examples.)

In case it's unclear, what's being requested is to make the "Test_Day" namespace more universal, so that we can gather all results from focused community testing -- not just from Test Days, but from organized Anaconda testing, or run-throughs on snapshots or RCs -- in one namespace, instead of having three, four, or more. "Test_Results" makes sense as a more generic name than "Test_Day," which is only about one type of event.

comment:4 Changed 5 years ago by jlaska

Hi Mike, Liam is interested in allowing for anonymous contributions to installation test events in Fedora QA. For example ... https://fedoraproject.org/wiki/Category:Fedora_12_Test_Results

I like the idea of using a single namespace for anonymous test feedback. However, since we've already had 1 mass page rename, I wonder if this question would come up again for another future use for anonymous feedback in QA. I don't have any preference on the name, but do others think that one of the following be more generic any future QA uses?

  • Test_Results:
  • Results:
  • Testing:
  • Public:

comment:5 Changed 5 years ago by spot

We need to be extremely careful what we use the anonymous namespace for, and how we name it.

The reason I signed off on permitting an anonymous namespace for Test_Day: was that I determined that it was safe to assume that the results reported during Test Days were not copyrightable, thus, there was no worry about not having that content under the CLA (we have to assume anonymous users have not signed it). So, a "Test_Results:" namespace would be fine, but I am extremely hesitant to make it more broad than that, definitely not a "Public:" or "Testing:".

comment:6 Changed 5 years ago by jlaska

Thanks for the guidance Spot ... let's go with Test_Results.

comment:7 Changed 5 years ago by mmcgrath

  • Status changed from new to assigned

Ok, so we're go to get rid of "Test_Day" and have instead a "Test_Results" do you want the Test_Day pages moved to Test_Results?

comment:8 follow-up: ↓ 10 Changed 5 years ago by mmcgrath

Ok, Test_Results has been created. I've not killed off Test_Day until I get the ok from someone in this ticket. But please do verify the new space is working and let me know when I can destroy the old.

comment:9 Changed 5 years ago by ianweller

I strongly recommend the removal of Test_Day and moving (with redirection, obviously) of all pages to the new namespace.

comment:10 in reply to: ↑ 8 Changed 5 years ago by liam

Replying to mmcgrath:

Ok, Test_Results has been created. I've not killed off Test_Day until I get the ok from someone in this ticket. But please do verify the new space is working and let me know when I can destroy the old.

Thanks for mmcgrath, I create a page with this name space ,it works.

comment:11 Changed 5 years ago by mmcgrath

  • Status changed from assigned to closed
  • Resolution set to fixed

Sounds like all is well. I'll close this ticket. If we need to open it again, just open it :)

Note: See TracTickets for help on using tickets.