Re: [qubes-devel] GSoC Introduction

[WillyPillow]

On Sunday, March 29, 2020 10:37 PM, WillyPillow  wrote:

> On Sunday, March 29, 2020 9:07 PM, donoban dono...@riseup.net wrote:
> 

> > On 2020-03-29 14:55, unman wrote:
> 

> > > > What you mean with Template manager? If you refer to the
> > > > "Template Manager" integrated with Qubes Manager, I am working on
> > > > a rewrite of Qube Manager using QT model/view which simplifies
> > > > things like multiple row selection [1].
> > > > Currently it supports multiple VM's selection and
> > > > start/stop/remove/etc... options. I think that It should be easy
> > > > to integrate a Template change option in context menu and make
> > > > the current Template Manager obsolete. This way you could select
> > > > some halted VM's directly in Qube Manager, right click and choose
> > > > "Change Template", see submenu of available templates and select
> > > > the desired one .
> > > > I hope to finish the pull request soon (it delayed too long :/
> > > > ).
> > > > [1] https://github.com/QubesOS/qubes-manager/pull/195
> 

> > > I think this is more about maintaining, updating, and distributing
> > > the available templates, than applying those to qubes, which is
> > > what you are talking about. It's a difficult topic but worth
> > > pursuing.
> 

> > Oh I see. Definitively a separated window where add, remove and
> > upgrade templates will improve Qubes usability.
> 

> Hi.
> 

> Indeed, I meant what unman was talking about. Thanks for helping me clarify 
> that :)
> 

> --WillyPillow
> 

> > https://blog.nerde.pw/
> > PGP fingerprint = 6CCF 3FC7 32AC 9D83 D154 217F 1C16 C70E E7C3 1C84
> > Protonmail PGP = D02D CEFF ACE5 5A7B FF5D 871E 4004 1CB1 F52B 127E
> 

> --

Hi.

The following is a draft for my proposal to GSoC 2020 regarding templates. 
Feedback and critique are greatly appreciated.

(I apologize terribly for sending this so late. TBH I did not realize that 
Qubes was in GSoC until very recently :/)

# Introduction

This is a project intended to improve template handling in Qubes OS. Currently, 
images of template VMs are distributed by RPM packages and managed by 
`yum`/`dnf`. However, tracking inherently dynamic VM images with a package 
manager that is suited for tracking static files creates some challenges. For 
example, users may accidentally update the images, overriding local changes 
(#996, #1647). (Or in the case of #2061, want to specifically override the 
changes.) Other operations that work well on non-RPM template VMs are also 
somewhat inconsistent on RPM-managed templates, such as renaming (#839), 
removing (#5509) and backup/restore (#1385, #1453, [1], [2]), creating 
inconvenience and confusion for users (#1403, #4518).

In addition to the distribution mechanism, users may also wish to have an 
integrated template management application for better UX (#2062, #2064, #2534, 
#3040), as opposed to the current situation where multiple programs are 
required for different purposes, e.g., `qubes-dom0-update`, `dnf`, 
`qvm-remove`, `qubes-manager`.

To tackle these issues, I propose i) designing a better mechanism for handling 
template installation, and ii) creating a user-facing application to deal with 
the aforementioned mechanism and other template-related configuration, 
consolidating the management of templates.

[1]: https://groups.google.com/forum/#!topic/qubes-devel/rwc2_miCNNE/discussion

[2]: https://groups.google.com/forum/#!topic/qubes-users/uQEUpv4THsY/discussion

# Project goals

* Design a template distribution/handling mechanism
* Extracting and handling `root.img` from RPMs
* Template management application
* CLI/GUI
* Features:
* List available templates
* Download / install / reinstall / update / remove templates
* Switch VMs to certain templates
* Possibly other features mentioned in issues such as #2062, 
#2064, #2534, and #3040
* Ability to run outside of dom0 (UI for #1705)

# Implementation

The consensus among the developers seems to be that sticking with RPM but not 
installing the package directly is a better idea [3][3.1], which I agree with, 
in part because handling package integrity is a bit non-trivial and may lead to 
security issues (c.f. QSB-028 [3.2]).

Installed template versions can be kept either in a separate database or the 
metadata of the template VM. Alternatively, it is possible to keep the version 
number in the template name, with the benefit that multiple versions of the 
same template can be installed at the same time.

The extraction and verification of template packages can be done in DispVMs if 
necessary.

After extracting the `root.img`, it remains to install it via a process similar 
to the post-processing script in `linux-template-builder/templates.spec`, which 
mainly consists of calling `qvm-template-postprocess`.

The application can be written in Python to take advantage of APIs such as 
`qubes-core-admin` and 

Re: [qubes-devel] GSoC Introduction

[WillyPillow]

On Sunday, March 29, 2020 9:07 PM, donoban  wrote:

> On 2020-03-29 14:55, unman wrote:
> 

> > > What you mean with Template manager? If you refer to the
> > > "Template Manager" integrated with Qubes Manager, I am working on
> > > a rewrite of Qube Manager using QT model/view which simplifies
> > > things like multiple row selection [1].
> > > Currently it supports multiple VM's selection and
> > > start/stop/remove/etc... options. I think that It should be easy
> > > to integrate a Template change option in context menu and make
> > > the current Template Manager obsolete. This way you could select
> > > some halted VM's directly in Qube Manager, right click and choose
> > > "Change Template", see submenu of available templates and select
> > > the desired one .
> > > I hope to finish the pull request soon (it delayed too long :/
> > > ).
> > > [1] https://github.com/QubesOS/qubes-manager/pull/195
> > 

> > I think this is more about maintaining, updating, and distributing
> > the available templates, than applying those to qubes, which is
> > what you are talking about. It's a difficult topic but worth
> > pursuing.
> 

> Oh I see. Definitively a separated window where add, remove and
> upgrade templates will improve Qubes usability.

Hi.

Indeed, I meant what unman was talking about. Thanks for helping me clarify 
that :)

--WillyPillow

> https://blog.nerde.pw/
>
> PGP fingerprint = 6CCF 3FC7 32AC 9D83 D154 217F 1C16 C70E E7C3 1C84
>
> Protonmail PGP = D02D CEFF ACE5 5A7B FF5D 871E 4004 1CB1 F52B 127E

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/aTSbz-jEfh2WzqE-BwH8IYve9svusZmhQnG5feib0YObTmaEnCxHM_fCMSuPDoPulhcDWqvJUI6DXBiVDjssSCW5rP8EtGWSnPtIpFfEEOQ%3D%40nerde.pw.


publickey - wp@nerde.pw - 0xD02DCEFF.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: [qubes-devel] GSoC Introduction

[donoban]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 2020-03-29 14:55, unman wrote:
>> What you mean with Template manager? If you refer to the
>> "Template Manager" integrated with Qubes Manager, I am working on
>> a rewrite of Qube Manager using QT model/view which simplifies
>> things like multiple row selection [1].
>>
>> Currently it supports multiple VM's selection and
>> start/stop/remove/etc... options. I think that It should be easy
>> to integrate a Template change option in context menu and make
>> the current Template Manager obsolete. This way you could select
>> some halted VM's directly in Qube Manager, right click and choose
>> "Change Template", see submenu of available templates and select
>> the desired one .
>>
>> I hope to finish the pull request soon (it delayed too long :/
>> ).
>>
>> [1] https://github.com/QubesOS/qubes-manager/pull/195
>
> I think this is more about maintaining, updating, and distributing
> the *available* templates, than applying those to qubes, which is
> what you are talking about. It's a difficult topic but worth
> pursuing.
>

Oh I see. Definitively a separated window where add, remove and
upgrade templates will improve Qubes usability.
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEznLCgPSfWTT+LPrmFBMQ2OPtCKUFAl6AnXwACgkQFBMQ2OPt
CKX6bRAAqiUUJK+Huk8SwQQXfpiwSAepXJ0cQtvE8o3UdcaFWntH2ckbcJC1zA92
xloD46plu5jagFTnWDwzt4Hos4eEdy7Ne6qTRhh9BfjO5MQa1Ddoa3ELYCiRCDzo
TQB8cthml0Eu+GQFWSBflhYHrj+4bnhexI5FTReQ93NJOqAd8dfDaeDo5BmDKeIx
fnJW1ZQ0rJxEbVLbXUKFts53cG/A1Gswaf1dh9HIJkW54RaIkicMZoXZtR5oI4id
MWWRO9w4FfWE7o58VpRCuu5m0m6HtPGyJXgEfee43pK9cUJrvWGaxGrV4CsQl1SZ
oJB7qgLF3krr9aHHSRm20ugX7/5jOzWlh5FzPQdXg9cQ8xbMUTY8YkAxheVaA3xh
QPKcvavh3h5XS5uYYXcBi50q9RQMdfvDk2vVLOu0rSxb6uenaLPA65G8wrbI2qUz
/EDfQ2jGIBXnVemU8ENoBQPAi4zTh7DisoggzSQwm2LHsiNp0jDsYrlsnuhSoy5f
8FpsbUlOzyllBhDFptZMlpNFI0r0um86KPRkoDDMRSmCgG/nRDh0N3/TQaBR55Zr
EjveiBN3tW75R8iSq0vtfsh2xBgbqJ5u6wio+Y6LK7DO6r5aTvGmNcA1/YI5gqyB
lXT0ZbuSfDR2kFmhHXqNYf2/bhzhplx/N7NGkgOy2admgvhLlRU=
=6Z84
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/6b4dc3af-80ff-1de7-c782-21a8634ac1fe%40riseup.net.

Re: [qubes-devel] GSoC Introduction

[unman]

On Sun, Mar 29, 2020 at 12:53:33PM +0200, donoban wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> On 2020-03-28 18:49, ? wrote:
> > Hi.
> >
> > I am William Huang, an undergrad studying at National Taiwan
> > University. I have had experience with Qubes OS and (albeit
> > limited) interactions on the mailing lists (under the handle
> > WillyPillow) since the v3.x days. (In fact, this project is
> > probably my main reason to participate in GSoC 2020 :) )
> >
> > The projects that interest me the most are the following.
> >
> > - Mechanism for maintaining in-VM configuration - Template manager,
> > new template distribution mechanism
> >
> 
> Hi,
> 
> What you mean with Template manager? If you refer to the "Template
> Manager" integrated with Qubes Manager, I am working on a rewrite of
> Qube Manager using QT model/view which simplifies things like multiple
> row selection [1].
> 
> Currently it supports multiple VM's selection and
> start/stop/remove/etc... options. I think that It should be easy to
> integrate a Template change option in context menu and make the
> current Template Manager obsolete. This way you could select some
> halted VM's directly in Qube Manager, right click and choose "Change
> Template", see submenu of available templates and select the desired one
> .
> 
> I hope to finish the pull request soon (it delayed too long :/ ).
> 
> [1] https://github.com/QubesOS/qubes-manager/pull/195

I think this is more about maintaining, updating, and distributing the
*available* templates, than applying those to qubes, which is what you
are talking about.
It's a difficult topic but worth pursuing.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/20200329125546.GA16368%40thirdeyesecurity.org.

Re: [qubes-devel] GSoC Introduction

[donoban]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 2020-03-28 18:49, 黃于軒 wrote:
> Hi.
>
> I am William Huang, an undergrad studying at National Taiwan
> University. I have had experience with Qubes OS and (albeit
> limited) interactions on the mailing lists (under the handle
> WillyPillow) since the v3.x days. (In fact, this project is
> probably my main reason to participate in GSoC 2020 :) )
>
> The projects that interest me the most are the following.
>
> - Mechanism for maintaining in-VM configuration - Template manager,
> new template distribution mechanism
>

Hi,

What you mean with Template manager? If you refer to the "Template
Manager" integrated with Qubes Manager, I am working on a rewrite of
Qube Manager using QT model/view which simplifies things like multiple
row selection [1].

Currently it supports multiple VM's selection and
start/stop/remove/etc... options. I think that It should be easy to
integrate a Template change option in context menu and make the
current Template Manager obsolete. This way you could select some
halted VM's directly in Qube Manager, right click and choose "Change
Template", see submenu of available templates and select the desired one
.

I hope to finish the pull request soon (it delayed too long :/ ).

[1] https://github.com/QubesOS/qubes-manager/pull/195
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEznLCgPSfWTT+LPrmFBMQ2OPtCKUFAl6AfioACgkQFBMQ2OPt
CKUOQA//QZZ5T4jE/BPX5Hfen3C0whiyjadX/baWDl9n6Rva+ZkXfLmeaSLphkGN
B2OmZ4VNxpqIvFdTi+w9Mm0vYzlxZ0S9NLrveMCL5CV3LeNPU7VbrlD6RkvSzwTq
o+gV9f/Ta7soxCyYrS4Tx/m9vxPW9qJCInQpPf56VaEhWaO36TtXQfIp5cUgquxf
dbfyWCD8EdIibG6qQ17suey7FC4EDw25NWLDa8nh/rzfxyAA62aRmf4OfnDRfFKV
Ki2AvQc4m3mfp0nSeaxiD1TG3QIYoppN9hwtmhl+X6K4/SlIf7JZ7smC/UIEzq+t
7pYFWwuZ9Q6NPWcgVbtJ3gbX0mOEbkh8rq/hfizWpnul6nXKFr//XzBIqv5Rp/YN
8nhoiQ/cDjN66YxFhHrcnb9t78vugRhZ6eZsSVdrrO4riEM9EBAOeURglVfS7/Sk
CKC4ihLiI03zn7LEZ4wJ3WbHJCSr6Axz3PlAoRgTFZLWxP7xGwSnxf2A3bp79fxR
vuc6GEkcu0hTocQjueCMtenr9jy2img0USWhaWuw7XJ6HuC2tkiwgxvZD5JXkpkK
/qqG4S+6apRfjiBuDw8DZqxWZ2knjsF4LpOc0gHV5Y+UuFJy9ZGN3DQ7t8UnivrS
rIe+rUdmSMjL98RtHg3xKogBqqf/WT5Z90TdWfrumSRh2c6KkXg=
=HDvN
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/754a49b5-0b7f-cd5d-ab51-8741763b87f8%40riseup.net.

Re: [qubes-devel] GSOC Introduction

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Mon, Mar 23, 2020 at 08:06:03PM -0700, Aju Tamang wrote:
> Hi there,

Hello Aju,

> Hi, I'm Aju Tamang, currently freshman a college student and am new to the 
> open source community.Its been months that i started coding(in python) and 
> this GSoC program was introduced to me through blog article.
> I've been looking forward to it since then and it would be great if you 
> could help me out in USB passthrough to Windows qubes.

Have you tried Qubes before? If not, I would recommend trying to install
it somewhere first. For testing purposes it is ok to install on external
disk, or even sufficiently large USB stick (although it will be quite
slow).

If you install Qubes on a USB disk, you won't be able to use USB
passthrough with real devices (as the USB controller will be assigned to
the host system, to serve disk access). But there are plenty options for
using virtual devices, so it shouldn't be a blocker.

As for the task itself, you have some brief explanation on our GSoC
page:
https://www.qubes-os.org/gsoc/#usb-passthrough-to-windows-qubes

Some more details are:
 - how we do it for Linux: https://github.com/QubesOS/qubes-app-linux-usb-proxy/
 - general concept from the user point of view: 
https://www.qubes-os.org/doc/usb-devices/

Your task would be making it work also for Windows VMs. There are
various methods how to do that (two of them listed on our GSoC page),
but I would recommend going with the USBIP + qemu (second option), as it
would be mostly shell+python scripts, instead of Windows kernel drivers.

If you're still interested, the next step would be writing your
application with description of the project, above I have pointed you
where to look for inspiration.

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAl58GFYACgkQ24/THMrX
1yx5vgf+MZaq97Au6w9bmYnLkxUe8IDKaTLpqBo6Ty7ZVFu+WwOf0pLw/d1sAfPi
JUkbvBPsKlySb8uYhYyu9S3rhY99r9KUbORijobFUMTMJfNlpvKIFlNVPVnkJN9D
6fOtkBoObGGAXKvtSX6ThwV86Amx5EbcqjwRr5Rlvof0J0006FR6dRPgOcmqO90N
+0dz2LtKD4vRhUKgcvM829NFtPq5CptZRy2Vp8xQ3P126nknoYql3LR1cunWwsDY
dHHS1X1P1voYD3edrK8L+DKXvl3l/iWb+POexpOnftwaQuM1IWqsJm+HD1iw/vWc
hnHriDggWJO2VaIItDdy0x5thmrnhg==
=B10e
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/20200326024959.GC7869%40mail-itl.

Re: [qubes-devel] GSoC Introduction

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Tue, Mar 17, 2020 at 05:32:03PM -0700, Muhammad Usman wrote:
> Hi,

Hello Muhammad,

> My name is Muhammad Usman and I am a third year PhD student (Software 
> Engineering) at the University of Texas at Austin, USA. 
>  
> I am doing research in Automated Software Testing. I am interested in 
> contributing to the Android Development in Qubes project. 
> 
> Please guide me about the next steps.

Have you tried Qubes before? If not, I would recommend trying to install
it somewhere first. For testing purposes it is ok to install on external
disk, or even sufficiently large USB stick (although it will be quite
slow).

Once you have that, read this issue:
https://github.com/QubesOS/qubes-issues/issues/2233
There are various ideas how this could be achieved (not necessarily the
final design), you can also try some of them on just installed system.
This should give you ideas for the gsoc application.

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAl58FHwACgkQ24/THMrX
1yxdHwf/QD/URd+LBnNARmuBxL0bIt5npkj5H8oeyApIoWdKjDkK5qky+0KZXbN3
1LW/rpwbl8AMyg+vB4v/jLsgpHvE3bjLg3rLBgf0PftGAuq9B+Hp0UHOg5NI78Oy
mJyqeNpMMEs/dYMoeqX/bjnBIPxF4/sMBpVfGGqYFeU52vmORvAOOCi0YMDYBYqm
nmMf1uENcE7JMTgJyZJUxiJIWPZQu3wXKdwo22OP/fjkfcN0fLUmXQHftgg0Tlwk
h7chJjaF2H3BbrXOdbX2Z9o181l0vwZkGhNfh3ZdsmDQkkyWCv9ItePY2Rv/Jdb3
DGVSaNHQa7U4d/0VVQGVK7z/BW28KA==
=IwcB
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/20200326023334.GB7869%40mail-itl.

Re: [qubes-devel] GSoC Introduction

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Tue, Mar 17, 2020 at 01:39:29PM -0700, Nate Wolfe wrote:
> Hello everyone,

Hello Nate,

> I'm Nate Wolfe, a third-year student at Dalton State College. I'm pursuing 
> an undergraduate degree in Mathematics. I finished the two-year program my 
> college had available for computer science and earned the Associate's 
> Degree to go with it, but felt I would learn more by switching to a Math 
> major than by transferring and finishing a Bachelor's in Computer Science. 
> I'm interested in helping to port GNOME to dom0, but I'm open to working on 
> other projects instead if that's more advisable. This is the project that 
> caught my eye because GNOME has been my go-to DE since I was introduced to 
> Linux as a child, so GNOME in dom0 would make Qubes a dream come true for 
> me. 

Do you have some experience in configuring/styling GNOME? This project
requires some design/research about window decorations in GNOME.
Depending on the outcome, probably will require preparing some CSS and
also maybe some GNOME plugin.
You can find more information, including prior approaches here:
https://github.com/QubesOS/qubes-issues/issues/1806


- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAl58Ef4ACgkQ24/THMrX
1yyQxgf+IWcQ0jopluL+QtklwFxjFW0O7WOI3+uoNlFuElFQrZvpVMCAkOof7i7x
GFfHponnABSp9U5zYjvoiBbtv4iD5M8Z1sGtegGqff0Uh7IDdNSFocSGb09V8UuB
ytefp9yMOHpe7syqNTbwPRQ1eW0X6VD7/YQ4rR8qTDA5TMGdVDmkN81zKKIwYaAg
8iKqN+PSWjw98uj5bcbHR3EEkbWcXHWtS9dJH83Cz9uRNdXiCtQ+eZdy8KCC6mJi
w9BZ/r2RZeaXU5zUYREFD5dM++IjO3IZ4I97zM2qTx0vzTN6oPOp/LnNSxHaSkOR
Rqx+3vAMmZ0fFtVHnMns3dlL50GVyw==
=lpsB
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/20200326022256.GA7869%40mail-itl.

Re: [qubes-devel] GSoC Introduction

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Tue, Mar 10, 2020 at 04:07:24PM -0700, Rounak Agarwal wrote:
> Hello

Hi Rounak,

> I am Rounak Agarwal, a third year Graduate Student at Indian Institute of 
> Science. 
> Before enrolling as a Graduate Student I have worked as a Software 
> Developer for three years.
> At the university I am working on improving the security of Android payment 
> applications.
> 
> Amongst the ideas listed for GSoC I find the following two interesting.

Those are very good choices :)

> a) Progress towards reproducible builds

Besides resources linked on the GSoC ideas page, you may want to look
also at things linked to this issue:
https://github.com/QubesOS/qubes-issues/issues/816
Especially, at the end there is current status summary.

> b) Android development in Qubes

For this, you'll definitely want to read
https://github.com/QubesOS/qubes-issues/issues/2233 (linked also from
GSoC ideas page). It's quite long discussion, but will give you the
picture what tasks you'll face here.

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAl5pfl4ACgkQ24/THMrX
1yzTRgf/ci2yjwVbeEK3dYeMJr/2CJ4My5Rp2Fp0y2cQufQ2MCveMPlAVsIVctMN
1jLv1YiLk3co92LXIYdvcgSs5yZCZD24kDz2A35hgaMLV9LXvdWagVxOjWlXbqzL
eEY41nhvBM+N/ANh+8HEBZZ/xIRw3nm1At+ECvIhWI5V1seTxHq9Y3Lj+4XwfPGf
A7Lnj2YqzYx1FH5SuSH9xOlY41CL7y00cQa7+FRaxHCmrMbNsP4GeL3d0kMQMn/a
HwM8XuashNtcdg7y0M68OeArykMxW6JR5LuHaGEJ4fe/2HlvOUPVlfTr5P3PVHTp
EY0UFaAvkKAIn+AJ3ksvUnCMXzOmrQ==
=obAc
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/20200312001214.GM7869%40mail-itl.

Re: [qubes-devel] GSoC introduction

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Fri, Mar 06, 2020 at 09:24:30PM -0500, Arijit Paul wrote:
> Hi there,
> Hi, I'm Arijit Pal, current a college student and am new to the open source
> community.Its been two years that i started coding(in python) and this GSoC
> program was introduced to me by a friend of mine.
> I've been looking forward to it since then and it would be great if you
> could help me out as to which project I should start contributing as a
> beginner.

Hi Arijit,

Take a look at our project ideas here:
https://www.qubes-os.org/gsoc/

Each entry have "Knowledge prerequisite" listed, so I'm sure you'll find
something for you.

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAl5pfN8ACgkQ24/THMrX
1yxjegf9HI+VwgRPMN7VXGxNAZhMbHJgciFLxXVAsZeZ0/6OH8r1hGO3G1y8BHFF
bq9UX4JBH+Yq46LQq6XV1RX+ET665CJ3cotLWgM6otXZ/9bLornii+0Exu23Z/vg
rnond94EIQqfZt+2rxh8SmdqxFiC1vd7uJBGgwbz2EQT4uFoQxrb1Ku3Wv1VUKbA
Sm3nIN5KF1yvmkJ+i70GDcQAdarNnSEzKfsvlM8W04B3mRs4hfBZl8kOP6htJcY6
U0XQnczZcsd3AYZBLRaoSA2RhqUfkAPG8En70e9N6ahB/1KJcdeTcy6uFCztbBRu
lV93YiWvHHom29arcmGoF4uZKPKkvA==
=1rWw
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/20200312000551.GL7869%40mail-itl.

Re: [qubes-devel] GSOC Introduction

[John Casey]

On Sunday, 2 April 2017 19:43:34 UTC+1, Jean-Philippe Ouellet wrote:
>
> On Sun, Apr 2, 2017 at 1:50 PM, John Casey  > wrote: 
> > On Saturday, 1 April 2017 22:33:10 UTC+1, Marek Marczykowski-Górecki 
> wrote: 
> >> On Sat, Apr 01, 2017 at 01:52:27PM -0700, John Casey wrote: 
> >> > I like the idea of improving the usability of the project because a 
> >> > scary 
> >> > or non existence interface can often cause users move away. 
> >> > 
> >> > Playing with GTK, I think many of these issues should be suitable for 
> >> > GSOC. 
> >> 
> >> Oh, and there is one more thing - VM settings window. In Qubes 4.0 
> we're 
> >> going to decompose Qubes VM Manager into separate applications[2]. VM 
> >> status monitoring (moved to Xfce4 panel applet) is already handled by 
> >> Kalkin-, but it isn't all. Initially we've planned to reuse old 
> Qt-based 
> >> VM settings window as standalone application and simply call it from 
> the 
> >> menu and/or that applet. But if you'd like to rewrite it in GTK as GSoC 
> >> project, that would be great! That old Qt-based code isn't perfect 
> piece 
> >> of software... There was an attempt to do that already and also some 
> >> code is available[3], but it's far from complete and finishing that 
> work 
> >> (if any of that would be good enough to use...) would still be a 
> perfect 
> >> 3-month task. 
> > 
> > That sounds fantastic, as it would definitely improve my GTK knowledge. 
> I 
> > see that there hasn't been a commit to in almost a year. Has bnvk 
> > changed direction, or is it just waiting for someone to pick up the code 
> and 
> > work on it? 
>
> See [0], especially bnvk's note at the bottom. 
>
> [0]: 
> https://github.com/QubesOS/qubes-issues/issues/1870#issuecomment-223055937 
>

Thanks, that explains rather bare-bones nature of the above repo. That 
comment also serves as good introduction to the requirements for any 
implementation independent of the GTK vs Qt discussion.
 

>
> > Would rewriting it in GTK be busywork, or would it be more effective to 
> > learn and build it in Qt. Does Qubes plan to change to GTK entirely? 
>
> See discussion in 
> https://groups.google.com/d/topic/qubes-devel/2pWolRF3otY/discussion 
>
> AFAIK the current answer is "Yes, the plan is to change to GTK 
> entirely", but it's not clear to me whether or not this is the best 
> plan. 
>

I find it very interesting the process for choosing a technology in open 
source projects. In addition, it seems that no matter which is chosen, 
there will always be those who would have preferred the other. An example 
being the XFCE vs KDE argument I've seen elsewhere in the Qubes community.

So the Gnome change has been pushed into the future, and as a result, a lot 
of the benefit of GTK as also been pushed to the future. Is that 
approximately correct?

Additionally, I haven't been able to find any current sources for a Gnome 
transition to Qt, and that discussion is from 2013.

Finally, I feel the need to underline by inexperience in these matters as 
until the last month my knowledge of OSS has been limited to download, 
build and run. So take my input with a pinch of salt.

Regards,
John.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-devel@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/09dcd07b-2735-4498-92ce-a26302717496%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-devel] GSOC Introduction

[Jean-Philippe Ouellet]

On Sun, Apr 2, 2017 at 1:50 PM, John Casey  wrote:
> On Saturday, 1 April 2017 22:33:10 UTC+1, Marek Marczykowski-Górecki wrote:
>> On Sat, Apr 01, 2017 at 01:52:27PM -0700, John Casey wrote:
>> > I like the idea of improving the usability of the project because a
>> > scary
>> > or non existence interface can often cause users move away.
>> >
>> > Playing with GTK, I think many of these issues should be suitable for
>> > GSOC.
>>
>> Oh, and there is one more thing - VM settings window. In Qubes 4.0 we're
>> going to decompose Qubes VM Manager into separate applications[2]. VM
>> status monitoring (moved to Xfce4 panel applet) is already handled by
>> Kalkin-, but it isn't all. Initially we've planned to reuse old Qt-based
>> VM settings window as standalone application and simply call it from the
>> menu and/or that applet. But if you'd like to rewrite it in GTK as GSoC
>> project, that would be great! That old Qt-based code isn't perfect piece
>> of software... There was an attempt to do that already and also some
>> code is available[3], but it's far from complete and finishing that work
>> (if any of that would be good enough to use...) would still be a perfect
>> 3-month task.
>
> That sounds fantastic, as it would definitely improve my GTK knowledge. I
> see that there hasn't been a commit to in almost a year. Has bnvk
> changed direction, or is it just waiting for someone to pick up the code and
> work on it?

See [0], especially bnvk's note at the bottom.

[0]: https://github.com/QubesOS/qubes-issues/issues/1870#issuecomment-223055937

> Would rewriting it in GTK be busywork, or would it be more effective to
> learn and build it in Qt. Does Qubes plan to change to GTK entirely?

See discussion in
https://groups.google.com/d/topic/qubes-devel/2pWolRF3otY/discussion

AFAIK the current answer is "Yes, the plan is to change to GTK
entirely", but it's not clear to me whether or not this is the best
plan.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-devel@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/CABQWM_BSv1YcXfX%3DV7dGdKQ%2Biqy0zm0frJEPW2RLV9UUSTaOGA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-devel] GSOC Introduction

[John Casey]

On Saturday, 1 April 2017 22:33:10 UTC+1, Marek Marczykowski-Górecki wrote:
>
> -BEGIN PGP SIGNED MESSAGE- 
> Hash: SHA256 
>
> On Sat, Apr 01, 2017 at 01:52:27PM -0700, John Casey wrote: 
> > Hi all, 
>
> Hi! 
>
> > So I've been crushed by mid-terms for the last three weeks, as a result, 
> > I'm only now finishing my proposals for GSOC 2017. 
> > 
> > OSS has been an interest of mine for a while and GSOC has been the push 
> I 
> > needed to actually get involved. 
> > 
> > Looking at the issues list , 
> much 
> > of it seems to be far more complex than could be satisfied over the 
> summer. 
> > However, the issues raised in #1117 seem appropriate to me. 
>
> This list is very broad, I strongly suggest focusing on some subset of 
> it. Have you seen GSoC ideas list[1]? There are also GUI and/or UX 
> related ideas. 
>
> As for ideas not mentioned there, take a look issues with label "UX". 
> For example those: 
> https://github.com/QubesOS/qubes-issues/issues/2304 
> 
>  
> https://github.com/QubesOS/qubes-issues/issues/2329 
> https://github.com/QubesOS/qubes-issues/issues/2139 
> https://github.com/QubesOS/qubes-issues/issues/899 
> https://github.com/QubesOS/qubes-issues/issues/952 
>
>
Reading those, it strikes me that they could be a useful "Hello, World" for 
contributing to Qubes. Especially seeing as many of them involve 
interacting with different sub-systems within Qubes. 

>
> > I like the idea of improving the usability of the project because a 
> scary 
> > or non existence interface can often cause users move away. 
> > 
> > Playing with GTK, I think many of these issues should be suitable for 
> GSOC. 
>
> Oh, and there is one more thing - VM settings window. In Qubes 4.0 we're 
> going to decompose Qubes VM Manager into separate applications[2]. VM 
> status monitoring (moved to Xfce4 panel applet) is already handled by 
> Kalkin-, but it isn't all. Initially we've planned to reuse old Qt-based 
> VM settings window as standalone application and simply call it from the 
> menu and/or that applet. But if you'd like to rewrite it in GTK as GSoC 
> project, that would be great! That old Qt-based code isn't perfect piece 
> of software... There was an attempt to do that already and also some 
> code is available[3], but it's far from complete and finishing that work 
> (if any of that would be good enough to use...) would still be a perfect 
> 3-month task. 
>

That sounds fantastic, as it would definitely improve my GTK knowledge. I 
see that there hasn't been a commit to [0] in almost a year. Has bnvk 
changed direction, or is it just waiting for someone to pick up the code 
and work on it?

Would rewriting it in GTK be busywork, or would it be more effective to 
learn and build it in Qt. Does Qubes plan to change to GTK entirely?

>
> > If anyone has any usability/GUI tickets that you think I should look at 
> do 
> > let me know. 
> > 
> > So, I'm gonna call this fashionably late. 
> > John. 
> > 
>
> [1] https://www.qubes-os.org/gsoc/ 
> [2] https://github.com/QubesOS/qubes-issues/issues/2132 
> [3] https://github.com/QubesOS/qubes-issues/issues/1870 
>
> - -- 
> Best Regards, 
> Marek Marczykowski-Górecki 
> Invisible Things Lab 
> A: Because it messes up the order in which people normally read text. 
> Q: Why is top-posting such a bad thing? 
> -BEGIN PGP SIGNATURE- 
> Version: GnuPG v2 
>
> iQEcBAEBCAAGBQJY4ByQAAoJENuP0xzK19cs0dkH/1mRoFW2LSzzPyCwFOQn6+Cc 
> U7HTDi0vC6mQ5l8DZIkacTCl1mkrhdNQI1wKA2fRr2rJzhR4d6RqwHSr798vgd7J 
> GObKMuhErjSZaPtcYuy+JQYnf3x3aiwGowCn8ytCuhTzto8fG2eJ/nJJoqO8X6d/ 
> VBbMDFNKea6cK36nQJ2fIgjP3wrvrlGXAQlidbWGIfZzAPWBPu+Op7NK8qoFW6jH 
> 2yNq56+1ZuggtI9qknjbVell/F2PQ943XZ3m8jLRdgNXFF4/AVHu0jpPMFoApiY9 
> x26OvcfbqiNUexIp/Wfg/rOJT03L0mHGC6TOmdNxbI1J0VwvSgRAukgxDtc9nFg= 
> =6joP 
> -END PGP SIGNATURE- 
>

[0] https://github.com/bnvk/qubes-manager-new 

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-devel@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/6aaa1d97-fc8d-4bda-9b52-b6cdd16d59dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-devel] GSOC Introduction

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sat, Apr 01, 2017 at 01:52:27PM -0700, John Casey wrote:
> Hi all,

Hi!

> So I've been crushed by mid-terms for the last three weeks, as a result, 
> I'm only now finishing my proposals for GSOC 2017.
> 
> OSS has been an interest of mine for a while and GSOC has been the push I 
> needed to actually get involved.
> 
> Looking at the issues list , much 
> of it seems to be far more complex than could be satisfied over the summer. 
> However, the issues raised in #1117 seem appropriate to me.

This list is very broad, I strongly suggest focusing on some subset of
it. Have you seen GSoC ideas list[1]? There are also GUI and/or UX
related ideas.

As for ideas not mentioned there, take a look issues with label "UX".
For example those:
https://github.com/QubesOS/qubes-issues/issues/2304
https://github.com/QubesOS/qubes-issues/issues/2329
https://github.com/QubesOS/qubes-issues/issues/2139
https://github.com/QubesOS/qubes-issues/issues/899
https://github.com/QubesOS/qubes-issues/issues/952


> I like the idea of improving the usability of the project because a scary 
> or non existence interface can often cause users move away.
> 
> Playing with GTK, I think many of these issues should be suitable for GSOC.

Oh, and there is one more thing - VM settings window. In Qubes 4.0 we're
going to decompose Qubes VM Manager into separate applications[2]. VM
status monitoring (moved to Xfce4 panel applet) is already handled by
Kalkin-, but it isn't all. Initially we've planned to reuse old Qt-based
VM settings window as standalone application and simply call it from the
menu and/or that applet. But if you'd like to rewrite it in GTK as GSoC
project, that would be great! That old Qt-based code isn't perfect piece
of software... There was an attempt to do that already and also some
code is available[3], but it's far from complete and finishing that work
(if any of that would be good enough to use...) would still be a perfect
3-month task.

> If anyone has any usability/GUI tickets that you think I should look at do 
> let me know.
> 
> So, I'm gonna call this fashionably late.
> John.
> 

[1] https://www.qubes-os.org/gsoc/
[2] https://github.com/QubesOS/qubes-issues/issues/2132
[3] https://github.com/QubesOS/qubes-issues/issues/1870

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJY4ByQAAoJENuP0xzK19cs0dkH/1mRoFW2LSzzPyCwFOQn6+Cc
U7HTDi0vC6mQ5l8DZIkacTCl1mkrhdNQI1wKA2fRr2rJzhR4d6RqwHSr798vgd7J
GObKMuhErjSZaPtcYuy+JQYnf3x3aiwGowCn8ytCuhTzto8fG2eJ/nJJoqO8X6d/
VBbMDFNKea6cK36nQJ2fIgjP3wrvrlGXAQlidbWGIfZzAPWBPu+Op7NK8qoFW6jH
2yNq56+1ZuggtI9qknjbVell/F2PQ943XZ3m8jLRdgNXFF4/AVHu0jpPMFoApiY9
x26OvcfbqiNUexIp/Wfg/rOJT03L0mHGC6TOmdNxbI1J0VwvSgRAukgxDtc9nFg=
=6joP
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-devel@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/20170401213304.GW1208%40mail-itl.
For more options, visit https://groups.google.com/d/optout.