Hey everyone.
As you know, we currently have a RHOSP5 ancient cloud. After a bunch of
work last year, we got a RHOSP13 cloud up and mostly working, but it was
a ton of work. After hearing from the Fedora Council and our various
management chains we determined that it wouldn't really be a good use
On 1/29/19 5:14 AM, Leigh Griffin wrote:
> Hey everyone,
>
> I am trying to get a handle on the number of projects that we are
> actively working on for any given day of the week. Could I ask everybody to
> reply here with some information. At a minimum if you could share with me:
Yeah, I am in t
On 1/11/19 7:56 AM, Ben Cotton wrote:
> I am beginning to prepare the schedule for Fedora 31. One thing I want
> to do is to make sure it still accurately reflects the work of
> different teams within Fedora. Please look at the tasks on your team's
> schedule [1] and discuss them in your team. Let
This looks fine to me.
I guess we should coordinate a time to apply this and any other changes
at the same time?
kevin
signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To
On Thu, Jan 31, 2019 at 10:45 AM Karsten Hopp wrote:
>
> Wow, that's an impressive list !
>
> Mine is much shorter:
>
> - Pagure (see above)
>
Well, I work on Pagure too. I'm the maintainer for Pagure in Fedora
and EPEL now, as well as in Mageia and openSUSE. Mainly I fix things
related to makin
Similar to smooge, I'm on the ops side primarily, but I do bounce
around and try to be flexible when needed.
Notable things over the last few months:
- Lots of newcloud work with Kevin, Jim, and Patrick
- Maintained and deployed the websites -- at least enough to get them
updated -- for the last f
Wow, that's an impressive list !
Mine is much shorter:
- Pagure (see above)
- Fedora CI (gating)
https://fedoraproject.org/wiki/CI
- package maintenance, i.e. vim, libcap, ed, Add tests and enable gating
___
infrastructure mailing list -- inf
On Wed, Jan 30, 2019 at 5:07 PM Leigh Griffin wrote:
> Hey everyone,
>
> I am trying to get a handle on the number of projects that we are
> actively working on for any given day of the week. Could I ask everybody to
> reply here with some information. At a minimum if you could share with me:
>
>
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 bu
Thanks to those that responded, if you haven't had a chance with travel /
busy things going on, it would be really appreciated if you could take 5
minutes and give an overview.
To clarify by backlog / roadmap, I mean do you have future plans to do
certain things so that the Community can have an i
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 AW
On Thu, Jan 31, 2019 at 7:28 AM Igor Gnatenko
wrote:
>
> MayBe I …(can do something useful)?
>
> Hello,
>
> We've been discussing some (hopefully) nice idea with Mikolaj, Neal and Jakub
> how we could improve packager (and user) experience and we have some proposal
> which will be described belo
MayBe I …(can do something useful)?
Hello,
We've been discussing some (hopefully) nice idea with Mikolaj, Neal and
Jakub how we could improve packager (and user) experience and we have some
proposal which will be described below.
We would like to ask you to read it, understand it and ask us any
On Wed, 30 Jan 2019 at 21:41, Kevin Fenzi wrote:
>
> On 1/30/19 1:28 AM, Clement Verna wrote:
> > Hi all,
> >
> > I have started a document [0] to gather the releng tasks that would
> > benefit automation. At this point I am not looking for the HOW, but
> > more for the WHAT.
> >
> > So if you hav
14 matches
Mail list logo