With the consolidation/renaming about to happen in .NET, any objections to us renaming this repo to EFCore.PG? The projects are already all named that way and the full name is a lot to type! Nuget would obviously remain unchanged...
roji
All 4 comments
Should we just match dotnet/efcore by going to dotnet/efcore.pg (i.e. lowercase)?
austindrenski
on 9 Oct 2019
Maybe :) I slightly prefer EFCore.PG because that's the name used internally for the projects and it's the general .NET naming standard. Let's see what @YohDeadfall thinks.
roji
on 9 Oct 2019
I like @austindrenski's suggestion, because it's not only follows the naming rule in .NET organisation where EF resides, but it's also our naming style. Take a look at npgsql/npgsql, npgsql/doc, or at recently created by you npgsql/livedocs.
YohDeadfall
on 10 Oct 2019
OK, renamed to efcore.pg (note that github redirects from the old name).
roji
on 14 Oct 2019
Related issues
rakeshkotha
路
3Comments
guoyongchang
路
3Comments
newbiecse
路
4Comments
Joseph-Anthony-King
路
3Comments
bikeladam
路
3Comments
Most helpful comment
OK, renamed to efcore.pg (note that github redirects from the old name).