Re: [GitLab] Projects moved, tips of the week and question of the week

[Olav Vitters]

On Thu, Feb 08, 2018 at 04:34:24PM +0200, Alberts Muktupāvels wrote:
> It is not only script, right? Because repositories.txt does not exist under
> gitlab.gnome.org.

Please cut down on the excessive quoting.

I assume Gitlab has some API to show the available repositories. As
such, script is only thing which needs to change.

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

Re: 3.27.90 tarball deadline extended

[mcatanzaro]

Hi developers,

We're getting closer, but we're not yet at a point where we can 
recommend that you try generating release tarballs with BuildStream and 
expect it to work. So I have to reluctantly recommend that you use 
JHBuild to generate your 3.27.90 release tarballs, if your module has 
dependencies that can't be satisfied by your host system. Even though 
the release team is no longer maintaining JHBuild, you can make 
whatever changes to the modulesets you need, and I believe that it is 
still the easiest way to generate your release tarballs at this time.


The final tarball deadline for 3.27.90 will be Monday, February 12. Our 
release deliverable will still be a BuildStream project: that has not 
changed.


Due to this delay, we will skip the 3.27.91 release altogether, so the 
next tarball deadline will be 3.27.92, on March 5. Perhaps by then we 
will be able to recommend using BuildStream for tarball generation.


Thanks very much for your patience during this transition period.

Michael

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

Image of current cursror under Wayland

[Damir Porobic]

Hi Folks,

is there way to get an image/picture of the current mouse cursor under Wayland? 
I know that it's possible to get a screenshot, including the mouse cursor via 
DBus call, but I would need those two separate. Under X11 this is doable but 
under Wayland we need to rely on the Compositor to provide screenshots.

Cheers,
Damir

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

[GitLab] Projects moved, general comments, tips of the week, question of the week

[Carlos Soriano]

Our migration is going faster that I have planned. We reached our second
milestone today, the most core-ish platform-ish modules asked for a
migration and are now migrated. So allow me to do two claps 

*Projects migrated today*

- gtk  (no bugs yet)
- glib  (no bugs yet)
- gobject-introspection

- gnome-control-center 
(no bugs yet)
- gnome-settings-daemon
 (no bugs yet)
- gxml 

** for those without bug migrations yet, consult their respective
maintainers for more info on their plans.*



*General comments for maintainers*For those maintainers that migrated
switch the permissions of the master branch to "masters and developers" in
"settings → general → repository → protected branches → master", since
there is no API for that I cannot do it when migrating, but we want to
allow all developers to be able to push to the master branch.

For those that want to migrate, remember to have your doap files updated
since only maintainers will be able to change settings in the project.



*Tips- Modifying multiple MR and issues at the same time: *In the issues or
MR view, click the "edit issues/MR" button on the top right and select the
issues/MR you want to batch modify. You can apply labels, close them,
subscribe to them, etc.

*- Automatically make discussions resolved when the same line is updated:*
"Settings→General → Merge request settings → Automatically resolve merge
request diff discussions when they become outdated". This is something that
probably

* most of you want.- Show more code context in a review: *In a diff, click
the three dots on the corners. Example shown in this pic (with my
above-average GIMP skills):


*​*


*Question of the week*GitLab support issues templates, some text in
markdown that will be shown for reporters when creating a new issue.
Multiple issues template are supported, reporters can select them in a
dropdown. The question is,

* what issue template should we use for when reporters create an issue?*Ideally
we would have a common template and maintainers will tweak it if necessary
for their projects. Please comment on the issue
 your ideas an
thoughts, there is currently no proposal.

Enjoy and welcome to 2018.
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: [GitLab] Projects moved, tips of the week and question of the week

[Alberts Muktupāvels]

It is not only script, right? Because repositories.txt does not exist under
gitlab.gnome.org.

On Thu, Feb 8, 2018 at 12:06 AM, Olav Vitters  wrote:

> On Tue, Feb 06, 2018 at 03:41:03PM +0200, Alberts Muktupāvels wrote:
>
> > On Tue, Feb 6, 2018 at 3:33 PM, Alberto Ruiz  wrote:
>
> >
>
> > > Hello Alberts,
>
> > >
>
> > > I believe the hooks for emails are still installed, so there will be no
>
> > > regressions in this regard regardless of the web frontend. If the
> migrated
>
> > > projects are not sending commits to the mailing list we're doing
> something
>
> > > wrong.
>
> > >
>
> >
>
> >
>
> > Migrated projects are sending commits to mailing list, problem is that it
>
> > is not possible to subscribe to these projects. Migrated projects has
>
> > disappeared from "Which topic categories would you like to subscribe to?"
>
> > list -  https://mail.gnome.org/mailman/options/commits-list.
>
>
>
> The following script needs to be adjusted:
>
> https://gitlab.gnome.org/Infrastructure/sysadmin-bin/
> blob/master/mail/set-topics-svn-commits-list
>
>
>
>
>
> --
>
> Regards,
>
> Olav
>



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