Closed brminnick closed 3 months ago
@brminnick The .NET Foundation website only includes official .NET Foundation Member Projects. Please submit an application to have the .NET MAUI Community Toolkit considered as an official .NET Foundation project. You can find more information about the process here: https://github.com/dotnet-foundation/projects.
Hi @sbwalker! I'm a bit confused. We are members of the .NET Foundation.
The .NET MAUI Community Toolkits have been an official .NET Foundation Project since its inception in 2021.
👇 Here's some examples demonstrating our membership
The .NET Foundation is an official Owner
on NuGet of all of our NuGet Packages:
CommunityToolkit.Maui
CommunityToolkit.Maui.Core
CommunityToolkit.Maui.Markup
CommunityToolkit.Maui.MediaElement
We livestream every Monthly Standup to the .NET Foundation YouTube channel
I've worked with @ChrisSfanos to help resolve previous work tickets:
Each of READMEs highlight that we are members of the .NET MAUI Community Toolkit
@brminnick My apologies... the reason for my confusion is that I do not recall the Project Committee reviewing a Project Application for .NET MAUI Community Toolkit, nor can I locate a project application in the .NET Foundation issues - https://github.com/dotnet-foundation/projects/issues). The .NET MAUI Community Toolkit is also not represented on the .NET Foundation Project Trends site: https://www.dnfprojects.com/ where the Project Committee monitors ongoing activity of .NET Foundation projects. I will sync up with @ChrisSfanos to get more clarity.
No worries - thanks!
I believe we were grandfathered into the .NET Foundation as members of the .NET Community Toolkit org on GitHub. It was previous "Windows Community Toolkit" until 2021 when @michael-hawker and I teamed to rebrand to the ".NET Community Toolkit" so that we could add more toolkits outside of the Windows ecosystem.
Ahh.... this makes sense now, as the Windows Community Toolkit is an official member of the .NET Foundation. I just noticed that Windows Community Toolkit is represented on https://www.dnfprojects.com and points to https://github.com/CommunityToolkit/WindowsCommunityToolkit - should it be replaced with the .NET MAUI Community Toolkit?
Also the Windows Community Toolkit is listed on the .NET Foundation website: https://dotnetfoundation.org/projects/project-detail/windows-community-toolkit
Right on! We wouldn't want to replace "Windows Community Toolkit" with ".NET MAUI Community Toolkit" because the Windows toolkit it still exists: CommunityToolkit.WinUI
for example.
I see two paths forward:
.NET Community Toolkits
Hi folks - I'm happy to do either. From a user/Foundation visitor perspective, does it make sense to have two? Or is renaming/updating the existing entry to .NET Community Toolkits a better solution to drive overall traffic and exposure?
Adding @Sergio0694 here too, something the three of us should probably discuss on a call and figure out the path forward here. As we have our "Community Toolkit" GitHub organization: https://github.com/CommunityToolkit which has various projects underneath it (e.g. the Windows Community Toolkit, the .NET Community Toolkit, and the MAUI Community Toolkit).
Thought we removed the '.NET Community Toolkits' from the learn page as that's confusing with the '.NET Community Toolkit' itself.
Anyway, from the foundation perspective should the 'projects' page represent individual projects within the foundation's organizations or only the organization-level entities? @ChrisSfanos @sbwalker
Hey @michael-hawker - I don't think there is a hard and fast rule - I think it's really what's better from a community perspective. If having a separate entry for each project because they are distinct from a developer's perspective we can go that route. If it helps drive cross-traffic to both by having a single entry pointing to multiple items, then we should go that route
That makes sense.
From a community perspective, the .NET MAUI community (mobile) and the Windows community (desktop) don't have a huge overlap, so I agree that it'd make sense to highlight both projects separately on the Current Projects page, despite both projects being in the same CommunityToolkit org.
The works for me - so let's go with adding a .NET MAUI community toolkit entry
Please take a look at some existing Project entries and then drop in here your: 1) Project description 2) GitHub repo link 3) Any other site landing page you want to directly developers to
I'll grab the license and license link and add that
Thanks @ChrisSfanos - Sounds good!
@brminnick you have a typo in your GitHub Repo link it should be https://github.com/CommunityToolkit/Maui
Good catch - thanks! Fixed ✅
I would suggest keeping Windows Community Toolkit
and will add both the .NET Community Toolkit
and the .NET MAUI Community Toolkit
.
@ChrisSfanos is there action on us here? Do you need us to open a PR somewhere to add these two extra projects to the list?
I also noticed that our Windows Community Toolkit listing doesn't have a 'Project Website' button like the others.
We're also migrating our repository to https://github.com/CommunityToolkit/Windows, so we'll want to update the link ourselves for that:
Hey all - I'm trying to help clean some of these issues up. How's this look for everyone?
https://dotnetfoundation.org/projects/project-detail/.net-maui-community-toolkit
Thanks again @michael-hawker for your patience. Closing this one but please open a new issue if there are any more issues with the content.
Please fill in the information below:
Current Projects
page on .NET Foundation WebsiteHi Friends!
Could we add the .NET MAUI Community Toolkit to the
Current Projects
page on the .NET Foundation Website?👇 Currently, the .NET MAUI Community Toolkit isn't featured in the Current Projects page