Proposal of creating "Airship 1" core reviewer team
Hello Airship Community,
The Working Committee has been looking for a way to address core reviewer team challenges for the Airship 1 projects. Previously, the Airship 1 projects were split out into multiple core teams due to the large amount of active development and subject matter expertise in each of them. At this point, Airship 1 development is much lighter and a smaller group of developers are owning the responsibility end to end.
The Working Committee proposes: o Creating a new "Airship 1" core reviewer team o Membership in the new team would be composed of core reviewers from the current Airship 1 core teams, who have done Airship 1 code reviews in the last 12 months o Following that, the new core team would be able to nominate/vote in additional members as appropriate per usual process.
The WC is seeking feedback from the community. If this plan is supported by the community, the WC plans to put it into effect on July 15th.
Regards, Nishant
Bumping Nishant's request for feedback, since some folks were out on vacation last week. The WC would like to implement the Airship 1 core team plan below on July 15th, if the broader community is in favor of it.
Thanks, Matt
From: KUMAR, NISHANT nk613n@att.com Sent: Monday, June 29, 2020 4:28 PM To: airship-discuss@lists.airshipit.org Subject: [Airship-discuss] Proposal of creating "Airship 1" core reviewer team
***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hello Airship Community,
The Working Committee has been looking for a way to address core reviewer team challenges for the Airship 1 projects. Previously, the Airship 1 projects were split out into multiple core teams due to the large amount of active development and subject matter expertise in each of them. At this point, Airship 1 development is much lighter and a smaller group of developers are owning the responsibility end to end.
The Working Committee proposes: o Creating a new "Airship 1" core reviewer team o Membership in the new team would be composed of core reviewers from the current Airship 1 core teams, who have done Airship 1 code reviews in the last 12 months o Following that, the new core team would be able to nominate/vote in additional members as appropriate per usual process.
The WC is seeking feedback from the community. If this plan is supported by the community, the WC plans to put it into effect on July 15th.
Regards, Nishant
+1 to the proposal
Regards, Alexander Hughes
From: MCEUEN, MATT MM9745@att.com Sent: Tuesday, July 7, 2020 10:27 AM To: KUMAR, NISHANT nk613n@att.com; airship-discuss@lists.airshipit.org Subject: [External] Re: [Airship-discuss] Proposal of creating "Airship 1" core reviewer team
This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments. ________________________________
Bumping Nishant's request for feedback, since some folks were out on vacation last week. The WC would like to implement the Airship 1 core team plan below on July 15th, if the broader community is in favor of it.
Thanks, Matt
From: KUMAR, NISHANT <nk613n@att.commailto:nk613n@att.com> Sent: Monday, June 29, 2020 4:28 PM To: airship-discuss@lists.airshipit.orgmailto:airship-discuss@lists.airshipit.org Subject: [Airship-discuss] Proposal of creating "Airship 1" core reviewer team
***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.htmlhttps://urldefense.proofpoint.com/v2/url?u=http-3A__cso.att.com_EmailSecurity_IDSP.html&d=DwMFAg&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=Z0XiGbYoaIwJ8L5pZFRA0pcRwyCmDi2B8fcRbXgqMmc&m=Ub6bqZTHbCgn0tu2euYnr6AiQpYpQjIhxHcCXR_xAtw&s=4rwO5UJi9gIcPQ2WlcAlAOsb_X1XFNRhRS-9y7DEYg8&e= for more information. Hello Airship Community,
The Working Committee has been looking for a way to address core reviewer team challenges for the Airship 1 projects. Previously, the Airship 1 projects were split out into multiple core teams due to the large amount of active development and subject matter expertise in each of them. At this point, Airship 1 development is much lighter and a smaller group of developers are owning the responsibility end to end.
The Working Committee proposes: o Creating a new "Airship 1" core reviewer team o Membership in the new team would be composed of core reviewers from the current Airship 1 core teams, who have done Airship 1 code reviews in the last 12 months o Following that, the new core team would be able to nominate/vote in additional members as appropriate per usual process.
The WC is seeking feedback from the community. If this plan is supported by the community, the WC plans to put it into effect on July 15th.
Regards, Nishant
________________________________
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy. ______________________________________________________________________________________
www.accenture.com
Thanks everyone, this has been completed. The combined Airship 1 core team was implemented using the existing "airship-core" group, to avoid any review interruption.
The change affects the following Airship 1 projects:
* Armada * Deckhand * Divingbell * Drydock * MaaS * Pegleg * Promenade * Shipyard
All pre-existing Airship 1 core team members have been added to the consolidated group, since all have been active reviewers to A1 projects in the last 12 months (thanks, folks!). The exception is Matt Carter, who appears to no longer be in the backing database, and so couldn't be added to airship-core.
Please let the Working Committee know if you have any questions. Thanks! Matt
From: Hughes, Alexander W. alexander.w.hughes@accenture.com Sent: Tuesday, July 7, 2020 9:29 AM To: MCEUEN, MATT MM9745@att.com; KUMAR, NISHANT nk613n@att.com; airship-discuss@lists.airshipit.org Subject: RE: [External] Re: [Airship-discuss] Proposal of creating "Airship 1" core reviewer team
+1 to the proposal
Regards, Alexander Hughes
From: MCEUEN, MATT <MM9745@att.commailto:MM9745@att.com> Sent: Tuesday, July 7, 2020 10:27 AM To: KUMAR, NISHANT <nk613n@att.commailto:nk613n@att.com>; airship-discuss@lists.airshipit.orgmailto:airship-discuss@lists.airshipit.org Subject: [External] Re: [Airship-discuss] Proposal of creating "Airship 1" core reviewer team
This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments. ________________________________
Bumping Nishant's request for feedback, since some folks were out on vacation last week. The WC would like to implement the Airship 1 core team plan below on July 15th, if the broader community is in favor of it.
Thanks, Matt
From: KUMAR, NISHANT <nk613n@att.commailto:nk613n@att.com> Sent: Monday, June 29, 2020 4:28 PM To: airship-discuss@lists.airshipit.orgmailto:airship-discuss@lists.airshipit.org Subject: [Airship-discuss] Proposal of creating "Airship 1" core reviewer team
***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.htmlhttps://urldefense.proofpoint.com/v2/url?u=http-3A__cso.att.com_EmailSecurity_IDSP.html&d=DwMFAg&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=Z0XiGbYoaIwJ8L5pZFRA0pcRwyCmDi2B8fcRbXgqMmc&m=Ub6bqZTHbCgn0tu2euYnr6AiQpYpQjIhxHcCXR_xAtw&s=4rwO5UJi9gIcPQ2WlcAlAOsb_X1XFNRhRS-9y7DEYg8&e= for more information. Hello Airship Community,
The Working Committee has been looking for a way to address core reviewer team challenges for the Airship 1 projects. Previously, the Airship 1 projects were split out into multiple core teams due to the large amount of active development and subject matter expertise in each of them. At this point, Airship 1 development is much lighter and a smaller group of developers are owning the responsibility end to end.
The Working Committee proposes: o Creating a new "Airship 1" core reviewer team o Membership in the new team would be composed of core reviewers from the current Airship 1 core teams, who have done Airship 1 code reviews in the last 12 months o Following that, the new core team would be able to nominate/vote in additional members as appropriate per usual process.
The WC is seeking feedback from the community. If this plan is supported by the community, the WC plans to put it into effect on July 15th.
Regards, Nishant
________________________________
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policyhttps://urldefense.proofpoint.com/v2/url?u=https-3A__www.accenture.com_us-2Den_privacy-2Dpolicy&d=DwQFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=0XXhNSFzO3_3JFlmpkiurXPuwVcDBBJpSU5TTJ5B8ww&s=K3w9R6qof3wTEq6q80Af23HEEGuBXomT62zSNV_-4BA&e=. ______________________________________________________________________________________
participants (3)
-
Hughes, Alexander W.
-
KUMAR, NISHANT
-
MCEUEN, MATT