EntityFrameworkCore.Jet

EntityFrameworkCore.Jet copied to clipboard

This is a follow-up to the discussion under #34.

@bubibubi Please also set aside some time in the near future (within the next two weeks or so), to either convert the GitHub bubibubi account into a GitHub organization (which would mean you might want to move unrelated projects to a new personal account) or to create a new GitHub organization and move EntityFrameworkCore.Jet to it (in which case a new AZDO organization should be created as well; you could keep using the old one then for your personal account). If you want to go the latter route, we should brainstorm some new organization name.

Related articles:

• Converting a user into an organization
• Transferring a repository

@bubibubi Can we proceed with this over the course of this week?

(Since we are moving await from AZDO, it will likely be unnecessary to create a new AZDO account.)

/cc @ChrisJollyAU

@bubibubi Can we proceed with this over the course of this week?

@bubibubi Please confirm. Thank you.

@bubibubi Since you didn't respond (but were active in a different comment on this repo) I will now move along with this as I see fit.

• I will pick a name and then create a new GitHub organization.
• I will then add @bubibubi, @ChrisJollyAU and @lauxjpn to the organization.
• We then transfer bubibubi/EntityFrameworkCore.Jet to the new organization.
• There is no need for AZDO anymore, as we have prepared the switch to GitHub Actions.
• I will create a new myget.org feed to replace the AZDO feed.

This will happen over the course of the week and is tracked by this issue here.

@lauxjpn do you have the permissions to do the transfer?

Also, recommend changing the default merge behaviour to squash and merge

@lauxjpn do you have the permissions to do the transfer?

@ChrisJollyAU No, @bubibubi needs to do the transfer once the new organization is setup. Since this is a very simple process (see Transferring a repository), it should only take 5 minutes.

The other option is to simply fork the repository to the new org (and probably update the current repo to manually point to the new repo). For the existing user base, the official transfer is a bit smoother, since the old repo should then redirect automatically to the new one. However, the fork option would be good enough as well.

Also, recommend changing the default merge behaviour to squash and merge

Definitely!

---

@ChrisJollyAU If you have ideas for open source organization names (that are available), feel free to pitch.

So sorry guys that I can't help you. I will create the new org and I transfer the repository within a couple of days. And I also think that I will restart help you in mid 2024 that I will update my projects (that are still on EF 6, not EF Core).

I will create the new org and I transfer the repository within a couple of days.

@bubibubi Great! Do it until Sunday. Otherwise, I will do it myself on Monday.

If you have ideas for open source organization names (that are available), pitch them here first, so we can all decide on it.

All three of us need to be owners of the new org. You don't need to change/commit any files to match the new repo. We will take care of it, once the transfer has been done.

So sorry guys that I can't help you.

No worries. Will admit its been lonely in here with mostly just me around.

Only suggestion I have at the moment is something like: ~~CyrrusRed~~ CirrusRed

Only suggestion I have at the moment is something like: ~~CyrrusRed~~ CirrusRed

I would be fine with that. (Would also implicitly provide us with a primary color and maybe even a shape for things like a logo etc.)

Only suggestion I have at the moment is something like: ~~CyrrusRed~~ CirrusRed

I would be fine with that. (Would also implicitly provide us with a primary color and maybe even a shape for things like a logo etc.)

Actually, just realised I misspelt it. Should be CirrusRed.

MS Access originally went by the codename of Cirrus and the JET Database engine was also referred to as Jet Red. (Therre was a Jet Blue that was meant to supersede it, but it became the Extensible Storage Engine used in Exchange and Windows Search)

Ok for CirrusRed then!!! Don't ask me to draw a logo. I draw even worst than I write code 😆 I wait till tomorrow afternoon GMT just to be sure about name.

Should I also move the provider for EF 6? I'm considering it at end of life.

Great, its CirrusRed then.

Logo can come later 😄

Should I also move the provider for EF 6?

Sounds good. I think anything topic related makes sense.

Bad news... CirrusRed is already taken. We need other ideas...

Bad news... CirrusRed is already taken.

On no.

• RedCirrus
• JetRed

JetRed would be fine too, but it is taken, as is RedCirrus. CirrusBlue is still available.

If it should be a red-tone, we could use a name for some specific shade of red. There are many out there.

The only reason why the colour was red, was because the version of JET for mdb was called Jet Red. Got to think of other suggestions now

So guys, other ideas?

• CirrusBlue
• CirrusRedNet (or some other options)
• ???

Could add a dash somewhere

• Cirrus-Red
• CirrusRed-Net (might be the best option. don't think we can use the . in it so the dash is probably next best)

CirrusRed-Net and CirrusRedNet is both fine with me (and both are available).

(Note: For namespaces and places where dashes are not allowed, CirrusRed-Net would implicitly become CirrusRedNet.)

At least as long as nobody thinks that red net sounds like redneck. Otherwise, the Net could be replaced with Core.

There are also JetRedNet and JetRed-Net available, though they are a mouthful. There are also JetRedCore and JetRed-Core available.

In case we don't want to use a suffix like Net, there are other cloud types available, like CirrostratusRed or StratusRed.

We could also just put an Org at the end. CirrusRedOrg, CirrusRed-Org, JetRedOrg and JetRed-Org are all available (and their domain names too, btw.).

My preferred are

• CirrusRedOrg
• Cirrus-Red

The domains cirrusred.org and cirrus-red.org are both available.

@ChrisJollyAU , we need only your ok!

CirrusRedOrg should be fine

It's CirrusRedOrg then.

(THIS IS THE FIRST COMMENT ON THE NEW ORGANIZATION 😄 )

Ok, done. You are organization owners. When transferring I noted I could also change the name.

According with your suggestions I'd like to transfer also JetEntityFrameworkProvider that is the EF6 provider Probably is better that I also change the name according namings to EF6 also if we won't change the namespace. What do you think about transfer it (just to be sure) and changing name?

Can bring that in if you want. It is pretty much historical by now so might want to set it to archived status. Otherwise can just append .EF6 to its name

@lauxjpn Have disable the option to create a merge commit and added a protection rule to the master branch requiring linear history

I'll update the CI later today.

I sent out a couple of invitations for the new myget.org feeds.

I also created an organization account for nuget.org and made it one of the owners of the existing packages. @bubibubi I added you as an admin to the new nuget.org organization. @ChrisJollyAU If you post (or send me) your nuget.org username, I'll do the same for your account.

The nuget.org organization required an internal email address, so I created a dedicated one. If you want emails forwarded from that email address to your personal ones, just say so and I'll put them in as forwarding targets.

LAST STEPS

1. I've just bought the domain cirrusred.org. If we'd like to do something the domain is our.
2. We should also update the EF Core providers documentation. https://learn.microsoft.com/en-us/ef/core/providers/?tabs=dotnet-core-cli

I did have it on my mental to do list to get the compatible version updated (was aiming for when v8 was out)

1. I've just bought the domain cirrusred.org. If we'd like to do something the domain is our.

@bubibubi Just let it redirect to this repo for now.

Anything more to do on this topic? @lauxjpn @bubibubi