Convert account into an organization or create a new organization and move the project to it

[lauxjpn]

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

[lauxjpn]

@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

[lauxjpn]

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

@bubibubi Please confirm. Thank you.

[lauxjpn]

@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.

[ChrisJollyAU]

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

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

[lauxjpn]

@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.

[bubibubi]

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).

[lauxjpn]

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.

[ChrisJollyAU]

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

[lauxjpn]

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.)

[ChrisJollyAU]

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)