+1

+1

This proposal concerns me slightly as I am hesitant to set precedence that funds that should be used elsewhere can be reallocated to infrastructure. This is not to say that infra isn't important, it is just that this precedence is going to blur the line some. Our community is proud that we are more than a code/technical contribution community and the public budget is one way we drive that. This budget is a resource many other communities do not have.

However, I also recognize where we are in our spending plan and that this service will benefit more than just the technical/code contribution community. I'm currently +0/+1 on this.

I do not really follow what is actually paid for by the budget. Is it for covering hosting costs for a taiga instance until March 2019?

@till Yes, this is to cover the cost of the hosted service provided by Taiga.

I am okay with spending the money on a hosted taiga.io is shows that we are willing to invest in other upstream communities to help them stay opena nd to benefit Fedora as a user. As they say "Freedom is not free" I would like to make sure that it is tied into fas for authentication, I think that is not really an issue, and that we let all groups in Fedora know how they could take advantage of the service to help in their project planning.

Absolutely agreed the instance needs to work with FAS.

I would also like to see more features added to Taiga over time and hopefully our funds can help with that. Overall I'm +1 here.

@bcotton can we bring this to a vote today?

@bex I'll add it to the agenda for today's meeting

Passed by (lazy) consensus and affirmed at the 31 October Council Meeting - assigned to bex to do the processing.

This has been added to the budget. @mattdm and @jperrin and @pfrields please let me know if you need help processing the payment/invoice.