Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Committee Meeting - February 2024 Minutes #351

Closed
nicoleabuhakmeh opened this issue Jan 17, 2024 · 9 comments
Closed

Committee Meeting - February 2024 Minutes #351

nicoleabuhakmeh opened this issue Jan 17, 2024 · 9 comments

Comments

@nicoleabuhakmeh
Copy link
Contributor

nicoleabuhakmeh commented Jan 17, 2024

The Project Committee held their monthly meeting on February 8th at 5pm Eastern on Discord.

Discord link is open to current members of the Project Committee to meeting: https://discord.com/events/966483029830824008/1185240341675261962

Agenda Items

  1. Review of Project Applications
  • Jinget
    2/8/24 – include in Seed category
  • Emik.SourceGenerators.Choices
    2/8/24 - inform maintainer to submit application in the future once the project is more established and has more adoption
  • std.uritemplate
    2/8/24 - submit to BOD for consideration as a Member project (need to provide clarification that the repo does not include only .NET code… and clarify the intent to join via Assignment rather than Contribution).
  1. Review of Member Applications in the Project Repo - Nicole to follow up will the requests. Transfer the applications to the Project Committee as needed.
  1. Open Discussion items for Members of the Project Committee
    Avalonia – provide feedback to BOD that a project of this stature leaving the .NET Foundation does not send a positive message to the .NET community. If we are trying to improve the reputation of the .NET Foundation this will represent another step backward. Ask if there is any way to retain the project in the .NET Foundation, as there are very few reasons that a project should feel the need to leave (ie. a license change to a non-OS license, etc…).
@baywet
Copy link

baywet commented Jan 23, 2024

@nicoleabuhakmeh for std.uritemplate, do you need the maintainers to be present on the call? (@andreaTP and I) or is this more of a discussion between foundation committee members?

@andreaTP
Copy link

@baywet do we need to submit also the "Project Application"?

@sbwalker
Copy link
Collaborator

sbwalker commented Jan 23, 2024

@andreaTP you should use the standard issue template to submit your Project Application:

Select Create Issue in the Projects repo and then choose the appropriate option:

image

This ensures the application follows the workflow.

@sbwalker
Copy link
Collaborator

@baywet if new project applications are being reviewed by the Project Committee, then only the Project Committee members should be present in the meeting.

@baywet
Copy link

baywet commented Jan 23, 2024

@sbwalker thanks for the additional context here.
@adnreaTP FYI we've already filed the project application #349

@sbwalker
Copy link
Collaborator

@baywet issue #349 is not in the correct form - it is missing the majority of key project information which is reviewed by the Project Committee. Please re-resubmit using the Project Application template I included above in the screen shot.

@baywet
Copy link

baywet commented Jan 23, 2024

Thanks for pointing this out @sbwalker !! I indeed filed a "Membership request" which I believe was the link I was given during the January call. I'll go ahead I file a Project Application as well (unless we need to wait for the membership request to be approved first?)

@sbwalker
Copy link
Collaborator

@baywet the Membership request serves a different purpose in the .NET Foundation - it is for individuals, not projects. So you do not need to wait for the Membership request to be approved.

@baywet
Copy link

baywet commented Jan 23, 2024

created the project application issue #353

@nicoleabuhakmeh nicoleabuhakmeh changed the title Committee Meeting - February 2024 Committee Meeting - February 2024 Minutes Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants