[openstack-dev] Summit Core Party after Austin
doug.chivers at hpe.com
Fri Apr 22 17:17:45 UTC 2016
The Vancouver core party was a fantastic opportunity to meet some very smart people and learn a lot about the projects they worked on. It was probably one of the most useful parts of the summit, certainly more so than the greasy marketing party, and arguably a much better use of developer time.
An opportunity to chill out and talk to technical people over a quiet beer? Long may that continue, even if it is not the core party in its current form.
On 22/04/2016, 14:52, "Mike Perez" <thingee at gmail.com> wrote:
>On 18:57 Apr 21, Thierry Carrez wrote:
>> Thierry Carrez wrote:
>> >I think it's inappropriate because it gives a wrong incentive to become
>> >a core reviewer. Core reviewing should just be a duty you sign up to,
>> >not necessarily a way to get into a cool party. It was also a bit
>> >exclusive of other types of contributions.
>> >Apparently in Austin the group was reduced to only release:managed
>> >repositories. This tag is to describe which repositories the release
>> >team is comfortable handling. I think it's inappropriate to reuse it to
>> >single out a subgroup of cool folks, and if that became a tradition the
>> >release team would face pressure from repositories to get the tag that
>> >are totally unrelated to what the tag describes.
>> Small precision, since I realize after posting this might be taken the wrong
>> Don't get me wrong, HPE is of course free to invite whoever they want to
>> their party :) But since you asked for opinions, my personal wish if it
>> continues would be that it is renamed "the HPE VIP party" rather than
>> partially tie it to specific rights or tags we happen to use upstream.
>After seeing numerous threads from people in the community being upset by these
>parties, I'd be fine with them not continuing.
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev