Re: ansible-report git hook design
On Fri, Oct 25, 2019 at 3:28 PM Randy Barlow wrote: > On Fri, 2019-10-25 at 15:03 +0200, Clement Verna wrote: > > There are basically 2 possibility : > > There are other possibilities too, such as putting the repo on > gitlab.com and using their CI on pull requests Can’t we do this on Pagure with CentOS CI? Thank you. regards, bex . > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to > infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > -- Brian "bex" Exelbierd (he/him/his) Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org bexel...@redhat.com | b...@pobox.com ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: Bot Account for Bodhi Karma
This thread feels very related to https://pagure.io/fesco/issue/2207 On Thu, Aug 15, 2019 at 2:42 PM Dusty Mabe wrote: > > > > On 8/15/19 5:16 AM, Tim Flink wrote: > > After the Flock talk from the Facebook folks, they approached QA about > > the idea of submitting karma and/or test results from their internal > > testing as a bot account. > > > > Is this something that is possible? I know that we have done bot > > accounts at various points in time but I don't remember if automated > > karma is allowed or what the other restrictions on that were. > > > > +1 for this. In the Fedora CoreOS working group we have a few packages > where we'll be testing them extensively via automated tests and we'd like > to have those passing tests satisfy karma requirements for the packages to > be passed through to bodhi stable. Some packages we own and most likely > no one else cares about (like ignition) and others we'll test and simply add a > karma point such that it's a piece of data used to determine if the package > should be submitted to stable. > > Dusty > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org -- Brian "bex" Exelbierd (he/him/his) Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org bexel...@redhat.com | b...@pobox.com ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: Sunset of infinote (Gobby) service
Awesome! Thank you! regards, bex On Thu, Aug 1, 2019 at 12:18 PM Clement Verna wrote: > > On Thu, 1 Aug 2019 at 11:56, Brian (bex) Exelbierd > wrote: > > > > I believe that we need to announce things like this on higher traffic > > lists. Gobby users are not necessarily subscribed to this list. > > > > I suspect we need a magazine article and a devel or announce list posting. > > Devel-announce is pending moderation and this was also posted on > https://discussion.fedoraproject.org/t/sunset-of-infinote-gobby-service/2161 > > > > > regards, > > > > bex > > > > On Thu, Aug 1, 2019 at 10:34 AM Clement Verna > > wrote: > > > > > > Dear all, > > > > > > The Fedora Infrastructure is planning to retire the infinote [0] > > > service. This service allows text collaboration using the Gobby > > > client[1] and was mainly used by the Infrastructure team to coordinate > > > our weekly meeting and the mass update & reboot of the machines. > > > > > > The service will be taken offline on August 30th 2019. If you wish to > > > backup some of the document currently hosted, you should make sure > > > that you have downloaded them locally before that date. > > > > > > The Infrastructure team will most likely use the service provided by > > > hackmd.io [2] for their needs. Other alternatives like public etherpad > > > can also be used to replace this service. > > > > > > Thanks, > > > Clément > > > > > > [0] - https://infinote.fedoraproject.org/infinote/ > > > [1] - https://fedoraproject.org/wiki/Gobby > > > [2] - https://opensource.com/article/19/7/enable-collaboration-hackmd > > > ___ > > > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > > > To unsubscribe send an email to > > > infrastructure-le...@lists.fedoraproject.org > > > Fedora Code of Conduct: > > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > > List Archives: > > > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > > > > > > > > -- > > Brian "bex" Exelbierd (he/him/his) > > Fedora Community Action & Impact Coordinator > > @bexelbie | http://www.winglemeyer.org > > bexel...@redhat.com | b...@pobox.com > > ___ > > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org > > Fedora Code of Conduct: > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org -- Brian "bex" Exelbierd (he/him/his) Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org bexel...@redhat.com | b...@pobox.com ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: Sunset of infinote (Gobby) service
I believe that we need to announce things like this on higher traffic lists. Gobby users are not necessarily subscribed to this list. I suspect we need a magazine article and a devel or announce list posting. regards, bex On Thu, Aug 1, 2019 at 10:34 AM Clement Verna wrote: > > Dear all, > > The Fedora Infrastructure is planning to retire the infinote [0] > service. This service allows text collaboration using the Gobby > client[1] and was mainly used by the Infrastructure team to coordinate > our weekly meeting and the mass update & reboot of the machines. > > The service will be taken offline on August 30th 2019. If you wish to > backup some of the document currently hosted, you should make sure > that you have downloaded them locally before that date. > > The Infrastructure team will most likely use the service provided by > hackmd.io [2] for their needs. Other alternatives like public etherpad > can also be used to replace this service. > > Thanks, > Clément > > [0] - https://infinote.fedoraproject.org/infinote/ > [1] - https://fedoraproject.org/wiki/Gobby > [2] - https://opensource.com/article/19/7/enable-collaboration-hackmd > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org -- Brian "bex" Exelbierd (he/him/his) Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org bexel...@redhat.com | b...@pobox.com ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: New website or ... ?
Hi, We are doing some experiments with alternative hosting for Fedora Magazine. A bunch of email went out to contributors by accident. regards, bex On Sun, Jun 30, 2019 at 10:12 AM Cătălin George Feștilă wrote: > > I found this on my email ... > https://fedoramag.wpengine.com/ > This is a new magazine? > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org -- Brian "bex" Exelbierd (he/him/his) Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org bexel...@redhat.com | b...@pobox.com ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: pastebin plans
On Mon, May 20, 2019 at 8:13 PM Stephen John Smoogen wrote: > > > On Mon, 20 May 2019 at 13:47, Brian (bex) Exelbierd > wrote: > >> On Mon, May 20, 2019 at 7:36 PM Martin Kolman wrote: >> > >> > On Mon, 2019-05-20 at 13:11 -0400, Justin W. Flory wrote: >> > > On 5/20/19 12:56 PM, Ben Cotton wrote: >> > > > I don't see that running our own pastebin is valuable to the >> > > > community. There are plenty of other options for people to post >> things >> > > > (pastebin.com, GitHub gists, put a file in your web space on Fedora >> > > > people, etc). I'm in favor of option 3, with a long enough timeline >> > > > for the fpaste maintainers to handle the change and for the docs >> team >> > > > to make sure we update any docs that refer to pase.fp.o accordingly >> > > > (if any) >> > > > >> > > >> > > +1 to Option 3. >> > > >> > > My biggest use for paste.fp.o is via fpaste in CLI. To me, it also >> makes >> > > more sense to use an existing service and point the fpaste tool there. >> > > So long as fpaste continues to work, my use case and likely others' >> does >> > > not break. >> > Agreed, as long as fpaste continues to be working and puts the pasted >> text somewhere sensible >> > all would be more or less fine. >> >> I am seeing lots of early love for Option #3 - I am also great with >> this but I'd like to see two things: >> >> 1) Can we pick a suggested one that is the fpaste default to try and >> make it easy for infrequent users to not just be told "pick on" >> >> > I am for #2& myself. I think getting the CentOS one setup and into our > Community OpenShift would be a good solution for 3 things. 1 set of tools > to update, 1 set of systems to clean out and 2 no need to worry that our > paste of the week has turned into the GoatPornHub we are sending users too. > If we have this capacity in infra I’m fully onboard with a shared pastebin. I also think we should simply the install and maintenance with shared or neutral branding. > >> 2) Can we do something to help what ever paste bin we do use with >> their resourcing, perhaps a donation or sponsorship as a thank you? >> >> > This is a good idea, but will have to come from the council. I have found > that trying for our department to try and give funding/sponsorship etc is > almost impossible :/. > I’m separating source of funds from willingness :) Regards, bex > > >> regards, >> >> bex >> >> > >> > BTW, fpaste is available in the installation environment (both live & >> netinst images) >> > and is pretty handy for debugging various installation related issues >> as you can't >> > simply fpaste the relevant logs/error messaages and retrieve it on a >> different >> > computer by re-typing the URL. This is likely the easiest method for >> extracting logs >> > from a failed/invalid installation, others are more complicated (scp, >> mounting a flash drive, >> > filling in a libreport form). >> > >> > Actually, if any fpaste changes can give us a shorter to type URL, this >> would be very welcome. :) >> > >> > >> > > >> > > ___ >> > > infrastructure mailing list -- infrastructure@lists.fedoraproject.org >> > > To unsubscribe send an email to >> infrastructure-le...@lists.fedoraproject.org >> > > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >> > > List Guidelines: >> https://fedoraproject.org/wiki/Mailing_list_guidelines >> > > List Archives: >> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org >> > ___ >> > infrastructure mailing list -- infrastructure@lists.fedoraproject.org >> > To unsubscribe send an email to >> infrastructure-le...@lists.fedoraproject.org >> > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> > List Archives: >> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org >> >> >> >> -- >> Brian "bex" Exelbierd (he/him/his) >> Fedora Community Action & Impact Coordinator >> @bexelbie | http://www.winglemeyer.org >> bexel...
Re: pastebin plans
On Mon, May 20, 2019 at 7:36 PM Martin Kolman wrote: > > On Mon, 2019-05-20 at 13:11 -0400, Justin W. Flory wrote: > > On 5/20/19 12:56 PM, Ben Cotton wrote: > > > I don't see that running our own pastebin is valuable to the > > > community. There are plenty of other options for people to post things > > > (pastebin.com, GitHub gists, put a file in your web space on Fedora > > > people, etc). I'm in favor of option 3, with a long enough timeline > > > for the fpaste maintainers to handle the change and for the docs team > > > to make sure we update any docs that refer to pase.fp.o accordingly > > > (if any) > > > > > > > +1 to Option 3. > > > > My biggest use for paste.fp.o is via fpaste in CLI. To me, it also makes > > more sense to use an existing service and point the fpaste tool there. > > So long as fpaste continues to work, my use case and likely others' does > > not break. > Agreed, as long as fpaste continues to be working and puts the pasted text > somewhere sensible > all would be more or less fine. I am seeing lots of early love for Option #3 - I am also great with this but I'd like to see two things: 1) Can we pick a suggested one that is the fpaste default to try and make it easy for infrequent users to not just be told "pick on" 2) Can we do something to help what ever paste bin we do use with their resourcing, perhaps a donation or sponsorship as a thank you? regards, bex > > BTW, fpaste is available in the installation environment (both live & netinst > images) > and is pretty handy for debugging various installation related issues as you > can't > simply fpaste the relevant logs/error messaages and retrieve it on a different > computer by re-typing the URL. This is likely the easiest method for > extracting logs > from a failed/invalid installation, others are more complicated (scp, > mounting a flash drive, > filling in a libreport form). > > Actually, if any fpaste changes can give us a shorter to type URL, this would > be very welcome. :) > > > > > > ___ > > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org > > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org -- Brian "bex" Exelbierd (he/him/his) Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org bexel...@redhat.com | b...@pobox.com ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: old taiga instances
On Mon, Apr 29, 2019 at 7:11 PM Kevin Fenzi wrote: > > ok, so do all of you have the information you need from the old instance > now? > > Is it ok to retire? +1 - yes regards, bex > > kevin > > > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org -- Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: old taiga instances
On Thu, Apr 25, 2019 at 11:21 AM Brian (bex) Exelbierd
wrote:
>
> I'd appreciate seeing both of my projects loaded on the new system,
> even if I wind up deleting one.
nirik turned back on our old Taiga and I have successfully exported
and imported my projects as needed.
regards,
bex
>
> thanks,
>
> bex
>
> On Thu, Apr 25, 2019 at 12:58 AM Kevin Fenzi wrote:
> >
> > On 4/23/19 7:21 AM, Mohan Boddu wrote:
> > > Kevin and Jim, cant we just do the same thing as we did with the RelEng
> > > taiga instance, create a dump of the project and upload it to the new
> > > instance?
> >
> > Sure, we have a full backup that they could use for this I think.
> >
> > Or I still have not yet destroyed the instances, so we could get the
> > data from there.
> >
> > Jim: let me know if you need anymore info to restore Adams data on teams?
> >
> > kevin
> > --
> > >
> > > On Tue, Apr 23, 2019 at 9:34 AM Adam Samalik wrote:
> > >
> > >> I had the Fedora Docs [1] board in there where I tracked development of
> > >> the build pipeline. I probably missed the announcement about teams.fp.o
> > >> but
> > >> it's great it's live. Is there any way to migrate the Docs board over
> > >> there?
> > >>
> > >> [1] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/
> > >>
> > >> On Tue, Apr 23, 2019 at 3:27 PM Ben Cotton wrote:
> > >>
> > >>> I had a small board on the old one ("FPgM Working board" or something
> > >>> like that) to track a few things I was working on. I don't see it in
> > >>> the new instance. If it's easy to migrate, I'd appreciate having it
> > >>> back. If not, then it's no big deal. I wasn't super good about using
> > >>> it anyway.
> > >>>
> > >>> On Mon, Apr 22, 2019 at 4:04 PM Kevin Fenzi wrote:
> > >>>>
> > >>>> Greetings.
> > >>>>
> > >>>> We have 2 old taiga instances: taiga.fedorainfracloud.org and
> > >>>> taiga-stg.fedorainfracloud.org.
> > >>>>
> > >>>> Last week I disabled nginx on them so they aren't serving anything.
> > >>>>
> > >>>> Next week I would like to retire them both completely.
> > >>>>
> > >>>> My understanding is that any active users have moved to the new teams
> > >>>> instance.
> > >>>>
> > >>>> If there's something you need from them, let me know in the next week
> > >>>> before I retire them.
> > >>>>
> > >>>> Thanks,
> > >>>>
> > >>>> kevin
> > >>>>
> > >>>> ___
> > >>>> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> > >>>> To unsubscribe send an email to
> > >>> infrastructure-le...@lists.fedoraproject.org
> > >>>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> > >>>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > >>>> List Archives:
> > >>> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
> > >>>
> > >>>
> > >>>
> > >>> --
> > >>> Ben Cotton
> > >>> Fedora Program Manager
> > >>> TZ=America/Indiana/Indianapolis
> > >>> Pronouns: he/him
> > >>> ___
> > >>> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> > >>> To unsubscribe send an email to
> > >>> infrastructure-le...@lists.fedoraproject.org
> > >>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> > >>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > >>> List Archives:
> > >>> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
> > >>>
> > >>
> > >>
> > >> --
> > >>
> > >> Adam Šamalík
> > >> ---
> > >> Senior Software Engineer
> > >> Red Hat
> > >> ___
> &
Re: old taiga instances
On Thu, Apr 25, 2019 at 12:58 AM Kevin Fenzi wrote:
>
> On 4/23/19 7:21 AM, Mohan Boddu wrote:
> > Kevin and Jim, cant we just do the same thing as we did with the RelEng
> > taiga instance, create a dump of the project and upload it to the new
> > instance?
>
> Sure, we have a full backup that they could use for this I think.
>
> Or I still have not yet destroyed the instances, so we could get the
> data from there.
>
> Jim: let me know if you need anymore info to restore Adams data on teams?
Is Jim the only person who can do this?
regards,
bex
>
> kevin
> --
> >
> > On Tue, Apr 23, 2019 at 9:34 AM Adam Samalik wrote:
> >
> >> I had the Fedora Docs [1] board in there where I tracked development of
> >> the build pipeline. I probably missed the announcement about teams.fp.o but
> >> it's great it's live. Is there any way to migrate the Docs board over
> >> there?
> >>
> >> [1] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/
> >>
> >> On Tue, Apr 23, 2019 at 3:27 PM Ben Cotton wrote:
> >>
> >>> I had a small board on the old one ("FPgM Working board" or something
> >>> like that) to track a few things I was working on. I don't see it in
> >>> the new instance. If it's easy to migrate, I'd appreciate having it
> >>> back. If not, then it's no big deal. I wasn't super good about using
> >>> it anyway.
> >>>
> >>> On Mon, Apr 22, 2019 at 4:04 PM Kevin Fenzi wrote:
> >>>>
> >>>> Greetings.
> >>>>
> >>>> We have 2 old taiga instances: taiga.fedorainfracloud.org and
> >>>> taiga-stg.fedorainfracloud.org.
> >>>>
> >>>> Last week I disabled nginx on them so they aren't serving anything.
> >>>>
> >>>> Next week I would like to retire them both completely.
> >>>>
> >>>> My understanding is that any active users have moved to the new teams
> >>>> instance.
> >>>>
> >>>> If there's something you need from them, let me know in the next week
> >>>> before I retire them.
> >>>>
> >>>> Thanks,
> >>>>
> >>>> kevin
> >>>>
> >>>> ___
> >>>> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> >>>> To unsubscribe send an email to
> >>> infrastructure-le...@lists.fedoraproject.org
> >>>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> >>>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> >>>> List Archives:
> >>> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
> >>>
> >>>
> >>>
> >>> --
> >>> Ben Cotton
> >>> Fedora Program Manager
> >>> TZ=America/Indiana/Indianapolis
> >>> Pronouns: he/him
> >>> ___
> >>> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> >>> To unsubscribe send an email to
> >>> infrastructure-le...@lists.fedoraproject.org
> >>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> >>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> >>> List Archives:
> >>> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
> >>>
> >>
> >>
> >> --
> >>
> >> Adam Šamalík
> >> ---
> >> Senior Software Engineer
> >> Red Hat
> >> ___
> >> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> >> To unsubscribe send an email to
> >> infrastructure-le...@lists.fedoraproject.org
> >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> >> List Archives:
> >> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
> >>
> >
> >
> > ___
> > infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
> > Fedora
Re: old taiga instances
I'd appreciate seeing both of my projects loaded on the new system,
even if I wind up deleting one.
thanks,
bex
On Thu, Apr 25, 2019 at 12:58 AM Kevin Fenzi wrote:
>
> On 4/23/19 7:21 AM, Mohan Boddu wrote:
> > Kevin and Jim, cant we just do the same thing as we did with the RelEng
> > taiga instance, create a dump of the project and upload it to the new
> > instance?
>
> Sure, we have a full backup that they could use for this I think.
>
> Or I still have not yet destroyed the instances, so we could get the
> data from there.
>
> Jim: let me know if you need anymore info to restore Adams data on teams?
>
> kevin
> --
> >
> > On Tue, Apr 23, 2019 at 9:34 AM Adam Samalik wrote:
> >
> >> I had the Fedora Docs [1] board in there where I tracked development of
> >> the build pipeline. I probably missed the announcement about teams.fp.o but
> >> it's great it's live. Is there any way to migrate the Docs board over
> >> there?
> >>
> >> [1] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/
> >>
> >> On Tue, Apr 23, 2019 at 3:27 PM Ben Cotton wrote:
> >>
> >>> I had a small board on the old one ("FPgM Working board" or something
> >>> like that) to track a few things I was working on. I don't see it in
> >>> the new instance. If it's easy to migrate, I'd appreciate having it
> >>> back. If not, then it's no big deal. I wasn't super good about using
> >>> it anyway.
> >>>
> >>> On Mon, Apr 22, 2019 at 4:04 PM Kevin Fenzi wrote:
> >>>>
> >>>> Greetings.
> >>>>
> >>>> We have 2 old taiga instances: taiga.fedorainfracloud.org and
> >>>> taiga-stg.fedorainfracloud.org.
> >>>>
> >>>> Last week I disabled nginx on them so they aren't serving anything.
> >>>>
> >>>> Next week I would like to retire them both completely.
> >>>>
> >>>> My understanding is that any active users have moved to the new teams
> >>>> instance.
> >>>>
> >>>> If there's something you need from them, let me know in the next week
> >>>> before I retire them.
> >>>>
> >>>> Thanks,
> >>>>
> >>>> kevin
> >>>>
> >>>> ___
> >>>> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> >>>> To unsubscribe send an email to
> >>> infrastructure-le...@lists.fedoraproject.org
> >>>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> >>>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> >>>> List Archives:
> >>> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
> >>>
> >>>
> >>>
> >>> --
> >>> Ben Cotton
> >>> Fedora Program Manager
> >>> TZ=America/Indiana/Indianapolis
> >>> Pronouns: he/him
> >>> ___
> >>> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> >>> To unsubscribe send an email to
> >>> infrastructure-le...@lists.fedoraproject.org
> >>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> >>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> >>> List Archives:
> >>> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
> >>>
> >>
> >>
> >> --
> >>
> >> Adam Šamalík
> >> ---
> >> Senior Software Engineer
> >> Red Hat
> >> ___
> >> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> >> To unsubscribe send an email to
> >> infrastructure-le...@lists.fedoraproject.org
> >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> >> List Archives:
> >> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
> >>
> >
> >
> > ___
> > infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> > To unsubscr
Re: old taiga instances
On Mon, Apr 22, 2019 at 10:04 PM Kevin Fenzi wrote: > > Greetings. > > We have 2 old taiga instances: taiga.fedorainfracloud.org and > taiga-stg.fedorainfracloud.org. > > Last week I disabled nginx on them so they aren't serving anything. How can we access these to get data from them? regards, bex > > Next week I would like to retire them both completely. > > My understanding is that any active users have moved to the new teams > instance. > > If there's something you need from them, let me know in the next week > before I retire them. > > Thanks, > > kevin > > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org -- Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: Can't login to fedora.zanata.org
I talked to the current Zanata administrator and was told, "Fedora open id server is not allowing the authentication. No code has been changed on the Zanata server, and in other instances where we have seen this type of problem the problem lies on some changes on the Fedora open id side of things." Looks like we need someone to follow up on the ID side to see if we have errors we can troubleshoot. regards, bex On Wed, Apr 10, 2019 at 3:30 PM Martin Kolman wrote: > > Hi, > it looks like loging to the Fedora Zanata translation service instance no > longer works > When I go to Fedora Zanata (https://fedora.zanata.org) and click to "login", > nothing happens - no FAS loging page shows up as it used to before. > > Tried in both Firefox, Chrome and private mode, always the same. Also have > seen some > others having the same issue. > > In case this is not the proper channel to reaching the people taking care of > the Fedora Zanata instance, then please let me know which is the correct one > as > it seems to be rather unclear at the moment. > > Best Wishes > Martin Kolman > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org -- Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: FAS query question
On Sat, Feb 16, 2019 at 8:28 PM Matthew Miller wrote: > > On Sat, Feb 16, 2019 at 02:18:52PM +0100, Patrick Uiterwijk wrote: > > However, this will be changing in the near future when we move to the > > new account system, so you might want to make sure not to spend too > > long on this for now. > > Well, that raises another question: will the new system have this > capability? Because that's really what matters for Ben's purposes. The ability to query FAS is important when we have requirements like this. Is this planned? regards, bex > > -- > Matthew Miller > > Fedora Project Leader > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org -- Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: MBI (Playground 2.0)
On Thu, Jan 31, 2019 at 1:40 PM Mikolaj Izdebski wrote: > > On Thu, Jan 31, 2019 at 1:36 PM Josh Boyer wrote: > > Why does this need to be deployed in the fedora infrastructure cloud? > > Seems like you could stand it up in AWS or somewhere else. > > Because we (Fedora contributors) don't have budget to pay AWS bills. > If someone is willing to sponsor this then AWS would work well. I encourage you to specify what you need and then the Project can figure out if and how it wants to provide it. So if you need a specific kind of access, note that. If you just need machines, note that. If you need sysadmin work, note that, etc. regards, bex > > -- > Mikolaj > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org -- Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: How do we find the source code for our services?
On Thu, Jan 3, 2019 at 8:58 AM Sayan Chowdhury wrote: > On Wed, Jan 2, 2019 at 2:56 PM Brian (bex) Exelbierd > wrote: > > > > I was looking for the source to the badges website/application to fix > > > > https://pagure.io/fedora-badges/issue/612 > > > > How should I find it without asking someone on the infra team? > > We did fix and push the change in the source code in the 0.9.2 > release, but the *.rst files rendering the footer were getting pushed > via a config file (I did not know that) and a lot of times we push the > config files via our Ansible repository. So, it would be worth > checking the ansible repository too. > I see, I think, that someone fixed the files yesterday in that repo. That repo appears to live solely on a backend machine and has a file only mirror. I am not going to go on about how this was also undiscoverable without a human's help, but I do think it would be nice if our ansible playbooks were more easily findable so we could get PRs, issues, and more importantly show them off as part of the amazing OS created by Fedora. They are good models of infrastructure management. regards, bex > > -- > Sayan Chowdhury <https://words.yudocaa.in/> > GPG Fingerprint : 0F16 E841 E517 225C 7D13 AB3C B023 9931 9CD0 5C8B > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to > infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > -- Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: How do we find the source code for our services?
On Wed, Jan 2, 2019 at 7:57 PM Kevin Fenzi wrote: > On 1/2/19 1:25 AM, Brian (bex) Exelbierd wrote: > > I was looking for the source to the badges website/application to fix > > > > https://pagure.io/fedora-badges/issue/612 > > https://github.com/fedora-infra/tahrir > > How should I find it without asking someone on the infra team? > > A great question. :) > > It sure would be nice if we had some kind of standard 'about' page or > somthing that existed on all our apps that had such info as: > > What is the SLE of this app? > Where do I report bugs about it? > where is it's source code? > etc. > > In the case of badges, if you look at the footer of > badges.fedoraproject.org: > > > Running ﺎﻠﺘﺣﺮﻳﺭ (Tahrir) version 0.9.2 and Tahrir-API version 0.8.1. > > You can submit new badge ideas on the fedora-badges tracker. > > Please report bugs and file issues with التحرير (Tahrir) on the GitHub > issues tracker. > > This project is free software; you can find the source on GitHub. > > (where the GitHub word is a link to the repo) > So that repo doesn't seem to contain this text. Specifically I wanted to fix the link to the badges tracker link that is to the old site and is a redirect. That link doesn't seem to be in the repo. regards, bex > > kevin > > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to > infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > -- Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
How do we find the source code for our services?
I was looking for the source to the badges website/application to fix https://pagure.io/fedora-badges/issue/612 How should I find it without asking someone on the infra team? Thank you. regards, bex -- Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: infrastructure.fedoraproject.org
On Sun, Nov 11, 2018 at 9:18 PM Kevin Fenzi wrote: > > On 11/10/18 10:30 PM, Anatoli Babenia wrote: > > Good Sunday. ) > > > > I found this https://infrastructure.fedoraproject.org/ while searching for > > this list. > > > > Maybe make it a single page entrypoint for all related things? Static site > > generator > > with quick links to sources, SOP, wiki (?) and this list. > > I've no objection to putting something there. It's worth noting that is > mapped to batcave01, so it's our management host. We likely don't want > to run any strange apps or anything, the most would be a static page, IMHO. > > Would you want to work on some static page for this? We could easily generate a site for you on docs.fedoraproject.org from a Pagure repo ... #JustSaying :) regards, bex > > kevin > > > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org -- Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: FAS & openid application development
On Wed, Oct 10, 2018 at 3:25 PM Radka Janekova wrote: > Hi, > > please excuse me if this information is somewhere and I failed to find > it... > > I'm looking for a way to add an application / get an id, to be used in a > web application used to authenticate the user with Fedora account. I did > not see any mention of it in the auth/openid wiki page, I'm assuming that > it would be to create a ticket with infrastructure? > > Who would be the right person to talk to about this topic? Willing to > spare a bit of time to provide some guidance? (Czech would be welcome as it > is a local high school intern working on the project, and I'm not entirely > confident in his English :P) > > Project details to give you a better picture what am I talking about - A > website where the user will log-in with their Fedora account, then have > some options to choose from, these would be generated based on their > scope/groups ... > This sounds like a really cool project. I went looking for docs/descriptions and didn't see them. Where can I find it? Thanks, bex > > Thank you, > Radka > > -- > *Radka Janeková* > .NET Engineer, Red Hat > *radka.ja...@redhat.com * > IRC: radka | Freenode: Rhea > > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to > infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > -- Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: FBR: add lists.pagure.io to our mailing-lists
On Mon, Sep 24, 2018 at 8:05 PM Pierre-Yves Chibon wrote: > On Mon, Sep 24, 2018 at 02:46:00PM +0200, Brian (bex) Exelbierd wrote: > >On Fri, Sep 21, 2018 at 4:40 PM Aurelien Bompard < > aurel...@bompard.org> > >wrote: > > > > Hey folks! > > > > Pingou would like to announce the availability of mailing-lists on > > lists.pagure.io with the 5.0 release. The following patch should > add > > the new domain to our mailing list server. > > Affected services are the mailman server and the proxies. > > > >Where was lists.pagure.io announced? I'd like more details on what > it > >actually does. > > It wasn't announced since it doesn't exist yet :) > > It is basically another domain attached to our existing mailman3 > deployment so > projects hosted on pagure.io can ask for mailing lists. > The first two I'll ask for being pagure-devel and pagure-announce :) Ahh. If needed/helpful I suspect OSAS could host it as well :). Regards, bex > > > Pierre > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to > infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > -- Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: FBR: add lists.pagure.io to our mailing-lists
On Fri, Sep 21, 2018 at 4:40 PM Aurelien Bompard
wrote:
> Hey folks!
>
> Pingou would like to announce the availability of mailing-lists on
> lists.pagure.io with the 5.0 release. The following patch should add
> the new domain to our mailing list server.
> Affected services are the mailman server and the proxies.
>
Where was lists.pagure.io announced? I'd like more details on what it
actually does.
Thanks,
bex
>
> Can I get a couple +1s?
>
> A.
>
>
> commit 46c844f7ad9dfbd824c49fcbd95be3575345d2df
> Author: Aurélien Bompard
> Date: Thu Sep 20 08:28:47 2018 +
>
> Add lists.pagure.org to Mailman
>
> Signed-off-by: Aurélien Bompard
>
> diff --git a/playbooks/include/proxies-reverseproxy.yml
> b/playbooks/include/proxies-reverseproxy.yml
> index 8d35a5f..8461162 100644
> --- a/playbooks/include/proxies-reverseproxy.yml
> +++ b/playbooks/include/proxies-reverseproxy.yml
> @@ -71,6 +71,15 @@
> keephost: true
> proxyurl: "{{ varnish_url }}"
>
> + - role: httpd/reverseproxy
> +website: lists.pagure.io
> +destname: mailman3
> +localpath: /
> +remotepath: /
> +header_scheme: true
> +keephost: true
> +proxyurl: "{{ varnish_url }}"
> +
># The place for the raw originals
>- role: httpd/reverseproxy
> website: meetbot-raw.fedoraproject.org
> diff --git a/playbooks/include/proxies-websites.yml
> b/playbooks/include/proxies-websites.yml
> index 9c0e173..65597cd 100644
> --- a/playbooks/include/proxies-websites.yml
> +++ b/playbooks/include/proxies-websites.yml
> @@ -901,6 +901,12 @@
> - release-monitoring.org
> when: env == "staging"
>
> + - role: httpd/website
> +site_name: lists.pagure.io
> +sslonly: true
> +cert_name: lists.pagure.io.cert
> +SSLCertificateChainFile: lists.pagure.io.intermediate.cert
> +
> # fedorahosted is retired. We have the site here so we can redirect it.
>
>- role: httpd/website
> diff --git a/roles/base/files/postfix/main.cf/main.cf.smtp-mm
> b/roles/base/files/postfix/main.cf/main.cf.smtp-mm
> index 65e3cf7..3130cd0 100644
> --- a/roles/base/files/postfix/main.cf/main.cf.smtp-mm
> +++ b/roles/base/files/postfix/main.cf/main.cf.smtp-mm
> @@ -305,7 +305,7 @@ unknown_local_recipient_reject_code = 550
> #
> #relay_domains = $mydestination
>
> -relay_domains = $mydestination lists.fedoraproject.org
> lists.fedorahosted.org fedorahosted.org
> +relay_domains = $mydestination lists.fedoraproject.org
> lists.fedorahosted.org fedorahosted.org lists.pagure.io
>
> # INTERNET OR INTRANET
>
> diff --git a/roles/base/files/postfix/transports.mm-smtp
> b/roles/base/files/postfix/transports.mm-smtp
> index 582d455..ace4660 100644
> --- a/roles/base/files/postfix/transports.mm-smtp
> +++ b/roles/base/files/postfix/transports.mm-smtp
> @@ -2,4 +2,5 @@ lists.fedoraproject.org smtp:[
> mailman01.vpn.fedoraproject.org]
> lists.fedorahosted.org smtp:[mailman01.vpn.fedoraproject.org]
> redhat.com smtp:[mailman01.vpn.fedoraproject.org]
> lists2.fedoraproject.org smtp:[mailman01.vpn.fedoraproject.org]
> +lists.pagure.io smtp:[mailman01.vpn.fedoraproject.org]
> fedorahosted.org smtp:[bastion.vpn.fedoraproject.org]
> diff --git a/roles/mailman/tasks/main.yml b/roles/mailman/tasks/main.yml
> index 41e3ff6..a665bc1 100644
> --- a/roles/mailman/tasks/main.yml
> +++ b/roles/mailman/tasks/main.yml
> @@ -519,6 +519,14 @@
>- restart memcached
>
>
> +# SSL
> +- name: Letsencrypt for lists.pagure.org
> + include_role: name=letsencrypt
> + vars:
> +site_name: lists.pagure.io
> + when: env == 'production'
> +
> +
> # Start services
> - name: start services
>service: state=started enabled=yes name={{ item }}
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to
> infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
>
--
Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox.com
Fedora Community Action & Impact Coordinator
@bexelbie | http://www.winglemeyer.org
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: Flock Videos for Infra - Incomplete
On Thu, Aug 30, 2018 at 10:43 AM Zach Villers wrote: > Here is a link to a playlist for a few videos from Flock 2018 that may > help apprentices/contributors learn more about Fedora Infrastructure. I > don't think *all* the talks have been posted yet. I will try to update > the playlist if I see more. > Only the first two days are up so far. Regards, bex Flock Playlist > <https://mail.google.com/mail/?ui=2&ik=d0f39868b7&attid=0.0.1.1&th=1658b4a0da3625b2&view=att&disp=emb&zw> > > > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to > infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > -- Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: Infrastructure office hours
On Tue, May 29, 2018 at 12:43 PM, Till Maas wrote: > Hi, > > On Tue, May 29, 2018 at 09:00:49AM +0200, Clement Verna wrote: > > > Note that we already have a general "ask whatever, whenever" on > > #fedora-apps and #fedora-admin where anybody can "ask whatever, whenever" > > :-), but this does not seems to work since we have very few requests. > > > > So do you think that having a dedicated meeting where you know that > people > > are available would improve the situation ? > > the idea sounds great, maybe it could be mini hackfests where people can > get fast feedback on PRs and issues to get them resolved with a shorter > roundtrip time. > I'm +1 to both the "office hours" and the mini-hacks. I think the mini-hacks, in particular, would be a great way to help infra resolve a bunch of easyfixes - if we cuold get a block of time and advertise it. regards, bex > > Kind regards > Till > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-leave@lists. > fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/ > infrastructure@lists.fedoraproject.org/message/ > KMMYMLVWP356IPCESMRB5VDBUERT6AJE/ > -- Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/message/KBZR3GHSNZIS4OK4HF2PHIOZ6U7W5VE5/
Re: [PATCH] [FBR] Update Fedora Council / Flock email aliases
If needed, here is my +1 regards, bex ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: FBR: Forward trees from docs-old
> Hi, > > This should fix https://pagure.io/fedora-infrastructure/issue/6396. > Patch is big, but I generated the actual config file with the input > provided, and then: cat langredirs | sed -e 's./$..' | sed -E > 's/(.*)/Redirect "\/\1" > "https:\/\/docs-old.fedoraproject.org\/\1"/' should these include the "permanent" keyword in order to make them 301s and not 302s? Thanks, bex > > Regards, > Patrick > > > > commit 65aafdc9c7303685cdec332f4ec09f44199a72bf (HEAD -> master) > Author: Patrick Uiterwijk Date: Wed Sep 27 17:14:07 2017 +0200 > > Redirect old docs urls to docs-old > > Signed-off-by: Patrick Uiterwijk > diff --git a/roles/fedora-docs/proxy/files/fedora-docs-old.conf > b/roles/fedora-docs/proxy/files/fedora-docs-old.conf > new file mode 100644 > index 0..8157284b6 > --- /dev/null > +++ b/roles/fedora-docs/proxy/files/fedora-docs-old.conf > @@ -0,0 +1,124 @@ > +Redirect "/af" "https://docs-old.fedoraproject.org/af"; > +Redirect "/af_ZA" "https://docs-old.fedoraproject.org/af_ZA"; > +Redirect "/aln-AL" "https://docs-old.fedoraproject.org/aln-AL"; > +Redirect "/am" "https://docs-old.fedoraproject.org/am"; > +Redirect "/ar-SA" "https://docs-old.fedoraproject.org/ar-SA"; > +Redirect "/as-IN" "https://docs-old.fedoraproject.org/as-IN"; > +Redirect "/ast-ES" "https://docs-old.fedoraproject.org/ast-ES"; > +Redirect "/az" "https://docs-old.fedoraproject.org/az"; > +Redirect "/bal-PK" "https://docs-old.fedoraproject.org/bal-PK"; > +Redirect "/be" "https://docs-old.fedoraproject.org/be"; > +Redirect "/bg-BG" "https://docs-old.fedoraproject.org/bg-BG"; > +Redirect "/bn-BD" "https://docs-old.fedoraproject.org/bn-BD"; > +Redirect "/bn-IN" "https://docs-old.fedoraproject.org/bn-IN"; > +Redirect "/bo" "https://docs-old.fedoraproject.org/bo"; > +Redirect "/br" "https://docs-old.fedoraproject.org/br"; > +Redirect "/brx" "https://docs-old.fedoraproject.org/brx"; > +Redirect "/bs-BA" "https://docs-old.fedoraproject.org/bs-BA"; > +Redirect "/ca-ES" "https://docs-old.fedoraproject.org/ca-ES"; > +Redirect "/cs_CZ" "https://docs-old.fedoraproject.org/cs_CZ"; > +Redirect "/cs-CZ" "https://docs-old.fedoraproject.org/cs-CZ"; > +Redirect "/cy" "https://docs-old.fedoraproject.org/cy"; > +Redirect "/da-DK" "https://docs-old.fedoraproject.org/da-DK"; > +Redirect "/de-CH" "https://docs-old.fedoraproject.org/de-CH"; > +Redirect "/de-DE" "https://docs-old.fedoraproject.org/de-DE"; > +Redirect "/dz" "https://docs-old.fedoraproject.org/dz"; > +Redirect "/el-GR" "https://docs-old.fedoraproject.org/el-GR"; > +Redirect "/en-GB" "https://docs-old.fedoraproject.org/en-GB"; > +Redirect "/en_US" "https://docs-old.fedoraproject.org/en_US"; > +Redirect "/en-US" "https://docs-old.fedoraproject.org/en-US"; > +Redirect "/eo" "https://docs-old.fedoraproject.org/eo"; > +Redirect "/es_ES" "https://docs-old.fedoraproject.org/es_ES"; > +Redirect "/es-ES" "https://docs-old.fedoraproject.org/es-ES"; > +Redirect "/et-EE" "https://docs-old.fedoraproject.org/et-EE"; > +Redirect "/eu_ES" "https://docs-old.fedoraproject.org/eu_ES"; > +Redirect "/eu-ES" "https://docs-old.fedoraproject.org/eu-ES"; > +Redirect "/fa_IR" "https://docs-old.fedoraproject.org/fa_IR"; > +Redirect "/fa-IR" "https://docs-old.fedoraproject.org/fa-IR"; > +Redirect "/fi-FI" "https://docs-old.fedoraproject.org/fi-FI"; > +Redirect "/fr-FR" "https://docs-old.fedoraproject.org/fr-FR"; > +Redirect "/ga" "https://docs-old.fedoraproject.org/ga"; > +Redirect "/gl-ES" "https://docs-old.fedoraproject.org/gl-ES"; > +Redirect "/gu-IN" "https://docs-old.fedoraproject.org/gu-IN"; > +Redirect "/he-IL" "https://docs-old.fedoraproject.org/he-IL"; > +Redirect "/hi-IN" "https://docs-old.fedoraproject.org/hi-IN"; > +Redirect "/hr_HR" "https://docs-old.fedoraproject.org/hr_HR"; > +Redirect "/hr-HR" "https://docs-old.fedoraproject.org/hr-HR"; > +Redirect "/hu-HU" "https://docs-old.fedoraproject.org/hu-HU"; > +Redirect "/hy" "https://docs-old.fedoraproject.org/hy"; > +Redirect "/ia" "https://docs-old.fedoraproject.org/ia"; > +Redirect "/id-ID" "https://docs-old.fedoraproject.org/id-ID"; > +Redirect "/ilo" "https://docs-old.fedoraproject.org/ilo"; > +Redirect "/images" "https://docs-old.fedoraproject.org/images"; > +Redirect "/is-IS" "https://docs-old.fedoraproject.org/is-IS"; > +Redirect "/it_IT" "https://docs-old.fedoraproject.org/it_IT"; > +Redirect "/it-IT" "https://docs-old.fedoraproject.org/it-IT"; > +Redirect "/ja_JP" "https://docs-old.fedoraproject.org/ja_JP"; > +Redirect "/ja-JP" "https://docs-old.fedoraproject.org/ja-JP"; > +Redirect "/ka" "https://docs-old.fedoraproject.org/ka"; > +Redirect "/kk" "https://docs-old.fedoraproject.org/kk"; > +Redirect "/km" "https://docs-old.fedoraproject.org/km"; > +Redirect "/kn-IN" "https://docs-old.fedoraproject.org/kn-IN"; > +Redirect "/ko-KR" "https://docs-old.fedoraproject.org/ko-KR"; > +Redirect "/ks" "https://docs-old.fedoraproject.org/ks"; > +Redirect "/ku" "https://docs-old.fedoraproject.org/ku"; > +Redirect "/ky" "https://d
Re: Proposal: Infrastructure Apps documentation project
> On Jan 30, 2017, at 7:03 PM, Kevin Fenzi wrote: > > On Sat, 28 Jan 2017 09:50:44 +0100 > "Brian (bex) Exelbierd" wrote: > >>> On Jan 27, 2017, at 10:09 PM, Kevin Fenzi wrote: >>> >>> On Fri, 27 Jan 2017 15:56:27 -0500 >>> Jeremy Cline wrote: >>> >>>>> On 01/27/2017 07:19 AM, Clement Verna wrote: >>>>> I think I have mentioned this in an infra-meeting, but we could >>>>> use Pagure docs feature to host the infrastructure SOP. It would >>>>> make them a little bit more user friendly and easier to >>>>> access. >>>> >>>> My thinking was the SOPs would be a section of this documentation. >>>> Since showing is much easier than telling, I spent 20 minutes and >>>> sketched out (a bit) what I imagine this would look like: >>>> https://docs.pagure.org/infra-docs/ >>> >>> Thats pretty awesome. The sops moved over better than I thought they >>> would. :) >>> >>>>> Regarding the development side, I have rediscovered recently the >>>>> developer portal [0] and it looks great, but I don't think it is >>>>> well known or used. For example there is some doc on how to start >>>>> a flask project [1] >>>>> >>>>> Maybe instead of rewriting an app from scratch we could use the >>>>> developer portal. >>>> >>>> I did not know about this at all, and it looks great! It seems like >>>> it's more general in a lot of areas than what I want, but I think >>>> we could using it as a starting off point or link directly to it >>>> in some cases. >>> >>> I would very much like to not use the developer portal for our >>> specific docs. Improving parts of it like the flask area, etc of >>> course would be great. >> >> Wanna use the builder for the new budget infrastructure? It could >> also potentially host the docs. > > I think pagure docs might be a better fit for this... we can then use > the normal PR setup for changes, etc... I'm happy for you to use the best tool for you. The process I am talking about is PR driven. Regards, bex > > kevin > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: Proposal: Infrastructure Apps documentation project
> On Jan 27, 2017, at 10:09 PM, Kevin Fenzi wrote: > > On Fri, 27 Jan 2017 15:56:27 -0500 > Jeremy Cline wrote: > >>> On 01/27/2017 07:19 AM, Clement Verna wrote: >>> I think I have mentioned this in an infra-meeting, but we could use >>> Pagure docs feature to host the infrastructure SOP. It would make >>> them a little bit more user friendly and easier to access. >> >> My thinking was the SOPs would be a section of this documentation. >> Since showing is much easier than telling, I spent 20 minutes and >> sketched out (a bit) what I imagine this would look like: >> https://docs.pagure.org/infra-docs/ > > Thats pretty awesome. The sops moved over better than I thought they > would. :) > >>> Regarding the development side, I have rediscovered recently the >>> developer portal [0] and it looks great, but I don't think it is >>> well known or used. For example there is some doc on how to start a >>> flask project [1] >>> >>> Maybe instead of rewriting an app from scratch we could use the >>> developer portal. >> >> I did not know about this at all, and it looks great! It seems like >> it's more general in a lot of areas than what I want, but I think we >> could using it as a starting off point or link directly to it in some >> cases. > > I would very much like to not use the developer portal for our specific > docs. Improving parts of it like the flask area, etc of course would be > great. Wanna use the builder for the new budget infrastructure? It could also potentially host the docs. Regards, bex > > It uses it's own framework that nothing else we have does (jekyll). > It's not built in our infrastructure. (It builds from a github project > and then that result is checked in and we pull that to serve it on our > machines, which is pretty convoluted). > > kevin > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: [release] pagure: 2.11
> On Jan 20, 2017, at 5:10 PM, Pierre-Yves Chibon wrote: > > - Make issue reports public Are details about this available? Does this mean no more private issues? Regards, bex ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: fedorahosted sunset: need export of spacewalk Trac db
> On Oct 28, 2016, at 11:33 AM, Grant Gainey wrote: > > Hey folks, > > The last thing spacewalk needs to move off of fedorahosted is our Trac wiki. > Can someone give me a pointer to how to get a copy/export of the current > state of the wiki so we can start testing the move-to-github process? I'm > assuming (but don't know for sure) that we're using the default SQLite db. Are you moving to pagure or github? Is this fedora specific material or upstream material? Regards, bex > > Thanks, > Grant Gainey > -- > Grant Gainey > Principal Software Engineer, Red Hat Satellite > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
