Re: [GitLab] Group runners: And why CI is slow in forks

[Walter Vargas]

Hi Carlos,

Thank you for your concerns regarding the costs associated with CI
infrastructure; the last week I was talking to Emmanuel that I would
like to donate CPU capacity of one of my cloud accounts for the
runners.

Please let me know if we can schedule a quick call this week to discuss that.

Additionally, we can create a "Runners Support Program" to allow
people to contribute with runners, that will require:
  1. An automated mechanism to install the required software.
 -  This can be an UserData script or an AMI with all set that we
could publish to the AWS Market.
  2. Support from the Engagement Team to create a social media strategy, etc.

Warm Regards.

On Mon, Jul 23, 2018 at 7:28 AM Carlos Soriano  wrote:
>
> Hello all,
>
> In case you missed my treasurer report talk at GUADEC, our annual costs for 
> CI is around $22.000. This is okay since we are lucky to have GitLab Inc. as 
> the main sponsor of that. However, we cannot offload all of our needs on 
> them, even more in the long-term. So we need to 1) find sponsors, 2) make 
> sure we spend money on just GNOME software.
>
> In order to spend money just in GNOME software we restricted the fast runners 
> to the groups GNOME/ and Infrastructure/. The runners in there are AWS and DO 
> in a elastic set up, that means they get spawned dynamically as the load 
> increases and they are quite beefy. Ideally this would be in a wiki page, 
> with the set up and costs explained.
>
> However there is an issue, forks and MR of forks are no part of this, so they 
> get the local machine we have instead of the fast runners.
>
> I was surprised this wasn't mentioned before, but fear not, it's the most 
> upvoted issue upstream right now 
> https://gitlab.com/gitlab-org/gitlab-ce/issues/23902.
>
> Lately, if you think someone could sponsor part of that money or some machine 
> for the rest of the software not in those groups, please reach to me!
>
> Cheers
> ___
> 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: gtk-doc goes python

[Walter Vargas]

Thanks for clarify it Stefan :)

On Thu, Apr 13, 2017 at 5:25 PM Stefan Sauer <enso...@hora-obscura.de>
wrote:

>
>
>
>
>
>
>
>
>
>
> On 04/10/2017 03:45 AM, Walter Vargas
>
> wrote:
>
>
>
>
>
>
> How does it work?
>
>
>
>
> Sorry, how does what work? gtk-doc is the tool that is used by most
>
> gnome libraries to generate the api-doc. It was written in perl and
>
> shell-script and we're now porting it to python. So this thread is
>
> mostly a heads up for the existing users.
>
>
>
>
>
>
> Stefan
>
>
>
>
>
>
>
>
>
>
>
> 2017-04-09 16:48 GMT-04:00 Stefan Sauer
>
> <enso...@hora-obscura.de>:
>
>
> On 04/08/2017 08:37 PM, Sébastien Wilmet wrote:
>>
>>
>> > On Thu, Mar 30, 2017 at 09:51:27PM +0200, Stefan
>>
>> Sauer wrote:
>>
>>
>> >> as a heads up - Jussi Pakkanen and I are
>>
>> rewriting gtkdoc to python. The
>>
>>
>> >> shell scripts are already gone (so running gtkdoc
>>
>> won't need a shell
>>
>>
>> >> anymore). At the same time we're modernizing it a
>>
>> bit and adding more
>>
>>
>> >> and proper tests. This is all very much work in
>>
>> progress though. If we
>>
>>
>> >> break something, please ping us in irc (#gtkdoc)
>>
>> or file a bug. Also
>>
>>
>> >> help is very welcome.
>>
>>
>> > Very good news! I've tested with GtkSourceView and a
>>
>> few other projects,
>>
>>
>> > and everything seems to still work fine.
>>
>>
>> >
>>
>>
>> > --
>>
>>
>> > Sébastien
>>
>>
>>
>>
>>
>> Thanks for testing. We made more progress. Two tools
>>
>> left (gtkdoc-mkdb
>>
>>
>> (the biggest one) and gtkdoc-fixxref). Hopefully we're done
>>
>> in a week.
>>
>>
>> I've started to make the code more testable as well. Once
>>
>> the porting is
>>
>>
>> done, I'll report again to test this so that we can cut a
>>
>> release. More
>>
>>
>> cleanup then in a follow up release.
>>
>>
>>
>>
>>
>> Stefan
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ___
>>
>>
>> desktop-devel-list mailing list
>>
>>
>> desktop-devel-list@gnome.org
>>
>>
>> https://mail.gnome.org/mailman/listinfo/desktop-devel-list
>>
>>
>>
>>
>>
>>
>>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
>
>
>
>
>
>
>
>
>
>
> Walter Vargas
>
>
> http://ve.linkedin.com/in/walterve
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: gtk-doc goes python

[Walter Vargas]

How does it work?

2017-04-09 21:45 GMT-04:00 Walter Vargas <waltervar...@gmail.com>:

> How does it work?
>
> 2017-04-09 16:48 GMT-04:00 Stefan Sauer <enso...@hora-obscura.de>:
>
>> On 04/08/2017 08:37 PM, Sébastien Wilmet wrote:
>> > On Thu, Mar 30, 2017 at 09:51:27PM +0200, Stefan Sauer wrote:
>> >> as a heads up - Jussi Pakkanen and I are rewriting gtkdoc to python.
>> The
>> >> shell scripts are already gone (so running gtkdoc won't need a shell
>> >> anymore). At the same time we're modernizing it a bit and adding more
>> >> and proper tests. This is all very much work in progress though. If we
>> >> break something, please ping us in irc (#gtkdoc) or file a bug. Also
>> >> help is very welcome.
>> > Very good news! I've tested with GtkSourceView and a few other projects,
>> > and everything seems to still work fine.
>> >
>> > --
>> > Sébastien
>>
>> Thanks for testing. We made more progress. Two tools left (gtkdoc-mkdb
>> (the biggest one) and gtkdoc-fixxref). Hopefully we're done in a week.
>> I've started to make the code more testable as well. Once the porting is
>> done, I'll report again to test this so that we can cut a release. More
>> cleanup then in a follow up release.
>>
>> Stefan
>>
>> ___
>> desktop-devel-list mailing list
>> desktop-devel-list@gnome.org
>> https://mail.gnome.org/mailman/listinfo/desktop-devel-list
>>
>
>
>
> --
> Walter Vargas
> http://ve.linkedin.com/in/walterve
>
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

GitHub Development Platform for GNOME

[Walter Vargas]

I want to share my humble opinion and thoughts about GitHub/GitLab:

I get worried about the long-term viability of the GNOME project after
running
an iteration over OODA Loop (observe, orient, decide, act)[1].

Canonical's recent decision about not maintaining unity for Ubuntu makes it
quite clear that Desktop is not the priority anymore, IoT and Mobile are the
priority now, and now GitHub is the world leading development platform.

Since the primary goal is to provide a developer experience that does not
act as
a barrier to new contributors, Should we be more pragmatic about that and
reconsider GitHub as an option?

Is it a dogmatic foundational decision not to evaluate GitHub because it is
not
Free Software?

Kind Regards

[1] https://en.wikipedia.org/wiki/OODA_loop
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Help Needed | Conferences for 2017 and 2018

[Walter Vargas]

Hi Nuritzi,

I am at Venezuela; I can try to attend the conferences close to me (Latin
America) and help with some GNOME marketing materials like laptop stickers
and
t-shirts.

There is an Odoo module to manage events [1], and this module is available
for
the community version [2], I am a former Odoo developer so that I can
deploy a
demo on one of my servers for the marketing team tests.

Kind Regards.

[1] https://www.odoo.com/page/events
[2] https://github.com/OCA/event

2017-04-04 21:22 GMT-04:00 Nuritzi Sanchez :

> Hi all,
>
> The Engagement Team is putting together a list of conferences that our
> community hopes to attend in 2017 and 2018.
>
> Please take a look at our list so far and add any events and conferences
> that we are missing. These should be ones you think are important for the
> GNOME Project to have a presence at. The list is included below and the
> wiki page is here: https://wiki.gnome.org/Engagement/TargetedEvents
>
> *Why do we want a list? *
> We want to make sure people feel empowered to represent GNOME all over the
> world at conferences and events! This means supporting the community with
> resources (e.g. $$ for marketing materials, ideas on how to run a booth,
> help with speeches, etc).
>
> We also want to attend some strategic events to make sure that GNOME is
> seen as the vibrant and awesome organization that it is. If we know which
> conferences are coming up, we can try to target strategic ones and work
> with people attending to get materials that will make GNOME look baller.
>
> *We need your help*
> After we create this list, we'll need your help to attend strategic
> events. We obviously prefer for locals to attend events close to them, but
> we have a travel fund for a reason.
>
> Also - here's a shameless plug for the Engagement Team ;) If you're
> interested in helping us plan for conferences and event outreach, please us
> know. We have a lot of ideas for how to have a bigger presence all over the
> world - and we need more people to help execute on those ideas. We need you.
>
> Thanks in advance!
>
> Best,
> Nuritzi
>
>
> Events in 2017
> The full list, and the 2018 schedule, can be found here:
> https://wiki.gnome.org/Engagement/TargetedEvents
> April
>
>- Libre Graphics Meeting (Rio) - looking for attendees
>
> May
>
>- Linuxfest Northwest - looking for attendees
>- OpenSUSE conference - looking for attendees
>
> June
>
> July
>
>-
>
>*GUADEC * (UK) - placeholder for
>calendering purposes
>- Open Source Bridge (Portland)
>- FISL
>
> August
>
>- Deb Conf (Montreal) -looking for attendees
>- FLOCK - looking for attendees
>
> September
>
> October
>
>- OSCON London - looking for attendees
>-
>
>*GNOME.Asia* - placeholder for calendering purposes
>- Open Source India - looking for attendees
>
> November
>
>-
>
>*LAS GNOME* (US)- placeholder for calendering purposes
>
>
>
> 
> .
>
> *Nuritzi Sanchez*  |  +1.650.218.7388 |  Endless 
>
> ___
> 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: Looking at Jenkins for CD/CI of GNOME

[Walter Vargas]

Hi Allan,

Thanks for your reply, I am joining to #sysadmin to start talking about the
requirements and the approach to follow. The idea is to create a CI/CD
Pipeline
with Jenkins and Docker, I have been doing some tests with Docker and
jhbuild,
and now we can use the following docker resources to work on the Pipeline
POC
with gnome-todo:

 Docker image of jhbuild with all sysdeps installed [1]
 Docker image of jhbuild with the modules adwaita-icon-theme, dbconf,
glib-networking, gvfs, libcanberra. [2]
 Dockerfile to build gnome-todo using jhbuild. [3]

All these docker repositories have automatic builds on hub.docker.com
triggered by
git push, I am working with forks of jhbuild and gnome-todo in github.

Indeed I will need a machine with good internet connection and enough
storage; I
am performing my tests with the bandwidth of Latin America, and then you can
image the speed.

Thank you.

[1] https://hub.docker.com/r/waltervargas/jhbuild/
[2] https://hub.docker.com/r/waltervargas/jhbuild-sysdeps-usefull-packages/
[3] https://github.com/waltervargas/gnome-todo/blob/master/Dockerfile#L6

2017-03-28 5:04 GMT-05:00 <a...@gnome.org>:

> Hi Walter!
>
> Walter Vargas <waltervar...@linux.com> wrote:
> ...
>
> 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.
>
> ...
>
> 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.
>
>
> I'm not a developer, but I have used the continuous ostree images in the
> past. I can certainly say that anything to make our CI setup more reliable
> and easy to maintain would be a big plus, and it would be fantastic to have
> your help.
>
> The sysadmins have said that they'd be happy to create a VM that Jenkins
> can be installed to. I'd recommend joining #sysadmin to talk over the
> details with them.
>
> Looking forward to working with you,
>
> Allan
>
___
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