On 28/01/2016 1:03 AM, Steven Dake (stdake) wrote: > Choice is one of life's fundamental elements that make life interesting. > Let the Operators choose what they wish based upon technical merits rather > then "who was first to publish a project".
yes, it's nice when competing entities exists in the same domain... i'm not sure it's the same when it's also within the same community. i realise this is common practice in big enterprise where often they'll make multiple plays on the same thing because a) they built up a lot money in the past and b) they are too big and didn't realise someone else was doing it as well. regardless, it's quite obvious having multiple plays does split up your best talent and it's debatable whether the surviving solution is the best solution or just a solution. it also devalues the work each team is doing so workers care less about it but that's a psychological argument which i don't have a survey to reference. regardless if it's creative and original, my question would be why was your first step to create something new rather than advocate for change? i'll go a slight tangent because i feel like this is one of the root of the issues: i think we need to devalue what a PTL is. there are many companies who seek PTLs and even promote the number of PTLs on staff as if they are some infallible deity. this is not what a PTL is and you are doing it wrong if that's what you think it is. can we rebrand PTL to what it is? team administrator or secretary or liaison (wow, this is actually useful now)? maybe this will stop people from trying so hard to have a PTL in their title and they will attempt to collaborate first rather than duplicate. On 28/01/2016 6:34 AM, Chris Dent wrote: > Let's be honest: From my perspective Joe (and others) had it in for > Ceilometer and was hoping that the validation of Monasca would have some > impact on improving the Telemetry situation, so the lack of criteria > that would have prevent Monasca's inclusion is convenient. go back to silly-ometer dude :P cheers, -- gord __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
