Closing the vote, as all existing core members voted. Bharath - Welcome to the Tacker core team!
On Mon, Jun 6, 2016 at 11:39 AM, Stephen Wong <stephen.kf.w...@gmail.com> wrote: > +1 > > On Fri, Jun 3, 2016 at 9:23 PM, Haddleton, Bob (Nokia - US) < > bob.haddle...@nokia.com> wrote: > >> +1 >> >> Bob >> >> On Jun 3, 2016, at 8:24 PM, Sridhar Ramaswamy <sric...@gmail.com> wrote: >> >> Tackers, >> >> I'm happy to propose Bharath Thiruveedula (IRC: tbh) to join the tacker >> core team. Bharath has been contributing to Tacker from the Liberty cycle, >> and he has grown into a key member of this project. His contribution has >> steadily increased as he picked up bigger pieces to deliver [1]. >> Specifically, he contributed the automatic resource creation blueprint [2] >> in the Mitaka release. Plus tons of other RFEs and bug fixes [3]. Bharath >> is also a key contributor in tosca-parser and heat-translator projects >> which is an added plus. >> >> Please provide your +1/-1 votes. >> >> Thanks Bharath for your contributions so far and much more to come !! >> >> [1] >> http://stackalytics.com/?project_type=openstack&release=all&metric=commits&user_id=bharath-ves&module=tacker-group >> [2] >> https://blueprints.launchpad.net/tacker/+spec/automatic-resource-creation >> [3] https://bugs.launchpad.net/bugs/+bugs?field.assignee=bharath-ves >> <https://bugs.launchpad.net/bugs/+bugs?field.searchtext=&field.status%3Alist=NEW&field.status%3Alist=OPINION&field.status%3Alist=INVALID&field.status%3Alist=WONTFIX&field.status%3Alist=EXPIRED&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=FIXRELEASED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=bharath-ves&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.tag=&field.tags_combinator=ALL&field.status_upstream-empty-marker=1&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search&orderby=-targetname&start=0> >> >> __________________________________________________________________________ >> 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 >> >> >> __________________________________________________________________________ >> 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 >> >> > > __________________________________________________________________________ > 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 > >
__________________________________________________________________________ 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