Help adding documentation to Qubes Repository

33 views
Skip to first unread message

PR

unread,
May 11, 2017, 5:51:53 PM5/11/17
to qubes-users
Hello,

I need some help understanding how the collaborative documentation with
GitHub works.

I like to write down some notes after I've been able to make something work.

This might sound poor to the Linux Pro, but helps me in case I need to
repeat those steps again.

As such I tried to create a page about multimedia on qubes, summarizing
the steps I took to watch content from Spotify, Amazon Prime, Netflix
and to watch DVDs.

I've created a new page on Github, but the content is not shown as
doc/text but as code.

How to play multimedia content

https://github.com/phrabe/qubes-doc/blob/patch-2/configuration/multimedia

I also don't know if I need to do anything so that content gets either
published to the main branch or if it is not worth it.

Any help would be appreciated.

- P

Zrubi

unread,
May 12, 2017, 3:39:23 AM5/12/17
to PR, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 05/11/2017 11:51 PM, 'PR' via qubes-users wrote:
> Hello,
>
> I need some help understanding how the collaborative documentation
> with GitHub works.

https://www.qubes-os.org/doc/doc-guidelines/

TL;DR:
you only missed the create a pull request part.


- --
Zrubi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJZFWaVAAoJEH7adOMCkunmwXIP/0UQyl6MHuZ3SS3g8RwD9Keb
B94S5E7dXbadpkr91wJhmvLPg7Zki+hQM3NaLMbYywpoTtS0XNqWm3nqLHOhMPv3
LEUYJ8BmV6nzk0JdDfW0NQ9+XKJ1qS5Vf8W+vzmpwKUHHo2HfZk/2+DtFSHYFboG
Z3QYqqqlxRVED9DfCnG86LfNlIWMy6HO0GIGkikU/XQZRljP0mr5S8bq9yxFuOGO
P7l++S33dh6NWG1j9gMIcZMDB8JFJerwk9yz+8JtfdTDWyx72mE7T0ctpJWR3yjU
TfyiNeY7m+Y3AcceM2XQAjntrhsoaNebk3QaJ1vco5FVGZq2r2SbenA8sY4QodKy
VsDfNYS+zMD3STO/tQisMik3A2Vx6vweOJZJnGkHHvs+YJceTn0HXFq1C/oo/2G5
gUHxlMvrB8KzkLhgif8jB6W47qKBfGkb59l0obW1AvRXCKOHew7i9spCeoic0Pj6
JSAIZPEx7CwRKof/pWrIMP2oZ2sRPBbEsepB9XLxF4FuFvVD55Oy92/+xeF5H/FT
fzhkjyyXdpBBQDxrWXGIb7VvY088vTNN1EWBVt3L5TRC4dzK0Bdp/LcYFK4RINgC
MsA8MRTQtWVQz53nPo3wV2lL6EjEe4LpTzFbUQ/kFAWML1XSQ8q+MJOTU8j26DOg
akrCKaEDP/iikTJFAFn/
=MsWk
-----END PGP SIGNATURE-----

Zrubi

unread,
May 12, 2017, 3:50:04 AM5/12/17
to PR, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 05/12/2017 09:39 AM, Zrubi wrote:
> On 05/11/2017 11:51 PM, 'PR' via qubes-users wrote:
>> Hello,
>
>> I need some help understanding how the collaborative
>> documentation with GitHub works.
>
> https://www.qubes-os.org/doc/doc-guidelines/
>
> TL;DR: you only missed the create a pull request part.
>
>

Or if it is your pull request:
https://github.com/QubesOS/qubes-doc/pull/418

Then you made it right.
Now you just have to wait for someone to review and accept it into the
official doc's


- --
Zrubi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJZFWkXAAoJEH7adOMCkunmdnsP/RDMnkUZLHsYt1FfEOK9tFDM
7yhrqJzszYd99zWjJesdvne1ojUUekCA8hcyAfYYz2MbUhVvhGLX95P7Qv/TEgzI
gREkt3+dAJDgOM/FdW2Jw8PFb60ufQOdnTGyGmP4U0NS6Su1ir2HFKYRkub8lfiw
SOBgzZ2HDE2whcP9f4HS/JHaoBPjuDpR6VMAjLf2/Rrmx8oupGpGOr4BR9VFDZVG
ITzdcUBmEZYsAKRnpKW4xAXwxTMZlYmViS4OrDIafYxJJJ1xCUTpEfyKr64JIpMM
Fdn4MqEcC3bu9FoDxQBQxxlzCpeC+uqXwMKkws/J64Oe9e6o2eol2cPYvBgW0uvs
4uBaKz9EvVgkKpVBgiodHTduUVB1c+rsHZ6HiRmOxPxVT0gwOqMk5ymS6h1iPa8Z
fBW8VZpmWvO7wE8k9VUKF4RUyde8/q5tOkL+cpwblNJ9uxYKmyG+UZd1p8DX97K6
zLuyvOH4T3GxVZ/CCIT536LE6ArErJ/d2k22lJogIwNec/2iv+P0Z+nhWbrNq1u7
s6c7Gh9X3/WzltsGC2Ws91BU+FYKxKYBpXq57q6oVQh6WnXa2pq9lLyiIrn9/wxr
ndPLFHLKO/tI17Dpql4IFV9xdVY8G4SSZFrIe4zjvSgYyabDC1frJieA8u2i83pT
wN9jb3AwifHWw72J/8f6
=+nLj
-----END PGP SIGNATURE-----

Zbigniew Łukasiak

unread,
May 13, 2017, 3:27:19 PM5/13/17
to Zrubi, PR, qubes-users
This is something I am also struggling with - but shouldn't there be a
sign-off line in all the commit comments as described in
https://www.qubes-os.org/doc/license/ ? And by the way - shouldn't
that be somehow linked (or maybe moved into) from
https://github.com/QubesOS/qubes-doc/blob/master/CONTRIBUTING.md ?

Cheers,
Zbigniew
> --
> You received this message because you are subscribed to the Google Groups "qubes-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users...@googlegroups.com.
> To post to this group, send email to qubes...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4eca89c0-b10c-3787-f6ca-6dabfd9d6b32%40zrubi.hu.
> For more options, visit https://groups.google.com/d/optout.



--
Zbigniew Lukasiak
http://brudnopis.blogspot.com/
http://perlalchemy.blogspot.com/

Andrew David Wong

unread,
May 13, 2017, 4:22:20 PM5/13/17
to Zbigniew Łukasiak, Zrubi, PR, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2017-05-13 14:27, Zbigniew Łukasiak wrote:
> This is something I am also struggling with - but shouldn't there
> be a sign-off line in all the commit comments as described in
> https://www.qubes-os.org/doc/license/ ?

No, that only applies to Qubes OS code.

> And by the way - shouldn't that be somehow linked (or maybe moved
> into) from
> https://github.com/QubesOS/qubes-doc/blob/master/CONTRIBUTING.md ?
>

It's already linked there.

P.S. - Please don't top-post.

>
> On Fri, May 12, 2017 at 3:49 AM, Zrubi <ma...@zrubi.hu> wrote: On
> 05/12/2017 09:39 AM, Zrubi wrote:
>>>> On 05/11/2017 11:51 PM, 'PR' via qubes-users wrote:
>>>>> Hello,
>>>>
>>>>> I need some help understanding how the collaborative
>>>>> documentation with GitHub works.
>>>>
>>>> https://www.qubes-os.org/doc/doc-guidelines/
>>>>
>>>> TL;DR: you only missed the create a pull request part.
>>>>
>>>>
>
> Or if it is your pull request:
> https://github.com/QubesOS/qubes-doc/pull/418
>
> Then you made it right. Now you just have to wait for someone to
> review and accept it into the official doc's
>

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJZF2ryAAoJENtN07w5UDAwryIP/j344AB6YXwkrKB/gR5mXCCF
45Drzthugz6ZeK2NYbE5Z7XSSVBkHejOccEHmGAQ3GobsAAG3UHsrtXDaSKRk2B6
+rZ1mR8t9Ur87w3BlCFgkaAyoCsPGZoivwFDPOZC6F09H+c342yNd77HVrhwk6uQ
tu6/cm5BhlJVksv7hpsopVLs15/ByNX3jltUAYIx16cY69DwEW0QyQ6PtFvhE/AL
cyRWAg/oIbGW3por+BNt2fSyNAITdIm74+8ls9Aytq1Hvj/ieRJnZu7Xoe6ZB9aw
o2lfN+urrfMgm3YQ8rgJ12KZEPpQFdpzgXfj6mEeTofRWYlb2ZEk5xXTcJW06/EQ
I9422uz8KaX0SNNQVQBzBPw67QoMOX6Ulopg2nJWO/QqEZYNoUA2LYJjOX7DFXyO
Npne14BWnLhsa8HVxCcLMn93PMnKz9Fu6BdjFxhbQ8XIpHdkiKkThkwLhj/D3aur
fSCPL+XDwhdRDc1RCvvPqq/8EHKtBpGs+m0fVsn33QZmid5WbCQEKMvRGJEjDlMU
OlnyNQfbxofwO0t8HRSVEr4BQpmyZxrjz0pIXdd5dJgaNLRr9feiQWEGePxe0MH+
+MPvf4dc35dlyRYVCM8ctHoxfbpJLrroxAgwnO2kuv9B7JNYi9fW0RYskpk1o8Qn
68PPonpwYiTK3fg3MK0d
=l6Wr
-----END PGP SIGNATURE-----

Jean-Philippe Ouellet

unread,
May 22, 2017, 11:10:09 PM5/22/17
to Andrew David Wong, Zbigniew Łukasiak, qubes-users
On Sat, May 13, 2017 at 4:22 PM, Andrew David Wong <a...@qubes-os.org> wrote:
> On 2017-05-13 14:27, Zbigniew Łukasiak wrote:
>> This is something I am also struggling with - but shouldn't there
>> be a sign-off line in all the commit comments as described in
>> https://www.qubes-os.org/doc/license/ ?
>
> No, that only applies to Qubes OS code.

Except in practice it doesn't apply there either. See comments in #2517 [1].

[1]: https://github.com/QubesOS/qubes-issues/issues/2517#issuecomment-266658039
Reply all
Reply to author
Forward
0 new messages