Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notice for qubes-tunnel testing #637

Closed
wants to merge 4 commits into from
Closed

Notice for qubes-tunnel testing #637

wants to merge 4 commits into from

Conversation

tasket
Copy link
Contributor

@tasket tasket commented Apr 25, 2018

Issues #3503 #3520

@andrewdavidwong
Copy link
Member

I'm slightly worried about the wording here:

and is recommended for most users on Qubes 3.2 and 4.0

@marmarek, any opinion?

@tasket
Copy link
Contributor Author

tasket commented Apr 26, 2018

I chose that wording because I feel that attempts to use the new scripts (in service already under different naming) will lead to fewer issues for users than the existing method... despite the testing status.

But please feel free to re-word it as you see fit.

@tasket
Copy link
Contributor Author

tasket commented Apr 26, 2018

Also wondering, since qubes-tunnel appears to be more of a direct contribution (per Patrick's indication in #3503 ) instead of a 'Qubes-contrib' optional package, whether it should just be added to the Qubes testing repositories.

@@ -12,6 +12,15 @@ redirect_from:
How To make a VPN Gateway in Qubes
==================================

## Note on new qubes-tunnel availability!

A streamlined VPN option is in testing phase and is recommended for most users on Qubes 3.2 and 4.0. It is currently [available here](https://github.com/tasket/qubes-doc) and qubes-users discussion is [here](https://groups.google.com/d/msgid/qubes-users/ee24f104-efbc-23f7-aca3-6be86104ddaf%40posteo.net).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is https://github.com/tasket/qubes-doc really the correct URL?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oops... that should be 'tasket/qubes-tunnel'

@andrewdavidwong
Copy link
Member

I chose that wording because I feel that attempts to use the new scripts (in service already under different naming) will lead to fewer issues for users than the existing method... despite the testing status.

But please feel free to re-word it as you see fit.

I guess the reason for my uncertainty is that I don't know what our official position regarding that package is. It seems somewhat strange to recommend something from a non-official source to all users. I'll leave it for @marmarek to decide.

Also wondering, since qubes-tunnel appears to be more of a direct contribution (per Patrick's indication in #3503 ) instead of a 'Qubes-contrib' optional package, whether it should just be added to the Qubes testing repositories.

Also for @marmarek to decide. If it's a contrib package, though, we should make sure to follow our procedure for such packages:
https://www.qubes-os.org/doc/package-contributions/

@tasket
Copy link
Contributor Author

tasket commented Apr 28, 2018

For reference, Marek and Patrick comments have it as a direct Qubes inclusion:
QubesOS/qubes-issues#3503 (comment)

I was just wondering if qubes-testing was a better repository in this case. Then it wouldn't seem as strange to recommend it (or to use wording asking users to help test).

@marmarek marmarek mentioned this pull request Jul 2, 2018
@andrewdavidwong
Copy link
Member

Closing this for now due to the prolonged lack of activity. If you believe this is a mistake, or if anyone would like this PR to remain open, please leave a comment, and we'll be happy to reopen this. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants