Pomelo.EntityFrameworkCore.MySql
Pomelo.EntityFrameworkCore.MySql copied to clipboard
PomeloFoundation
Should we join the .NET Foundation?
@caleblloyd We should talk about this. Probably a good idea and we can likey help. /cc @divega
I have filled out the "Submit a Project" form on the .NET Foundation website.
Sorry for the slow communication here. We've moved to a public tracker on GitHub for tracking project applications. The form mentioned above was just to register interest, and after that we had a 3 page word doc to fill out. I don't think we have that application from you, if you previously sent it in it's the same as the GitHub issue template.
Can you open a new issue using the New Project Application here: https://github.com/dotnet-foundation/projects/issues/new/choose
We're going to be reviewing project applications this week, and I'd like to get this one in.
@caleblloyd I assume as maintainer you have authority to transfer the project to the .NET Foundation?
From looking at the contribution stats, I'd recommend that you have @caleblloyd @yukozh and @lauxjpn sign the contribution agreement.
After filling out a new project application, the board votes on whether the project should be accepted. After that, contribution agreement is sent out via DocuSign.
I assume as maintainer you have authority to transfer the project to the .NET Foundation?
Yes, @yukozh , @lauxjpn , and I should all have access to do that
I am supportive of filling out the application. Originally we had hoped that joining the .NET foundation would help with visibility, governance, and attracting more contributors. I think those would all still be helpful.
@lauxjpn since you have been the lead developer on the latest cycle of changes, what is your opinion? If you agree, would you like to fill out the application? I am also happy to fill out the application.
@caleblloyd I think it is a good idea and if this projects gets accepted might provide users/companies with additional confidence to choose this one over the oracle provider.
I will create a temporary branch for the application process on our repository and copy the template in there, so we can all work on it together until we are satisfied before submitting it.
It's probably a good idea to peek at the ones that got accepted in the past to get a better understanding about what the foundation (board) is looking for.
Let me know if you have any questions, and don't worry about getting everything right in the application. We have our monthly board meeting this Friday, so if you are able to get an application posted before Friday we can include for this month - otherwise we'd need to wait for next month.
We are not going to make the board meeting for this month but will be ready for the one in December.
Also referencing https://github.com/mysql-net/MySqlConnector/issues/535 in case @bgrainger has an interest.
What's the action item here? #949 is still in draft, so does someone need to update that form and get it submitted, or did I miss something in the thread and it's already been sent over?
What's the action item here? #949 is still in draft, so does someone need to update that form and get it submitted, or did I miss something in the thread and it's already been sent over?
No, that is exactly what we still need to do:
No, there has been no progress from our side.
I think this is a good suggestion. I've actually contributed my own project Ant Design Blazor to the foundation and completed all the processes, so I can offer some help.
We haven't really done anything to move this forward, but in light of recent events due to poor decisions from the upper management at Microsoft towards the OSS community and public concerns regarding Microsofts control over the .NET Foundation, we should not move this issue forward in the foreseeable future.
On an unrelated note but pertaining to Pomelo Foundation, should we apply for Package ID prefix reservation in NuGet?
I did this for "MySqlConnector" and it's a fairly simple process. (Though not sure if it'll be a problem if https://www.nuget.org/profiles/PomeloFoundation only owns 5 of the current Pomelo.* packages; you may have to consolidate ownership under one account first before getting a prefix reservation. I don't remember exactly how it works.)
[...] you may have to consolidate ownership under one account first before getting a prefix reservation [...]
I opened #1172 for this task last year, but have not gotten any response so far. I'll give it another bump.
Hi there! I'm a PM on the NuGet team and happy to help here. The consolidation isn't a strict requirement and I am happy to reserve for PomeloFoundation for now.
Since there is a number of community contributions, I assume a shared namespace would be best? That would give PomeloFoundation's Pomelo packages a verified status, but still allow contributors to publish within the prefix. Let me know what y'all think!
@jcjiang Thanks for joining in!
I just posted a couple of lists in regards to packages with the "Pomelo." prefix.
Of the packages not published by us, only the ones from @ChaosEngine seem to be significant. Maybe he is up to joining PomeloFoundation and to make this an official package, in which case we could close down the namespace to members of the PomeloFoundation as far as I am concerned.
The rest of the packages seem to be either very old forks, newer forks reviving the old and weirdly named Pomelo.EntityFrameworkCore.Lolita repo, which should probably be renamed, or packages doing something completely different with a very low download count.
The (nuget.org) authors of the other packages are (in order of significance):
| Authors |
|---|
| ChaosEngine |
| he1a2s0 |
| Mozbert |
| tcfialho |
| matocibo |
| tubo |
/cc @yukozh, @he1a2s0, @crozone