Initial creation of tutorials for 3rd party desktop applications #203

cschalle · 2017-06-08T18:20:11Z

Updated tutorial to now be split into smaller parts and put them into the deployment substructure as suggested

pvalena · 2017-06-13T07:41:15Z

deployment/desktop/how-to-propose-a-3rd-party-application-for-inclusion-in-fedora.md

+
+This will allow the Fedora Workstation Working group to review your application and ask any needed follow-up questions. For more in depth-information about the process and rules for including 3rd party software in Fedora Workstation you can see the [Third Party Software for Fedora](https://fedoraproject.org/wiki/Workstation/Third_party_software_proposal) page.
+
+[Back to index](how-to-package-a-desktop-application.md) 


These back to index are unnecessary, because there is a link in left panel pointing to that page. This link(ending with .md) would also most probably not work.

pvalena · 2017-06-13T07:42:11Z

deployment/desktop/how-to-package-a-desktop-application.md

+AppStream files allow us to build a modern software center experience either using legacy distro packages with yum-style metadata or with the new flatpak application deployment framework. By including a desktop file and AppData file for your Linux binary build your application can be easily installed by end users.
+###Future Work
+AppData currently uses the OARS content rating system which will be expanded for more uses cases and filtering options.
+###	Related Work


I think you have a typo (whitespace) here. I do not know how it would reflect in resulting document.

pvalena · 2017-06-13T07:43:28Z

deployment/desktop/how-to-package-a-desktop-application.md

@@ -0,0 +1,34 @@
+#**Adding Applications to the GNOME Software Center**


Title is auto-generated.

pvalena · 2017-06-13T07:44:32Z

Have you tested this to see the result? I mean: you can start your local developer-portal instance in vagrant or docker on your computer to see what the web will look like.

cschalle · 2017-06-13T13:23:04Z

Hi Pavel, No I haven't tested it, didn't even know we had such docker images available. I was only told that the agreement that Ryan Lerch and Richard Hughes had made to get this onto the developer website was that we convert it to markdown, which is what I did. Christian

…

On Tue, Jun 13, 2017 at 3:44 AM, Pavel Valena ***@***.***> wrote: Have you tested this to see the result? I mean: you can start your local developer-portal instance in vagrant or docker on your computer to see what the web will look like. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#203 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AUrzSu9p0vVGh5QK_sGgSmM5rGgvWDSuks5sDj3ggaJpZM4N0cVJ> .

pvalena · 2017-06-15T10:49:02Z

Once again: Jekyll headers are missing, thus the pages or any content would not be visible/displayed on the web and thus merging this PR would not yield any result on the Developer Portal.

No I haven't tested it, didn't even know we had such docker images available.

There is even a Vagrantfile in websites repository. Please make sure the result will be what you actually want before requesting us to accept the changes.

Let me know if you run into any issues.

cschalle · 2017-06-15T18:30:26Z

Sigh, getting something onto the developer site seems rather hard for someone who is just a causal contributor. It is not clear to me how I get a link onto the deployment.html page. I tried adding 'jekyll' headers by cut and pasting the --- section from another document without that seemingly making a difference for getting the pages onto the website. I am at this point wondering wether it is better to just post this on the workstation wiki pages. Christian

…

On Thu, Jun 15, 2017 at 6:49 AM, Pavel Valena ***@***.***> wrote: Once again: Jekyll headers are missing, thus the pages or any content would not be visible/displayed on the web and thus merging this PR would not yield any result on the Developer Portal. No I haven't tested it, didn't even know we had such docker images available. There is even a Vagrantfile in websites repository. Please make sure <https://github.com/developer-portal/website/blob/master/DEVELOPMENT.md#development> the result will be what you actually want before requesting us to accept the changes. Let me know if you run into any issues. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#203 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AUrzSkSSaEBhF84mVOs9n3pkfEbxeTMbks5sEQwegaJpZM4N0cVJ> .

pvalena · 2017-06-22T13:04:50Z

Sigh, getting something onto the developer site seems rather hard for
someone who is just a causal contributor. It is not clear to me how I get a
link onto the deployment.html page. I tried adding 'jekyll' headers by cut
and pasting the --- section from another document without that seemingly
making a difference for getting the pages onto the website. I am at this
point wondering wether it is better to just post this on the workstation
wiki pages.

So there is an issue with writing the headers? I guess it should be explained better in the contribution guide.

On the main page (Order 1) you have to state section: deployment in the jekyll header(example) and the subsection name has to be unique in the section. Well any minor issues we can fix later on, but it should at least work.
Please also push your changes(even WIP) to your github fork (no need to close this PR; and you can do git push --force if you need to) so I can see the changes. Let me know, ideally on irc, if I can be of any help.

The content seems cool, so please do not give up on us!

Thanks,
Pavel

stickster · 2017-06-22T19:48:47Z

This is tested and builds/renders fine now. There are still some issues I'm working on, like missing images and readability tweaks. But it should work OK now.

stickster · 2017-07-13T20:54:34Z

Note that the new section here for desktop deployment requires a graphic in the website static/logo/ folder. I recommend using the graphic at https://people.gnome.org/~engagement/logos/GnomeLogoVertical.svg for this.

pvalena · 2017-07-13T21:02:48Z

Note that the new section here for desktop deployment requires a graphic in the website static/logo/ folder.

Please create a PR(to websites repo) with addition of that logo in case it does not exist yet.

pvalena · 2017-08-28T13:53:45Z

Sadly noone got time time to reiew this, including me. To speed this up, please go through the acceptance checklist in issues, as I think at least some of them are still relevant for this PR.

Re: developer-portal/content#203 (comment)

See developer-portal/content#203 (comment)

stickster · 2017-09-20T20:27:42Z

I believe I've now addressed (if you include the website PR linked above) all the issues, with the possible exception of squashing these commits further. Let me know if that's still an issue.

stickster · 2017-10-06T12:17:20Z

Hi @pvalena, could you look at this PR for me?

pvalena

Hello @stickster,
I've gone through your PR and commented on the code directly. I've put only few examples in, as the same issues repeat throughout the PR.

Before you submit more changes, please read through our contributing guide, especially the whole writing section.

Please also do build the site yourself - locally - and check the result looks actually as intended.
Regarding that, if you encounter some issues, you can contact us on our IRC channel #developer-portal on Freenode, as well as on our mailing list.

pvalena · 2017-10-30T20:39:03Z

deployment/desktop/desktop-application-metadata-overview.md

+
+# {{page.title}}
+
+### System Architecture


You're jumping from level 1 to level 3 title.

pvalena · 2017-10-30T20:39:50Z

deployment/desktop/desktop-application-metadata-overview.md

+	MimeType=application/x-openscad;
+	Categories=Graphics;3DGraphics;Engineering;
+	Keywords=3d;solid;geometry;csg;model;stl;
+	Keywords[de]=3D;solid;Geometrie;csg;Modell;stl;


This needs to be in a 'block of code'.

Like this.

pvalena · 2017-10-30T20:40:34Z

deployment/desktop/desktop-application-metadata-overview.md

+	  <url type="homepage">https://wiki.gnome.org/Apps/MultiWriter</url>
+	  <url type="bugtracker">https://bugzilla.gnome.org/browse.cgi?product=gnome-multi-writer</url>
+	  <translation type="gettext">gnome-multi-writer</translation>
+	</component>


Definitely needs a block of code.

pvalena · 2017-10-30T20:43:47Z

deployment/desktop/desktop-application-metadata-overview.md

+
+If the application is being built on your own machines or cloud instance then the distributor will need to generate the AppStream metadata manually. This would for example be the case when internal-only or closed source software is being either used or produced. This document assumes you are currently building RPM packages and exporting yum-style repository metadata for Fedora or RHEL although the concepts are the same for rpm-on-OpenSuse or deb-on-Ubuntu.
+
+NOTE: If you are building packages, make sure that there are not two applications installed with one single package. If this is currently the case split up the package so that there are multiple subpackages or mark one of the *.desktop* files as *NoDisplay=true*. Make sure the application-subpackages depend on any *-common* subpackage and deal with upgrades (perhaps using a metapackage) if you’ve shipped the application before.


Above is huge block of text that is on the 4th level of 'nesting' (lvl4 title) and IMHO every reasonable developer will skip this text. Please be more user-friendly! Developer Portal is not site intended for documentation, but for a quick reference! There should be only a link to documentation and few tips, fedora-specific issues etc..

Please check other content on Developer Portal for reference.

pvalena · 2017-10-30T20:45:46Z

deployment/desktop/desktop-application-metadata-overview.md

+1. [Filesystem Hierarchy Standard: 17th October 2016](https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard) 
+2. [Desktop Specification: 17th October 2016](https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html#introduction) 
+3. [AppStream Specification 0.10: 17th October 2016](https://www.freedesktop.org/software/appstream/docs/) 
+4. [SPDX license list](https://spdx.org/licenses/)


No citations needed here. This is not a formal document.

Page should provide only 'handy' links. What user might actually need, to get more information on subject, installation instructions, or github repositories etc..

pvalena · 2017-10-30T20:46:19Z

deployment/desktop/desktop-software-hosting.md

+
+You can install appstream-builder in Fedora Workstation by using this command:
+
+	dnf install libappstream-glib-builder


Needs sudo and $ and code block again.

pvalena · 2017-10-30T20:49:27Z

deployment/desktop/how-to-setup-and-host-flatpaks.md

+	git add -A
+	git commit -a -m "first commit"
+	git remote add origin git@github.com:yourgitaccount/myrepo.git
+	git push -u origin master


Please just link to some git guide.
This page should not cover everything.
Such common git instructions would be more suitable for an actual git section of Developer Portal(there's none so far).

pvalena · 2017-10-30T20:50:37Z

deployment/desktop/how-to-package-a-desktop-application.md

+
+4. How to [setup and host flatpaks](how-to-setup-and-host-flatpaks.html)
+
+5. How to [propose third party software for Fedora listing](how-to-propose-a-3rd-party-application-for-inclusion-in-fedora.html)


No overview or content-list please. This should be covered by the side menu itself (i.e. split into multiple pages).

pvalena · 2017-10-30T20:51:26Z

deployment/desktop/how-to-package-a-desktop-application.md

+
+### Related Work
+
+The ODRS[1] is a web service which provides end-user moderated application reviews using the AppStream application ID.


Link is missing and I also do not believe this is of any value for developer.

pvalena · 2017-10-30T20:52:31Z

deployment/desktop/how-to-package-a-desktop-application.md

+5. How to [propose third party software for Fedora listing](how-to-propose-a-3rd-party-application-for-inclusion-in-fedora.html)
+
+
+### Summary


Do I see correctly there's Introduction and next's Summary?

pvalena · 2017-10-30T21:17:23Z

I believe I've now addressed (if you include the website PR linked above) all the issues, with the possible exception of squashing these commits further. Let me know if that's still an issue.

I think you've missed a few. You also need to fullfill all of them (including the squashing) for this PR to be acceptable.

pvalena · 2017-10-30T21:32:07Z

The file naming also seems somehow redundant. Please drop desktop from the prefix, as you're already in desktop subsection. And also please do not prefix files with how-to-.

New desktop deployment section

stickster · 2017-12-08T23:01:33Z

OK, I think the new fixes should be correct. More or less a whole rewrite. I tried to squash down but couldn't avoid the merge I did at cschalle's fork.

pvalena · 2018-01-23T00:03:05Z

deployment/desktop/hosting-metadata.md

+
+Metadata for distribution tools and GNOME Software must be refreshed
+periodically, such as when new versions of [packaged
+applications](desktop-software.html) are released for consumption by


Where should this link point? I'd say no such path exists. Please use full paths like, f.e. /tech/languages/csharp/csharp-ide.html.

Invariably I missed a couple links while rewriting this heavily. It was a very substantial amount of change.

Sure, don't worry, we just need those fixed. That's what reviews are for.

pvalena · 2018-01-23T00:04:04Z

deployment/desktop/hosting-metadata.md

+
+## Generating yum repository metadata
+
+1. Run these commands to create the initial metadata for source


Why is the numbering here? It's a bit confusing, as the following one is also 1..

These are steps in a procedure. If it's forbidden to number those, I'll leave them out. But using "1." for each step results in a properly numbered set of steps "1., 2., 3.," etc. without having to renumber manually in the event of a change. Is that not acceptable.

Hmm, I did not know that. Does that work with GH-flavored MD? That's what jekyll uses to generate the resuilting website.

I see what you mean by steps. However, like I said, this should NOT be a complete guide, thus no steps are needed. You can however outline what's usually done and how, but this web is meant only as a reference pointing to the full-featured guides if needed.

pvalena · 2018-01-23T00:04:34Z

deployment/desktop/hosting-metadata.md

+    configuration. At this point you can also verify the application
+    is visible in the *yourcompanyname.xml.gz* file.
+
+1. Next, take the generated XML and the tarball of icons and add it to


Here also 1.. What's the purpose of that?

pvalena · 2018-01-23T00:05:03Z

deployment/desktop/hosting-metadata.md

+Writing /tmp/asb-md/appstream.xml.gz...
+Writing /tmp/asb-md/appstream-icons.tar.gz...
+Writing /tmp/asb-md/appstream-screenshots.tar...
+Done!


Please do remove the sample output, as someone could accidentally paste it into terminal.

pvalena · 2018-01-23T00:10:16Z

deployment/desktop/hosting-metadata.md

+	Deploying this metadata allows GNOME Software to add the
+	application metadata the next time the repository is refreshed.
+
+## Hosting a DNF repository on Github


Is this actually a proper workflow? Do many people host their repository on Github? I'm also not sure this is the correct place to insert guide for git. Some git section, or external git guide would be better. This is not exactly relevant to the topic.
Note that this shouldn't in any way by a complete guide, but merely a starting point and links to additional content. We expect the developers do learn themselves.

This is also probably not a good idea to tell people to do, since it might not necessarily be something GitHub would appreciate...

pvalena · 2018-01-23T00:11:19Z

deployment/desktop/hosting-metadata.md

+	For more information on this format, consult the [repository
+    options in the DNF configuration documentation](http://dnf.readthedocs.io/en/latest/conf_ref.html#repo-options).
+
+1. Copy this file to */etc/yum.repos.d* on your computer and load up


Now this is some people would struggle, as you need to use $ sudo for that and you should include at least some sample command here.

pvalena · 2018-01-23T00:14:13Z

deployment/desktop/hosting-metadata.md

+
+## Generating Flatpak metadata
+
+The [Flatpak](https://flatpak.org) application packaging standard is another way to provide metadata for consumers. This guide assumes you are familiar with this standard, along with the [manifest and basic build operations required](http://docs.flatpak.org/en/latest/flatpak-builder.html).  You can find extensive information on building Flatpaks and on hosting and signing flatpak repostories [here](https://blogs.gnome.org/alexl/2017/02/10/maintaining-a-flatpak-repository/).


This guide assumes you are familiar with this standard, along with...

Please do remove that sentence, as well as the following one. I do not think it's relevant, but you can include those two links in a reference section.

pvalena · 2018-01-23T00:15:20Z

deployment/desktop/hosting-metadata.md

+Create an empty repository in a *repo* folder with this command:
+
+```console
+$ ostree init --mode=archive-z2 --repo=repo


Does this command need an empty directory? Shouldn't there be a command to create it and cd to it also?

pvalena · 2018-01-23T00:16:49Z

deployment/desktop/hosting-metadata.md

+
+```console
+$ flatpak-builder --verbose --force-clean \
+        --repo=repo --gpg-homedir=gpg --gpg-sign=$GPG_KEY \


Where do I find the $GPG_KEY? Do I leave the variable empty?

pvalena · 2018-01-23T00:21:50Z

deployment/desktop/hosting-metadata.md

+   your database is up to date.  You should then be able to search in
+   GNOME software and find your new application.
+
+## Generating Flatpak metadata


I'm a bit lost, because there's too much content for one page. This is line 132 and our pages are usually like 40 lines long. It should be just a quick helpful reference, not a full-featured guide.

Flatpack usage does deserve it's own page....

Relevant issue: #245

pvalena · 2018-01-23T00:23:04Z

Please do work on the content a bit more. I think I did not even get half way through but I think you get the picture. Ref: #203 (comment)

pvalena · 2018-01-23T00:24:12Z

deployment/desktop/software-appdata.md

+   The required fields are *Name*, *Comment*, *Icon*, *Categories*,
+   *Keywords*, and *Exec*.  Here is an example:
+
+   ```console


This is definitely not a console. You can leave it empty if you cannot decide.

The type is ini.

pvalena · 2018-01-23T00:25:52Z

deployment/desktop/software-appdata.md

+
+Normally distributions take care of hosting operations from this
+point.  However, if you want to host your own metadata for use with
+yum/DNF or Flatpak, [this guide](hosting-metadata.html) may be of use.


This link is also not pointing anywhere.

I also find this whole block / paragraph useless from developer POV.

pvalena · 2018-01-23T00:27:30Z

deployment/desktop/software-appdata.md

+   Window Sizer* which you installed earlier.  To resize the window of
+   your application to 16:9 format, focus it and press *Ctrl+Alt+s*.
+   Your application window is resized to a perfect 16:9 aspect ratio
+   so you can screenshot it with *Alt+PrtScn*.


Likewise I do not think this is a place for a basic usage of any Screenshot tool. You can link to a relevant guide.

pvalena · 2018-01-23T00:33:45Z

Just a quick check reminds me that I'm repeating myself with directions on how to fix this PR.

Please do go through all the comments I've already made and make sure you've somehow incorporated appropriate fix, or please do respond to that comment so we can discuss the issue.

Please do not tell me once more you've addressed all the issues, when you in fact didn't.

pvalena · 2018-01-23T15:46:00Z

Additionally -if you can- please replace the screenshot with some that's of an open-source app. Steam does not look like a right choice from Fedora POV.

pvalena · 2018-02-02T14:08:47Z

Please let me know when you've addressed all issues.

Conan-Kudo · 2018-03-22T02:11:58Z

deployment/desktop/hosting-metadata.md

+
+## Hosting a Flatpak repository on Github
+
+Github isn't ideal for hosting Flatpak repositories, but this method currently works.


Again, probably not a good idea...

Conan-Kudo · 2018-03-22T02:12:30Z

deployment/desktop/software-appdata.md

+   to provide correct data for your application in this file.  Here is
+   an example for the Frobnicator app:
+
+   ```console


The type is xml

pvalena · 2020-02-14T21:44:03Z

Please give it a look, so we can merge it (it does not have to be perfect, just give it a byte of love).

Note: The release will be soon (~1-2weeks), and after that there will be maintenance (decomissioning) of the release infrastucture(no updates for some time). The website updates still need some manual handling, but openshift will change that.

pvalena reviewed Jun 13, 2017

View reviewed changes

stickster force-pushed the master branch from b37af85 to daee547 Compare July 13, 2017 20:52

stickster added a commit to stickster/website that referenced this pull request Sep 20, 2017

Add GNOME logo for desktop deployment section

b162a87

Re: developer-portal/content#203 (comment)

stickster added a commit to stickster/website that referenced this pull request Sep 20, 2017

Add GNOME logo for desktop deployment section

4597a57

See developer-portal/content#203 (comment)

stickster mentioned this pull request Sep 20, 2017

Add GNOME logo for desktop deployment section developer-portal/website#56

Merged

stickster force-pushed the master branch from daee547 to 398c9e7 Compare September 20, 2017 18:58

stickster added a commit to stickster/website that referenced this pull request Sep 20, 2017

Add GNOME logo for desktop deployment section

0f436b0

See developer-portal/content#203 (comment)

pvalena requested changes Oct 30, 2017

View reviewed changes

stickster force-pushed the master branch from 398c9e7 to 0d0eddc Compare December 8, 2017 22:48

stickster added 2 commits December 8, 2017 17:55

New desktop deployment section

4a154f9

Merge pull request #1 from cschalle/wip-paul

9f61e17

New desktop deployment section

pvalena reviewed Jan 23, 2018

View reviewed changes

pvalena added Status: Review Needed Type: New Content Section: Deploy and Distribute labels Jan 23, 2018

pvalena self-assigned this Feb 2, 2018

pvalena added Status: In Progress and removed Status: Review Needed labels Feb 2, 2018

Conan-Kudo reviewed Mar 22, 2018

View reviewed changes

pvalena added Status: Help Needed and removed Status: In Progress labels Mar 29, 2018

Sesivany mentioned this pull request May 4, 2018

The repo doesn't integrate with GNOME Software phracek/pycharm-community-edition#47

Closed


		This will allow the Fedora Workstation Working group to review your application and ask any needed follow-up questions. For more in depth-information about the process and rules for including 3rd party software in Fedora Workstation you can see the [Third Party Software for Fedora](https://fedoraproject.org/wiki/Workstation/Third_party_software_proposal) page.

		[Back to index](how-to-package-a-desktop-application.md)

		@@ -0,0 +1,34 @@
		#Adding Applications to the GNOME Software Center


		If the application is being built on your own machines or cloud instance then the distributor will need to generate the AppStream metadata manually. This would for example be the case when internal-only or closed source software is being either used or produced. This document assumes you are currently building RPM packages and exporting yum-style repository metadata for Fedora or RHEL although the concepts are the same for rpm-on-OpenSuse or deb-on-Ubuntu.

		NOTE: If you are building packages, make sure that there are not two applications installed with one single package. If this is currently the case split up the package so that there are multiple subpackages or mark one of the .desktop files as NoDisplay=true. Make sure the application-subpackages depend on any -common subpackage and deal with upgrades (perhaps using a metapackage) if you’ve shipped the application before.


		You can install appstream-builder in Fedora Workstation by using this command:

		dnf install libappstream-glib-builder


		4. How to [setup and host flatpaks](how-to-setup-and-host-flatpaks.html)

		5. How to [propose third party software for Fedora listing](how-to-propose-a-3rd-party-application-for-inclusion-in-fedora.html)


		### Related Work

		The ODRS[1] is a web service which provides end-user moderated application reviews using the AppStream application ID.

		5. How to [propose third party software for Fedora listing](how-to-propose-a-3rd-party-application-for-inclusion-in-fedora.html)


		### Summary


		## Generating yum repository metadata

		1. Run these commands to create the initial metadata for source


		## Generating Flatpak metadata

		The [Flatpak](https://flatpak.org) application packaging standard is another way to provide metadata for consumers. This guide assumes you are familiar with this standard, along with the [manifest and basic build operations required](http://docs.flatpak.org/en/latest/flatpak-builder.html). You can find extensive information on building Flatpaks and on hosting and signing flatpak repostories [here](https://blogs.gnome.org/alexl/2017/02/10/maintaining-a-flatpak-repository/).


		## Hosting a Flatpak repository on Github

		Github isn't ideal for hosting Flatpak repositories, but this method currently works.

Initial creation of tutorials for 3rd party desktop applications #203

Are you sure you want to change the base?

Initial creation of tutorials for 3rd party desktop applications #203

Conversation

cschalle commented Jun 8, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

pvalena commented Jun 13, 2017

cschalle commented Jun 13, 2017 via email

pvalena commented Jun 15, 2017

cschalle commented Jun 15, 2017 via email

pvalena commented Jun 22, 2017

stickster commented Jun 22, 2017

stickster commented Jul 13, 2017

pvalena commented Jul 13, 2017

pvalena commented Aug 28, 2017

stickster commented Sep 20, 2017

stickster commented Oct 6, 2017

pvalena left a comment • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

pvalena Oct 30, 2017 • edited Loading

Choose a reason for hiding this comment

pvalena Oct 30, 2017 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

pvalena Oct 30, 2017 • edited Loading

Choose a reason for hiding this comment

pvalena Oct 30, 2017 • edited Loading

Choose a reason for hiding this comment

pvalena Oct 30, 2017 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

pvalena commented Oct 30, 2017

pvalena commented Oct 30, 2017

stickster commented Dec 8, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

pvalena Jan 23, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

pvalena commented Jan 23, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

pvalena commented Jan 23, 2018

pvalena commented Jan 23, 2018

pvalena commented Feb 2, 2018

Choose a reason for hiding this comment

Choose a reason for hiding this comment

pvalena commented Feb 14, 2020

pvalena left a comment •

edited

Loading

pvalena Oct 30, 2017 •

edited

Loading

pvalena Oct 30, 2017 •

edited

Loading

pvalena Oct 30, 2017 •

edited

Loading

pvalena Oct 30, 2017 •

edited

Loading

pvalena Oct 30, 2017 •

edited

Loading

pvalena Jan 23, 2018 •

edited

Loading

pvalena commented Jan 23, 2018 •

edited

Loading