criteria clarification: change HTTP to HTTP(S) and drop FTP in select criteria

[Kamil Paral]

This has been already discussed before [1], but the discussion died down.
Here's an updated proposal.

Change the following:

1.
https://fedoraproject.org/wiki/Basic_Release_Criteria#Remote_package_sources
From: "When using a release-blocking dedicated installer image, the
installer must be able to use either HTTP or FTP repositories (or both) as
package sources. Release-blocking network install images must default to a
valid publicly-accessible package source."
To: "...must be able to use HTTP(S) repositories as package sources..."
Also add a new footnote:
"Covered repository types
This criterion only covers direct repository URLs ("baseurl"), and doesn't
cover mirrorlist or metalink URLs."

2. https://fedoraproject.org/wiki/Basic_Release_Criteria#Update_image
From: "The installer must be able to download and use an installer update
image from an HTTP server."
To: "...from an HTTP(S) server."

3.
https://fedoraproject.org/wiki/Fedora_33_Beta_Release_Criteria#Remote_pac...
From: "When using the dedicated installer images, the installer must be
able to use HTTP, FTP and NFS repositories as package sources."
To: "...must be able to use HTTP(S) and NFS repositories..."
Also update its footnotes in the same spirit.
Also add a new footnote:
"Covered repository types
This criterion only covers direct repository URLs ("baseurl"), and doesn't
cover mirrorlist or metalink URLs."

It will also have an effect on our test cases:

4.
https://fedoraproject.org/wiki/QA:Testcase_install_repository_HTTP/FTP_gr...
Rename to QA:Testcase_install_repository_HTTP_graphical
Update the contents by replacing HTTP with HTTP(S) and dropping FTP
mentions.

5.
https://fedoraproject.org/wiki/QA:Testcase_install_repository_HTTP/FTP_va...
Rename to QA:Testcase_install_repository_HTTP_variation
Update the contents by replacing HTTP with HTTP(S) and dropping FTP
mentions.

6. https://fedoraproject.org/wiki/QA:Testcase_Anaconda_updates.img_via_URL
Update the contents by replacing HTTP with HTTP(S).


Please approve or comment, thanks.

[1]
https://lists.fedoraproject.org/archives/list/[e-mail]...

[Matthew Miller]

On Mon, Jan 04, 2021 at 02:40:58PM +0100, Kamil Paral wrote:
>  To: "...must be able to use HTTP(S) repositories as package
> sources..." 
Let's drop the (S) and make it just HTTPS. With the parenthesis, I'm unclear
if it means "http or https, whichever works" or "both http and https".
And
in 2021+, if there's a weird case where https works but plain http does not,
the answer should be to fix it so http isn't needed.


-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Adam Williamson]

On Mon, 2021-01-04 at 11:30 -0500, Matthew Miller wrote:
>  On Mon, Jan 04, 2021 at 02:40:58PM +0100, Kamil Paral wrote:
>  > To: "...must be able to use HTTP(S) repositories as package sources..."
>  
>  Let's drop the (S) and make it just HTTPS. With the parenthesis, I'm unclear
>  if it means "http or https, whichever works" or "both http and
> https". And
>  in 2021+, if there's a weird case where https works but plain http does not,
>  the answer should be to fix it so http isn't needed. 
I guess the case for non-S is if you're just setting up a mirror on
your local network or something and there's really no need to go to the
trouble of getting a cert for it which the installer would trust...

I'm OK with both choices so far.
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

[Kamil Paral]

On Mon, Jan 4, 2021 at 5:30 PM Matthew Miller <mattdm(a)fedoraproject.org&gt;
wrote:

>  On Mon, Jan 04, 2021 at 02:40:58PM +0100, Kamil Paral wrote:
>  > To: "...must be able to use HTTP(S) repositories as package sources..."
>
>  Let's drop the (S) and make it just HTTPS. With the parenthesis, I'm
>  unclear
>  if it means "http or https, whichever works" or "both http and
> https". And
>  in 2021+, if there's a weird case where https works but plain http does
>  not,
>  the answer should be to fix it so http isn't needed.
>  
I'd like to keep HTTP required to be working. Because of the stubbornness
with which some applications (like browsers) reject self-signed
certificates, some local use cases (including debugging and development)
are unnecessarily difficult. If you think HTTP(S) is unclear, I can reword
it as "HTTP and HTTPS". Is that better?

[Matthew Miller]

On Tue, Jan 05, 2021 at 09:09:46AM +0100, Kamil Paral wrote:
>  I'd like to keep HTTP required to be working. Because of the
> stubbornness
>  with which some applications (like browsers) reject self-signed
>  certificates, some local use cases (including debugging and development)
>  are unnecessarily difficult. If you think HTTP(S) is unclear, I can reword
>  it as "HTTP and HTTPS". Is that better? 
I can live with that, but let's revisit in five years. :)


-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Kamil Paral]

On Mon, Jan 4, 2021 at 2:40 PM Kamil Paral <kparal(a)redhat.com&gt; wrote:

>  This has been already discussed before [1], but the discussion died
> down.
>  Here's an updated proposal.
>
>  Change the following:
>
>  1.
>  https://fedoraproject.org/wiki/Basic_Release_Criteria#Remote_package_sources
>  From: "When using a release-blocking dedicated installer image, the
>  installer must be able to use either HTTP or FTP repositories (or both) as
>  package sources. Release-blocking network install images must default to a
>  valid publicly-accessible package source."
>  To: "...must be able to use HTTP(S) repositories as package sources..."
>  Also add a new footnote:
>  "Covered repository types
>  This criterion only covers direct repository URLs ("baseurl"), and doesn't
>  cover mirrorlist or metalink URLs."
>
>  2. https://fedoraproject.org/wiki/Basic_Release_Criteria#Update_image
>  From: "The installer must be able to download and use an installer update
>  image from an HTTP server."
>  To: "...from an HTTP(S) server."
>
>  3.
>  https://fedoraproject.org/wiki/Fedora_33_Beta_Release_Criteria#Remote_pac...
>  From: "When using the dedicated installer images, the installer must be
>  able to use HTTP, FTP and NFS repositories as package sources."
>  To: "...must be able to use HTTP(S) and NFS repositories..."
>  Also update its footnotes in the same spirit.
>  Also add a new footnote:
>  "Covered repository types
>  This criterion only covers direct repository URLs ("baseurl"), and doesn't
>  cover mirrorlist or metalink URLs."
>
>  It will also have an effect on our test cases:
>
>  4.
>  https://fedoraproject.org/wiki/QA:Testcase_install_repository_HTTP/FTP_gr...
>  Rename to QA:Testcase_install_repository_HTTP_graphical
>  Update the contents by replacing HTTP with HTTP(S) and dropping FTP
>  mentions.
>
>  5.
>  https://fedoraproject.org/wiki/QA:Testcase_install_repository_HTTP/FTP_va...
>  Rename to QA:Testcase_install_repository_HTTP_variation
>  Update the contents by replacing HTTP with HTTP(S) and dropping FTP
>  mentions.
>
>  6. https://fedoraproject.org/wiki/QA:Testcase_Anaconda_updates.img_via_URL
>  Update the contents by replacing HTTP with HTTP(S).
>
>
>  Please approve or comment, thanks.
>
>  [1]
>
> https://lists.fedoraproject.org/archives/list/[e-mail]...
>  
Since there were no further concerns following Matthew's and Adam's emails,
I implemented the changes today:

https://fedoraproject.org/w/index.php?title=Basic_Release_Criteria&ty...
https://fedoraproject.org/w/index.php?title=Fedora_34_Beta_Release_Criter...
https://fedoraproject.org/w/index.php?title=QA%3ATestcase_install_reposit...
https://fedoraproject.org/w/index.php?title=QA%3ATestcase_install_reposit...
https://fedoraproject.org/w/index.php?title=QA%3ATestcase_Anaconda_update...
https://fedoraproject.org/w/index.php?title=Template%3AInstallation_test_...