Re: [openstack-dev] sign up for oslo liaisons for kilo cycle
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 06/10/14 17:56, Doug Hellmann wrote: The Oslo team is responsible for managing code shared between projects. There are a LOT more projects than Oslo team members, so we created the liaison program at the beginning of the Juno cycle, asking each team that uses Oslo libraries to provide one volunteer liaison. Our liaisons facilitate communication and work with us to make the application code changes needed as code moves out of the incubator and into libraries. With this extra help in place, we were able to successfully graduate 7 new libraries and begin having them adopted across OpenStack. With the change-over to the new release cycle, it’s time to ask for volunteers to sign up to be liaisons again. If you are interested in acting as a liaison for your project, please sign up on the wiki page [1]. It would be very helpful to have a full roster before the summit, so we can make sure liaisons are invited to participate in any relevant discussions there. Thanks, Doug [1] https://wiki.openstack.org/wiki/Oslo/ProjectLiaisons Quoting the page: The liaison should be a core reviewer for the project. Is it a reasonable limitation? I suspect that being an Oslo liaison usually does not really require the core status. Any team member with visible level of participation in the project and decent communication skills should be able to do the job. Why I ask: I would probably consider signing up for the liaison program from Neutron side if 1) the program rules would not be that tight; and 2) current Neutron Oslo liaison (Salvatore?) wouldn't be against it. Cheers, /Ihar -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUM9SVAAoJEC5aWaUY1u57jEYIAK3MTR+WwkHP9YxrexRQZl0R sJ5Y2fDZVbfUzypLIpOdEizTmPVs7jvHzUZnK48cgTG1RDiuO2BBZA0F08nsZnXN 9eJ6VABiD1ZRyctIa9yMeuSIspenDpJYWoPnnE6Z0y0vnJz0JlXnsgHRpvvIOwYI bS73fUlpr7X5bHBE4+QT1ByeWVklBjO/TPzmiyzeMONBw2sg2feRXKtWJ0S1COuv 04U7hvjbAn7ujP7nC8VhnRsIDqYoZ0l7I0zPuZXKqWLME6JLRL8XYt3GL77RCrLf tQJVynpRrAYCgM33NqqEqIxqnHo7gLHDjEj10ekUO+1d6ZFEdR48apA1Zc6Q7YM= =+HC1 -END PGP SIGNATURE- ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] sign up for oslo liaisons for kilo cycle
I am totally not against it. I agree with you that probably the restriction on core-only might be lifted, but that decision lies with the oslo team. Salvatore On 7 October 2014 13:55, Ihar Hrachyshka ihrac...@redhat.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 06/10/14 17:56, Doug Hellmann wrote: The Oslo team is responsible for managing code shared between projects. There are a LOT more projects than Oslo team members, so we created the liaison program at the beginning of the Juno cycle, asking each team that uses Oslo libraries to provide one volunteer liaison. Our liaisons facilitate communication and work with us to make the application code changes needed as code moves out of the incubator and into libraries. With this extra help in place, we were able to successfully graduate 7 new libraries and begin having them adopted across OpenStack. With the change-over to the new release cycle, it’s time to ask for volunteers to sign up to be liaisons again. If you are interested in acting as a liaison for your project, please sign up on the wiki page [1]. It would be very helpful to have a full roster before the summit, so we can make sure liaisons are invited to participate in any relevant discussions there. Thanks, Doug [1] https://wiki.openstack.org/wiki/Oslo/ProjectLiaisons Quoting the page: The liaison should be a core reviewer for the project. Is it a reasonable limitation? I suspect that being an Oslo liaison usually does not really require the core status. Any team member with visible level of participation in the project and decent communication skills should be able to do the job. Why I ask: I would probably consider signing up for the liaison program from Neutron side if 1) the program rules would not be that tight; and 2) current Neutron Oslo liaison (Salvatore?) wouldn't be against it. Cheers, /Ihar -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUM9SVAAoJEC5aWaUY1u57jEYIAK3MTR+WwkHP9YxrexRQZl0R sJ5Y2fDZVbfUzypLIpOdEizTmPVs7jvHzUZnK48cgTG1RDiuO2BBZA0F08nsZnXN 9eJ6VABiD1ZRyctIa9yMeuSIspenDpJYWoPnnE6Z0y0vnJz0JlXnsgHRpvvIOwYI bS73fUlpr7X5bHBE4+QT1ByeWVklBjO/TPzmiyzeMONBw2sg2feRXKtWJ0S1COuv 04U7hvjbAn7ujP7nC8VhnRsIDqYoZ0l7I0zPuZXKqWLME6JLRL8XYt3GL77RCrLf tQJVynpRrAYCgM33NqqEqIxqnHo7gLHDjEj10ekUO+1d6ZFEdR48apA1Zc6Q7YM= =+HC1 -END PGP SIGNATURE- ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] sign up for oslo liaisons for kilo cycle
Ihar, Welcome! and thanks for considering signing up to be liaison :) As oslo core, i'd support the relaxation. I think the thinking behind the wording was it would help if folks were core -- dims On Tue, Oct 7, 2014 at 7:55 AM, Ihar Hrachyshka ihrac...@redhat.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 06/10/14 17:56, Doug Hellmann wrote: The Oslo team is responsible for managing code shared between projects. There are a LOT more projects than Oslo team members, so we created the liaison program at the beginning of the Juno cycle, asking each team that uses Oslo libraries to provide one volunteer liaison. Our liaisons facilitate communication and work with us to make the application code changes needed as code moves out of the incubator and into libraries. With this extra help in place, we were able to successfully graduate 7 new libraries and begin having them adopted across OpenStack. With the change-over to the new release cycle, it’s time to ask for volunteers to sign up to be liaisons again. If you are interested in acting as a liaison for your project, please sign up on the wiki page [1]. It would be very helpful to have a full roster before the summit, so we can make sure liaisons are invited to participate in any relevant discussions there. Thanks, Doug [1] https://wiki.openstack.org/wiki/Oslo/ProjectLiaisons Quoting the page: The liaison should be a core reviewer for the project. Is it a reasonable limitation? I suspect that being an Oslo liaison usually does not really require the core status. Any team member with visible level of participation in the project and decent communication skills should be able to do the job. Why I ask: I would probably consider signing up for the liaison program from Neutron side if 1) the program rules would not be that tight; and 2) current Neutron Oslo liaison (Salvatore?) wouldn't be against it. Cheers, /Ihar -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUM9SVAAoJEC5aWaUY1u57jEYIAK3MTR+WwkHP9YxrexRQZl0R sJ5Y2fDZVbfUzypLIpOdEizTmPVs7jvHzUZnK48cgTG1RDiuO2BBZA0F08nsZnXN 9eJ6VABiD1ZRyctIa9yMeuSIspenDpJYWoPnnE6Z0y0vnJz0JlXnsgHRpvvIOwYI bS73fUlpr7X5bHBE4+QT1ByeWVklBjO/TPzmiyzeMONBw2sg2feRXKtWJ0S1COuv 04U7hvjbAn7ujP7nC8VhnRsIDqYoZ0l7I0zPuZXKqWLME6JLRL8XYt3GL77RCrLf tQJVynpRrAYCgM33NqqEqIxqnHo7gLHDjEj10ekUO+1d6ZFEdR48apA1Zc6Q7YM= =+HC1 -END PGP SIGNATURE- ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Davanum Srinivas :: https://twitter.com/dims ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] sign up for oslo liaisons for kilo cycle
On Oct 7, 2014, at 7:55 AM, Ihar Hrachyshka ihrac...@redhat.com wrote: Signed PGP part On 06/10/14 17:56, Doug Hellmann wrote: The Oslo team is responsible for managing code shared between projects. There are a LOT more projects than Oslo team members, so we created the liaison program at the beginning of the Juno cycle, asking each team that uses Oslo libraries to provide one volunteer liaison. Our liaisons facilitate communication and work with us to make the application code changes needed as code moves out of the incubator and into libraries. With this extra help in place, we were able to successfully graduate 7 new libraries and begin having them adopted across OpenStack. With the change-over to the new release cycle, it’s time to ask for volunteers to sign up to be liaisons again. If you are interested in acting as a liaison for your project, please sign up on the wiki page [1]. It would be very helpful to have a full roster before the summit, so we can make sure liaisons are invited to participate in any relevant discussions there. Thanks, Doug [1] https://wiki.openstack.org/wiki/Oslo/ProjectLiaisons Quoting the page: The liaison should be a core reviewer for the project. Is it a reasonable limitation? I suspect that being an Oslo liaison usually does not really require the core status. Any team member with visible level of participation in the project and decent communication skills should be able to do the job. Why I ask: I would probably consider signing up for the liaison program from Neutron side if 1) the program rules would not be that tight; and 2) current Neutron Oslo liaison (Salvatore?) wouldn't be against it. We need someone who can push patches into the project and understands the code well enough to be able to do that without delay. Usually that means a core reviewer. If the Neutron team commits to working closely with you on patches to avoid delays, that would achieve the same ends. Doug ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] sign up for oslo liaisons for kilo cycle
On 10/07/2014 02:50 PM, Doug Hellmann wrote: On Oct 7, 2014, at 7:55 AM, Ihar Hrachyshka ihrac...@redhat.com wrote: Signed PGP part On 06/10/14 17:56, Doug Hellmann wrote: The Oslo team is responsible for managing code shared between projects. There are a LOT more projects than Oslo team members, so we created the liaison program at the beginning of the Juno cycle, asking each team that uses Oslo libraries to provide one volunteer liaison. Our liaisons facilitate communication and work with us to make the application code changes needed as code moves out of the incubator and into libraries. With this extra help in place, we were able to successfully graduate 7 new libraries and begin having them adopted across OpenStack. With the change-over to the new release cycle, it’s time to ask for volunteers to sign up to be liaisons again. If you are interested in acting as a liaison for your project, please sign up on the wiki page [1]. It would be very helpful to have a full roster before the summit, so we can make sure liaisons are invited to participate in any relevant discussions there. Thanks, Doug [1] https://wiki.openstack.org/wiki/Oslo/ProjectLiaisons Quoting the page: The liaison should be a core reviewer for the project. Is it a reasonable limitation? I suspect that being an Oslo liaison usually does not really require the core status. Any team member with visible level of participation in the project and decent communication skills should be able to do the job. Why I ask: I would probably consider signing up for the liaison program from Neutron side if 1) the program rules would not be that tight; and 2) current Neutron Oslo liaison (Salvatore?) wouldn't be against it. We need someone who can push patches into the project and understands the code well enough to be able to do that without delay. Usually that means a core reviewer. If the Neutron team commits to working closely with you on patches to avoid delays, that would achieve the same ends. Agreed with Doug. It's not really a strong requirement. The request of the liaison to be a core reviewer is more a suggestion for the projects themselves in order to make the interaction between both teams easier. That said, we could probably re-word that somehow to reflect the above. Flavio -- @flaper87 Flavio Percoco ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] sign up for oslo liaisons for kilo cycle
On Tue, Oct 7, 2014 at 7:50 AM, Doug Hellmann d...@doughellmann.com wrote: On Oct 7, 2014, at 7:55 AM, Ihar Hrachyshka ihrac...@redhat.com wrote: Signed PGP part On 06/10/14 17:56, Doug Hellmann wrote: The Oslo team is responsible for managing code shared between projects. There are a LOT more projects than Oslo team members, so we created the liaison program at the beginning of the Juno cycle, asking each team that uses Oslo libraries to provide one volunteer liaison. Our liaisons facilitate communication and work with us to make the application code changes needed as code moves out of the incubator and into libraries. With this extra help in place, we were able to successfully graduate 7 new libraries and begin having them adopted across OpenStack. With the change-over to the new release cycle, it’s time to ask for volunteers to sign up to be liaisons again. If you are interested in acting as a liaison for your project, please sign up on the wiki page [1]. It would be very helpful to have a full roster before the summit, so we can make sure liaisons are invited to participate in any relevant discussions there. Thanks, Doug [1] https://wiki.openstack.org/wiki/Oslo/ProjectLiaisons Quoting the page: The liaison should be a core reviewer for the project. Is it a reasonable limitation? I suspect that being an Oslo liaison usually does not really require the core status. Any team member with visible level of participation in the project and decent communication skills should be able to do the job. Why I ask: I would probably consider signing up for the liaison program from Neutron side if 1) the program rules would not be that tight; and 2) current Neutron Oslo liaison (Salvatore?) wouldn't be against it. We need someone who can push patches into the project and understands the code well enough to be able to do that without delay. Usually that means a core reviewer. If the Neutron team commits to working closely with you on patches to avoid delays, that would achieve the same ends. I am 100% onboard with Ihar being the Neutron team's Osli liaison. Thanks for signing up Ihar, and thanks for working with us here Doug! Kyle Doug ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] sign up for oslo liaisons for kilo cycle
Last cycle the Ironic liaison wasn't a core reviewer and things worked. So I agree with the idea of relaxing the recommendation. Ghe Rivero (Ironic liaison) On 07/10/14 14:50, Doug Hellmann wrote: On Oct 7, 2014, at 7:55 AM, Ihar Hrachyshka ihrac...@redhat.com wrote: Signed PGP part On 06/10/14 17:56, Doug Hellmann wrote: The Oslo team is responsible for managing code shared between projects. There are a LOT more projects than Oslo team members, so we created the liaison program at the beginning of the Juno cycle, asking each team that uses Oslo libraries to provide one volunteer liaison. Our liaisons facilitate communication and work with us to make the application code changes needed as code moves out of the incubator and into libraries. With this extra help in place, we were able to successfully graduate 7 new libraries and begin having them adopted across OpenStack. With the change-over to the new release cycle, it’s time to ask for volunteers to sign up to be liaisons again. If you are interested in acting as a liaison for your project, please sign up on the wiki page [1]. It would be very helpful to have a full roster before the summit, so we can make sure liaisons are invited to participate in any relevant discussions there. Thanks, Doug [1] https://wiki.openstack.org/wiki/Oslo/ProjectLiaisons Quoting the page: The liaison should be a core reviewer for the project. Is it a reasonable limitation? I suspect that being an Oslo liaison usually does not really require the core status. Any team member with visible level of participation in the project and decent communication skills should be able to do the job. Why I ask: I would probably consider signing up for the liaison program from Neutron side if 1) the program rules would not be that tight; and 2) current Neutron Oslo liaison (Salvatore?) wouldn't be against it. We need someone who can push patches into the project and understands the code well enough to be able to do that without delay. Usually that means a core reviewer. If the Neutron team commits to working closely with you on patches to avoid delays, that would achieve the same ends. Doug ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] sign up for oslo liaisons for kilo cycle
The Oslo team is responsible for managing code shared between projects. There are a LOT more projects than Oslo team members, so we created the liaison program at the beginning of the Juno cycle, asking each team that uses Oslo libraries to provide one volunteer liaison. Our liaisons facilitate communication and work with us to make the application code changes needed as code moves out of the incubator and into libraries. With this extra help in place, we were able to successfully graduate 7 new libraries and begin having them adopted across OpenStack. With the change-over to the new release cycle, it’s time to ask for volunteers to sign up to be liaisons again. If you are interested in acting as a liaison for your project, please sign up on the wiki page [1]. It would be very helpful to have a full roster before the summit, so we can make sure liaisons are invited to participate in any relevant discussions there. Thanks, Doug [1] https://wiki.openstack.org/wiki/Oslo/ProjectLiaisons ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
