Re: gtk-doc and meson

[Michael Biebl]

2017-03-25 19:16 GMT+01:00 Jan Alexander Steffens :
> On Sat, Mar 25, 2017 at 12:21 PM Tim-Philipp Müller  wrote:
>>
>> IIRC most issues could be worked around by copying things into the
>> build directory.
>
>
> Yes. See, for example,
> https://git.gnome.org/browse/grilo/commit1/?id=c5eac4907f9a99280064aa001485f9696f5ebe10

Having to copy the files manually is rather ugly though and it's easy
to miss when new files are added.

I would hope that gtk-doc can be improved that workarounds like that
are not necessary.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: gtk-doc and meson

[Jan Alexander Steffens]

On Sat, Mar 25, 2017 at 12:21 PM Tim-Philipp Müller  wrote:

> IIRC most issues could be worked around by copying things into the
> build directory.
>

Yes. See, for example,
https://git.gnome.org/browse/grilo/commit1/?id=c5eac4907f9a99280064aa001485f9696f5ebe10

.
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Looking at Jenkins for CD/CI of GNOME

[Walter Vargas]

Hello everyone,

I have been talking with @ebassi at irc about the idea of work on a proof of
concept that replaced the existing Continuous pipeline with Jenkins.

>From my understanding is basically make a list of components, create a set
of
Jobs to build the components, we can even use the docker plugin of Jenkins
to
build the components using docker, build a Pipeline with the corresponding
stages for polling, compile, test, build images put the resulting tree into
an
ostree commit, notifies committers on build failures, generate the artifacts
like docker images, virtualbox images, vagrant boxes, and deploy to QA env.

I am looking forward to know your thoughts and collaborate on this, I have
been
working daily with Jenkins for CI/CD of aws infrastructure and applications
from
the last two/three years.

Regards.
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Searching mentor for GSoC Proposal on GNOME Disks

[Michael Catanzaro]

On Sat, 2017-03-25 at 06:38 -0400, Carlos Soriano via desktop-devel-
list wrote:
> On possibility is Michael/GNOME can mentor you, or, a co-mentor
> project could arise, the gtk+ part by someone from GNOME/Michael and
> the udisk part from someone from udisks sharing the work.

Hi,

I'm not planning to take a GSoC student this year, but I can vouch for
Kai's proposal. He also has a significant contribution to Disks on
GitHub that I'm planning to merge soon. The main problem here is that
Disks does not have an active maintainer right now. Ideally Kai would
become the new maintainer after the project, but he's obviously not
going to be accepted unless someone is interested in mentoring.

Michael
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: gtk-doc and meson

[Tim-Philipp Müller]

On Sat, 2017-03-25 at 05:23 +0100, Michael Biebl wrote:

> With Meson gaining more traction in GNOME I guess it's about time to
> improve gtk-doc's support for out-of-tree builds.
> At least people should be aware of issues like
> https://bugzilla.gnome.org/show_bug.cgi?id=776427
> when porting to Meson. Out-of-tree builds are rarely tested for
> gtk-doc and there can be subtle breakages like missing images, code
> samples etc.

https://bugzilla.gnome.org/show_bug.cgi?id=758313

might also be of interest in that context, as well as

https://github.com/mesonbuild/meson/issues/550


IIRC most issues could be worked around by copying things into the
build directory.

Cheers
 -Tim
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: GSoC student introduction

[Carlos Soriano via desktop-devel-list]

Hello Armin,

I'm Carlos Soriano, one of the mentors in GNOME.
This project idea looks like a key project for GNOME and I'm sure all of us are 
looking forward to see it happen!

I read your proposal and the points outlined and goals looks good. I understand 
the complexity of Mutter + Wayland prevents you to have a clear idea and 
timeline of it, but I think it will be better if you dig a little more in the 
code and have a clearer idea of it, so a rough timeline can be done. I think 
it's important to know how much time every goal will take and what do you think 
you are capable of, and it's also important for us. But again, I completely 
understand this is going to be difficult for this project.

Also put a link to your previous GSoC and a link to your contributions in other 
FOSS projects so it's easier to evaluate your proposal (this is part of the 
GNOME template, would be nice to have it already since it's an important point 
for the evaluation and it can help the GNOME community to get excited about the 
you and the project :) )

In any case, your potential mentors will help you more on the details. Feel 
free to share with us the final proposal again when it's done.

Looking forward to see your contributions!
Carlos Soriano

 Original Message 
Subject: GSoC student introduction
Local Time: March 24, 2017 9:22 PM
UTC Time: March 24, 2017 8:22 PM
From: krezovic.ar...@gmail.com
To: desktop-devel-list@gnome.org, gnome-shell-l...@gnome.org
kat.g...@gmail.com

Hello everyone,

I am Armin Krezović, and I've decided to apply to Google Summer
of Code to work on Mutter.

I have completed all the necessary steps outlined in [1], and
also written a proposal (can be still considered as a draft),
which can be found at [2]. The proposal was written trying to
answer as many questions outlined in [1], but not all of them
could be answered (at this point, or at all).

I'd like to know if that would pose a problem, and if it could
be improved somehow. I would be thankful to anyone who could
take the time to quickly review the proposal.

Looking forward to working with you.

TIA, Armin.

[1] https://wiki.gnome.org/Outreach/SummerOfCode/Students
[2] 
https://docs.google.com/document/d/1C7iCqTdCZR4aLSHfACfleRFqfKRzojBHKI8C30XHs9k/edit?usp=sharing
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Searching mentor for GSoC Proposal on GNOME Disks

[Carlos Soriano via desktop-devel-list]

Hello Kai!

I'm Carlos Soriano, one of the mentors in GNOME.
It's great you came up with this proposal, and you seem to have a decent 
understanding of the technologies involved, it's great to see you would like to 
tackle this part of the stack. Everyone will love seeing work on this!

Did you try to mention this to Michael or the udisks maintainer?
https://github.com/storaged-project/udisks/blob/master/AUTHORS
And maybe an email to
https://lists.freedesktop.org/mailman/listinfo/devkit-devel?

On possibility is Michael/GNOME can mentor you, or, a co-mentor project could 
arise, the gtk+ part by someone from GNOME/Michael and the udisk part from 
someone from udisks sharing the work.

To be fair is a little late in the GSoC timeline to find a mentor, but I think 
it's possible if your contributions are great!
In case we cannot find a mentor, would you be interested in continue your 
contribution during the year and try again for Outreachy[0] if you are eligible 
or for next year GSoC?

Looking forward to see your contributions!
Carlos Soriano

[0] https://www.gnome.org/outreachy/

 Original Message 
Subject: Searching mentor for GSoC Proposal on GNOME Disks
Local Time: March 24, 2017 3:30 PM
UTC Time: March 24, 2017 2:30 PM
From: kailu...@riseup.net
To: desktop-devel-list@gnome.org

Hello,

after going through many of the listed ideas from organizations in the
Google Summer of Code program, I came to the conclusion that I would
like to propose working on GNOME Disks.

Why?
I use it very often and it mostly does a good job. But recently I had to
use GParted again for resizing and moving partitions and realized that
it can't work in a Wayland session (because it runs as root).
Since the storaged/UDisks transition also might give the chance to work
on related features in UDisks, I think working on GNOME Disks would make
up a good GSoc project in order to provide functionality which was
offered GParted.

What?
The suggestion is to first accurately list available filesystem choices
(needs some UDisk work) and then support resizing and checking. As
moving partitions is not so essential and may be out of scope for UDisk,
this would be at most a stretch goal.
On the way there are other maintenance tasks and the whole project also
reachs out to UDisks/libblockdev for resizing and fixing filesystems.

Is there anyone who would like to be a mentor for me?
https://wiki.gnome.org/Outreach/SummerOfCode/Mentors
I'm in the process of reading code and open bugs reports and have
started working on a new feature with guidance from Michael Catanzaro:
https://github.com/pothos/gnome-disk-utility/tree/create-disk-image

Some words on myself: I'm in the computer science master program at TU
Berlin and finished my bachelor last year at FU Berlin. Up to now I'm
not a great contributor :/ but was at GUADEC in Strasbourg and follow
the planet.gnome.org since many years.

Thank you for reading!
Regards,
Kai

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list