├── img
├── dotnetfdn.png
├── membership-request.png
└── website-copy
│ └── jessica.jpg
├── .github
├── CODEOWNERS
├── pull_request_template.md
├── ISSUE_TEMPLATE
│ ├── membership_request.md
│ └── meeting_agenda.md
└── CONTRIBUTING.md
├── .vscode
└── settings.json
├── meetings
├── 2020
│ ├── 06-20-update-policy-change.md
│ ├── 11-17-meeting-minutes.md
│ └── 06-17-meeting-minutes.md
├── 2021
│ ├── 02-16-meeting-minutes.md
│ ├── 04-20-meeting-minutes.md
│ ├── 11-17-meeting-minutes.md
│ ├── 01-19-meeting-notes.md
│ ├── 05-18-meeting-minutes.md
│ ├── 02-02-meeting-minutes.md
│ ├── 05-04-meeting-minutes.md
│ ├── 06-01-meeting-minutes.md
│ ├── 07-06-meeting-minutes.md
│ ├── 03-16-meeting-minutes.md
│ ├── 03-02-meeting-minutes.md
│ ├── 11-03-meeting-minutes.md
│ ├── 10-20-meeting-minutes.md
│ ├── 07-20-meeting-minutes.md
│ └── 04-06-meeting-minutes.md
├── 2022
│ ├── 04-27-meeting-minutes.md
│ ├── 02-16-meeting-minutes.md.md
│ ├── 03-02-meeting-minutes.md
│ ├── 10-12-meeting-minutes.md
│ ├── 05-16-meeting-minutes.md
│ ├── 01-26-meeting-minutes.md
│ ├── 03-23-meeting-minutes.md
│ ├── 02-02-meeting-minutes.md
│ ├── 11-02-meeting-minutes.md
│ ├── 08-03-meeting-minutes.md
│ ├── 09-07-meeting-minutes.md
│ ├── 01-05-meeting-minutes.md
│ ├── 06-01-meeting-minutes.md
│ ├── 04-06-meeting-minutes.md
│ ├── 06-15-meeting-minutes.md
│ ├── 12-07-meeting-minutes.md
│ ├── 11-16-meeting-minutes.md
│ └── 07-06-meeting-minutes.md
├── 2023
│ ├── 12-05-meeting-minutes.md
│ ├── 05-17-meeting-minutes.md
│ ├── 09-20-meeting-minutes.md
│ ├── 02-15-meeting-minutes.md
│ ├── 01-04-meeting-minutes.md
│ ├── 04-19-meeting-minutes.md
│ ├── 03-05-meeting-minutes.md
│ ├── 01-18-meeting-minutes.md
│ ├── 03-01-meeting-minutes.md
│ ├── 10-04-meeting-minutes.md
│ ├── 11-01-meeting-minutes.md
│ └── 04-05-meeting-minutes.md
└── template-meeting-minutes.md
├── resources
├── templates
│ ├── recruiting-board
│ │ ├── tweet-dm-template.md
│ │ └── email-template.md
│ ├── recruiting-nominating-committee
│ │ ├── tweet-dm-template.md
│ │ └── email-template.md
│ └── README.md
├── website-copy
│ ├── README
│ └── committees-2022.md
├── dnf-champions
│ └── champions-proposal.md
├── timelines
│ └── nomination-schedule.md
├── member-documentation
│ ├── membership-criteria.md
│ └── member-participation-types.md
├── commitee-documentation
│ └── membership-committee-charter.md
└── recruiting-board
│ └── board-responsibilities.md
├── CODE_OF_CONDUCT.md
├── LICENSE
└── README.md
/img/dotnetfdn.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/dotnet-foundation/wg-membership/HEAD/img/dotnetfdn.png
--------------------------------------------------------------------------------
/.github/CODEOWNERS:
--------------------------------------------------------------------------------
1 | * @wordshaker @jguadagno @ovebastiansen @nicoleabuhakmeh @codehippie1 @jorgelevy @1kevgriff
--------------------------------------------------------------------------------
/img/membership-request.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/dotnet-foundation/wg-membership/HEAD/img/membership-request.png
--------------------------------------------------------------------------------
/img/website-copy/jessica.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/dotnet-foundation/wg-membership/HEAD/img/website-copy/jessica.jpg
--------------------------------------------------------------------------------
/.vscode/settings.json:
--------------------------------------------------------------------------------
1 | {
2 | "markdownlint.config": {
3 | "MD028": false,
4 | "MD025": {
5 | "front_matter_title": ""
6 | }
7 | }
8 | }
--------------------------------------------------------------------------------
/.github/pull_request_template.md:
--------------------------------------------------------------------------------
1 | ## Description Of Change
2 |
3 | _Short description of the changes made_
4 |
5 | ## Purpose Of Change
6 |
7 | _Why the changes were made_
8 |
9 | ## Related Issue
10 |
--------------------------------------------------------------------------------
/meetings/2020/06-20-update-policy-change.md:
--------------------------------------------------------------------------------
1 | A proposal was voted on to change the wording of the policy, and was approved by all board members last Friday. We've spent the weekend updating the website (and forgot to update a few places- sorry! We are fixing that!)
2 |
--------------------------------------------------------------------------------
/resources/templates/recruiting-board/tweet-dm-template.md:
--------------------------------------------------------------------------------
1 | Hi _Name_
2 |
3 | I'm reaching out as I think you would be a valuable addition to the .NET Foundations Board.
4 |
5 | Part of why I think you would be great for this is _add some personal detail helping the candidate recognize why they would be great_
6 |
7 | Please let me know if this is of interest to you, and I'll send you more information about the role.
--------------------------------------------------------------------------------
/resources/website-copy/README:
--------------------------------------------------------------------------------
1 |
2 | 
3 |
4 |
5 | # Website Copy
6 |
7 | ## Committees Page
8 |
9 | ### Link
10 | [https://dotnetfoundation.org/about/committees](https://dotnetfoundation.org/about/committees)
11 |
12 | ### About
13 |
14 | This page lists all the committees in the .NET Foundation with a brief summary and important links.
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Code of Conduct
2 |
3 | We ask that you read and abide to the [Contributor Covenant Code of Conduct](https://dotnetfoundation.org/about/code-of-conduct).
4 |
5 | Any violations will be dealt with in accordance to the actions outlined on that linked page.
6 |
7 | ## Raising violations
8 |
9 | If you experience or witness a Code of Conduct violation in relation to the membership committee meetings or related presence you can raise it in the following ways:
10 |
11 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/membership_request.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Apply to the Membership Committee
3 | about: Join us to help guide the direction of DNF Membership
4 | labels: membership
5 | assignees:
6 | - wordshaker
7 | - nicoleabuhakmeh
8 | ---
9 |
10 | ## Name:
11 |
12 | _Your name_
13 |
14 | ## Handles:
15 |
16 | - GitHub: _GitHub Handle_
17 | - Discord: _Discord Handle_
18 |
19 | ## Interests:
20 |
21 | _What do you think you can contribute to the committee? What are your interest areas?_
22 |
--------------------------------------------------------------------------------
/resources/templates/recruiting-nominating-committee/tweet-dm-template.md:
--------------------------------------------------------------------------------
1 | Hi _Name_
2 |
3 | I'm reaching out as I think you would be a great addition to the .NET Foundation nomination committee. The purpose of the committee is to reach out to people you think should apply for the .NET Foundation board, and to refine the applications down to a list of candidates for the .NET Foundation members to then vote on, based on their submissions.
4 |
5 | If you might be interested, please let me know and I'll give you more details about what this role involves and how to take part.
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/meeting_agenda.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Agenda
3 | about: Agenda for upcoming Membership Committee Meetings
4 | labels: repository
5 | assignees:
6 | - wordshaker
7 | - ovebastiansen
8 | - nicoleabuhakmeh
9 | - codehippie1
10 | - jorgelevy
11 | - 1kevgriff
12 | ---
13 |
14 | The Membership Committee will be having their monthly meeting on DATE at 3pm Eastern.
15 |
16 | Discord link is open to current members of the Membership Committee to meeting: [https://discord.com/events/966483029830824008/1175074291344232479](https://discord.com/events/966483029830824008/1175074291344232479)
17 |
18 |
19 | ## Agenda Items
20 |
21 | 1. Applications
22 |
23 | *
24 | 2.
--------------------------------------------------------------------------------
/meetings/2023/12-05-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # .NET Membership Committee Meeting #
2 | Wednesday, 05 December 2023, 3PM EDT
3 |
4 | ### Meeting Attendees ###
5 |
6 | * Jessica Brentnall, *Chair*
7 | * Ove Bastiansen
8 | * Aneesh Gopalakrishnan
9 | * Nicole Miller
10 | * Madison Hardy, Scribe
11 |
12 | ### Attachment
13 | [Membership Form](https://forms.office.com/pages/responsepage.aspx?id=3G8HFsH8FUqxyjLJolWQDm8F03uiB2VCoiyUmNsltiBUQ0FDWDBFUFVURFRaQUdCUEg4MlExSEQ0OS4u)
14 |
15 | ### Membership Applications
16 | *
17 |
18 | ### .NET Conf
19 | *
20 |
21 | ### DNF Champions
22 | * Jessica has sent an email to the Board members for approval
23 |
24 | ### Committee Admin
25 | *
26 |
27 | **The meeting adjourned at X:XX PM EDT.**
--------------------------------------------------------------------------------
/meetings/template-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # .NET Membership Committee Meeting
2 |
3 | ### DD Month Year Time GMT / Time EST
4 |
5 | ### Meeting Attendees
6 |
7 | * Jessica Brentnall, *Chair*
8 | *
9 | * Madison Hardy, *Scribe*
10 |
11 | ---
12 |
13 | ## Updates on previous meetings actions
14 |
15 | ###
16 |
17 | ---
18 |
19 | ## Agenda
20 |
21 | * Bring up GitHub Projects to check for any agenda items.
22 |
23 | ### **Membership Form Updates**
24 |
25 | *
26 |
27 | ### **Review actions from the previous meeting**
28 |
29 | *
30 |
31 | ### **Agenda item 1**
32 |
33 | *
34 |
35 | ### **Any Other Business**
36 |
37 | *
38 |
39 | ---
40 |
41 | ### The meeting adjourned at __:__PM ET.
42 |
--------------------------------------------------------------------------------
/resources/dnf-champions/champions-proposal.md:
--------------------------------------------------------------------------------
1 | # DNF Champions
2 |
3 | ## Items to agree
4 |
5 | - [ ] Agree name of programme
6 | - [ ] Programme Benefits for .NET Foundation
7 | - [ ] Programme Benefits for members
8 | - [ ] Minimum requirements
9 | - [ ] Process for application
10 | - [ ] Review process
11 | - [ ] Programme Benefits
12 |
13 | ## Name of programme
14 |
15 | -
16 |
17 | ## Programme Benefits for .NET Foundation
18 |
19 | - Encourages enagement in committees
20 | - More structured contributions
21 |
22 | ## Programme Benefits for members
23 |
24 | - PDF Certificate
25 |
26 | ## Minimum requirements
27 |
28 | - Time served on committee?
29 |
30 |
31 | ## Process for application
32 |
33 | -
34 |
35 |
36 | ## Review process
37 |
38 | -
39 |
40 |
--------------------------------------------------------------------------------
/resources/templates/README.md:
--------------------------------------------------------------------------------
1 | # Templates Folder
2 |
3 | This folder contains templates for various communications that may be used by the .NET Foundation Membership Working Group or the Nomination Committee.
4 |
5 | ## Recruiting Nominating Committee
6 |
7 | This folder contains templates for communications when reaching out to potential members for the nomination committee.
8 |
9 | - [Email template](./recruiting-nominating-committee/email-template.md)
10 | - [Twitter DM template](./recruiting-nominating-committee/tweet-dm-template.md)
11 |
12 | ## Recruiting Board Candidates
13 |
14 | This folder contains templates for communications when reaching out to potential members for the .NET Foundation Board.
15 |
16 | - [Email template](./recruiting-board/email-template.md)
17 | - [Twitter DM template](./recruiting-board/tweet-dm-template.md)
--------------------------------------------------------------------------------
/resources/website-copy/committees-2022.md:
--------------------------------------------------------------------------------
1 |
2 | # [Membership](https://github.com/dotnet-foundation/wg-membership#readme)
3 |
4 | The committee is responsible for:
5 | * evaluating new member applications
6 | * discussing membership criteria
7 | * improving the membership value and offering
8 | * discussing how to build a great community and make membership appealing to more groups
9 | * managing the nomination and election process
10 |
11 | Head to the repository for more information about how to join and get involved.
12 |
13 | ## Details
14 |
15 | **Meets:** 1st and 3rd Wednesday of each month at 7:00pm UTC
16 |
17 | **Repository:** https://github.com/dotnet-foundation/wg-membership
18 |
19 |
20 | ## Chairperson(s)
21 |
22 | **Name:** Jessica White
23 |
24 | **Email:** jessica.white@dotnetfoundation.org
25 |
26 |
27 | 
28 |
29 |
--------------------------------------------------------------------------------
/meetings/2021/02-16-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # Meeting minutes: Tuesday Feb 16, 2021
2 |
3 | ## Open Discussion: Membership profiles
4 |
5 | The Membership Committee reviewed the [Membership Profile pull request](https://github.com/dotnet-foundation/wg-membership/pull/14). They discussed creating the following membership profiles, their contributions and why each member profile would want to join the .NET Foundation. The Committee also reviewed groups of interest based on each membership profile.
6 |
7 | - The Event Organizer
8 | - Sharers of Knowledge
9 | - Educators
10 | - The Student
11 | - The Observer
12 |
13 | ## Actions:
14 |
15 | - Bill Wagner to add notes to Membership Committee’s GitHub repository.
16 | - Jessica White to replace the membership profile with participant types in Membership Profile.
17 |
18 | ## Open Discussion: Upcoming board meeting
19 |
20 | The Membership Committee briefly discussed topics to take to the next Board Meeting.
21 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2019 .NET Foundation
4 |
5 | Permission is hereby granted, free of charge, to any person obtaining a copy
6 | of this software and associated documentation files (the "Software"), to deal
7 | in the Software without restriction, including without limitation the rights
8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 | copies of the Software, and to permit persons to whom the Software is
10 | furnished to do so, subject to the following conditions:
11 |
12 | The above copyright notice and this permission notice shall be included in all
13 | copies or substantial portions of the Software.
14 |
15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21 | SOFTWARE.
22 |
--------------------------------------------------------------------------------
/meetings/2023/05-17-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # .NET Membership Committee Meeting
2 |
3 | ### 17 May 2023 Time 8PM GMT / 3PM ET
4 |
5 | ### Meeting Attendees
6 |
7 | * Jessica White, *Chair*
8 | *
9 | * Madison Hardy, *Scribe*
10 |
11 | ---
12 |
13 | ## Updates on previous meetings actions
14 |
15 | ### New Members
16 |
17 | * Welcome Jorge
18 |
19 | ### Discord
20 |
21 | * Jessica - Make new channels
22 | * review-my-talk
23 | * requests-for-contribution
24 | * good-first-issue
25 |
26 | * Make and send form to find out current members discord handles
27 | * Needs to have github handle and github handle for us to check
28 | * Jess needs help as shes rubbish with Microsoft forms.
29 |
30 | ### Nomination Updates
31 |
32 | * Those successful making the slate have been informed
33 | * Elections open
34 |
35 | ---
36 |
37 | ## Agenda
38 |
39 | * Bring up GitHub Projects to check for any agenda items.
40 |
41 | ### **Membership Form Updates**
42 |
43 | *
44 |
45 | ### **Review actions from the previous meeting**
46 |
47 | *
48 |
49 | ### **Nomination Updates**
50 |
51 | *
52 |
53 | ### **Any Other Business**
54 |
55 | *
56 |
57 | ---
58 |
59 | ### The meeting adjourned at __:__PM ET.
60 |
--------------------------------------------------------------------------------
/meetings/2022/04-27-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # .NET Membership Committee Meeting #
2 |
3 | Wednesday, 27 April 2022, 3PM ET
4 |
5 | **Meeting Attendees**
6 |
7 | ---
8 | * Bill Wagner _Chair_
9 | * Ove Bastiansen
10 | * Aneesh Ambikavally
11 | * Calvin Allen
12 | * Joe Guadagno
13 | * Jessica White
14 | * Nicole Miller
15 | * Tom Pappas
16 |
17 | ## Agenda ##
18 |
19 | * **Nominating Committee / Board Elections**
20 | * The committee discussed the ongoing search for participants in the Nominating committee and the Board elections. Several names were added to each list, and the committee considered outside contacts that could broaden the regional representation of the Foundation.
21 | * **Suggested Revisions for Minutes**
22 | * To suggest edits to the posted meeting minutes, please submit a PR with the revisions in the working group for review. If approved, the PR will be merged and the minutes updated.
23 |
24 | ## Next Steps / Action Items
25 |
26 | * All: Propose members for Nominating Committee and Board of Directors.
27 | * Jessica W: Submit list of candidates to Bill W, as discussed.
28 | * Aneesh A: Submit a proposal within the Membership Committee Repo for improvements, which will be added to future agendas for open discussion.
29 |
30 | **The meeting adjourned at 3:24PM ET**
31 |
--------------------------------------------------------------------------------
/meetings/2022/02-16-meeting-minutes.md.md:
--------------------------------------------------------------------------------
1 | # Meeting minutes: Wednesday February 16, 2022
2 |
3 | ## Meeting Attendees
4 |
5 | - Jessica White
6 | - Joe Guadagno
7 | - Nicole Miller
8 | - Tom Pappas
9 | - Ove Bastiansen
10 | - Nadeem Abutaa
11 |
12 | ## Board updates
13 |
14 | - **Updates from other committees**: The maintainers committee has published the draft of the [project exit process](https://github.com/dotnet-foundation/Home/discussions/68?sort=new#discussioncomment-2168432). We're watching feedback for potential updates. The education committee has held their first re-started meeting.
15 |
16 | ## Membership Portal actions
17 |
18 | We agreed to use the current application form, expanded to provide more prompts to allow for more contributions from a variety of [member profiles](../member-profiles.md).
19 |
20 | ## All-committee meeting
21 |
22 | Jessica is getting feedback from all committees on their main objectives now.
23 |
24 | ## Open Discussion: Membership Value Proposition
25 |
26 | - Review new [issue items](https://github.com/dotnet-foundation/wg-membership/labels/Values%20%2F%20Initiatives). (Didn't get to this discussion in the meeting. Carrying on the discussion online.)
27 |
28 | ## Actions
29 |
30 | - All: Consider nominees for the nominating committee for this year's board elections.
31 |
--------------------------------------------------------------------------------
/meetings/2021/04-20-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # Meeting minutes: Tuesday April 20, 2021
2 |
3 | ## Review action items
4 |
5 | - [X] Bill Wagner to reach out to Beth Massi for the RD & MVP Communities email list for the Nominating Committee.
6 | - [X] Tom Pappas to send the Membership Committee suggested language to use for candidates who were not chosen.
7 |
8 | ## Review and comment on Issues
9 |
10 | ### [#20 - Setting up nomination committee for elections](https://github.com/dotnet-foundation/wg-membership/issues/20)
11 |
12 | Previous committee members have been contacted.
13 |
14 | ### [#21 - Determine the value proposition for membership](https://github.com/dotnet-foundation/wg-membership/issues/21)
15 |
16 | Discussion on benefits from corporate members in the foundation. What benefits would members enjoy that would also benefit the corporate members? We don't have an answer yet, but we'll continue to discuss.
17 |
18 | Proposed other program ideas that could benefit members:
19 |
20 | - Sponsor training or conference attendance.
21 | - Mentoring from other foundation members.
22 | - Promote an "ask the experts" around different projects or areas of the .NET ecosystem.
23 |
24 | Should these different benefits be tied to different [membership participation types](../member-profiles.md)?
25 |
26 | ## Board election timeline and nomination committee
27 |
28 | We set a goal for having the nomination committee set by the next meeting.
29 |
--------------------------------------------------------------------------------
/meetings/2022/03-02-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # Meeting minutes: Wednesday March 2, 2022
2 |
3 | ## Meeting Attendees
4 |
5 | - [Bill Wagner](https://github.com/BillWagner) _Chair_
6 | - [Joe Guadagno](https://github.com/jguadagno)
7 | - [Ova Bastiansen](https://github.com/ovebastiansen)
8 | - [Nicole Miller](https://github.com/nocolebuhakmeh)
9 | - [Calvin Allen](https://github.com/CalvinAllen)
10 | - Tom Pappas
11 |
12 | ## Board updates
13 |
14 | The board will vote to approve the project exit procedure at our next meeting. The board will also vote to approve no-fee membership beginning in the next fiscal year.
15 | Update: The board has approved the process as written.
16 |
17 | ## Membership Portal actions
18 |
19 | ~~Presentation from Virtual on the portal, questions from committee members.~~. This is rescheduled for next meeting.
20 |
21 | ## All-committee meeting
22 |
23 | Jessica could not make this occurence. No update.
24 |
25 | ## Nominating committee
26 |
27 | Consider names for the next nominating committee. Consider possible candidates for the board elections.
28 |
29 | ## Open Discussion: Membership Value Proposition
30 |
31 | - Review new [issue items](https://github.com/dotnet-foundation/wg-membership/labels/Values%20%2F%20Initiatives). (Didn't get to this discussion in the meeting. Carrying on the discussion online.)
32 | - Great discussion from Michael Hawker on any number of value proposition ideas: https://github.com/dotnet-foundation/Home/discussions/61#discussioncomment-2085200
33 |
34 | ## Actions
35 |
36 |
--------------------------------------------------------------------------------
/meetings/2022/10-12-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # .NET Membership Committee Meeting
2 |
3 | Wednesday, 12 October 2022, 3PM ET
4 |
5 | ## Meeting Attendees
6 |
7 | * Bill Wagner _Chair_
8 | * Jessica White
9 | * Nicole Miller
10 | * Madison Hardy, Scribe
11 |
12 | ## Agenda
13 |
14 | * **Officer Assignments**
15 | * The election for Board of Directors has closed. As the three outgoing members depart, the Membership and Outreach Committees will need new chairs. The Board will nominate officers at the upcoming Board meeting (October 27, 2022) and will vote via email to confirm the new chairs. Bill and Jessica discussed who of the three incoming Board members might be interested in holding the positions.
16 | * The committee briefly discussed the international representation on the Outreach Committee, noting that it is generally North American-central. Bill added that the fastest growing countries for .NET adoption are India, Brazil, and China which is interesting as no Board member or committee chair represents those communities. Bill and Jessica discussed reaching out to members of the community to gain momentum.
17 | * **VMX transition**
18 | * Bill asked for a status update for the membership portal. Nicole reported that she had asked the VMX representative for access but hadn't received a response. Madison and Eric Schneider will follow up; Nicole will announce the transition in the newsletter when the portal opens.
19 |
20 | ## Next Steps / Action Items
21 |
22 | * Madison to coordinate VMX update with Eric S.
23 | * Nicole to prep newsletter announcement for VMX.
24 |
25 | **The meeting adjourned at 3:09PM ET**
26 |
--------------------------------------------------------------------------------
/resources/templates/recruiting-board/email-template.md:
--------------------------------------------------------------------------------
1 | Hi _Name_
2 |
3 | I'm reaching out as I think you would be a valuable addition to the .NET Foundations Board.
4 |
5 | Part of why I think you would be great for this is _add some personal detail helping the candidate recognize why they would be great_
6 |
7 | Below is some more detail about what is entailed:
8 |
9 | **Time Commitments**
10 | - 1.5 hours per month to attend regular board meetings. Expect another 1 hour per month to review materials from committees to prepare for the meeting.
11 | - 5 hours per month serving on one of the .NET Foundation committees. Board members are expected to work with one of the committees.
12 | - 6 to 4 hours per month on tasks for committees, or working with foundation members.
13 |
14 | **Responsibilities**
15 | - Set goals for the foundation.
16 | - Set strategic direction to achieve those goals.
17 | - Set the yearly budget to ensure the financial wellbeing of the foundation.
18 | - Manages the foundation’s performance against the yearly budget.
19 | - You can learn more by reading the [board responsibilities](../recruiting-board/board-responsibilities.md) document.
20 |
21 | If you are interested, I would be happy to help you through the process of the application. Please let me know and we can arrange between us the best way to go forward.
22 |
23 | You will first need to be a member of the .NET Foundation, if you aren't already.
24 |
25 | https://dotnetfoundation.org/member/become-a-member
26 |
27 | Again, I can help guide you through the application process if you have any questions.
28 |
29 | Looking forward to hearing from you.
--------------------------------------------------------------------------------
/meetings/2023/09-20-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # .NET Membership Committee Meeting #
2 | Wednesday, 20 September 2023, 3PM EDT
3 |
4 | ### Meeting Attendees ###
5 |
6 | * Jessica Brentnall, *Chair*
7 | * Kevin Griffin
8 | * Madison Hardy, Scribe
9 |
10 | ### Attachment
11 | [Membership Form](https://forms.office.com/pages/responsepage.aspx?id=3G8HFsH8FUqxyjLJolWQDm8F03uiB2VCoiyUmNsltiBUQ0FDWDBFUFVURFRaQUdCUEg4MlExSEQ0OS4u)
12 |
13 | ### Membership Applications
14 | * Since the last committee meeting, Jessica and Nicole updated the membership application form to focus on the applicant's anticipated participation in the Foundation, to gauge their interest in getting involved, and understand what membership value they're looking for.
15 | * The committee previously agreed to provide the application in multiple languages and has been working to find a solution. Jessica noted that Microsoft Forms can auto-translate the information on the form, but the group hasn't determined how to translate responses. The group also needs to select which languages to translate the forms into.
16 |
17 | ### DNF Champions
18 | * Development for this acknowledgement initiative is still ongoing. Jessica and Kevin discussed whether it is possible to create badges in GitHub and will do more research offline.
19 |
20 | ### Committee Admin
21 | * Madison will send a poll to committee members to determine whether meetings should continue bi-weekly or change to a monthly series. Jessica noted that the committee's function has changed a bit, and until more work is identified, it's a better use of time to meet once a month and address any urgent or outstanding tasks via email.
22 |
23 | **The meeting adjourned at 3:19 PM EDT.**
--------------------------------------------------------------------------------
/meetings/2021/11-17-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # MEMBERSHIP COMMITTEE MEETING OF .NET FOUNDATION
2 |
3 | **11/17/2021**
4 |
5 | **Meeting Attendees:**
6 |
7 | - Bill Wagner
8 | - Calvin Allen
9 | - Nicole Miller
10 | - Mitchel Sellers
11 | - Ove Bastiansen
12 |
13 | **Virtual Inc Staff Observers:**
14 |
15 | - Nadeem Abutaa
16 | - Tom Pappas
17 |
18 | ## Introduction
19 |
20 | Bill Wagner, the Membership Committee Chair, gave a quick introduction and began going through agenda items.
21 |
22 | ***Open Discussion: Directing Money at time of Membership Sign Up***
23 |
24 | Committee discussed members being given the ability to support different initiatives with membership fee. Tom Pappas mentioned that there may be some administrative and accounting challenges. It could potentially become a popularity contest with regards to which projects could start receiving funding but there was ways to mitigate that.
25 |
26 | Committee members discussed the idea that members could choose a broader topic to direct/donate money to specifically open source or specifically maintainer support, etc. With that in mind, members could be given the option to earmark only a portion of membership dues to a specific goal. Committee may need to work on differentiating between how they may handle corporate members vs individual members.
27 |
28 | Committee also discussed the foundation instituting a pool of funds for different initiatives where members can request funds either ahead of time or pay out of pocket and request reimbursement. The one challenge that can come up is a member paying for something expecting reimbursement and the getting denied.
29 |
30 | ***Open Discussion: All other business to be taken to the board***
31 |
32 | No new items.
33 |
--------------------------------------------------------------------------------
/meetings/2022/05-16-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # .NET Membership Committee Meeting
2 |
3 | Wednesday, 18 May 2022, 3PM ET
4 |
5 | ## Meeting Attendees
6 |
7 | - [Bill Wagner](https://github.com/BillWagner) _Chair_
8 | - [Aneesh Ambikavally](https://github.com/codehippie1)
9 | - [Calvin Allen](https://github.com/CalvinAllen)
10 | - [Joe Guadagno](https://github.com/jguadagno)
11 | - [Jessica White](https://github.com/wordshaker)
12 | * Tom Pappas
13 | * Madison Hardy, Scribe
14 |
15 | ## Agenda
16 |
17 | * **Membership Portal**
18 | * Tom Pappas provided an update regarding membership dues and the membership platform. It is the committee's intent to present the final proposal for membership dues (or lack thereof) at the May Board meeting for review and approval. With that solved, the membership platform can continue building the portal. If the Foundation does not require membership dues, VMX will discount the services.
19 | * **Nominating Committee**
20 | * Members provided a status update on their outreach for the Nominating Committee. At this time, there are three confirmed members. According to the Foundation bylaws, the Nominating Committee must consist of at least three people, but no more than five. The committee intends to present six names to the Board for consideration and therefore must confirm three more participants by next week's Board meeting.
21 | * **Any Other Business**
22 | * The committee discussed the upcoming .NET Virtual Conference. Nicole Miller asked the committee to submit projects to her or through the GitHub repo that could be highlighted at the conference.
23 | * For more information about .NET Day, visit [the .NET Day Discussion Page](https://github.com/dotnet-foundation/wg-outreach/issues/48).
24 |
25 | ## Next Steps / Action Items
26 |
27 | * Members to continue outreach for the Nominating Committee.
28 |
29 | **The meeting adjourned at 3:15PM ET**
30 |
--------------------------------------------------------------------------------
/meetings/2021/01-19-meeting-notes.md:
--------------------------------------------------------------------------------
1 | # Meeting minutes -- January 19, 2021
2 |
3 | c Update Membership Software System
4 |
5 | The Membership Committee discussed the current membership system and Virtual’ s Membership platform. The Committee agreed to move forward with using the VForce platform for individual membership. Bill will work with Claire to create process documentation for the current membership process. The Committee will partner with the Marketing Committee to develop a membership promotion plan.
6 |
7 | **ACTIONS:**
8 |
9 | - Bill Wagner and Claire Novotny to create a process document for the current membership process.
10 | - Bill Wagner will connect with Terracia King to schedule a meeting with the VForce Developers.
11 | - Bill Wagner to send Beth Massi an email discussion about individual membership promotion.
12 |
13 | ## Open Discussion: 2021 Boar of Directors Elections
14 |
15 | The Membership Committee discussed the 2020 Board of Directors election process. Jessica White, a previous Nominating Committee member, shared the challenges the Committee faced with diversity, lack of viable information from nominees, transparency, and nomination criteria. The Membership Committee decided to create onboarding material for Board Members to distribute to nominees prior to the election. They agreed to extend both the nominating and campaign periods in the upcoming election. The Committee also discussed Board Member requirements, clarifying fiduciary responsibilities, expectations, and utilizing a Board Emeritus mailing list to assist with questions.
16 |
17 | **ACTIONS:**
18 |
19 | - Bill Wagner to add the Board Election topic in the Membership Committee’s GitHub to continue the discussion asynchronously.
20 | - Bill Wagner to add the different classifications and levels of membership topic to the next meeting’s agenda.
21 | - Dado to create a prototype or plan to start a parallel membership team in different languages.
22 |
--------------------------------------------------------------------------------
/meetings/2022/01-26-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # Meeting minutes: Wednesday January 5, 2022
2 |
3 | ## Meeting Attendees
4 |
5 | - [Bill Wagner](https://github.com/BillWagner) _Chair_
6 | - Ove Bastiansen
7 | - Nicole Miller
8 | - Jessica White
9 | - Bill Wagner
10 | - Nadeem Abutaa
11 | - Tom Pappas
12 |
13 | ## Board updates
14 |
15 | - **Update on project exit process**: There have been some projects that have expressed interest in leaving the foundation. From a foundation standpoint, we want to ensure that packages are being properly updated/changed when leaving. The Maintainers committee is working on a potential solution.
16 | - **Updates from other committees**: Frank Odoom, Shawn Wildermuth and Bill Wagner will be meeting this Friday to discuss the education committee.
17 |
18 | ## Membership Portal actions
19 |
20 | ## All-committee meeting
21 |
22 | Jessica will reach out to committee chairs to plan actions and a forum (online meeting or asynchronously) for the chairs and other members to work together better.
23 |
24 | ## Open Discussion: Membership Value Proposition
25 |
26 | The committee discussed different ways that the foundation may increase the visibility of projects and increase engagement between members and project maintainers. Perhaps we could have a sort of pull request for members to contribute to different projects. Bill Wagner briefly discussed the idea of the foundation bringing back the TSG in a new form and having that as an advantage of some sponsors. The committee also discussed a mentor/mentee program; this could be the driving force for the Education Committee in terms of running it. This could be a joint venture considering it is a value proposition for members. The Committee also discussed sending a starter pack to each members; this would be in the form of a guide, how to present your project, how to discuss, etc. Tom Pappas added that resume writing, job boards, etc. could be beneficial to our members.
27 |
28 | ## Actions
29 |
30 |
--------------------------------------------------------------------------------
/.github/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 |
2 | 
3 |
4 |
5 | # Contributing to this repository
6 |
7 | [Code of Conduct](CODE_OF_CONDUCT.md)
8 |
9 | [How Can I Contribute?](#how-can-i-contribute)
10 | - [Contributing to this repository](#contributing-to-this-repository)
11 | - [Code of Conduct](#code-of-conduct)
12 | - [How Can I Contribute?](#how-can-i-contribute)
13 | - [Suggesting Ideas To The Membership Committee](#suggesting-ideas-to-the-membership-committee)
14 | - [Suggesting Enhancements To This Repository](#suggesting-enhancements-to-this-repository)
15 | - [Raising Pull Requests](#raising-pull-requests)
16 | - [Licensing](#licensing)
17 |
18 | # Code of Conduct
19 |
20 | Please read and refer to [this file](../CODE_OF_CONDUCT.md) and it's links.
21 |
22 | # How Can I Contribute?
23 |
24 | There are many ways you can help the .NET Foundation Membership Committee:
25 | - Join us
26 | - Send us your suggestions to improve the membership offering
27 | - Contribute to the repository
28 |
29 |
30 | ## Suggesting Ideas To The Membership Committee
31 |
32 | - Head to the `Issues` section of this repository.
33 | - Select the `Idea For Membership Committee` issue template
34 | - Fill in the details and submit
35 |
36 | If you assign one of the members of the committee, we will aim to discuss the idea in an upcoming meeting. Alternatively you can come to a meeting and present it yourself.
37 |
38 | ## Suggesting Enhancements To This Repository
39 |
40 | - Head to the `Issues` section of this repository.
41 | - Select the `Change for Repository` issue template
42 | - Fill in the details and submit
43 |
44 | # Raising Pull Requests
45 |
46 | - Fork the repository
47 | - Open a branch and commit your changes
48 | - Raise a pull request and fill in the information asked for in the description
49 | - The membership committee will automatically be added as reviewers as code owners of this repository
50 |
51 | # Licensing
52 | [Repo license file](./../LICENSE)
--------------------------------------------------------------------------------
/resources/templates/recruiting-nominating-committee/email-template.md:
--------------------------------------------------------------------------------
1 | Hi _Name_
2 |
3 | I'm reaching out as I think you would be a great addition to the .NET Foundation nomination committee. The purpose of the committee is to reach out to people you think should apply for the .NET Foundation board, and to refine the applications down to a list of candidates for the .NET Foundation members to then vote on, based on their submissions.
4 |
5 | Below is some more detail about what is entailed:
6 |
7 | **Time Commitments**
8 | - Meet every other week to discuss outreach progress and a number of submissions.
9 | - Once all the submissions are in, 2 - 3 hours to go through and rate the submissions based on the given criteria.
10 | - The time for outreach is flexible depending on what the individual has the capacity to do.
11 |
12 | **Responsibilities**
13 | - Outreach to others to ask them to consider submitting for a board position and answer any queries about the role of a board member and their commitments.
14 | - Assess diversity split (on all aspects of diversity) and propose what needs doing to encourage a diverse range of submissions for board members.
15 | Share on your networks the opportunity to submit to be a part of the board or become a member of the .NET Foundation.
16 | - Attend meetings.
17 | - Rate submissions based on given criteria.
18 | - Agree on which applications will go through to the final voting stage of the process.
19 | - Help with the copy for communications around how the process was conducted when there are queries after the elections.
20 |
21 | **If you are part of the nomination committee you cannot apply for the .NET Foundation Board.** If you are planning to apply for the board, I would be happy to help you with your application and support you in any way I can.
22 |
23 | You will also need to be a member of the .NET Foundation. If you aren't already, I can help guide you through the application process.
24 |
25 | Please let me know if you are interested or not. Looking forward to hearing from you.
--------------------------------------------------------------------------------
/meetings/2022/03-23-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # Meeting minutes: Wednesday March 23, 2022
2 |
3 | ## Meeting Attendees
4 |
5 | - [Bill Wagner](https://github.com/BillWagner) _Chair_
6 | - [Ova Bastiansen](https://github.com/ovebastiansen)
7 | - [Joe Guadagno](https://github.com/jguadagno)
8 | - [Nicole Miller](https://github.com/nocolebuhakmeh)
9 | - [Jessica White](https://github.com/wordshaker)
10 | - Tom Pappas
11 |
12 | ## Board updates
13 |
14 | - The board expressed concerns about removing the annual membership fee. The concerns weren't over funding, or the amount. Rather, that a free membership would make it easier for fake or bot accounts to be created. Discussion followed later in the meeting.
15 | - The board has approved the off-boarding process for projects that wish to leave the foundation. The [Marten](https://martendb.io/) project will be the first project. After that others that have expressed interest will be managed.
16 |
17 | ## Membership Portal actions
18 |
19 | Presentation from Virtual on the portal, questions from committee members. We worked through the current approval process, making some modifications to notify committee members to approve based on contributions. Approved moving forward.
20 |
21 | ## Nominating committee
22 |
23 | Discussion on potential candidates, and potential board candidates.
24 |
25 | ## Membership fee
26 |
27 | We discussed other ways to protect the foundation against bot accounts for members without using a fee. The concerns with a fee (regardless of cost) is that many communities aren't as likely to have a credit card. Also, because we don't store credit card info, a small fee doesn't prevent a person from creating multiple accounts. It just costs more.
28 |
29 | We're considering using GitHub profiles and validating contributions as a better metric. While someone could create multiple GitHub accounts and submit contributions under multiple identities, that's far less likely.
30 |
31 | ## Actions
32 |
33 | - All: Propose members for the nominating committee at our next meeting.
34 |
--------------------------------------------------------------------------------
/meetings/2021/05-18-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # Meeting agenda: Tuesday May 18, 2021
2 |
3 | ## Review action items
4 |
5 | - [X] Bill to reach out to Beth and Rodney on the sponsor program
6 | - [ ] Bill to propose next fiscal year's membership committee budget.
7 | - [ ] Tom to share information on other groups mentor programs.
8 | - [X] All: Review volunteers for nominating committee.
9 |
10 | ## Finalize the nominating committee
11 |
12 | The Membership Committee discussed the upcoming Nominating Committee. The Committee discussed how to prevent the Board elections from being simply a popularity contest. The following Nominating Committee members were selected.
13 |
14 | - Samdip Basu
15 | - Dave Brock
16 | - Iris Classon (remember member)
17 | - Benjamin Day
18 | - Dhanajay Kumar
19 | - Rabeb Othmani (returning member)
20 | - Irina Scurtu
21 |
22 | ## Actions
23 |
24 | - Bill Wagner to send emails to all selected Nominating Committee members.
25 | - Bill Wagner and Beth Massi will partner to create a Board expectations document for upcoming elections.
26 | - Bill Wagner to connect with Iris Classon and Rebeb Othmani to start connecting with the other Nominating Committee members.
27 | - Bill Wagner to send the Membership Committee’s budget wish list to the Finance team.
28 |
29 | ## Open Discussion on .NET Survey Results
30 |
31 | The Membership Committee reviewed the survey results. The Committee held a discussion on the demographic of the .NET community. The survey proved that the .NET community is overwhelmingly dominating by males and that the top three regions were Europe, North America, and Asia. The Committee discussed better ways to highlight women engineers based on their skillset. The Membership Committee then discussed the Code of Conduct and the lack of awareness that it exists. The Committee agreed to brainstorm ways to improve the gender gaps and encourage new developers to join the .NET community.
32 |
33 | **ACTION**: The Membership Committee members to brainstorm ways to improve the gender gaps in the .NET Community and be prepared to discuss in the next meeting.
34 |
--------------------------------------------------------------------------------
/meetings/2022/02-02-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # Meeting minutes: Wednesday February 2, 2022
2 |
3 | ## Meeting Attendees
4 |
5 | - [Bill Wagner](https://github.com/BillWagner) _Chair_
6 | - Nicole Miller
7 | - Ove Bastiansen
8 | - Jess White
9 | - Nadeem Abutaa
10 | - Tom Pappas
11 |
12 | ## Board updates
13 |
14 | - **Updates from other committees**: Katie Savage and Frank Odoom will co-chair the education committee. They are currently reaching out to existing committee members to get the status of work in progress.
15 |
16 | ## Membership Portal (VMX)
17 |
18 | Tom Pappas gave an update on the new membership portal and briefly talked about financial considerations. He then discussed the need for a membership application and asked for feedback with regard to whether the committee would want a vetting phase for applications.
19 |
20 | The committee then discussed pricing for membership as well as options for changing the pricing model. Instead of the barrier to entry being financial, it would be effort based. For example, must volunteer for a workgroup. The committee then discussed doing away with membership fees altogether, given sponsorship opportunities coming in.
21 |
22 | Bill emphasized the need to enforce the Code of Conduct and make that known as new members join the foundation.
23 |
24 | What do we want as a vetting process?
25 | - Github contributions (projects, issues, discussions, etc)
26 | - run a meetup
27 | - community action
28 | - other activities from the [member profiles](../member-profiles.md).
29 |
30 | ## All-committee meeting
31 |
32 | Update from Jessica: This is starting with an asynchronous discussion among the committees on each committee's goals and projects. From there we will determine what synchronous meeting is best.
33 |
34 | ## Open Discussion: Membership Value Proposition
35 |
36 | Can we take some of the brainstorming ideas from recent meetings and add them to a backlog board?
37 | - update: Several tasks have been created.
38 |
39 | ## Actions
40 |
41 | - Work with Tom and the Executive Committee to make membership be free while maintaining that vetting be done as members apply for membership.
42 |
--------------------------------------------------------------------------------
/meetings/2020/11-17-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | The following are the minutes from the main discussions during meeting. For privacy, I've edited out the emails of attendees. I've edited out general business notes (approval of agenda, minutes, etc) for brevity.
2 |
3 | *Call to action:* This meeting was all discussion of ideas, nothing below was formally proposed. We want your ideas and thoughts.
4 |
5 | ***OPEN DISCUSSION: WHAT BENEFITS WOULD ATTRACT MEMBERS?***
6 |
7 | The Membership Committee discussed which benefits would attract members. The Committee also discussed their own membership experiences and why they decided to join the .NET Foundation. The following ideas were discussed during this discussion.
8 |
9 | - The Foundation should have different membership levels
10 | - The membership levels could be broken into different classifications such as open source contributors and open source project membership. Each classification would receive different benefits.
11 | - The membership levels could be broken into a level for students, a membership level to foster developers, and a level for leaders who are not developers within the Foundation.
12 | - Limit the amount of free memberships allowed to prevent devaluing the membership.
13 | - Increase the difficulty level of becoming a member to increase membership value.
14 | - Reward members for their contributions, participation and/or for completing set goals.
15 | - Limit the ability to vote on decisions for members with a certain level of contributions.
16 | - Ensure the set goals are aligned with the .NET Foundation’s initiatives.
17 | - Move forward with the IAMDotNet program to highlight member accomplishments on the public website.
18 | - Create a mentorship program
19 | - Gamify the membership levels
20 |
21 | ***OPEN DISCUSSION: WHAT SHOULD BE REQUIREMENTS TO BECOME A MEMBER***
22 |
23 | The Membership Committee discussed which requirements should be implemented to become a member. The Committee agreed to revisit membership requirements after the new membership categories and levels are determined. The Committee will work to create a survey to better understand what membership categories and levels are needed.
24 |
25 |
--------------------------------------------------------------------------------
/meetings/2022/11-02-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # .NET Membership Committee Meeting
2 |
3 | ### Wednesday, 2 November 2022, 3PM ET / 7PM GMT
4 |
5 | ### Meeting Attendees
6 |
7 | * Jessica White, *Chair*
8 | * Aneesh Ambikavally
9 | * Ove Bastiansen
10 | * Eric Schneider
11 | * Nicole Miller
12 | * Madison Hardy, Scribe
13 |
14 | ## Agenda
15 |
16 | ### Updates on previous meetings actions
17 |
18 | * Madison to coordinate VMX update with Eric S / Nicole to prep newsletter announcement for VMX.
19 | * See VMX Updates in discussion points below.
20 |
21 | ### Discussion points
22 |
23 | * **VMX Update**
24 | * Eric reported that the backend work for the membership portal has finished and the link for members to join is ready to publish on the website. Unfortunately, the MSA for the service was not signed before the previous Executive Director departed. Eric and DNF Chair Javier Lozano are working to resolve.
25 | * The committee discussed ways to promote the DNF membership. Once the portal is live, Nicole will promote access in the DNF newsletter. Jessica mentioned an upcoming mentoring event and the opportunity to partner with the Education Committee to develop mentor/mentee relationships and foster membership growth.
26 |
27 | * **Committee Admin**
28 | * Jessica has been elected Chair of the Membership Committee following the certification of the 2023 Board of Directors election. She gave a brief overview of her first Board meeting, which included updates from each committee, financial reports, and general review of DNF operations.
29 | * The committee agreed to continue communicating initiatives and proposals through the [GitHub repo](https://github.com/dotnet-foundation/wg-membership). Jessica will update the read.me to include her contact information as Chair.
30 |
31 | ### Upcoming Meetups Events
32 |
33 | * Festive Tech Calendar: [https://sessionize.com/festive-tech-calendar-2022/](https://sessionize.com/festive-tech-calendar-2022/)
34 |
35 | ## Next Steps / Action Items
36 |
37 | * **Action Owner: [Jessica White](https://github.com/wordshaker)**
38 | * Update README with dotnetfoundation email details
39 | * Propose update to website copy.
40 | * Organise issues
41 |
42 | ### The meeting adjourned at 3:34PM ET
43 |
--------------------------------------------------------------------------------
/meetings/2022/08-03-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # .NET Membership Committee Meeting #
2 |
3 | Wednesday, 3 August 2022, 3PM ET
4 |
5 | ## Meeting Attendees ###
6 |
7 | * Bill Wagner _Chair_
8 | * Calvin Allen
9 | * Joe Guadagno
10 | * Jessica White
11 | * Aneesh Ambikavally
12 | * Tom Pappas
13 | * Madison Hardy, Scribe
14 |
15 | ## Agenda ##
16 |
17 | * **Nominating Committee**
18 | * Bill provided an update on the Nominating Committee's progress. The group agreed to build a spreadsheet to track members who have run in the past, contact those members, and update the spreadsheet to reflect their interest.
19 | * The spreadsheet will help in the future to track who has served and the term limits for each Board member.
20 | * The Nominating Committee is close to finalizing the slate and there will likely be 7-9 candidates. Those who have expressed interest in running for the Board will likely hear from the Committee within the next week.
21 | * Once the list is finalized, the candidates' names will be publicized, and their campaigns will begin.
22 | * Bill noted that due to a late start and the summer holidays, the Nominating Committee is running a little slow with recruitment. He suggested submitting a PR to update the templates and processes to ensure the process starts earlier moving forward.
23 | * **Membership Portal**
24 | * Tom and Bill discussed the membership portal and reviewed outstanding items to send to Shaina, the VMX representative. Bill confirmed that membership@dotnetfoundation.org should be used as the main contact point; Tom will discuss with Claire and Nicole to confirm whether the email address is active.
25 | * Bill noted that he sent the membership roster to Shaina. Tom added that the information he obtained from Open Collective is too raw to use and that he would like to find a way to cross-check both spreadsheets.
26 | * The membership tier has been deactivated; members will no longer receive renewal notices.
27 |
28 | ## Next Steps / Action Items ##
29 |
30 | * Bill to respond to Shaina regarding the VMX portal / membership email address.
31 | * Bill to submit PR to update the templates and processes for the Nominating Committee.
32 | * Tom to discuss membership email address with Claire, check with Nicole if necessary.
33 |
34 | **The meeting adjourned at 3:12PM ET**
35 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 |
2 | 
3 |
4 |
5 | # The .NET Foundation Membership Committee
6 |
7 | The committee is responsible for evaluating new member applications and discussing membership criteria. [See more information on .NET Foundation Committees here](https://dotnetfoundation.org/community/committees)
8 |
9 | ## Details
10 |
11 | **Chairperson(s):** [Jessica Brentnall](https://github.com/wordshaker)
12 |
13 | **Meets:** 1st Wednesday of each month at 7:00pm UTC
14 |
15 | **Repository:** https://github.com/dotnet-foundation/wg-membership
16 |
17 | ## Governance
18 |
19 | The meeting notes are available [here](meetings).
20 |
21 | This committee seeks to have a diverse set of representatives from various stakeholders. At the same time, we try to keep the committee somewhat small so that we can have productive meetings. But in order to satisfy the desire for open participation from everyone – and in the sake of transparency – we made this repo public, which includes notes and proposals that documents the progress of the committee. If you have any questions, please open a discussion.
22 |
23 | ## Contributing
24 |
25 | Please refer to our [Contributing file](./.github/CONTRIBUTING.md)
26 |
27 | ## Joining And Attending Membership Meetings
28 |
29 | - [Create an issue](https://github.com/dotnet-foundation/wg-membership/issues/new/choose) using the "Membership" issue template
30 | - On seeing this [Jessica White](https://github.com/wordshaker) will accept the issue and close it, then send you the next meetings invite.
31 |
32 |
33 | 
34 |
35 |
36 |
37 | ## Current Membership
38 |
39 | **Chair:** [Jessica Brentnall](https://github.com/wordshaker)
40 |
41 | **Scribe(s)** Madison Hardy, Stacey Ramsey
42 |
43 | **Members**
44 | - [Nicole Miller](https://github.com/nicolebuhakmeh)
45 | - [Ove Bastiansen](https://github.com/ovebastiansen)
46 | - [Aneesh Ambikavally](https://github.com/codehippie1)
47 | - [Jorge Levy](https://github.com/jorgelevy)
48 |
49 | ## Code Of Conduct
50 |
51 | [See the Code of Conduct here](CODE_OF_CONDUCT.md).
52 |
53 | For other queries you aren't happy sharing publicaly you can contact Jessica by email - [Jessica.White@dotnetfoundation.org](mailto:Jessica.White@dotnetfoundation.org)
54 |
--------------------------------------------------------------------------------
/meetings/2021/02-02-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # Membership meeting: February 2, 2021
2 |
3 | ## Open discussion: 2021 board of directors elections
4 |
5 | The Membership Committee discussed the 2020 Board of Directors Election process and ways to better inform nominees of what to expect. The Committee agreed that they would like to have VForce in place before the next election. After the Committee reviewed the 2020 Board Election Schedule and discussed creating a timeline for 2021. They mentioned starting the nominee process in June. The following suggestions were mentioned:
6 |
7 | - Create a video that explains what to expect.
8 | - Create a consolidated webpage for Board Information.
9 | - List the Board Member’s job description on webpage.
10 | - List the Committees and their charter’s on webpage.
11 | - List “How to get involved in each Committee and any criteria.” on webpage.
12 | - List meeting cadences on webpage.
13 |
14 | **ACTIONS:**
15 |
16 | - Bill Wagner to present the public Board webpage to the Board of Directors to approve.
17 | - Bill Wagner to create documentation of the current membership process to start the VForce conversation.
18 | - Tom Pappas will reach out to the VForce Developers for the status of the Corporate Membership.
19 | - Jessica White to create a T-minus list for the Board Elections.
20 |
21 | ## Open discussion: Membership classification and levels
22 |
23 | The Membership Committee discussed the possibility of creating different membership classifications or levels for individual memberships. There was ambiguity around who could be a .NET member in the past. The Committee agreed to develop a webpage that would display the different types of membership categories and criteria. They also agreed to provide examples of member contributions to encourage more members to join.
24 |
25 | **ACTION:** Jessica White to create a pull request in the Membership Committee’s GitHub repository for examples of different types of memberships.
26 |
27 | ## Open Discussion: Introducting membership committee in different languages
28 |
29 | The Membership Committee briefly discussed the idea of translating membership communications into different languages. They addressed the risk of fragmenting member communication. The goal would be to use this to be able to leverage community members in more communities. More to come.
30 |
--------------------------------------------------------------------------------
/meetings/2021/05-04-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # Meeting minutes: Tuesday May 4, 2021
2 |
3 | ## Review action items
4 |
5 | None outstanding.
6 |
7 | ## Review and comment on Issues
8 |
9 | ### [#20 - Setting up nomination committee for elections](https://github.com/dotnet-foundation/wg-membership/issues/20)
10 |
11 | We have interested from most of the returning committee members. We've gotten a good response from the RD and MVP community as well. We'll work to finalize offline and begin the nomination process soon.
12 |
13 | ### [#21 - Determine the value proposition for membership](https://github.com/dotnet-foundation/wg-membership/issues/21)
14 |
15 | We focused on three different areas:
16 |
17 | - **Benefits from sponsors**: We've been trying to determine how to structure a program that benefits members, sponsors, and the foundation. We think we've found a way to structure a program that does benefit all participants. Members earn awards through participation in the foundation. Those awards are provided by sponsors. We need to formalize this in our next meetings, along with the marketing and corporate member committees. Our thinking is that different participant profiles would earn awards in different ways. It could be contributing to a .NET Foundation project, creating learning materials, running meetups, or any of the activities outlined in the [participant profiles](../member-profiles.md). We'd structure the program so that more participation activities leads to more benefits. We have more work to do, but we like the concept.
18 | - **Career development**: We are pursuing the idea of a mentorship program. Here again, there is more work to structure the program, but we think it would benefit membership overall.
19 | - **Networking**: The year of pandemic isolation is taking its toll on many. We're exploring some form of in person event, when it is safe to do so.
20 |
21 | ### [#22 - Strengthen and Build Community Culture](https://github.com/dotnet-foundation/wg-membership/issues/22)
22 |
23 | Any discussion was combined with the previous issue.
24 |
25 | **ACTIONS**:
26 |
27 | - [ ] Bill to reach out to Beth and Rodney on the sponsor program
28 | - [ ] Bill to propose next fiscal year's membership committee budget.
29 | - [ ] Tom to share information on other groups mentor programs.
30 | - [ ] All: Review volunteers for nominating committee.
31 |
--------------------------------------------------------------------------------
/meetings/2021/06-01-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # Meeting agenda: Tuesday June 1, 2021
2 |
3 | ## Review action items
4 |
5 | - [ ] Tom to share information on other groups mentor programs. *In progress*
6 | - [X] Bill Wagner to send emails to all selected Nominating Committee members.
7 | - [ ] Bill Wagner and Beth Massi will partner to create a Board expectations document for upcoming elections. *In progress*
8 | - [X] Bill Wagner to connect with Iris Classon and Rebeb Othmani to start connecting with the other Nominating Committee members.
9 | - [ ] Bill Wagner to send the Membership Committee’s budget wish list to the Finance team. *In progress*
10 |
11 | ## Budget discussion
12 |
13 | The Membership Committee discussed their budget wish list. The Committee agreed to ask for a budget of $15,000. The following wish list items were discussed:
14 |
15 | - Define tooling to build a community.
16 | - Create career development opportunities.
17 | - Better member benefits awareness
18 | - Promoting diversity within the organization
19 | - Sponsor members to attend conferences and code camps.
20 | - Offer a childcare credit to members who attend certain events.
21 |
22 | ### [#21 - Determine the value proposition for membership](https://github.com/dotnet-foundation/wg-membership/issues/21)
23 |
24 | The Membership Committee held a discussion on the .NET Foundation’s value proposition. The following ideas were discussed:
25 |
26 | - Create “How to” guides for promoting the Foundation’s projects and encourage participation.
27 | - Promote the new member participation types and their benefits on the website.
28 | - Promote current member contributions from the community.
29 | - Encourage more corporate member contributions to the Foundation to offset Microsoft’s contributions.
30 | - Promote ways members can get involved in the community that can be rewarded.
31 | - Teach members how to find a “good” issue or PR.
32 | - Look into creating a "standard" way for projects to highlight "external" contributors in the last month. dot.net/thanks but for those thanks you's now listed under powertoys/microsoft terminal releases.
33 |
34 | ## New actions:
35 |
36 | - [ ] Bill Wagner to contact Khalid to invite him to join the value proposition discussion.
37 | - [ ] The Membership Committee to brainstorm ways to encourage member contribution and prepare to discuss at the next meeting.
38 |
--------------------------------------------------------------------------------
/meetings/2022/09-07-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # Wednesday, 7 September 2022, 3PM ET
2 |
3 | ## Meeting Attendees ##
4 |
5 | * Bill Wagner _Chair_
6 | * Joe Guadagno
7 | * Jessica White
8 | * Ove Bastiansen
9 | * Nicole Miller
10 | * Tom Pappas
11 | * Madison Hardy, Scribe
12 |
13 | ## Agenda
14 |
15 | * **Nominating Committee**
16 | * Bill provided an update on the Nominating Committee's progress. There is a slate of eight candidates, and seven have submitted their campaign statements. Once all the statements are submitted, Isaac Levin will help merge the PRs and post them to the DNF website. The committee members will coordinate and conduct the interviews in the coming weeks. Ideally, the interviews will be scheduled to be accessible for multiple regions, including the Americas, Africa, and Europe.
17 | * Bill asked Nicole to publicize the election, the campaign statements, and the interviews on the DNF social sites and the newsletter.
18 | * **Membership Portal**
19 | * Tom discussed the VMX portal. The contact email was changed to foundation-membership@dotnetfoundation.org, as the membership@ address goes to the Membership Committee to manage general member topics. The foundation-membership@ address will filter membership applications, and will include members from the VMX team. Nicole will promote the VMX portal in the newsletter.
20 | * Tom discussed officially closing down Open Collective. Nicole noted that DNF has received $3,200 since July 1st that either needs to be refunded or transitioned to a sponsorship donation. She has responded to a few members who have asked about the dues and will send a list to Tom of all the members who have paid dues.
21 | * **Website update**
22 | * Bill reminded the group that DNF is updating the website and each committee is responsible for rewriting their page's content. At the next meeting, the group will discuss proposed updates.
23 | * **[GitHub issues](https://github.com/dotnet-foundation/wg-membership/issues)**
24 | * Jessica noted there are several Issues in the membership repo that should be addressed. Bill will manage.
25 |
26 | ## Next Steps / Action Items
27 |
28 | * Nicole to publicize the Board election.
29 | * Nicole to publicize the new membership portal in the newsletter.
30 | * Nicole to send Tom the list of members who paid dues.
31 | * Bill to manage the repo Issues.
32 |
33 | **The meeting adjourned at 3:18PM ET**
34 |
--------------------------------------------------------------------------------
/meetings/2021/07-06-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # Meeting agenda: Tuesday June 15, 2021
2 |
3 | ## Review action items
4 |
5 | - [ ] Tom to share information on other groups mentor programs. *In progress*
6 | - [ ] Bill Wagner and Beth Massi will partner to create a Board expectations document for upcoming elections. *In progress*
7 | - [ ] Bill Wagner to send the Membership Committee’s budget wish list to the Finance team. *In progress*
8 | - [ ] Bill Wagner to contact Khalid to invite him to join the value proposition discussion.
9 | - [ ] The Membership Committee to brainstorm ways to encourage member contribution and prepare to discuss at the next meeting.
10 |
11 | ## Meeting schedule
12 |
13 | Khalid now has a conflict on Tuesday mornings (eastern time). Does a move to Wednesday work?
14 |
15 | ## Nominating committee update
16 |
17 | I'll share any updates from the board nominating committee.
18 |
19 | ## Budget discussion
20 |
21 | The Membership Committee discussed their budget wish list. The Committee agreed to ask for a budget of $15,000. The following wish list items were discussed:
22 |
23 | - Define tooling to build a community.
24 | - Create career development opportunities.
25 | - Better member benefits awareness
26 | - Promoting diversity within the organization
27 | - Sponsor members to attend conferences and code camps.
28 | - Offer a childcare credit to members who attend certain events.
29 |
30 | I proposed more, because the committee is also responsible for a few more expenses:
31 |
32 | - The VForce managment system (Which can handle some of the items above)
33 | - The .NET Foundation Meetup Pro subscription.
34 |
35 | ### [#21 - Determine the value proposition for membership](https://github.com/dotnet-foundation/wg-membership/issues/21)
36 |
37 | The Membership Committee held a discussion on the .NET Foundation’s value proposition. The following ideas were discussed:
38 |
39 | - Create “How to” guides for promoting the Foundation’s projects and encourage participation.
40 | - Promote the new member participation types and their benefits on the website.
41 | - Promote current member contributions from the community.
42 | - Encourage more corporate member contributions to the Foundation to offset Microsoft’s contributions.
43 | - Promote ways members can get involved in the community that can be rewarded.
44 | - Teach members how to find a “good” issue or PR.
45 |
--------------------------------------------------------------------------------
/meetings/2021/03-16-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # Meeting minutes: Tuesday March 16, 2021
2 |
3 | ## Review action items
4 |
5 | - [X] Bill Wagner to connect with the Marketing Committee to add the Membership Profile on the website.
6 | - [X] Bill Wagner to add a note to the pull request stating that the project types are not mutually exclusive.
7 | - [X] Bill Wagner to add a not to the pull request that we can leverage the profiles to encourage future participation.
8 | - [ ] Bill Wagner to reach out to Beth Massi for the RD & MVP Communities email list for the Nominating Committee. *In progress*
9 | - [ ] Tom Pappas to send the Membership Committee suggested language to use for candidates who were not chosen. *In progress*
10 |
11 | ## Task board review: quarter progress, prepare for next quarter
12 |
13 | The Membership Committee reviewed their [Task Board in GitHub](https://github.com/dotnet-foundation/wg-membership/projects/1). The following items were discussed:
14 |
15 | - Update Membership Software System: *In Progress*
16 | - How do we run the next and future elections: *In Progress*
17 | - Build the Membership Framework: *Completed*
18 | - Survey different Member’s needs: *Completed*
19 |
20 | Open issues created for consideration in the 2nd quarter:
21 |
22 | - [#20](https://github.com/dotnet-foundation/wg-membership/issues/20)
23 | - [#21](https://github.com/dotnet-foundation/wg-membership/issues/21)
24 | - [#22](https://github.com/dotnet-foundation/wg-membership/issues/22)
25 |
26 | Other goals that are not currently captured in issues are:
27 |
28 | - Run the Board Election
29 | - Work together to process members through the Membership Spreadsheet.
30 | - Clarify and promote the .NET Foundation’s value proposition.
31 | - Address the .NET Foundation’s lack of community for members.
32 |
33 | ## Finalize board election timeline
34 |
35 | The Membership Committee reviewed the [proposed nomination schedule](https://github.com/dotnet-foundation/wg-membership/pull/18). The Committee agreed not to enforce term limits for the Nominating Committee members. They also decided to require at least three new members to join the Nominating Committee each Board Election year. The Membership Committee discussed creating a formal Board election policy by the next scheduled meeting.
36 |
37 | **ACTIONS**:
38 |
39 | - Jessica White to send the Membership Committee a list of the previous Nominating Committee members.
--------------------------------------------------------------------------------
/meetings/2021/03-02-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # Meeting minutes: Tuesday March 2, 2021
2 |
3 | ## Chair report: News from February board meeting
4 |
5 | The Membership Committee discussed the outcomes of the February Board Meeting. There have been various discussions around project copyrights and updating the Foundation’s project documentation. Due to this, all project onboarding was stopped until further notice. Claire shared an update with the Committee that the project onboarding process will commence. All Committee members were encouraged to take the survey and share with others. The .NET survey will close in two weeks.
6 |
7 | ## Create proposal: Membership participation types
8 |
9 | Complete review of [Membership participation types pull request](https://github.com/dotnet-foundation/wg-membership/pull/14) and approve current implementation.
10 |
11 | The Membership Committee discussed the Participation Type discussion in GitHub. The Committee approved the participation types suggested.
12 |
13 | **Actions**:
14 |
15 | - Bill Wagner to connect with the Marketing Committee to add the Membership participation types on the website.
16 | - Bill Wagner to add a note to the pull request stating that the project types are not mutually exclusive.
17 | - Bill Wagner to add a note to the pull request that we can leverage the participation types to encourage future participation.
18 |
19 | ## Upcoming board election: Develop schedule
20 |
21 | The Membership Committee reviewed the proposed nomination schedule. The Committee also reviewed the Foundation’s Election Policy document. The Committee held a discussion on how the Nomination Committee will handle Board Members running for re-election. They discussed rather they will be automatically added to the election slate or if they will need to be nominated by the Nomination Committee. They also discussed the need for transparency around the election process.
22 |
23 | **Actions**:
24 |
25 | - Bill Wagner to reach out to Beth Massi for the RD & MVP Communities email list for the Nominating Committee.
26 | - Tom Pappas to send the Membership Committee suggested language to use for candidates who were not chosen.
27 | - Jessica White will write the timeline for the workflow from forming the nominating commmittee through running the election.
28 |
29 | ## Task board review: quarter progress, prepare for next quarter
30 |
31 | Due to timing, the agenda will be discussed during the next meeting.
32 |
--------------------------------------------------------------------------------
/meetings/2021/11-03-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # Meeting minutes: Wednesday November 3, 2021
2 |
3 | ## Meeting Attendees
4 |
5 | - Bill Wagner
6 | - Calvin Allen
7 | - Nicole Miller
8 |
9 | **Virtual Inc Staff Observers:**
10 |
11 | - Nadeem Abutaa
12 | - Tom Pappas
13 |
14 | ## Introduction
15 |
16 | ## Review Action Items
17 |
18 | - *Bill Wagner* to discuss keeping committees apprised on board meetings at next board meeting. For example, what would you like to bring up to the board, here is what you missed at the board meeting, etc. *Still pending*
19 | - *Bill Wagner*: Propose to the board quarterly "All-committee meetings" to brainstorm initiatives that span multiple committees. *Still pending*
20 | - *To all committee chairs*: Document the charter of each committee on the website. Point to where ongoing committee updates are published (typically a GitHub repo). *In progress.*
21 | - *Nicole*: Add contact email addresses for project leaders, .NET Foundation individual and corporate members, and general information. *in progress*
22 | - *Membership committee*: Post [Membership profiles](https://github.com/dotnet-foundation/wg-membership/blob/main/member-profiles.md) on the main website. *Not started*.
23 |
24 | ## Issue template to join
25 |
26 | The new maintainers committee is finding that an issue template to join the committee is encouraging participation. The membership committee will try that out as it seemed to be successful. *Completed*
27 |
28 | The maintainers committee put out a template to attract new members and effectively increase participation.
29 |
30 | ## Open Discussion: VMX Membership Portal
31 |
32 | Bill Wagner and committee discussed getting the membership up and running and discussed logistics with regard to who receives applications, requirements to join, etc.
33 |
34 | ## Action Items:
35 |
36 | - Nadeem to work with Nicole to create a central .Net Membership Calendar with all of the committee meetings.
37 | - Tom Pappas to touch base with VMX team at virtual to get the process started with regard to conversion.
38 | - Bill Wagner to give membership committee write access for GitHub Template. *Done*
39 | - Nicole to include a call for membership profiles on Newsletter.
40 |
41 | ## Build project board for November, December
42 |
43 | Let's return to the process of using a quarterly project board to set tasks and goals for ourselves.
44 |
45 | Some brainstorming ideas:
46 |
47 | - Regular online meetings hosted by board / committee.
48 |
--------------------------------------------------------------------------------
/meetings/2023/02-15-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # .NET Membership Committee Meeting
2 |
3 | ### Wednesday, 15 Feburary 2023, 3PM ET
4 |
5 | ### Meeting Attendees
6 |
7 | * Jessica White, *Chair*
8 | * Aneesh Ambikavally
9 | * Ove Bastiansen
10 | * Nicole Miller
11 | * Stacey Ramsey, Scribe
12 |
13 | ### Updates on previous meetings actions
14 |
15 | **Nicole to draft form for application to be a member**
16 |
17 | * **ACTION** : Any questions we want to add by next meeting?
18 | * **ACTION** : Find the VMX onboarding questions
19 |
20 | **Jessica to submit webpage edits for review.**
21 |
22 | * Add member participation types
23 | * Issue raised https://github.com/dotnet-foundation/wg-membership/issues/101 ✓
24 | * Page created https://dotnetfoundation.org/membership/participation-types ✓
25 |
26 | * Update apply for membership page
27 | * Issue raised: https://github.com/dotnet-foundation/wg-membership/issues/100 ✓
28 | * Copy updated: https://dotnetfoundation.org/membership/become-a-member ✓
29 | * **ACTION** Need to agree on new form and add link to webpage
30 |
31 | **Aneesh/Jessica to ask Outreach about process for updating the Speakers Page**
32 |
33 | * Raise issue in the Marketing Committees GitHub.
34 | * Raise to add information for how to edit your details
35 |
36 | **Jessica to ask about archiving the old GitHub repo for the .NET Foundation Website**
37 |
38 | * Issue Raised https://github.com/dotnet-foundation/wg-membership/issues/97 ✓
39 | * Updates being done by Joe ✓
40 | * Repository has been archived 13 Feb ✓
41 |
42 | **Aneesh to ask about who can be set up as Discord Admins**
43 |
44 | * Do you want Nicole or I to reach out to Jon?
45 | * **ACTION** : Jess to message Jon about creating Admins
46 |
47 | **Nicole to look into 'Welcome' email**
48 |
49 | * Nicole has a template she is working on.
50 |
51 | ## Agenda
52 |
53 | Bring up GitHub Projects to check for any agenda items.
54 |
55 | ### **Review actions from the previous meeting**
56 |
57 | - ✓
58 |
59 | ### **Review membership submissions**
60 |
61 | - ✓
62 |
63 | ### **Membership Form Updates**
64 |
65 | - Agreed changes to add participation types and evidence.
66 |
67 | ### **Frequency of meetings**
68 |
69 | - Every two weeks is good at the moment.
70 |
71 | ### Sitefinity metrics
72 |
73 | * **ACTION** : Find out if we can get metrics on page hits, interactions etc.
74 |
75 | ---
76 |
77 | ### The meeting adjourned at 3:39PM ET
78 |
--------------------------------------------------------------------------------
/meetings/2023/01-04-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # .NET Membership Committee Meeting
2 |
3 | ### 04 January 2023, 3PM ET / 7PM GMT
4 | ### Meeting Attendees
5 |
6 | * Jessica White, *Chair*
7 | * Aneesh Ambikavally
8 | * Ove Bastiansen
9 | * Nicole Miller
10 | * Madison Hardy, Scribe
11 |
12 | ### Updates on previous meetings actions
13 |
14 | * Jessica to merge [Membership Committee Charter](https://github.com/dotnet-foundation/wg-membership/pull/89/files) ✓
15 |
16 | * Jessica to clear up GitHub Teams for Committee ✓
17 |
18 | ### Discussion points
19 |
20 | * 2023 Goals
21 | * The committee discussed goals and how to improve membership for the DNF community. They discussed organizing member benefits and stating a clear value offering, building a package that entices people. Jessica suggested CV/resume support or speaker support, and Nicole noted that she hopes to see partnership amongst the DNF committees to accomplish some of these overlapping initiatives.
22 |
23 | * [Nomination Committee](https://github.com/dotnet-foundation/wg-membership/issues/81)
24 | * The committee reviewed the proposed changes to the Nomination Committee; there was no opposition. The proposal remains under review.
25 |
26 | * [Membership Committee Charter](https://github.com/dotnet-foundation/wg-membership/pull/89/files)
27 | * Jessica provided an update: the charter was published, and the member audit was completed.
28 |
29 | * VMX Portal
30 | * The Executive Committee is re-reviewing the proposal from VMX and determining a cost/benefit. As the tool was introduced under different leadership, the EC wants to be sure the portal meets the current needs of the Foundation.
31 |
32 | * December Board Meeting
33 | * Jessica gave a brief recap from the December Board Meeting. The LastPass breach was discussed, and the Foundation is reviewing the costs for itself and member projects to move to a new service. A project was approved to join the Foundation. The Board is prioritizing sponsorship efforts as revenue has decreased after discontinuing membership dues. The Marketing Committee asked for content for the new website, and Margot Rodger was announced as the DNF Account Manager.
34 |
35 | * [DNF Summit](https://github.com/dotnet-foundation/wg-outreach/discussions/73#discussion-4525129)
36 | * Nicole reported that the presenters for the summit met to review the run of show. She continues to work on the backend code with Aneesh and will coordinate with marketing to promote the event in the coming weeks.
37 |
38 | ### Upcoming Meetups Events
39 |
40 | * DNF Summit
41 |
42 | ### The meeting adjourned at 3:39PM ET
43 |
--------------------------------------------------------------------------------
/meetings/2020/06-17-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | Sorry for posting a few days late, things have en very hectic!
2 |
3 | I will be posting meeting notes here after meetings and significant discussions.
4 |
5 | From last Wednesday, June 17th:
6 |
7 | The nominating committee wants to be transparent about their process and discussions, and therefore we will be posting updates from our meetings.
8 |
9 | The nominating committee has had a first introductory meeting and discussed what is going to happen the next few weeks. All the committee members attended.
10 |
11 | In short, the following was discussed:
12 |
13 | The Director Candidate Expectations in the Election Policy do not align with the nomination form questions and might deter candidates from applying. Additionally, the criteria might result in a non-diverse board that is not representative of the .NET community. The committee suggests changing the wording to reflect the expectations. This is not to suggest that there are no requirements, but rather that a candidate can be strong contributor in different areas, be that OSS, organizational, community, etc.
14 |
15 | A second concern was raised, and that was that a candidate must be a member which comes with a fee that is currently set at 100USD. Two problems were pointed out. Electronic payment might not be possible for all candidates , and the fee is a set amount and doesn’t take into account the currency of the candidates country or BNP etc. Although an applicant can request to have the fee waived, the website states it is for those that are students or experience financial hardship, which might not apply to candidates that cannot pay for other reasons. The ongoing pandemic and the economic consequences add to this.
16 |
17 | The concerns will be discussed in the next DNF meeting, and updates/result will be posted here.
18 | Diversity was discussed further, and the members agreed that they want to actively encourage diversity while maintaining **the same criteria and expectations.**
19 |
20 | The committee also discussed how to reach out to people (personally), tools that can be used to anonymously rank candidates on a set of common criteria, and if a committee member can opt to not rank on a criteria if information is missing (yes).
21 |
22 | A second meeting has been scheduled for next week and until then the members will actively reach out to people, while keeping an eye on the number of responses from the nomination form. Once the nomination period (ends on 26th of June) is over the committee will go through the candidates individually, before having a meeting to discuss the result.
23 |
24 | Side note:
25 | The nominating committee
26 |
--------------------------------------------------------------------------------
/meetings/2022/01-05-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # Meeting minutes: Wednesday January 5, 2022
2 |
3 | ## Meeting Attendees
4 |
5 | - [Bill Wagner](https://github.com/BillWagner) _Chair_
6 | - Nicole Miller
7 | - Ove Bastiansen
8 | - Joe Guadagno
9 | - Jess White
10 | - Calvin Allen
11 |
12 | Virtual Inc Staff Observers:
13 |
14 | - Nadeem Abutaa
15 | - Tom Pappas
16 |
17 | ## Open Discussion: Membership Portal
18 |
19 | Tom Pappas discussed the idea that we can repurpose the membership portal originally implemented for the corporate membership portal for individual members. While the corporate membership and sponsorship programs are being redefined, we can revamp it for individual members.
20 |
21 | ## Open Discussion: Membership Value Proposition
22 |
23 | Bill Wagner opened the floor to committee members to discuss different value propositions for members. What can we prioritize for 2022 and how can we bring together the committees for membership? The committee discussed first outlining the priorities of the foundation for the year and evaluate the charters of committee accordingly as opposed to evaluating the committees first. Ultimately, it may be wise to have an overreaching goal and then have the committees that each have their charges reach that overreaching goal.
24 |
25 | ## Open Discussion: Goals for 2022
26 |
27 | Two goals came up, to increase the reach of .Net and to increase the number of contributions to the .Net open source ecosystem. With regard to .Net, it would be good to try and push for a level of diversity. This is something we can discuss at least, from a foundation point of view.
28 |
29 | As a brainstorming exercise, we discussed some possible actions from the membership committee's view. All of these are at the ideas stage
30 |
31 | - Could membership work with the project and maintainers committee to link meetup groups and project maintainers? Would members be interested in presentations on member projects? Could that drive contribution or use of projects?
32 | - Could membership work with the corporate sponsors committee to provide value for individual members, meetup groups, and sponsors?
33 |
34 | ## Open Discussion: Building Trust
35 |
36 | The committee discussed that many of the issues that the foundation is still facing and its lack of growth can be traced back to the lack of trust. Part of starting to mitigate that for membership is being more transparent about what committees are doing, driving participation, etc.
37 |
38 | ## Open Discussion: Budget
39 |
40 | Bill Wagner discussed the rearranging of the budget and informed the committee that there may be some funds that are part of the membership committee that are repurposed.
41 |
42 | ## Actions
43 |
44 | - Jess White and Nicole to touch base regarding the newsletter.
45 | - Tom and Bill to develop plan for updated membership portal.
46 |
--------------------------------------------------------------------------------
/meetings/2022/06-01-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # .NET Membership Committee Meeting
2 |
3 | Wednesday, 01 June 2022, 3PM ET
4 |
5 | ## Meeting Attendees
6 |
7 | - [Bill Wagner](https://github.com/BillWagner) _Chair_
8 | - [Ova Bastiansen](https://github.com/ovebastiansen)
9 | - [Calvin Allen](https://github.com/CalvinAllen)
10 | - [Joe Guadagno](https://github.com/jguadagno)
11 | - [Nicole Miller](https://github.com/nicolebuhakmeh)
12 | - [Jessica White](https://github.com/wordshaker)
13 | * Tom Pappas
14 |
15 | ## Board Update
16 |
17 | - **Membership Dues** - Board is voting by email 6 yes’s to do away with individual membership fee starting in new fiscal year. Bill started a markdown file and people can help refine this. Created as a draft PR.
18 | - **Membership Portal** – Tom will work with Shaina on this.
19 | - Many got their membership fees charged this month, so July 1 no fees going forward – and go back a quarter – April 1 through June 30.
20 | - We will ask if the foundation can keep their fees as a donation. We will let them know all of this in the newsletter/website. We have to announce what we plan to do so that everyone is informed early enough. We will state that we will stop charging June 30 and this fiscal year (22-23) there won’t be any membership dues.
21 | - Tom will reach out to Open Collective to let them know what we’re planning to do (shut the membership fees down) and he will find out what needs to be done to issue refunds if people ask. He also needs to talk to them about turning off auto renewals.
22 | - **Corporate sponsorship** – supporting (Iron level) is for smaller groups to make a contribution. We can finalize everything at the next meeting (before the next board meeting) after Tom gets the information from Open Collective.
23 |
24 | ## Nominating Committee
25 |
26 | - Committee is Layla, Stacy, Tanner, Veronika and Bill. Joe and Jessica expressed interest in running for the board. We can reach out to others for the additional seat. The committee names can be publicized. Bill, Frank and possible Shawn would be the third one running.
27 |
28 | ## Swag
29 |
30 | - There is a lot of swag that Nicole needs to get rid of – belts, shoelaces, scrunchies, etc. There were some groups that reached out and asked for them but we would have to pay to ship them, some internationally. She’s had 34 people in 6 user groups reach out that requested the swag. We can also put swag out at events that people are speaking at. Let Nicole know and she can send you some to take with you.
31 |
32 | ## Action Items
33 |
34 | - Marketing Comm: We will be going out to every committee to ask for at least one person to be part of it.
35 | - Tom: Contact Open Collective to find out the process for stopping auto renewals, turning off membership dues, and refunds when requested.
36 |
37 | *The meeting adjourned at 3:25PM EST*
38 |
--------------------------------------------------------------------------------
/meetings/2022/04-06-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # Meeting agenda: Wednesday April 6, 2022
2 |
3 | ## Meeting Attendees
4 |
5 | - [Bill Wagner](https://github.com/BillWagner) _Chair_
6 | - [Ova Bastiansen](https://github.com/ovebastiansen)
7 | - [Aneesh Ambikavally](https://github.com/codehippie1)
8 | - [Calvin Allen](https://github.com/CalvinAllen)
9 | - Tom Pappas
10 | - [Nicole Miller](https://github.com/nicolebuhakmeh)
11 | - Madison Hardy
12 |
13 | ## Board Updates
14 |
15 | - The Board is hoping to activate the Nominating Committee soon, elections at the end of May
16 |
17 | ## Membership Portal
18 |
19 | - Regarding the project timeline, the portal should be live by July 1, 2022 (beginning of the fiscal year). The VMX team continues to work on the demo for the portal for individual membership.
20 |
21 | ## Membership Fee
22 |
23 | - No substantial update from the Board regarding membership fees.
24 | - Discussion from committee:
25 | - There are concerns about charging a fee as the value of the Dollar varies across regions. Membership currently reflects demographics in North America and Western Europe, but there’s a lot of activity in the .NET ecosystem in Brazil, India, and China without representation in leadership.
26 | - Continued conversation (from March 23, 2022) about reviewing membership based on contributions within the community. Considered submitting a proposal to the Board to monitor contributions as the membership metric for a year and re-evaluate the success in 2023.
27 |
28 | ## Membership Value Proposition, Open Discussion
29 |
30 | - The committee discussed focusing on two main themes for benefits:
31 | - Career Advancement: to include a job board from sponsors, mentoring programs, resume review
32 | - Building connection within the .Net community: providing active members invitations to conferences (Open Source .NET Foundation Conference), encouraging meet-ups
33 | - The committee (through/with the Board) plans to create a survey to gain feedback from members about preferred benefits and support. It is important to gain feedback on how to best serve the broad ranging constituencies
34 | - The committee discussed improving the onboarding process as incoming members need better access to resources and community
35 |
36 | ## Other Business
37 |
38 | - Introduction of Aneesh Ambikavally – currently involved with Education, Outreach, and Membership committees. He is eager to volunteer and put his resources and extensive knowledge to use. Welcome, Aneesh!
39 | - The Membership Committee meeting for March 20th is rescheduled for March 27th.
40 |
41 | ## Action Items
42 |
43 | - All: Propose members for Nominating Committee
44 | - Nicole M: Compile a list of survey questions for member benefits for next meeting
45 | - Aneesh A.: Submit a proposal within the Membership Committee GitHub Repo for “bug bounties” to create value such as fixing issues/making corrections within the foundation repos.
46 |
--------------------------------------------------------------------------------
/meetings/2023/04-19-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # .NET Membership Committee Meeting
2 |
3 | ### 19 April 2023 8PM GMT / 3PM ET
4 |
5 | ### Meeting Attendees
6 |
7 | * Jessica White, *Chair*
8 | * Ove Bastiansen
9 | * Nicole Miller
10 | * Madison Hardy, *Scribe*
11 |
12 | ---
13 |
14 | ## Updates on previous meetings actions
15 |
16 | ### Discord
17 | * Nicole to update the membership application to request Discord handles.
18 |
19 | ✓ Jessica to create member role on discord to set up private channels for .NET Foundation members to access
20 |
21 | * Jessica to draft the form allowing members to access the private Discord channel.
22 | * Need to do.
23 |
24 | * Aneesh to update his proposal to include a Discord channel for sponsors.
25 |
26 | * Jessica to contact the Sponsorship Committee chair (Iris) regarding the Discord channels.
27 | * Going to raise this at the Board meeting next week
28 |
29 | ### Board of Directors Nominations
30 | * Nicole to draft the new BoD candidate application form.
31 |
32 | * Javier/Jessica to discuss next steps for the 2023 BoD election.
33 | * * Going to raise this at the Board meeting next week
34 |
35 | ---
36 |
37 | ## Agenda
38 |
39 | Bring up GitHub Projects to check for any agenda items.
40 |
41 | ### **Review actions from the previous meeting**
42 | -
43 |
44 | ### **Membership Form Updates**
45 |
46 | * The committee reviewed new membership applications and assigned newly received applications to committee members. The template email for denied applications is still being drafted.
47 |
48 | * **3/1/23 Action Item:** Nicole to draft template email for denied membership applications.
49 |
50 | ### **Discord:**
51 |
52 | * Jessica created the DNF Member role in Discord, and the committee can start adding channels for the role type. The form to collect social handles from the members has not yet been drafted. Jessica intends to follow up with the Board regarding administrative access.
53 |
54 | ### **Nominating Committee**
55 |
56 | * Nicole drafted the nomination form and has distributed it for review. She suggested adding a platinum sponsor representative to the Nominating Committee, which would add a benefit to the sponsor level and ensure an active participant on the committee. The Executive Committee will discuss the proposal at an upcoming meeting.
57 |
58 | ### **Any Other Business**
59 |
60 | * Jessica noted that the Board of Directors page of the website only includes the Officer’s name, Twitter handle, and headshot. She asked if each of the Officers should draft a short bio to include on the page and will add it to the April Board agenda.
61 |
62 | * Jessica asked whether being listed in the speaker directory is a member perk; Nicole noted that the Outreach Committee would best know and agreed it should be a member benefit.
63 |
64 | ---
65 |
66 | ### The meeting adjourned at 3:25PM ET.
67 |
--------------------------------------------------------------------------------
/resources/timelines/nomination-schedule.md:
--------------------------------------------------------------------------------
1 | # Proposed Nomination Schedule
2 |
3 |
4 |
5 | | Event | Time Taken | What's involved |
6 | | :------------------------------ |:-----------| :---------------|
7 | | Forming nomination committee | 3 weeks | - Approaching potential nomination committee members
- Deciding and confirming who will form the nomination committee |
8 | | Marketing | 2+ months | - Announce the nomination schedule at Build end of May.
- Comms/PR plan (become a member campaign).
- Co-marketing plan with partners & corporate sponsors.
- Create promotion assets and copy. |
9 | | Promotion of board nominations | 2+ weeks | - Raise awareness of the board nominations coming up.
- Share requirements for being eligible for being a board member.
- Share the commitments and responsibilities of being a board member.
- Share how to nominate yourself or someone else for the board.
- Share how and why to become a member of the .NET Foundation. |
10 | | Application Period | 3 - 4 weeks | - Nomination process is marketed.
- People nominate themselves and others for the board positions.
- Nomination committee reaches out to potential candidates to go forward for the board. |
11 | | Nomination committee shortlist | 1 week | - Nomination committee produces shortlist from submissions based on set criteria. |
12 | | Promotion of candidates | 2 weeks | - Shortlist of candidates is shared with the public.
- Promotional activities to share more about the candidates to help combat the "popularity contest". |
13 | | Voting period | 2 weeks | - Members to vote on who they want as the board members. |
14 |
15 |
16 |
17 | ## Lessons from last time
18 |
19 | - We need a clear and universal message for what are the requirements for becoming a board member.
20 | - They need to be a .NET Foundation member.
21 | - They need to identify with one or more of the member participation types (don't have to be OSS contributors).
22 | - How this aligns to the purpose of the .NET Foundation (that the .NET Foundation is not purely for OSS).
23 | - Promotion and outreach with diverse groups could be beneficial. We struggled with representation last year.
24 | - Clarity on what is involved in being a board member may help those who aren't sure about going forward for it.
25 | - A list of members for the nomination committee will help them know who they can reach out to and offer support with their applications.
26 | - Are there alternate channels we can promote through beyond the .NET Foundation media channels? Such as asking members who run events to promote the board nomination process.
27 | - When reaching out to potential members of the nominating committee, be sure to explain that nominating committee members can't stand for election.
28 | - We need to reach out underrepresented geographies and groups for the nominating committee to encourage members of those groups and geographies to run for board seats.
29 |
--------------------------------------------------------------------------------
/meetings/2022/06-15-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # .NET Membership Meeting June 15, 2022
2 |
3 | ## Attendance
4 |
5 | * Aneesh Amnbikavally
6 | * Ove Bastiansen
7 | * Nicole Miller
8 | * Tom Pappas
9 | * Bill Wagner
10 | * Jessica White
11 |
12 | ## Agenda
13 |
14 | ### Swag
15 |
16 | * If there are any user groups that could use swag, let Nicole know and she can send. We will go to on Demand marketing instead of housing – don’t have to keep inventory on hand.
17 |
18 | ### Nominating committee
19 |
20 | * Tanner confirmed his participation in the Nominating Committee.
21 | * People running for the Board are Ove, Jessica, James M, and Joe.
22 | * Shawn Wildermuth is not running in this cycle.
23 | * If you know of anyone that you think would be interested in running, let Bill know.
24 |
25 | ### [Pull Request #58](https://github.com/dotnet-foundation/wg-membership/pull/58)
26 |
27 | * PR that Bill made to update our criteria was shared. The transcription of edits is below:
28 | * We’ve had some educators talk about coming into this realm. Bill will talk to the education committee, plural site authors, academic authors and Microsoft Learn team to start building curriculum.
29 | * The MeetUp one is primarily if it’s your MeetUp. If you try a MeetUp, it needs to be done for at least 6 months before it’s given up.
30 | * A link to the community guidelines needs to be added to the document.
31 | * Bill would like to fold in vetting new applications with the new portal – we’d get pinged when one comes in, and whoever grabs it can do that.
32 | * Links to documents need to be fixed.
33 | * Membership goes through open collective today, but he is having trouble getting in touch with our rep. Membership data is stored there. When we go to VMX, it will be there. Will not require people to get a GitHub account.
34 | * Username must match as a maintainer for open source projects so they would need a GitHub account, but it won’t be required on the form. That should be a question on the form so that it can be added by the person.
35 | * You can have more than 1 role, so you should be able to add these from a drop-down.
36 | * The form will be in the VMX portal.
37 |
38 | ## Action Items
39 |
40 | * Bill will bring up the vote to stop membership fees July 1 at the board meeting next week because he hasn’t heard from anyone except Frank.
41 | * Tom will sunset the membership portal but someone signed up so he will reach out and see if they want to move that money over to be an iron sponsor.
42 | * Jessica will work on the templates to reach out to potential board candidates. She will put it in one repository with the others.
43 | * Jessica will give Bill contact info for someone from the Pi organization.
44 | * Bill will update it based on everyone’s comments and get it to the Board for approval.
45 | * Bill to reach out to Outreach Committee to ask them to get testimony from people stating why they are a Foundation member.
46 | * Bill will reach out to his contacts in the UK to connect Aneesh’s contact who needs a job. He’s new to the UK.
47 |
--------------------------------------------------------------------------------
/meetings/2021/10-20-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # Meeting minutes: Wednesday October 20, 2021
2 |
3 | ## Meeting Attendees:
4 |
5 | - Joe Guadagno
6 | - Bill Wagner
7 | - Jessica White
8 | - Nicole Miller
9 | - Ove Bastiansen
10 | - Mitchel Sellers
11 |
12 | ## Introduction
13 |
14 | Bill Wagner, the Membership Committee Chair, gave a quick introduction and spoke about the Membership Committee charter
15 |
16 | **Open Discussion:** Feedback/Questions About Membership Committee Strategy Going Forward
17 |
18 | Bill Wagner opened for questions and comments about strategic direction of the Membership Committee going forward. Committee members agreed that we can take steps to set clear lines/boundaries on what falls under the Membership Committee charter.
19 |
20 | **Open Discussion**: Corporate Memberships
21 |
22 | Bill Wagner discussed and clarified the previous push towards corporate membership in a sense that, the previous board felt they provided the opportunity for the foundation to grow. This would ultimately lead to better project maintenance and support, permanent staffing, etc. The board will reevaluate that going forward.
23 |
24 | **Open Discussion**: Forum for .Net Foundation Members to Ask Questions, Get Help, Provide Feedback
25 |
26 | Bill Wagner and the committee members in attendance discussed which forum to use when asking .Net members for feedback or even where members can go for help. Ultimately, members need somewhere that they will feel like they are supported. We need to hold ourselves accountable, follow through with action items, follow through on charter, etc. That will increase member trust, engagement, and growth.
27 |
28 | Historically, GitHub issues have not ben addressed as quickly as they should be. However, the recent discussions seem to indicate that GitHub should be the center of open conversations in the future.
29 |
30 | **Open Discussion**: Committee Liaisons
31 |
32 | Committee members discussed the prospect of having “Liaisons” from other committees, citing that the efficient dissemination of information was essential to following through on action items and making sure everyone was on the same page. The idea evolved into a monthly meeting of all committees/all committee liaisons.
33 |
34 | We reaffirmed that the committee's project board was useful, and we rededicate ourselves to using it. We'll suggest it to other committees as a good practice.
35 |
36 | ## Action Items
37 |
38 | - *Bill Wagner* to discuss keeping committees apprise on board meetings at next board meeting. For example, what would you like to bring up to the board, here is what you missed at the board meeting, etc.
39 | - *Bill Wagner*: Propose to the board quarterly "All-committee meetings" to brainstorm initiatives that span multiple committees.
40 | - *To all committee chairs*: Document the charter of each committee on the website. Point to where ongoing committee updates are published (typically a GitHub repo).
41 | - *Nicole*: Add contact email addresses for project leaders, .NET Foundation individual and corporate members, and general information.
42 | - *Membership committee*: Post [Membership profiles]
43 | (https://github.com/dotnet-foundation/wg-membership/blob/main/member-profiles.md) on the main website.
44 |
--------------------------------------------------------------------------------
/meetings/2023/03-05-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # .NET Membership Committee Meeting
2 |
3 | ### 05 March 2023 8PM GMT / 3PM ET
4 |
5 | ### Meeting Attendees
6 |
7 | * Jessica White, *Chair*
8 | * Ove Bastiansen
9 | * Aneesh Gopalakrishnan
10 | * Madison Hardy, *Scribe*
11 |
12 | ---
13 |
14 | ## Updates on previous meetings actions
15 |
16 | ### Board of Directors
17 |
18 | * Jessica brought up the suggested changes to add more information to the website about current board members. Each Board member is going to provide a couple of sentences about themselves and we are going to arrange for new videos to be made and published on the site about each board member
19 |
20 | * Told the other committees about the .NET Foundation Member role in Discord and how we can set up private channels. Outreach are open to doing work on this with us.
21 |
22 | * Nomination Committee is not going to be run by the membership committee this year. Jessica is going to still be heavily involved.
23 |
24 | ### Membership Form Updates
25 |
26 | * Nicole - what to send to denied applications
27 |
28 | ### Discord
29 |
30 | * Jessica needs help doing the form right. For an MVP she's really bad at working with Microsoft products.
31 |
32 | ---
33 |
34 | ## Agenda
35 |
36 | * Bring up GitHub Projects to check for any agenda items.
37 |
38 | ### **Membership Form Updates**
39 |
40 | * There were no new applications to review. The committee discussed a few outstanding applications and determined whether to approve or deny them.
41 |
42 | ### **Review actions from the previous meeting**
43 |
44 | *
45 |
46 | ### **Discord**
47 |
48 | * Jessica noted that she needs to ask Nicole to create the Microsoft form to collect social handles from the Discord users.
49 |
50 | * The committee discussed other member-only channels or benefits to add to the Discord server, such as the call for speakers.
51 | * Aneesh suggested a scanning tool for CVs or a subscription bot to create better resumes.
52 | * Jessica suggested a “review my talk” channel so members can give feedback on a presentation’s relevancy and content.
53 | * Ove suggested adding tags to projects that could notate a project’s need for help, requests for contribution, and general promotion.
54 | * Aneesh suggested bug bounties so members can help resolve any issues within a project. He added that DNF could add a financial incentive or form of recognition for those who participate in the bounties.
55 | * Jessica noted that the committee can coordinate with the Projects and Maintainers Committees to define the need for bug bounties and implement the idea. She added that the Foundation doesn’t necessarily have the budget for incentives and subscriptions but agreed that recognizing different levels of participation could be a good incentive. The committee discussed establishing a badging system that recognizes contribution to DNF projects, participation on DNF committees, and ways to link the badges to other social profiles
56 |
57 | ### Membership Value - Open Discussion
58 |
59 | * Jessica noted that the committee needs to revisit the formal training initiative with the Education Committee. · Aneesh suggested partnering with the Mentoring Club, which is a nonprofit start-up that connects members to experts in the community
60 |
61 | ---
62 |
63 | ### The meeting adjourned at 3:24 PM ET.
64 |
--------------------------------------------------------------------------------
/meetings/2023/01-18-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # .NET Membership Committee Meeting
2 |
3 | ### Wednesday, 18 January 2023, 3PM ET
4 |
5 | ### Meeting Attendees
6 |
7 | * Jessica White, *Chair*
8 | * Ove Bastiansen
9 | * Nicole Miller
10 | * Madison Hardy, Scribe
11 |
12 | ### Updates on previous meetings actions
13 |
14 | ## Agenda
15 |
16 | * 2023 Goals
17 | * The committee continued their discussion on goals and benefits of membership. Nicole presented the following pillars that can be used to develop specific initiatives.
18 | * As a Member, you want more connections and to help develop and foster a healthy community. Opportunities include contributing to member projects, speaking to world-wide user groups and establishing their place in the community.
19 | * As a Project, you want less out of pocket costs and more collaboration opportunities within the community. As a Maintainer of a project, you can be connected with others that also want to contribute to the health of the community.
20 | * As a Sponsor, you want to deepen the connections you have within the community by investing funds back into the growth of sustainability and continuation of a project that they may depend on for their core business. By funding the conservatorship of the projects that the community was built on they are aiding sustainability.
21 | * The committee expressed concerns about how to drive member benefits without a forum to focus the efforts. Without the membership portal, the DNF community is widespread across different social platforms and it is difficult to reach everyone. Jessica noted that hopefully the committee's new mission statement will start the needed momentum.
22 |
23 | * VMX Portal
24 | * There is no substantial update regarding the membership portal. The committee reinforced the need to focus attention on one forum, and if approved, VMX should fill the gap.
25 |
26 | * [DNF Summit](https://www.dnfsummit.org/)
27 | * The DNF Summit was successfully held on January 17, 2023. Initial feedback is quite positive, and the session is available to watch on the [DNF Youtube page](https://www.youtube.com/embed/LHCi6i3P0xA).
28 | * The committee discussed the option to restrict content for DNF members, providing an incentive to join the Foundation to access the presentations. Though it is unlikely the event will ever be privatized, an important to ensure only members and member projects are allowed to participate as presenters.
29 |
30 | * Membership - General
31 | * The committee discussed who is responsible for managing membership applications. Jessica has been managing adding members to the committee / committee meeting, but was unsure who was approving membership applications as Bill Wagner did this as the previous chair, but did not train or pass the ownership to Jessica.
32 | * **ACTION:** Nicole to clarify approval process.
33 | * Ove noted that the [Membership page](https://dotnetfoundation.org/membership/become-a-member) of the DNF site instructs individuals to contact DNF via email to become a member and displays the membership application form rather low on the page. He suggested editing the page to move the membership form higher and change the language to clearly detail how to apply rather than defaulting to contacting DNF.
34 |
35 | * Website Content
36 | * The DNF website launched it's update in late 2022 and committees are responsible for updating their pages' content. Jessica has reviewed the language and will submit edits for committee review for the next meeting.
37 | * **ACTION:** Jessica to submit webpage edits for review.
38 |
39 |
40 | ### The meeting adjourned at 3:39PM ET
41 |
--------------------------------------------------------------------------------
/meetings/2021/07-20-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # Meeting minutes: Tuesday July 20, 2021
2 |
3 | ## Review action items
4 |
5 | - [X] Tom to share information on other groups mentor programs.
6 | - We want to be careful to avoid risk seen as endorsing potential mentors, owning responsibility for behavior. How do we vet potential mentors to ensure they are aligned with our goals and community standards. Could be as simple as forums to enable connecting to a formal program where .NET Foundation manages the program. Do we tie to membership levels in different focus areas?
7 | - [ ] The Membership Committee to brainstorm ways to encourage member contribution and prepare to discuss at the next meeting.
8 |
9 | ## Meeting schedule
10 |
11 | Survey sent. We'll discuss options at the next meeting. Responses missing from some. Waiting for more options. The 4:00 pm times in CEST don't work well for Ove.
12 |
13 | ## Nominating committee update
14 |
15 | - PR merged for timeline / updated committee members.
16 | - Blog post asking for candidates. So far only 3 responses. We need 9, so now focusing on outreach to find potential candidates. Committee members were assigned different geographic regions to recruit candidates.
17 | - Call for amplifying the recruiting post.
18 |
19 | ## CoC and membership discussion
20 |
21 | - We should mirror the policies used by the product team / project team
22 | - We should consider recruiting members to be part of the team.
23 | - We should consider some kind of "scale" for violations.
24 | - Do we have policies in the membership agreement to enable enforcement? Bill to check for next meeting.
25 | - Can we enforce on meetup, etc? Bill to investigate with Claire.
26 | - Has (or will) the CoC change policies over time? Historically, any changes have been minor grammar updates, but not changes in policy or rules.
27 |
28 | ## Fiscal year 2022
29 |
30 | The board is having a special meeting to set goals for the fiscal year from July 2021 - July 2022. Let's discuss what the membership committee views as the goals.
31 |
32 | - Drive toward "what is the value proposition for joining the foundation?"
33 | - Items discussed have included:
34 | - Mentoring
35 | - contributions in OSS.
36 | - training for .NET Foundation members.
37 | - discounts for members into conferences.
38 | - travel assistance for conferences (in return for volunteering).
39 | - Recurring theme: Members appreciate discounts as perks. But perks should not be the primary reason to join
40 | - Gamification: leveling up (tiers) could mean more perks.
41 | - Getting more members to participate in committees could provide more perks, and help the organization scale up more.
42 |
43 | Side discussion:
44 |
45 | We had a brief side discussion to determine if the new members are comfortable making contributions to our OSS projects. We believe there's an opportunity to help more members in this area.
46 |
47 | ### [#21 - Determine the value proposition for membership](https://github.com/dotnet-foundation/wg-membership/issues/21)
48 |
49 | The Membership Committee held a discussion on the .NET Foundation’s value proposition. The following ideas were discussed:
50 |
51 | - Mentoring might be an FY23 goal. We need to deliver on the current member value proposition first.
52 | - Education / academy might be a better cohort (20 people) for the first round of mentees.
53 | - How do we get the first group of mentors? How do we ensure diversity of mentors?
54 | - Do mentors self-nominate? Or is "everyone a mentor because we are part of this community?"
55 | First take: Informal, ask community members questions.
56 | - What structure to questions / topics / etc? limits on areas of advice?
57 |
58 | Other topics:
59 |
60 | - We should develop a new *Welcoming letter* for new members. It should include:
61 | - Find organization discussion / minutes
62 | - Find projects
63 | - Join a committee
64 | - Find a meetup / conference
65 | - Specifically .NET Conf!
66 | - Follow us on the socials
67 |
--------------------------------------------------------------------------------
/meetings/2021/04-06-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # Meeting minutes: Tuesday April 6, 2021
2 |
3 | ## Review action items
4 |
5 | - [x] Jessica White to send the Membership Committee a list of the previous Nominating Committee members. *In progress*
6 | - [ ] Bill Wagner to reach out to Beth Massi for the RD & MVP Communities email list for the Nominating Committee. *In progress*
7 | - [ ] Tom Pappas to send the Membership Committee suggested language to use for candidates who were not chosen. *In progress*
8 |
9 | **Note from Jessica**
10 | I added comments to the issues in GitHub as we discussed them. Below is more details about the conversation surrounding those comments.
11 |
12 | ## Review and comment on Issues
13 |
14 | ### [#20 - Setting up nomination committee for elections](https://github.com/dotnet-foundation/wg-membership/issues/20)
15 | - Need to confirm committee by 1st May
16 | - Jessica (@wordshaker) to email previous members to see if they are interested in doing it again.
17 |
18 | ### [#21 - Determine the value proposition for membership](https://github.com/dotnet-foundation/wg-membership/issues/21)
19 | - General agreement that there is lots of transparency from the .NET Foundation but a lack of clarity. We don't know what has been achieved since the creation of the foundation, what the tangible goals of the foundation are. Is it to improve the technical estate of .NET or the people and community aspects of .NET
20 | - It's the committee's view that the people side of the .NET ecosystem should be more of a focus than the tech.
21 | - Reviewed why each of us joined: for networking, for support, to support, to promote opportunities.
22 | - The value of corporate sponsorship was raised. What is the value for corporate sponsors.
23 | - It was suggested the foundation could explore sponsored projects. Corporate sponsorship spots for targeted and achievable projects aligning with the .NET Foundations overarching goal.
24 | - Should we be surveying those who don't renew their memberships as well as those joining?
25 | - @khalidabuhakmeh shared an article from The Register relating to this issue as a comment on the issue.
26 |
27 | ### [#22 - Strengthen and Build Community Culture ](https://github.com/dotnet-foundation/wg-membership/issues/22)
28 |
29 | - Dependant on [#21](https://github.com/dotnet-foundation/wg-membership/issues/21): Need to have a value proposition to build a community around.
30 |
31 | - Would like to hear from the board on how it is going since they have joined and the main impacts they think the .NET Foundation has had? How their original goals are progressing/are they achievable? Maybe using videos. Different format from the emails and posts as all on the call found the long emails difficult to process.
32 |
33 | ## Board election timeline and nomination committee
34 |
35 | The committee would like dates around the timeline for the board elections so we have deadlines to work to.
36 |
37 | The time commitment of nomination committee members would also like to be known for when we are approaching others about taking part.
38 |
39 | DJ has raised his interest in being a member of the nomination committee. It's agreed he would be a good addition.
40 |
41 | ## Extra News
42 |
43 | - The portal for corporate sponsors is still in progress, which once done will enable a membership portal to be released. This will include membership payment management and a forum for discussions.
44 |
45 | **ACTIONS**:
46 |
47 | - Jessica White to email previous Nominating Committee members to ask if they want to do it again.
48 | - [Committee last time: Rabeb Othmani (BiBi), Iris Classon, Julie Lerman, Steve "ardalis" Smith and Jessica White.](https://dotnetfoundation.org/blog/2020/06/15/net-foundation-election-2020-nominations-open)
49 | - Group to identify low hanging fruit / small wins the committee can commit to, to show evidence to progress to external members
50 | - Bill to find out from the board what the .NET Foundations tangible goal is. Something we can link a value proposition to.
51 |
--------------------------------------------------------------------------------
/meetings/2022/12-07-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # .NET Membership Committee Meeting
2 |
3 | ### 07 December 2022 Time 3PM ET / 7PM GMT
4 | ### Meeting Attendees
5 |
6 | * Jessica White, *Chair*
7 | * Aneesh Ambikavally
8 | * Ove Bastiansen
9 | * Nicole Miller
10 | * Madison Hardy, Scribe
11 |
12 | ## Agenda
13 |
14 | ### Updates on previous meetings actions
15 |
16 | * **[Membership Committee Charter](https://github.com/dotnet-foundation/wg-membership/issues/87)**
17 | * Jessica to drafted the Membership Committee Charter and distribute to the committee for review: https://github.com/dotnet-foundation/wg-membership/pull/89 ✓
18 |
19 | * **[GitHub Teams Tidyup](https://github.com/dotnet-foundation/wg-membership/issues/84)**
20 | * Deferred until membership charter is published △
21 | * Nicole to distribute information about this action in the upcoming newsletter and on messaging platforms. △
22 |
23 | * **[Board and Committee responsibilities](https://github.com/dotnet-foundation/wg-membership/issues/75)**
24 | * Tagged Bill. Awaiting response. △
25 |
26 | * **DNF Summit**
27 | * Nicole to connect with Jayme Singleton
28 | * Aneesh to start the "Count-down Clock" for the event once the date is finalized.
29 |
30 | ---
31 |
32 | ### Discussion points
33 |
34 | * [Nomination Committee](https://github.com/dotnet-foundation/wg-membership/issues/81)
35 | * The committee discussed establising a clear timeline for the Nomination Committee. Although it was agreed that the committee should operate throughout the year to maintain momentum into the election cycle, Nicole suggested ramping up their meeting schedule beginning in April/May of each year.
36 | * The committee discussed who should be involved on the committee, including outgoing Board members and active members of the DNF community. There were concerns that the last committee was out of touch as none of the members regularly attend committee meetings. Nicole asked if it would be a conflict of interest for outgoing members to recruit candidates for the Board. During the last election cycle, the Chair advised against promoting one candidate over another, but the Bylaws do not prohibit an outgoing Director from serving on the committee.
37 | * The committee discussed whether the Nomination Committee should be a free-stanidng committee, or a subcommittee managed by either the Executive or Membership committees. It was agreed that Nominations should remian a subcommittee and Membership should maintain responsibility.
38 |
39 | * [Membership Committee Charter](https://github.com/dotnet-foundation/wg-membership/pull/89/files)
40 | * Jessica presented the drafted membership charter for the committee's review. The PR will remain on GitHub for another week to allow for final amendments. Jessica will work with Bill Wagner to finalize outstanding items associated with the PR and present the charter at the next Board meeting.
41 | * Once the charter is official, the membership committee audit can begin. Nicole suggested removing all inactive committee members and adding any interested members back upon request.
42 | * ACTION: Jessica to merge the PR
43 |
44 | * VMX Portal
45 | * Javier and Eric are reviewing the MSA to initiate VMX access, aiming for a portal release in January.
46 |
47 | * [DNF Summit](https://github.com/dotnet-foundation/wg-outreach/discussions/73#discussion-4525129)
48 | * The next DNF Summit is scheduled for January 17, 2023. Shaun Walker is slated to present and particpate as a host. 8 people have volunteered to present, including representatives from Clifford, .VVM, Reactor, Volosoft, and Wix Toolset. The form to sign up as a presenter will close next week, and Nicole will coordinate a meeting series for planners and presenters.
49 | * Aneesh will continue to update the webite, including the SEO keywords, content, and the event countdown clock.
50 |
51 | ---
52 | ### Upcoming Meetups Events
53 | * N/A
54 |
55 | ---
56 | ## Next Steps / Action Items
57 |
58 | * Jessica to merge [Membership Committee Charter](https://github.com/dotnet-foundation/wg-membership/pull/89/files)
59 |
60 | * Jessica to clear up GitHub Teams for Committee
61 |
62 | ### The meeting adjourned at 3:39PM EST
63 |
--------------------------------------------------------------------------------
/resources/member-documentation/membership-criteria.md:
--------------------------------------------------------------------------------
1 | # Membership criteria
2 |
3 | When you apply for membership, we review your application based on the [membership participation types](membership-participation-types.md) defined. We ask for some basic information about you.
4 |
5 | ## Basic information
6 |
7 | First, we validate the personal information:
8 |
9 | - First and Last name are reviewed to eliminate potential 'bots'.
10 | - A valid email address: We only validate that it is a valid email address format. Later, when an invitation is sent, that verifies that it's a real address.
11 | - Optionally, a valid GitHub ID: If you provide a GitHub ID, we validate the profile appears to be human.
12 |
13 | In addition, we ask for contribution activity in one or more of the [Membership participation types](member-participation-types.md). An application need not fill out each section, but may include any relevant contributions in any section. The application will be reviewed in total: breadth across areas and depth in a single area are both considered.
14 |
15 | ## Open Source Maintainer, Open Source Contributor
16 |
17 | See [Open source maintainer](membership-participation-types.md#the-open-source-maintainer) and the [Open source contributor](membership-participation-types.md#the-open-source-contributor).
18 |
19 | We look at the contribution links. All activity must conform to the .NET Foundation [Code of Conduct (CoC)](https://dotnetfoundation.org/about/code-of-conduct). Activities examined include:
20 |
21 | - Pull Requests (PRs) created. We evaluate the participation in the community. Does the PR match the project's guidelines? Does the author engage constructively with reviewers?
22 | - PR review, and helping new contributors. Are comments in line with the spirit of the CoC? Does the reviewer provide necessary assistance?
23 | - Issues created. These should be well-defined issues. We don't evaluate issue quality based on the project maintainer's decision to accept or reject the idea. We do evaluate issues based on the clarity and completeness.
24 | - Discussion forums. Does the person participate in discussions in a constructive manner?
25 |
26 | A person need not participate in all these areas, but should be active in some of them. The GitHub user name must match any contribution links provided. GitHub activity mentioned in the contribution statement should match this ID.
27 |
28 | ## Event organizer
29 |
30 | See [Event organizer participation type](membership-participation-types.md#the-event-organizer).
31 |
32 | We look at the event or user group activities. Examples include:
33 |
34 | - Events listed have a CoC that reflects the .NET Foundation's [community guidelines](https://dotnetfoundation.org/about/code-of-conduct).
35 | - For user groups, a consistent track record of meeting in person or virtually is better. Larger events such as code camps, community conferences and such may have a shorter track record offset by the greater work needed to organize such events.
36 | - If the event is a user group, the meetup is listed with the .NET Foundation.
37 | - Responsibility for tasks related to the meetup or conference.
38 | - Building a community among related groups or conferences. This could be sharing speakers, creating partnered events, or other activities that grow the community.
39 |
40 | ## Educator
41 |
42 | See [Educator participation type](membership-participation-types.md#the-educator).
43 |
44 | We look to the educator's creation and delivery of curriculum in any of the following ways:
45 |
46 | - Teaching. Whether that be bootcamp courses, college or high school level courses in software development where the .NET platform is a signification part of the curriculum.
47 | - Creating .NET based curriculum for any of these area.
48 | - Creating or delivering .NET based curriculum in online platforms such as Pluralsight, LinkedIn Learning, Micrsoft Learn, or others.
49 |
50 | ## Knowledge sharers
51 |
52 | See [Sharer of knowledge participation type](membership-participation-types.md#the-sharer-of-knowledge).
53 |
54 | The content that the applicant creates and/or delivers to spread knowledge. These include, but are not limited to:
55 |
56 | - Books
57 | - Conference talks
58 | - Twitch streams
59 | - Blogs
60 | - Online courseware
61 | - Stack overflow answers
62 |
63 | We'll look for consistency of the work. Formats such as blogs, Twitch streams, StackOverflow answers and conference talks should have a longer, more consistent track record than book authors or online courseware authors.
64 |
65 | ## Students
66 |
67 | See [Student participation type](membership-participation-types.md#the-student).
68 |
69 | Students have had less time to build a resume of participation. For that reason, we look to their involvement opportunities and if they are helping to bring their perspective in any of the other areas. In addition, we look at any involvement in volunteer activities while at school that are within the .NET community.
70 |
--------------------------------------------------------------------------------
/meetings/2023/03-01-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # .NET Membership Committee Meeting
2 |
3 | ### 01 March 2023 8PM GMT / 3PM ET
4 |
5 | ### Meeting Attendees
6 |
7 | * Jessica White, *Chair*
8 | * Aneesh Ambikavally
9 | * Ove Bastiansen
10 | * Nicole Miller
11 | * Madison Hardy, *Scribe*
12 |
13 | ---
14 |
15 | ## Updates on previous meetings actions
16 |
17 | **Nicole to draft form for application to be a member**
18 |
19 | * New form has been published
20 |
21 | **Jessica to submit webpage edits for review.**
22 |
23 | * Changes have been published
24 |
25 | **Jessica to ask Outreach about process for updating the Speakers Page**
26 |
27 | * Has been raised to the Board. Out of our hands now.
28 |
29 | **Aneesh to ask about who can be set up as Discord Admins**
30 |
31 | * Board members now admins
32 |
33 | **Nicole to look into 'Welcome' email**
34 |
35 | * Nicole has a template she is working on.
36 |
37 | ---
38 |
39 | ## Agenda
40 |
41 | Bring up GitHub Projects to check for any agenda items.
42 |
43 | ### **Review actions from the previous meeting**
44 | - ✓
45 |
46 | ### **Membership Form Updates**
47 |
48 | * The new membership form is live, and 14 responses have been received. Nicole expressed concerns as several submissions came in before the form was finalized and will need to be verified. · The committee briefly reviewed the spreadsheet and added columns to notate assignees and status updates. Committee members were assigned applications to review offline and will provide updates at the next meeting.
49 |
50 | * **Approval Criteria:**
51 | * the committee agreed to approve applications if members are able to confirm engagement and general activity of the applicant.
52 |
53 | * **Timeline:**
54 | * Review new applications and assign verification responsibilities during each Membership Committee meeting (every two weeks).
55 |
56 | * Nicole will distribute an updated spreadsheet with newly received applications prior to/during each Memb.Cmt. meeting.
57 |
58 | * **ACTION:** Jessica/Nicole to update the website to indicate the 2-week lead time for approvals.
59 | * Next Steps: Once approved, Nicole will send the “Welcome” email to new members. This will include instructions on how to join the Discord channel, GitHub repos, links to DNF social and professional accounts and DNF policies.
60 |
61 | * **ACTION:** Nicole to update Welcome template with suggested links.
62 |
63 | * **ACTION:** Nicole to draft template email for denied applications.
64 |
65 |
66 | ### **Discord:**
67 |
68 | * Jessica reported that Eric Schneider (DNF ED) is in contact with Jon Galloway and will help support the efforts to update the Discord admins. Once the Membership Committee has proper access, they will be able to better manage participants and include Discord as a value add to members.
69 |
70 | * Aneesh suggested creating a CFP channel on Discord.
71 |
72 | ### **Nominating Committee**
73 |
74 | * Jessica attended the 3/1 Executive Committee (EC) meeting to discuss the structure and timeline of the Nominating Committee. It was agreed to recruit members of the Board to fill committee positions, particularly the outgoing Chair. Jessica also suggested sourcing members from other DNF committees, noting who is most active in the community and understands the needs of the Foundation.
75 |
76 | * Javier Lozano, DNF Board Chair, volunteered to chair the Nom.Cmt. for the upcoming election cycle.
77 |
78 | * Aneesh had previously suggested updating the candidate application form to shift the focus from coding to leadership experience and the EC agreed.
79 |
80 | * **ACTION:** Javier and Jessica to edit the application form.
81 |
82 | * The committee discussed the Board terms to better understand the staggered structure and identify which Board members’ terms are expiring. Aneesh suggested updating the BoD page to include information about the terms (how many terms served, limits, etc).
83 |
84 | ### **Any Other Business**
85 |
86 | * The DNF Code of Conduct policy is specifically directed to Contributors. The committee discussed whether this should be updated to include all DNF membership/activity types.
87 |
88 | * **ACTION:** Jessica to add suggestion as an agenda item for the March Board meeting.
89 |
90 | ---
91 |
92 | ## Action Items
93 |
94 | * Jessica/Nicole to update the website to indicate the 2 week lead time for approvals.
95 |
96 | * Nicole to update Welcome template with suggested links.
97 |
98 | * Nicole to draft template email for denied membership applications.
99 |
100 | * Javier and Jessica to edit the BoD candidate application form.
101 |
102 | * Jessica to add Code of Conduct update as an agenda item for the March Board meeting.
103 |
104 | ---
105 |
106 | ### The meeting adjourned at 3:39PM ET.
107 |
108 |
--------------------------------------------------------------------------------
/resources/commitee-documentation/membership-committee-charter.md:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | # Membership Commitee Charter
6 |
7 |
8 | ## Mission Statement
9 |
10 | To manage and improve the membership offering of the .NET Foundation.
11 |
12 | ## Membership
13 |
14 | The option to take part and be involved in the membership committee is open to all members of the .NET Foundation.
15 |
16 | We ask that you have a GitHub profile set up, as our organisation and tooling is all based in this GitHub repository.
17 |
18 | ### How To Join The Membership Committee
19 |
20 | - [Create an issue](https://github.com/dotnet-foundation/wg-membership/issues/new/choose) using the "Membership" issue template
21 |
22 |
23 | 
24 |
25 |
26 | - On seeing this [Jessica White](https://github.com/wordshaker) will accept the issue and close it, then send you the next meetings invite.
27 | - After attending two meetings, you will be added to the CODEOWNERS of this repository and be added to the committee GitHub Teams.
28 |
29 | ### Expected Level of Contribution
30 |
31 | To remain a member of the committee we ask that you attempt to attend meetings at least once a month. If you are unable to attend at this frequency or have to miss a couple for extenuating circumstances, you will be expected to raise this with the committee. You won't need to provide specifics, it's to let the group know you intend to take part in future.
32 |
33 | If you cannot attend at that frequency, you could also contribute by submitting issues or pull requests to the repository.
34 |
35 | Each committee meeting will have a draft agenda in GitHub available before the meeting. This is how to check when issues you are passionate about are going to be up for discussion and action votes.
36 |
37 | ## Termination of Committee Membership
38 |
39 | On a quarterly basis, the chair, scribe or appointed representative will review levels of contribution from [members of the membership GitHub Teams](https://github.com/orgs/dotnet-foundation/teams/membership/members). If the expected contribution levels have not been met, without you talking to the committee about the reasoning for the decline in your contributions you will be contacted via email. If you have not responded within 30 days of attempted contact, your membership to this team will be revoked.
40 |
41 | After termination, you can re-apply to join the committee if you so wish.
42 |
43 | ## Chairperson
44 |
45 | The Chairperson of the committee is an elected member of the Board of Directors. They will have volunteered to be the chair and spokesperson of the committee.
46 |
47 | The current Chairperson of the membership committee is [Jessica White](mailto:Jessica.White@dotnetfoundation.org)
48 |
49 | ### Decisions and disputes
50 | Decisions are made via vote. If the committee cannot come to agreement on an action, it will be postponed or the chairperson will discuss with other board members to determine which decision would be in the best interests of the foundation.
51 |
52 | ### Feedback to the board
53 | The Chairperson will feedback to the other members of the Board of Directors on a monthly basis. This includes topics that are currently in discussion, actions being taken and measures of success.
54 |
55 | The membership committee will also be informed and updated about board discussions, and their thoughts on these topics are encouraged.
56 |
57 | ## Duties, and Responsibilities
58 |
59 | The committee meets on the 1st and 3rd Wednesday of each month at 7:00pm UTC. This time will be revisited once a year or as the makeup changes and different times work better in different time zones.
60 |
61 | Meetings have an agenda which is shared on GitHub and can be contributed to by any committee member. Each agenda item will have a GitHub Issue assigned which provides more context to the discussion point.
62 |
63 | Minutes of each meeting are written up after each meeting and can be viewed [here](https://github.com/dotnet-foundation/wg-membership/tree/main/meetings).
64 |
65 | ### Responsibilities
66 |
67 | The committee is responsible for:
68 | * evaluating new member applications
69 | * discussing membership criteria
70 | * improving the membership value and offering
71 | * discussing how to build a great community and make membership appealing to more groups
72 | * managing the nomination and election process
73 |
74 | ### Duties
75 |
76 | **Duty of care** :
77 | Exercise reasonable care when making decisions relating to the committee and the .NET Foundation.
78 |
79 | **Duty of loyalty** :
80 | Act in the best interests of the committee and the .NET Foundation
81 |
82 | **Duty of obedience**:
83 | Act in a way that is consistent with the goals of the committee and the .NET Foundation.
84 |
85 | ---
86 |
87 | _Last Reviewed:_
88 |
89 | _Last Approved:_
--------------------------------------------------------------------------------
/meetings/2022/11-16-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # .NET Membership Committee Meeting
2 |
3 | ### Wednesday, 16 November 2022, 3PM ET / 7PM GMT
4 | ### Meeting Attendees
5 |
6 | * Jessica White, Chair
7 | * Aneesh Ambikavally
8 | * Nicole Miller
9 | * Madison Hardy, _Scribe_
10 |
11 | ## Agenda
12 |
13 | ### Updates on previous meetings actions
14 |
15 | * Jessica: Update README with dotnetfoundation email details ✓
16 | * Jessica: Propose update to website copy. [PR 86](https://github.com/dotnet-foundation/wg-membership/pull/86) ✓
17 | * Jessica: Organise issues ✓
18 |
19 | ### Discussion points
20 |
21 | * **[Membership Committee Charter](https://github.com/dotnet-foundation/wg-membership/issues/87)**
22 | * Jessica suggested drafting a charter for the committee, detailing expectations, participation and contribution thresholds, and overall guidance to members. There are currently 58 members in GitHub, though this is not represented in committee meetings. Publishing the charter could allow the committee to restrict access to those who do not participate, disabling their rights to edit PRs and Issues. Using the attendee list from meeting minutes, admins could track participation and remove inactive members as needed.
23 |
24 | * **[GitHub Teams Tidyup](https://github.com/dotnet-foundation/wg-membership/issues/84)**
25 | * The committee agreed to audit the member list in GitHub, establish a minimum threshold of participation, and remove inactive members. This action is not final, and anyone interested in remaining active in the GitHub repo will have the option to sign-up again.
26 |
27 | * **[Nomination Committee Future Structure](https://github.com/dotnet-foundation/wg-membership/issues/81)**
28 | * The committee discussed how the Nominating Committee should be organized and structured moving forward, following feedback from the 2023 elections process. It was suggested that outgoing Board members should participate as they have experience on the Board and could better answer questions from potential candidates regarding roles and responsibilities. The timeline should begin in the spring, allowing more time to operate and conduct outreach as needed.
29 | * Jessica encouraged committee members to submit suggestions in GitHub.
30 |
31 | * **[Board and Committee responsibilities.](https://github.com/dotnet-foundation/wg-membership/issues/75)**
32 | * This is an ongoing project that will likely require coordination with DNF committee chairs and Board members. It will be important to set goals for 2023 and publicize them for greater transparency in the community.
33 |
34 | * VMX Portal
35 | * The DNF Board intends to sign the MSA to initiate VMX access. The committee discussed whether the portal will include a chat function as it could drive membership value if there is a forum to communicate. More information to come.
36 |
37 | * **VMX Portal**
38 | * The DNF Board intends to sign the MSA to initiate VMX access. The committee discussed whether the portal will include a chat function as it could drive membership value if there is a forum to communicate. More information to come.
39 |
40 | * **[Website copy](https://github.com/dotnet-foundation/wg-membership/pull/86)**
41 | * The Marketing Committee continues to lead the website transition. Phase 1 was released November 8th, with more pages and content to be released in the coming months. The Membership committee discussed updates to their content. Members are encouraged to submit suggestions in GitHub.
42 |
43 | * **Holidays with DNF**
44 | * There are currently no DNF events or specific outreach plans for the holiday season, though the committee considered whether this could be beneficial. Members are encouraged to submit suggestions!
45 |
46 | ### Upcoming Meetups Events
47 |
48 | * [DNF Summit](https://github.com/dotnet-foundation/wg-outreach/discussions/73#discussion-4525129)
49 | * The first planning meeting is scheduled for November 17th, and the link to join is available in the discussion thread. Nicole noted that the event needs a host and detailed hosting responsibilities, including introducing speakers and fielding questions from the audience. Jessica suggested contacting Jayme Singleton as she is active within the Virtual User Group and hosts events in the EU. The event is tentatively scheduled for mid-January 2023.
50 | * **ACTION:** Nicole to connect with Jayme Singleton
51 | * **ACTION:** Aneesh to start the "Count-down Clock" for the event once the date is finalized.
52 |
53 | ## Next Steps / Action Items
54 |
55 | **Membership Committee Charter**
56 | * Jessica to draft the Membership Committee Charter and distribute to the committee for review.
57 |
58 | **GitHub Teams Tidyup**
59 | * Nicole to distribute information about this action in the upcoming newsletter and on messaging platforms.
60 |
61 | **Board and Committee responsibilities**
62 | * Jessica to connect with Bill Wagner to resolve.
63 |
64 | **DNF Summit**
65 | * Nicole to connect with Jayme Singleton
66 | * Aneesh to start the "Count-down Clock" for the event once the date is finalized.
67 |
68 | ### The meeting adjourned at 3:27PM EST
69 |
--------------------------------------------------------------------------------
/meetings/2023/10-04-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # .NET Membership Committee Meeting #
2 | Wednesday, 4 October 2023, 3PM EDT
3 |
4 | ### Meeting Attendees ###
5 |
6 | * Jessica Brentnall, *Chair*
7 | * Ove Bastiansen
8 | * Aneesh Gopalakrishnan
9 | * Nicole Miller
10 | * Madison Hardy, Scribe
11 |
12 | ### Attachment
13 | [Membership Form](https://forms.office.com/pages/responsepage.aspx?id=3G8HFsH8FUqxyjLJolWQDm8F03uiB2VCoiyUmNsltiBUQ0FDWDBFUFVURFRaQUdCUEg4MlExSEQ0OS4u)
14 |
15 | ### Membership Applications
16 | * 64 member applications were received throughout September. The group split the batch for review and approvals. Jessica noted that since the application questions were updated, submissions have been easier to review, and it was a much faster approval process.
17 |
18 | ### .NET Conf
19 | * Nicole provided a bit of context about DNF's previous involvement with .NET Conf. When Javier Lozano was on the Board, DNF was very active in the planning because Javier was involved in the programming. This year, DNF has not been asked and is not involved in the planning, but was asked to promote the conference through DNF channels. The Marketing Committee has been working on this through Mailchimp.
20 | * Jessica noted that the group is available to help as needed. She added that the UK MVP community has been very effectively marketing .NET Conf with swag and viewing parties.
21 |
22 | ### DNF Champions
23 | * Jessica drafted a file in GitHub to track the initiative's development. The group discussed the following:
24 | * Program Name
25 | * Aneesh: I like the name "DNF Champions", but maybe we shorten it - DNF Champ? I also think we can make a competition out of this. Create a small survey, publish it on Discord and in the newsletter, get members engaged.
26 | * Jessica: Good idea. Do want to offer a few pre-determined options so we don't end up with something silly. But this is a good way to get engagement.
27 | * Program Benefits for the Foundation
28 | * Jessica will draft a proposal
29 | * Program Benefits for Members
30 | * PDF Certificate
31 | * Aneesh: Something we could do here different than MVPs would be a hand-signed certificate. Joe (or whoever is DNF President) could sign.
32 | * Enamel Pin
33 | * Jessica: Do we have a budget for this?
34 | * Nicole: Yes, if we could get a sponsor, they could target funds for this. We can get pins pretty cheaply through [Wizard Pins](https://https://wizardpins.com/products/soft-enamel-pins?variant=14042600669239&utm_source=google&utm_medium=shopping&utm_term=Pins&utm_content=soft-enamel-pins_s3&nbt=nb%3Aadwords%3Ag%3A10022067833%3A102400061273%3A434604154450&nb_adtype=pla&nb_kwd=&nb_ti=pla-968229587997&nb_mi=125251762&nb_pc=online&nb_pi=soft-enamel-pins_s3&nb_ppi=968229587997&nb_placement=&nb_si=%7Bsourceid%7D&nb_li_ms=&nb_lp_ms=&nb_fii=&nb_ap=&nb_mt=&utm_source=google&utm_medium=paid&utm_campaign=10022067833&utm_content=102400061273&utm_term=&gadid=434604154450&nbt=nb%3Aadwords%3Ag%3A10022067833%3A102400061273%3A434604154450&nb_adtype=pla&nb_kwd=&nb_ti=pla-968229587997&nb_mi=125251762&nb_pc=online&nb_pi=soft-enamel-pins_s3&nb_ppi=968229587997&nb_placement=&nb_si=%7Bsourceid%7D&nb_li_ms=&nb_lp_ms=&nb_fii=&nb_ap=&nb_mt=&gad=1&gclid=Cj0KCQjwmvSoBhDOARIsAK6aV7hye027RXp6vo_Z551JK1DcWkK3joe6vjnjm0K0W2I6-R08Hn-a74YaAjlREALw_wcB)
35 | * Aneesh: We would need a logo, something to put on the pin. Create another competition for members!
36 | * Minimum Requirements
37 | * Time Served on Committees
38 | * Jessica: Should this be 6 months?
39 | * Ove: The committee chair will need to confirm the applicant's activity in the committee.
40 | * Jessica: The chairs will know, this will be straightforward to confirm.
41 | * Jessica: We are building a brand - people are unsure about DNF and what we do, so we need to align on DNF's values. We want committee involvement here because active members run for the Board (which encourages this alignment between the committees and the Board).
42 | * Project Involvement?
43 | * Aneesh: I agree that committee participation is necessary, but we should think beyond just that. Maybe project-related?
44 | * Jessica: It may be too big of an ask, requiring someone to see a project through, because we're not structured like that.
45 | * Nicole: We also need to consider how to verify an approve these things.
46 | * Aneesh: We also can't limit the requirements to project involvement because members of the Education Committee likely aren't working on projects.
47 | * Ove: Maybe the requirement isn't that someone owns the project, but that they're contributing. We can track how many meaningful PRs, code changes, etc they've worked on.
48 | * Jessica: We'll need to define "meaningful" but yes. They'll need to provide links to their projects/files if we include this requirement.
49 | * Blogs / Presentations / Marketing
50 | * Aneesh: People that write for DNF blogs?
51 | * Jessica: Writing on your own blog doesn't carry as much weight as writing on a DNF blog, so we can account for that.
52 | * Ove: Maybe speakers, people that present content at .NET events/conferences.
53 | * Process for Application - TBD
54 | * Review Process
55 | * Ove: How many do we approve each year?
56 | * Jessica: It depends on how many applications we receive, we could be flexible here.
57 | * The group discussed whether "DNF" was approved for marketing, with Nicole noting that it's used for the DNF Summit and there's precedent for referencing the Foundation as such. Ove suggested confirming that there won't be any legal issues by using DNF, particularly around copyrights.
58 | * Once the branding is determined, the group can focus on swag.
59 |
60 | ### Committee Admin
61 | * Madison sent the poll to committee members to determine the meeting schedule moving forward. All of the respondents so far have preferred meeting on a monthly basis, and most are available to meet on the first Wednesday of each month. Madison will update the calendar invite next week.
62 |
63 | **The meeting adjourned at 3:40 PM EDT.**
--------------------------------------------------------------------------------
/meetings/2023/11-01-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # .NET Membership Committee Meeting #
2 | Wednesday, 01 November 2023, 3PM EDT
3 |
4 | ### Meeting Attendees ###
5 |
6 | * Jessica Brentnall, *Chair*
7 | * Ove Bastiansen
8 | * Aneesh Gopalakrishnan
9 | * Nicole Miller
10 | * Madison Hardy, Scribe
11 |
12 | ### Attachment
13 | [Membership Form](https://forms.office.com/pages/responsepage.aspx?id=3G8HFsH8FUqxyjLJolWQDm8F03uiB2VCoiyUmNsltiBUQ0FDWDBFUFVURFRaQUdCUEg4MlExSEQ0OS4u)
14 |
15 | ### Membership Applications
16 | * 64 member applications were received throughout September. The group split the batch for review and approvals. Jessica noted that since the application questions were updated, submissions have been easier to review, and it was a much faster approval process.
17 |
18 | ### .NET Conf
19 | * Nicole provided a bit of context about DNF's previous involvement with .NET Conf. When Javier Lozano was on the Board, DNF was very active in the planning because Javier was involved in the programming. This year, DNF has not been asked and is not involved in the planning, but was asked to promote the conference through DNF channels. The Marketing Committee has been working on this through Mailchimp.
20 | * Jessica noted that the group is available to help as needed. She added that the UK MVP community has been very effectively marketing .NET Conf with swag and viewing parties.
21 |
22 | ### DNF Champions
23 | * Jessica drafted a file in GitHub to track the initiative's development. The group discussed the following:
24 | * Program Name
25 | * Aneesh: I like the name "DNF Champions", but maybe we shorten it - DNF Champ? I also think we can make a competition out of this. Create a small survey, publish it on Discord and in the newsletter, get members engaged.
26 | * Jessica: Good idea. Do want to offer a few pre-determined options so we don't end up with something silly. But this is a good way to get engagement.
27 | * Program Benefits for the Foundation
28 | * Jessica will draft a proposal
29 | * Program Benefits for Members
30 | * PDF Certificate
31 | * Aneesh: Something we could do here different than MVPs would be a hand-signed certificate. Joe (or whoever is DNF President) could sign.
32 | * Enamel Pin
33 | * Jessica: Do we have a budget for this?
34 | * Nicole: Yes, if we could get a sponsor, they could target funds for this. We can get pins pretty cheaply through [Wizard Pins](https://https://wizardpins.com/products/soft-enamel-pins?variant=14042600669239&utm_source=google&utm_medium=shopping&utm_term=Pins&utm_content=soft-enamel-pins_s3&nbt=nb%3Aadwords%3Ag%3A10022067833%3A102400061273%3A434604154450&nb_adtype=pla&nb_kwd=&nb_ti=pla-968229587997&nb_mi=125251762&nb_pc=online&nb_pi=soft-enamel-pins_s3&nb_ppi=968229587997&nb_placement=&nb_si=%7Bsourceid%7D&nb_li_ms=&nb_lp_ms=&nb_fii=&nb_ap=&nb_mt=&utm_source=google&utm_medium=paid&utm_campaign=10022067833&utm_content=102400061273&utm_term=&gadid=434604154450&nbt=nb%3Aadwords%3Ag%3A10022067833%3A102400061273%3A434604154450&nb_adtype=pla&nb_kwd=&nb_ti=pla-968229587997&nb_mi=125251762&nb_pc=online&nb_pi=soft-enamel-pins_s3&nb_ppi=968229587997&nb_placement=&nb_si=%7Bsourceid%7D&nb_li_ms=&nb_lp_ms=&nb_fii=&nb_ap=&nb_mt=&gad=1&gclid=Cj0KCQjwmvSoBhDOARIsAK6aV7hye027RXp6vo_Z551JK1DcWkK3joe6vjnjm0K0W2I6-R08Hn-a74YaAjlREALw_wcB)
35 | * Aneesh: We would need a logo, something to put on the pin. Create another competition for members!
36 | * Minimum Requirements
37 | * Time Served on Committees
38 | * Jessica: Should this be 6 months?
39 | * Ove: The committee chair will need to confirm the applicant's activity in the committee.
40 | * Jessica: The chairs will know, this will be straightforward to confirm.
41 | * Jessica: We are building a brand - people are unsure about DNF and what we do, so we need to align on DNF's values. We want committee involvement here because active members run for the Board (which encourages this alignment between the committees and the Board).
42 | * Project Involvement?
43 | * Aneesh: I agree that committee participation is necessary, but we should think beyond just that. Maybe project-related?
44 | * Jessica: It may be too big of an ask, requiring someone to see a project through, because we're not structured like that.
45 | * Nicole: We also need to consider how to verify an approve these things.
46 | * Aneesh: We also can't limit the requirements to project involvement because members of the Education Committee likely aren't working on projects.
47 | * Ove: Maybe the requirement isn't that someone owns the project, but that they're contributing. We can track how many meaningful PRs, code changes, etc they've worked on.
48 | * Jessica: We'll need to define "meaningful" but yes. They'll need to provide links to their projects/files if we include this requirement.
49 | * Blogs / Presentations / Marketing
50 | * Aneesh: People that write for DNF blogs?
51 | * Jessica: Writing on your own blog doesn't carry as much weight as writing on a DNF blog, so we can account for that.
52 | * Ove: Maybe speakers, people that present content at .NET events/conferences.
53 | * Process for Application - TBD
54 | * Review Process
55 | * Ove: How many do we approve each year?
56 | * Jessica: It depends on how many applications we receive, we could be flexible here.
57 | * The group discussed whether "DNF" was approved for marketing, with Nicole noting that it's used for the DNF Summit and there's precedent for referencing the Foundation as such. Ove suggested confirming that there won't be any legal issues by using DNF, particularly around copyrights.
58 | * Once the branding is determined, the group can focus on swag.
59 |
60 | ### Committee Admin
61 | * Madison sent the poll to committee members to determine the meeting schedule moving forward. All of the respondents so far have preferred meeting on a monthly basis, and most are available to meet on the first Wednesday of each month. Madison will update the calendar invite next week.
62 |
63 | **The meeting adjourned at 3:40 PM EDT.**
--------------------------------------------------------------------------------
/resources/recruiting-board/board-responsibilities.md:
--------------------------------------------------------------------------------
1 | # Board member responsibilities
2 |
3 | The purpose of this document is to outline the responsibilities of board members and committee chairs and estimated time one needs to spend volunteering for the .NET Foundation.
4 |
5 | ## Summary
6 |
7 | The purpose of the board of directors is to drive the strategic direction of the .NET Foundation in order to have a meaningful, positive impact on the .NET open source ecosystem. The board takes into consideration many things including approving budgets pend, driving membership,bringing in sponsorship income, supporting projects, growing our community, education and awareness, and legal issues to support the strategic initiatives. Many of these areas are driven by committees and working groups. The board functions as a leadership team, directing the activities of these committees. In addition, the board has the responsibility to create the foundation’s budget and track progress on income and expenses based on that budget. The board uses these income projections to plan how quickly the foundation can scale its activities.
8 |
9 | The .NET Foundation is a young organization. Therefore it has an active board, meaning that each board member is responsible for the success of at least one committee, either by chairing the committee or being an active participant. Each committee has a different set of priorities and number of volunteers helping. Depending on the committee, a board member may need to take a very active role as a committee chair, or may be able to participate in multiple committees that require less time. In either case, the board member’s role is to provide insight into the foundation’s activities as a whole and its current financial health.
10 |
11 | ## Board responsibilities
12 |
13 | The .NET Foundation board functions as the leadership team for the .NET Foundation. The board:
14 |
15 | - Sets goals for the foundation
16 | - Sets strategic direction to achieve those goals
17 | - Sets the yearly budget to ensure the financial wellbeing of the foundation
18 | - Manages the foundation’s performance against the yearly budget
19 |
20 | In addition to the overall direction of the foundation, individual board members are active in each of the Foundation’s committees. On these committees, the board member may take an active leadership role, or may function as a liaison with other committees and the board as whole. Committee chairs are chosen at the first board meeting following new board members being sworn in. The new board members and current committee chairs work together to determine new and changed assignments.
21 |
22 | **Board members are expected to allocate at least 4 hours per week to Foundation tasks.** This encompasses the overall board tasks and all committee related tasks.
23 |
24 | ## Committee roles and responsibilities
25 |
26 | ### [Marketing Committee](https://github.com/dotnet-foundation/wg-marketing)
27 |
28 | The marketing committee is here to help spread the message of openness in the .NET ecosystem. We support community and project initiatives, drive awareness and increase membership. We create consistent, powerful storytelling to increase share of conversation and establish industry relevance for the .NET Foundation.
29 |
30 | The marketing committee is composed of volunteers that are primarily marketers, not developers (although there are some more technical than others). They are developer marketing and technical marketers that care about and/or have bet their businesses on .NET. This is a smaller committee because most people that show interest in volunteering are not interested in marketing and are referred to the outreach committee which is focused on community activities and education.
31 |
32 | The main goals of the marketing committee are:
33 |
34 | - Increase membership
35 | - Generate awareness (of .NET open source and the .NET Foundation itself)
36 | - Foster and grow an open, healthy.NET community
37 |
38 | #### Marketing Committee Chair
39 |
40 | The marketing committee chair is responsible for directing the committee’s marketing strategy and execution.
41 |
42 | **Always-on activities** The chair runs monthly meetings with members and is on point for all announcements and air cover (for dealing with bad PR if needed as it arises). They are responsible for the foundation’s web presence, running all the social handles(Twitter, Facebook, LinkedIn) and growing followers, pulling together and sending the bi-monthly newsletter(MailChimp), driving leads(for newsletter and membership), running the [SWAG store](https://store.dotnetfoundation.org), writing and sending press releases.
43 |
44 | **Other activities** They are also responsible for new project “go-to-market” GTM, co-marketing initiatives, event sponsorships & presence, some event management (i.e. .NET Conf), website design & copy,branding and logos, surveys, presentation decks, and coordination with other committees around messaging and awareness as needed.
45 |
46 | ***Time commitment: 40-60 hrs./month***
47 |
48 | ## [Outreach Committee](https://github.com/dotnet-foundation/wg-outreach)
49 |
50 | The Outreach Committee is here to welcome developers of all backgrounds,education, and technology ecosystems into the .NET ecosystem. We are here to help you organize and evangelize.
51 |
52 | High-level goals:
53 |
54 | - Encourage new developers to build with .NET
55 | - Empower underrepresented segments of the coder community to become leaders and contributors
56 | - Assist event organizers with evangelism and growth
57 |
58 | ## [Membership Committee](https://github.com/dotnet-foundation/wg-membership)
59 |
60 | The committee is responsible for evaluating new member applications, discussing membership criteria, and providing services to the foundation's individual members.
61 |
62 | High-level goals:
63 |
64 | - Grow the membership in the foundation.
65 | - Ensure that the foundation provides value to members.
66 | - Provide programs that facilitate communication among and between members.
67 |
68 | This committee works to create new initiatives that encourage our membership to participate more in the foundation’s activities. These encompass many different roles, from open source projects to career development and mentoring to education opportunities.
69 |
--------------------------------------------------------------------------------
/meetings/2023/04-05-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # .NET Membership Committee Meeting
2 |
3 | ### 05 April 2023 8PM GMT / 3PM ET
4 |
5 | ### Meeting Attendees
6 |
7 | * Jessica White, *Chair*
8 | * Aneesh Ambikavally
9 | * Nicole Miller
10 | * Madison Hardy, *Scribe*
11 |
12 | ---
13 |
14 | ## Updates on previous meetings actions
15 |
16 | **Membership Form Updates**
17 |
18 | ✓ **ACTION:** Jessica/Nicole to update the website to indicate the 2-week lead time for approvals.
19 | * [Membership Form](https://forms.office.com/pages/responsepage.aspx?id=3G8HFsH8FUqxyjLJolWQDgWp4dniQhJJjdIubC8LTKVUQ0FDWDBFUFVURFRaQUdCUEg4MlExSEQ0OSQlQCN0PWcu)
20 |
21 | ✓ **ACTION:** Nicole to update Welcome template with suggested links.
22 |
23 | * **ACTION:** Nicole to draft template email for denied applications.
24 | * Deferred
25 |
26 | **Nominating Committee**
27 |
28 | * **ACTION:** Javier and Jessica to edit the BoD candidate application form.
29 | * Need to book meeting.
30 |
31 | **Any Other Business**
32 |
33 | * **ACTION:** Jessica to add Code of Conduct update as an agenda item for the March Board meeting.
34 | * Will add to the next board meeting
35 |
36 | ---
37 |
38 | ## Agenda
39 |
40 | Bring up GitHub Projects to check for any agenda items.
41 |
42 | ### **Review actions from the previous meeting**
43 | -
44 |
45 | ### **Membership Form Updates**
46 |
47 | * The committee reviewed new membership applications.Nicole moved the form into Google for better accessibility and sharing. She noted that rows highlighted in green have Welcome Emails prepped and ready to send. The second tab of the spreadsheet includes a template of the welcome email. Nicole added that when she sends the welcome email, she will send the same information to the new member via GitHub.
48 |
49 | * The committee discussed whether to approve or deny applications that meet all the eligibility requirements but have low activity/commit metrics on GitHub. They agreed to approve the applications and monitor for suspicious activity.
50 |
51 | * The website hasn’t been updated yet to indicate the 2-week processing period for new applications, but the application itself indicates that the Membership Committee meets every two weeks and applicants should expect processing delays.
52 |
53 | * The committee assigned applications for review during the call.
54 |
55 | * **3/1/23 Action Item:** Nicole to draft template email for denied membership applications.
56 |
57 | * **Update: Item in progress;** need to agree on the threshold metrics for accepting applications to inform why an application is denied.
58 |
59 | ### **Discord:**
60 |
61 | * **Jessica proposed two options to increase the membership value of the Discord channels:**
62 | 1. Remove non-members
63 | 2. Create private channels specifically for DNF members.
64 |
65 | The committee would need to verify Discord handles compared to other verified social handles for each member, which could be time-consuming. The membership application would be updated to request Discord handles moving forward.
66 |
67 | * ACTION: Nicole to update the membership application to include discord handles.
68 |
69 | * Aneesh noted that making a private channel may not be the best solution. The newsletter includes a link to join the Discord channels, and many members may not actively post in the channels but do appreciate the forum. He added that he created several issues in GitHub to establish membership molds, identifying DNF “insiders,” project maintainers, educators, etc., using tags.
70 |
71 | * Jessica commented that this will be helpful in the future, but the first step is to create the member channel.
72 |
73 | * The committee discussed how to obtain the Discord handles for current members. Aneesh suggested publishing a form in the general channel that would ask users to verify their DNF membership and join the private channel.
74 |
75 | * **ACTION:** Jessica to draft the form.
76 | * The committee discussed whether to create a channel for DNF sponsors.
77 |
78 | * **ACTION:** Aneesh to update his proposal to include a channel for sponsors.
79 |
80 | * **ACTION:** Jessica to contact the Sponsorship Committee chair (Iris).
81 |
82 | * The committee discussed whether to change the URL for $5/month. Aneesh noted that $5/month for a large communication channel isn’t that much; Jessica added that depending on the other benefits provided, $5 to change a URL may be excessive as it's per member.
83 |
84 | ### GitHub Issues:
85 |
86 | * **Issue Raised** [Exclusivity of Discord #108](https://github.com/dotnet-foundation/wg-membership/issues/108)
87 |
88 | * **Issue Raised** [A CFP (Call for proposal) channel on Discord #106](https://github.com/dotnet-foundation/wg-membership/issues/106)
89 | * **Issue Raised** [Customize discord invite url #104](https://github.com/dotnet-foundation/wg-membership/issues/104)
90 |
91 | ---
92 |
93 | ### **Nominating Committee**
94 |
95 | * Javier and Jessica are reviewing the proposed timeline for the 2023 election cycle. The original candidate application form is no longer accessible, so Nicole will draft a new version. Jessica and Javier intend to meet in the coming weeks to discuss next steps.
96 |
97 | * **ACTION:** Nicole to draft the candidate application form.
98 |
99 | * **ACTION:** Javier/Jessica to discuss next steps.
100 |
101 | ### **Any Other Business**
102 |
103 | * Rich Lander has received several emails from someone claiming to have submitted a membership application and requesting an update. Nicole noted there is no record of the individual’s application and is working to resolve.
104 |
105 | * The Call for Proposals for the June DNF Summit was published in the recent newsletter; one proposal was received. The Outreach Committee will manage the DNF Summits moving forward.
106 |
107 | * The Marketing Committee is drafting a survey for DNF members and will likely be distributed next month.
108 |
109 | * Nicole is conducting another audit of the MeetUp groups, working to downsize again.
110 |
111 | * Jess suggested publishing a .NET Dogs edition of the newsletter (slightly in jest)
112 |
113 | ---
114 |
115 | ## Action Items
116 | * Nicole to update the membership application to request Discord handles.
117 |
118 | * Jessica to draft the form allowing members to access the private Discord channel.
119 |
120 | * Aneesh to update his proposal to include a Discord channel for sponsors.
121 |
122 | * Jessica to contact the Sponsorship Committee chair (Iris) regarding the Discord channels.
123 |
124 | * Nicole to draft the new BoD candidate application form.
125 |
126 | * Javier/Jessica to discuss next steps for the 2023 BoD election.
127 |
128 | ---
129 |
130 | ### The meeting adjourned at 3:35PM ET.
131 |
132 |
--------------------------------------------------------------------------------
/resources/member-documentation/member-participation-types.md:
--------------------------------------------------------------------------------
1 | # Member Participation Types
2 |
3 | The .NET Foundation welcomes participation and input from it's many types of member. The Foundation wants to benefit the whole .NET ecosystem and recognizes that there are many types of technologist within this.
4 |
5 | This document outlines some of the different characteristics of a .NET Foundation member. It includes:
6 |
7 | * Who are they?
8 | * What is their involvement?
9 | * Which groups would be of interest?
10 | * Why would they want to join?
11 |
12 | You may identify with a number of the below, and that's great! All the more reason to sign up to be a member.
13 |
14 | Committees do have limited membership and different sign up procedures, but all value transparency. This means as a member you will have the opportunity to keep up to date with what they are doing, and have the opportunity to have your say and participate through varying means.
15 |
16 |
17 |
18 | ## The Open Source Maintainer
19 | ---
20 |
21 | ### Who are they?
22 |
23 | A founder or maintainer of one or multiple open source repositories. Ideally written in, or in support of, an aspect of the .NET Ecosystem.
24 |
25 | ### What is their involvement?
26 |
27 | They have founded or maintain an open source repository which is written in, or is in support of, an aspect of the .NET Ecosystem.
28 |
29 | ### Which groups would be of interest?
30 |
31 | - [The Projects Committee](https://github.com/dotnet-foundation/projects#readme)
32 |
33 | ### Why would they want to join?
34 |
35 | - To have access to [the various support the .NET Foundation provides for projects](https://dotnetfoundation.org/projects/why-join)
36 | - To have the opportunity to have their project featured in [the .NET Foundation's Spotlight](https://dotnetfoundation.org/projects/spotlight) and be shared in the .NET correspondence.
37 | - To have a say in what support the .NET foundation should provide to Open Source projects.
38 | - To have visibility of what is happening in the .NET Foundation and any opportunities that arise.
39 | - To have access to other .NET Foundation members to talk to.
40 |
41 |
42 |
43 | ## The Open Source Contributor
44 | ---
45 |
46 | ### Who are they?
47 |
48 | Anyone contributing to open source projects written in or relating to the .NET ecosystem. These contributions can be in many forms including code, updating documentation or design but should be accepted as maintainers as meaningful.
49 |
50 | ### What is their involvement?
51 |
52 | They have contributed to an open source project and therefore helped and improve an element of the .NET ecosystem and community.
53 |
54 | ### Which groups would be of interest?
55 |
56 | - [The Projects Committee](https://github.com/dotnet-foundation/projects#readme)
57 |
58 | ### Why would they want to join?
59 |
60 | - To have a say in what support the .NET foundation should provide to Open Source contributors.
61 | - To have visibility of what is happening in the .NET Foundation and any opportunities that arise.
62 | - To have access to other .NET Foundation members to talk to.
63 |
64 |
65 |
66 | ## The Event Organizer
67 | ---
68 |
69 | ### Who are they?
70 |
71 | Someone who organizes events around an aspect of the .NET Foundation. These events can include meetups, conferences and other gatherings. The person may be doing this individually or as part of a group/committee.
72 |
73 | **Examples of events include:**
74 | - .NET focused or generalist tech conferences
75 | - .NET (C# / F# / Q# / Unity etc.) centered meetup
76 | - Other tech events virtual and in person.
77 |
78 | ### What is their involvement?
79 |
80 | They are helping to build a great communities and providing opportunities for knowledge sharing. They run or organize these events on an individual basis or part of a group.
81 |
82 | ### Which groups would be of interest?
83 |
84 | - [The Outreach Committee](https://github.com/dotnet-foundation/wg-outreach#readme)
85 | - [The Marketing Committee](https://github.com/dotnet-foundation/wg-marketing#readme)
86 |
87 | ### Why would they want to join?
88 |
89 | - To have the opportunity to promote your event on through the [.NET Foundation website](https://dotnetfoundation.org/community/meetups) or correspondence.
90 | - To have the opportunity to stream a talk you are hosting on the [.NET Foundation YouTube channel](https://www.youtube.com/channel/UCiaZbznpWV1o-KLxj8zqR6A)
91 | - To have visibility of what is happening in the .NET Foundation and any opportunities that arise.
92 | - To have a say in how the .NET Foundation can support events and growing a great community.
93 | - To have access to the many great members of the .NET Foundation and get their help and involvement in your event.
94 |
95 |
96 |
97 | ## The Educator
98 | ---
99 | ### Who are they?
100 |
101 | Those helping to drive and encourage education in and around .NET. This can include using any part of the .NET ecosystem at any level.
102 |
103 | **Educational spaces can include:**
104 | - Bootcamps
105 | - Individual Courses
106 | - Arranging/taking part in technical mentorship
107 | - Working with educational facilities on their curriculum including schools, colleges and universities.
108 |
109 | They may be an organizer, facilitator, teacher, coach, mentor or any other role related to education of .NET.
110 |
111 | ### What is their involvement?
112 |
113 | They are promoting .NET and encouraging new people to be included and take part in the .NET community. Bringing in new people, fresh ideas and diverse view points can only help to make .NET grow positively.
114 |
115 | It also shows that the languages and professions in the .NET ecosystem are open and suited to beginners as well as experienced professionals.
116 |
117 | ### Which groups would be of interest?
118 |
119 | - The Education Committee (this is new)
120 | - [The Outreach Committee](https://github.com/dotnet-foundation/wg-outreach#readme)
121 |
122 | ### Why would they want to join?
123 |
124 | - To have visibility of how the .NET Foundation can support your educational group.
125 | - To have visibility of resources available.
126 | - To knowledge share with other .NET Foundation members in this space.
127 | - To get support from other .NET Foundation members in this space.
128 | - To have a say in how the .NET Foundation can support educational spaces.
129 | - To be able to reach out to other .NET Foundation to get volunteers for your area of training.
130 |
131 |
132 |
133 | ## The Sharers of Knowledge
134 | ---
135 | ### Who are they?
136 |
137 | Anyone who is sharing .NET related knowledge in some format on a semi-frequent or frequent basis.
138 |
139 | **Knowledge sharing may include:**
140 |
141 | - Speaking
142 | - Blogging
143 | - Podcasting
144 | - Streaming
145 | - Content Creation
146 |
147 | ### What is their involvement?
148 |
149 | They are helping people develop knowledge about .NET and providing different formats for people to learn in the space. This can be aimed at a number of levels.
150 |
151 | Knowledge sharing, in all its forms, can also work as an outreach activity. It can promote working and creating in the .NET space and encourage other people to explore the .NET Ecosystem.
152 |
153 | ### Which groups would be of interest?
154 |
155 | - [The Outreach Committee](https://github.com/dotnet-foundation/wg-outreach#readme)
156 | - [The Marketing Committee](https://github.com/dotnet-foundation/wg-marketing#readme)
157 |
158 | ### Why would they want to join?
159 |
160 | - To have visibility of what is happening in the .NET Foundation and any opportunities that arise.
161 | - To find out about opportunities to share your knowledge through other members of the .NET Foundation.
162 | - To have a say in how the .NET Foundation can support knowledge sharing and building a great community.
163 |
164 |
165 |
166 | ## The Student
167 | ---
168 |
169 | ### Who are they?
170 |
171 | Someone who is studying in tech and may be learning directly in a .NET technology/language. Education is now available in many different formats.
172 |
173 | **Types of student:**
174 | - Self-taught
175 | - Formal Education (College, University etc)
176 | - Apprentices
177 | - Bootcampers
178 |
179 | ### What is their involvement?
180 |
181 | They are bringing new viewpoints and perspectives to .NET.
182 |
183 | ### Which groups would be of interest?
184 |
185 | Any and all of the groups may be of interest. See the full list [here](https://dotnetfoundation.org/community/committees).
186 |
187 | ### Why would they want to join?
188 |
189 |
190 | - To have visibility of what is happening in the .NET Foundation and any opportunities that arise.
191 | - To have a say and represent those who are newer to .NET to help guide the direction of the .NET Foundation.
192 | - To have access to other .NET Foundation members to talk to.
193 |
--------------------------------------------------------------------------------
/meetings/2022/07-06-meeting-minutes.md:
--------------------------------------------------------------------------------
1 | # .NET Membership Committee Meeting
2 |
3 | Wednesday, 6 July 2022, 3PM ET
4 |
5 | ## Meeting Attendees
6 |
7 | * Bill Wagner _Chair_
8 | * Shaina Sullivan
9 | * Nicole Miller
10 | * Joe Guadagno
11 | * Jessica White
12 | * Aneesh Ambikavally
13 | * Tom Pappas
14 | * Madison Hardy, Scribe
15 |
16 | ## Agenda
17 |
18 | * **[Pull Request #63: Committee Templates](https://github.com/dotnet-foundation/wg-membership/pull/63)**
19 | * Bill and Jessica have been updating the language for the DNF templates, specifically templates for recruiting participants for the Nomination Committee and candidates for the Board of Directors.
20 | * **[Pull Request #68: Board Responsibilities](https://github.com/dotnet-foundation/wg-membership/pull/68)**
21 | * Bill and Jessica are also updating the responsibilities for members of the Board to standardize the structure and expectations. Descriptors for the Marketing Cmt and Membership Cmt are most detailed, and Tom has provided resources on the general responsibilities for the Board to the overall organization.
22 | * Bill: Knowing this is still incomplete, should we merge this and continue to work with other committees to update. We can create a second PR for overall Board responsibilities.
23 | * Joe: Maybe we should merge and have others add as they get to it.
24 | * Bill: Yes, rather not hold up progress.
25 | * ACTION: Bill to merge PR #68
26 | * **Nominating Committee**
27 | * The kick-off meeting is tentatively scheduled for July 8th.
28 | * ACTION: Jessica to contact Stacy to complete meeting poll
29 | * **Membership Portal**
30 | * Shaina Sullivan, the VMX representative, presented an update on the membership portal and the process flow to ensure the committee has current information. As an application is submitted as a lead, VMX will take the information (name, email, GitHub username, contributions) and send it to an approved email for DNF review (membership@dotnetfoundation.org). If approved, the applicant is pushed through as a new member and receives a "Welcome Email."
31 | * ACTION: Committee to send outline of information to include in Welcome Email.
32 | * Jessica suggested drafting a short piece on what it means to be involved as part of a committee, why she engages, and what has been accomplished over the last few years. Bill agreed and added that Jeremy Sinclair of the Projects Committee could do something similar.
33 | * Shaina added that she could send samples of different welcome letters - one that includes general information on DNF, and another that includes information on how to get involved and testimonials.
34 | * VMX can auto-enroll the new member into designated GitHub repositories. Bill noted that while specific repos could later be assigned, it would be beneficial to enroll everyone in the parent team within GitHub. Ultimately, DNF would like to leverage this platform to get people more involved in efforts that align with stated goals.
35 | * Shaina recommended establishing touch-points after someone joins at three months, and again at six months to check in.
36 | * Bill stated that this responsibility would likely fall to the Membership Committee. Tom suggested that depending on the new member, the Maintainers could also assist, though it was noted that if a new member is not actively involved within DNF, someone from Membership would be the better point of contact.
37 | * Shaina asked if it would be beneficial to include a question on the membership application that asks which committee the applicant would like to join.
38 | * Yes; when someone applies, they include contributions from 1+ membership profiles and that can instruct the Foundation as to where the new member can be most involved.
39 | * The membership portal can generate and distribute monthly reports that can show broad information (new members, lost members), but can also show member participation in committees. Shaina asked if there was a way to track new members and when they joined through GitHub.
40 | * As an admin of the DNF GitHub, Bill has access to see some of this information, but it is likely out of date. Moving forward, it would be preferable to receive this report from VMX.
41 | * In order for the membership report to be accurate, the chairs of each committee would send a roster of the members monthly. This usually occurs in the first two weeks of each month.
42 | * When members indicate they want to leave the Foundation, VMX can send questions as a retention measure to better understand member concerns. Shaina recommended that someone established within DNF should also reach out as it is a more meaningful gesture.
43 | * Aneesh noted several points from his personal onboarding experience that could be improved for new members:
44 | * Clearly establish next steps - what to do, which committees to join, where to get information, etc; Auto-subscribe members to the newsletter.
45 | * Consider adjusting titles based on engagement: someone subscribed to DNF would be a member; someone active within committees could be a "Fellow."
46 | * Establish touch-points or create a system to reach out to people who aren't engaged and address any concerns.
47 | * Re-engage with members who are absent and keep track of attendee lists to best encourage involvement in meetings.
48 | * Bill expressed a concern about the multiple avenues of communication. Touch-points are important, but there is a divide within the community between which platforms are used for communication (email, newsletter, GitHub, Discord, Slack, etc.). With so many channels, it become inefficient to reach out to everyone, and members become siloed within their preferred platform. He asked Shaina if the VMX portal could consolidate those channels and become a place where everyone can get information and stay involved.
49 | * Jessica added that a common issue is moderation. There is a [Code of Conduct](https://dotnetfoundation.org/about/code-of-conduct), but it is not always clear where to draw the line and who holds a member accountable when the code is broken.
50 | * Shaina: Communication is always the biggest problem. Some clients hire a full-time moderator to be the manager and connection between all the platforms. Other clients shrink the tools available so there are less options to utilize.
51 | * Bill: The Microsoft .NET Product Teams have a good model. There's an internal group of 15 members that discuss any issues and 4 of those members moderate and hold everyone accountable. It's diverse in its makeup and has enough people to work yet is small enough so it's not time-consuming. Unfortunately, the worst offenses occur on Twitter, and that isn't a DNF platform. On GitHub or the portal, it is easier to enforce the code.
52 | * Tom: VMX is establishing a Community Function. When that goes live, DNF can revisit it as an option to narrow the scope for discussion platforms.
53 | * The Community Function is similar to GitHub in that there are "All Member" pages and individual groups for people to join. When a new member joins a group, the chair is notified (if approval is needed, the chair is notified and can approve/deny).
54 | * Bill noted that when onboarding current members, there should be an option to allow people to include PII on their profile. Shaina responded that no information about the members is made public without their knowledge.
55 | * Shaina said that in order to create the community page, VMX will need a CSV file with the current DNF member roster that includes any information DNF wants to store in the database. Bill advised that DNF would store the name, email, and GitHub handle of each member and allow individuals to add more information if they want.
56 | * The team discussed how to find a report that would indicate when each member joined DNF. Immediate investigation into GitHub did not prove helpful, and Tom asked if that statistic was tracked in Open Collective. Tom also suggested looking through the payment record log to find the first payment for membership dues.
57 | * ACTION: Bill and Tom to review Open Collective data to find user join dates.
58 | * ACTION: Tom to review payment records and export a spreadsheet for membership dues.
59 | * Aneesh added reference photos and [links](https://api.github.com/users//repos) in the chat showing committee join dates in GitHub.
60 | * Shaina said that VMX can migrate the DNF membership without specific join dates (though exact dates will make membership reports more precise).
61 | * Next Steps: Shaina to distribute the below within the next two weeks to membership@dotnetfoundation.org and board@dotnetfoundation.org
62 | * Sample welcome emails
63 | * Email template for retention
64 | * Email template for touch points and a proposed timeline for each touch point
65 | * Online Application draft
66 | * Final draft of full migration process
67 | * Sample membership report
68 |
69 | ## Next Steps / Action Items
70 |
71 | * Bill to merge PR #68
72 | * Jessica to contact Stacy to complete meeting poll
73 | * Committee to send outline of information to include in Welcome Email, respond to Shaina's email when received
74 | * Bill and Tom to review Open Collective data to find user join dates
75 | * Tom to review payment records and export a spreadsheet for membership dues
76 | * Shaina to distribute documents for VMX migration next steps
77 |
78 | **The meeting adjourned at 3:55PM ET**
79 |
--------------------------------------------------------------------------------