Based on the marketing guidelines a certain company is now using for a
different Apache project, I think the simplest way to avoid issues would be
to include a trademark disclaimer on pages including the name log4net as
well as making sure to call it "Apache log4net" in titles and such. A
disclaime
Thanks for sharing this idea! I'm a great fan of this. Please do not
misunderstand my late response, lately spare time has become really rare,
sorry. Further I hope that in the near future, we may decide to split up
log4net into multiple packages. This trend can be observed about
everywhere, also l
It certainly sounds like a good idea. As for sub prefixes, that's an
interesting question because there would be Apache trademark issues there
potentially, though I'm not entirely sure about that and would need to
investigate further.
On 28 April 2018 at 00:27, Sean Rose wrote:
> Now that NuGet
Now that NuGet has package ID prefix reservation
(https://docs.microsoft.com/en-us/nuget/reference/id-prefix-reservation) are
there plans to reserve the log4net.* prefix?
If so, will a particular sub prefix be left available for community created
packages?
For example:
- log4net.Community
