On 07/06/2015 04:01 AM, Niall Douglas wrote:
Trying to change or upgrade infrastructure is a Kafka-esque soul draining affair - even getting the Boost SSL cert replaced, which *still* hasn't happened, has proven that. Nobody knows who to go talk to about something half the time because the lists of names responsible for infrastructure are so out of date.
This is has been too true for the SSL. I've been working as the middle man to try and get the cert updated for several weeks now. Not as a member of the steering committee... just as an annoyed member of the community. I finally have all the right players involved but still no personal control to make it happen. It is crazy frustrating!
It shouldn't be as hard as it is to contribute to Boost outside the libraries you maintain. It shouldn't be hard to upgrade infrastructure at all. It should be*easy*.
Agreed! Were you able to find a list of who-is-responsible for infrastructure? Perhaps we can come up with a list of items and who in the community has permissions or control. If you found a list we could use that as a starting point. Otherwise, I suspect you and I have a list of things we have been trying to do that require knowing a responsible party. I'd be happy to try and keep such a thing up-to-date.
It definitely shouldn't be the case that Boost infrastructure is rotting away, and nobody is doing anything about it and any attempts to get the steering committee to move on this go nowhere, despite repeated attempts by myself and others.
Well, I don't think this is a completely accurate characterization. You have been trying to do something. I am trying to do something. I have several infrastructure test servers running evaluations of things my team is trying to pull together for Boost. It sounds like Rene is working on some things. Maybe we should have a location that our non-library ventures and efforts are described/updated so people can know what is going on and get involved if they are interested? michael -- Michael Caisse ciere consulting ciere.com