Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

2018-07-19 Thread sean . covel 
Dominik,

There are a number of issues in your tracker that are directly related to 
sticking with NetStandard 1.3.  That was an early release and must have been 
painful to try to do a full implementation of Log4Net.  2 issues dear to me are 
Variable Expansion (Environment.GetEnvironmentVariable was not implemented in 
1.3, but was in 1.4) and Line Numbers (StackTrace in 1.3 was not fully 
implemented, but was added by 1.5). 

Personally I see NetStandard 2.0 as the first release where a large project 
could be ported, or started from scratch in .Net Core.  It finally has the 
features and the performance to be a contender with .Net and other languages 
(NodeJs, Java, etc).  We're coding on Windows/Mac and deploying on RHEL 7.  
Having a full implementation of log4net is very important.  NetStandard 1.3 
implemented "most" of log4net.  NetStandard could bring the rest of the missing 
features.

BTW, some list of what is missing might be good.  Unless i missed it, it's left 
up to the user to discover.

Thanks,

Sean   

On 2018/06/28 06:31:26, Dominik Psenner  wrote: 
> Hi Bart,
> 
> thanks for your interest in log4net. There's an issue for this and we 
> have an open pull request that adds this target. We have however no plan 
> yet of when this should happen. By targeting log4net against 
> netstandard-1.3 it can be referenced from that netstandard and any 
> netstandard from that onwards. Therefore we do not see any functional 
> requirement that explains of why we should add netstandard-2.0 as a 
> target. Would you like to join the mailing list (dev@logging.apache.org) 
> to explain further why you would like to have log4net add the 
> netstandard-2.0 target on top of netstandard-1.3?
> 
> Best regards,
> Dominik
> 
> 
> 
>  Forwarded Message 
> Subject:  [NuGet Gallery] Message for owners of the package 'log4net'
> Date: Wed, 27 Jun 2018 22:01:04 +
> From: NuGet Gallery 
> Reply-To: Logging PMC , bartsipes 
> 
> To:   Apache.Logging 
> 
> 
> 
> _User bartsipes <[disclosed-email]> sends the following message to the owners 
> of Package '[log4net 2.0.8](https://www.nuget.org/packages/log4net/2.0.8)'._
> 
> Hi, will you be updating log4net to target .NET Standard 2.0 any time soon?
> 
> Thanks, Bart.
> 
> ---
> 
>  To stop receiving contact emails as an owner of this package, sign in to 
> the NuGet Gallery and
>  [change your email notification settings](https://www.nuget.org/account).
> 
> 
>

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

2018-07-20 Thread Dominik Psenner 



On 2018-07-19 22:17, sean.co...@gmail.com wrote:

Dominik,

There are a number of issues in your tracker that are directly related to 
sticking with NetStandard 1.3.  That was an early release and must have been 
painful to try to do a full implementation of Log4Net.  2 issues dear to me are 
Variable Expansion (Environment.GetEnvironmentVariable was not implemented in 
1.3, but was in 1.4) and Line Numbers (StackTrace in 1.3 was not fully 
implemented, but was added by 1.5).

Personally I see NetStandard 2.0 as the first release where a large project could be 
ported, or started from scratch in .Net Core.  It finally has the features and the 
performance to be a contender with .Net and other languages (NodeJs, Java, etc).  We're 
coding on Windows/Mac and deploying on RHEL 7.  Having a full implementation of log4net 
is very important.  NetStandard 1.3 implemented "most" of log4net.  NetStandard 
could bring the rest of the missing features.

BTW, some list of what is missing might be good.  Unless i missed it, it's left 
up to the user to discover.


Hi Sean,

I love to see your interest in log4net and I'll gladly help with 
information and guidance where ever I can.


The netstandard-1.3 target came in as a patch. I'm afraid the original 
contributor will not maintain that contribution. Personally, I would 
drop the support for the netstandard-1.3 target and replace it with 
netstandard-2.0. I also see netstandard-2.0 as a good candidate to 
become the one and only supported target framework. This would greatly 
reduce the maintenance hell we're currently in because of the dozens of 
framework targets that log4net currently supports. Unfortunately such a 
decision would break compatibility with previous releases and would also 
drop the support for long living targets like net-2.0. Further it is far 
beyond the reach of any future release with the human resources that the 
project has available at the moment. This means that it is left up to 
the community to decide about the future of log4net. As stated in a 
previous comment about this topic, I also envision to re-shape log4net 
into a core assembly along with various satellite assemblies that 
provide appenders and other functionality. Such a move can be made when 
the community decides to break backwards compatibility.


I'm willing to invest time into these topics and am intrigued to look 
forward to the future of this project. At the same time I see it as a 
requirement that more people step up to help shaping the future of 
log4net. Until today I've invested into reducing the number of hurdles 
developers have to face when starting to contribute to log4net, for 
example by improving the continuous integration. Unfortunately this has 
not yet produced the results that I hoped for but I'll keep that task up 
with the time that I can donate to the community.


Cheers,
Dominik

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

2020-09-07 Thread Davyd McColl 

Hi Ralph

I'll investigate this today. I'd like more information, particularly 
configuration and, eg if the ado.net appender is used, table structures.


Joseph, please open a ticket at  
https://issues.apache.org/jira/browse/LOG4NET to help me track this.


-d


On September 7, 2020 23:35:12 Ralph Goers  wrote:

For some reason all messages from NuGet are routed to the Apache Logging 
PMC list. This one clearly does not need to be private. Just know that the 
person who sent this is apparently not subscribed to the ASF mailing lists 
so won’t see a response unless he is cc’d.


I’m not familiar with NuGet but it sure would be nice if they could be 
pointed to our mailing lists. The PMC has gotten a fair number of these 
that we have tried to respond to.


Ralph


Begin forwarded message:

From: NuGet Gallery 
Subject: [NuGet Gallery] Message for owners of the package 'log4net'
Date: September 7, 2020 at 2:25:32 PM MST
To: 
Reply-To: "Logging PMC" 
Reply-To: 

User jmitola  sends the following message to the 
owners of Package 'log4net 2.0.8 
'.


Has version 2.0.9 been thoroughly tested running in .Net framework 4.6? I 
ask because I recently upgraded from 2.0.8 which was working with no issues 
to version 2.0.9. Now, it completely crashes the application pool in IIS 
for any application running .Net framework v4.5 and higher which has 
referenced the log4net library v2.0.9. Furthermore, it will not output any 
error logs even with internal logging option turned on. Do you have any 
suggestions as to how I could debug this?


Thanks, Joseph

To stop receiving contact emails as an owner of this package, sign in to 
the NuGet Gallery and change your email notification settings 
.


Privacy Statement 
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052 USA

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

2020-09-07 Thread Davyd McColl 
Ralph

I understand that the emails provide a bit of workload, and I'm trying to 
figure out a solution to help everyone -- obviously there are people who submit 
mails (and wonder where they went) and people who have to handle those mails.

We use Trello at work and have built our own custom solution which bridges 
Trello and email (called Sendboard). It looks like 
https://community.atlassian.com/t5/Jira-questions/create-ticket-from-email-in-jira/qaq-p/806165
 gives an idea of how to do something similar for JIRA. Would that perhaps help 
to make things flow a bit better?

Unlike npmjs.com, nuget.org doesn't provide a mechanism for a quick link to an 
issues board -- the best I can see is either the project url or the associated 
email address (which is probably why most people reach out on email). So the 
possible solutions I see here are to 
- automate handling the email
- make the issue reporting url clearer on the project page.

The project url links to logging.apache.org/log4net -- perhaps I should update 
the landing page to include a more obvious link to reporting issues? There is 
already a link in the project's README.md which surfaces on GitHub. At the end 
of the day, I'd like the situation to be better for both the PMC and users. I'm 
open to any suggestions.

-d

On 2020/09/08 07:24:25, Davyd McColl  wrote:
Hi Ralph
I'll investigate this today. I'd like more information, particularly 
configuration and, eg if the ado.net [http://ado.net] appender is used, table 
structures.
Joseph, please open a ticket at  https://issues.apache.org/jira/browse/LOG4NET 
[https://issues.apache.org/jira/browse/LOG4NET] to help me track this.
-d

On September 7, 2020 23:35:12 Ralph Goers  wrote:
For some reason all messages from NuGet are routed to the Apache Logging PMC 
list. This one clearly does not need to be private. Just know that the person 
who sent this is apparently not subscribed to the ASF mailing lists so won’t 
see a response unless he is cc’d.
I’m not familiar with NuGet but it sure would be nice if they could be pointed 
to our mailing lists. The PMC has gotten a fair number of these that we have 
tried to respond to.
Ralph
Begin forwarded message:
From: NuGet Gallery 
Subject: [NuGet Gallery] Message for owners of the package 'log4net'
Date: September 7, 2020 at 2:25:32 PM MST
To: 
Reply-To: "Logging PMC" 
Reply-To: 
User jmitola  sends the following message to the owners 
of Package 'log4net 2.0.8 '.
Has version 2.0.9 been thoroughly tested running in .Net framework 4.6? I ask 
because I recently upgraded from 2.0.8 which was working with no issues to 
version 2.0.9. Now, it completely crashes the application pool in IIS for any 
application running .Net framework v4.5 and higher which has referenced the 
log4net library v2.0.9. Furthermore, it will not output any error logs even 
with internal logging option turned on. Do you have any suggestions as to how I 
could debug this?
Thanks, Joseph
To stop receiving contact emails as an owner of this package, sign in to the 
NuGet Gallery and change your email notification settings 
.
Privacy Statement 
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052 USA

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

2020-09-08 Thread Dominik Psenner 
In the past security vulnerabilities were reported via nuget and it is not
a good idea to publish those in an automated way.

I suggest to update the nuget project documentation and prominently point
to our mailing lists and discourage the communication via nuget. Users may
continue sending messages via nuget to pmc but hopefully the volume is
reduced. Unfortunately most users consume log4net via nuget and apparently
do not care about the mailing list and/or the official project website.

--
Sent from my phone. Typos are a kind gift to anyone who happens to find
them.

On Tue, Sep 8, 2020, 08:34 Davyd McColl  wrote:

> Ralph
>
> I understand that the emails provide a bit of workload, and I'm trying to
> figure out a solution to help everyone -- obviously there are people who
> submit mails (and wonder where they went) and people who have to handle
> those mails.
>
> We use Trello at work and have built our own custom solution which bridges
> Trello and email (called Sendboard). It looks like
> https://community.atlassian.com/t5/Jira-questions/create-ticket-from-email-in-jira/qaq-p/806165
> gives an idea of how to do something similar for JIRA. Would that perhaps
> help to make things flow a bit better?
>
> Unlike npmjs.com, nuget.org doesn't provide a mechanism for a quick link
> to an issues board -- the best I can see is either the project url or the
> associated email address (which is probably why most people reach out on
> email). So the possible solutions I see here are to
> - automate handling the email
> - make the issue reporting url clearer on the project page.
>
> The project url links to logging.apache.org/log4net -- perhaps I should
> update the landing page to include a more obvious link to reporting issues?
> There is already a link in the project's README.md which surfaces on
> GitHub. At the end of the day, I'd like the situation to be better for both
> the PMC and users. I'm open to any suggestions.
>
> -d
>
> On 2020/09/08 07:24:25, Davyd McColl  wrote:
> Hi Ralph
> I'll investigate this today. I'd like more information, particularly
> configuration and, eg if the ado.net [http://ado.net] appender is used,
> table structures.
> Joseph, please open a ticket at
> https://issues.apache.org/jira/browse/LOG4NET [
> https://issues.apache.org/jira/browse/LOG4NET] to help me track this.
> -d
>
> On September 7, 2020 23:35:12 Ralph Goers 
> wrote:
> For some reason all messages from NuGet are routed to the Apache Logging
> PMC list. This one clearly does not need to be private. Just know that the
> person who sent this is apparently not subscribed to the ASF mailing lists
> so won’t see a response unless he is cc’d.
> I’m not familiar with NuGet but it sure would be nice if they could be
> pointed to our mailing lists. The PMC has gotten a fair number of these
> that we have tried to respond to.
> Ralph
> Begin forwarded message:
> From: NuGet Gallery 
> Subject: [NuGet Gallery] Message for owners of the package 'log4net'
> Date: September 7, 2020 at 2:25:32 PM MST
> To: 
> Reply-To: "Logging PMC" 
> Reply-To: 
> User jmitola  sends the following message to the
> owners of Package 'log4net 2.0.8 <
> https://www.nuget.org/packages/log4net/2.0.8 [
> https://www.nuget.org/packages/log4net/2.0.8]>'.
> Has version 2.0.9 been thoroughly tested running in .Net framework 4.6? I
> ask because I recently upgraded from 2.0.8 which was working with no issues
> to version 2.0.9. Now, it completely crashes the application pool in IIS
> for any application running .Net framework v4.5 and higher which has
> referenced the log4net library v2.0.9. Furthermore, it will not output any
> error logs even with internal logging option turned on. Do you have any
> suggestions as to how I could debug this?
> Thanks, Joseph
> To stop receiving contact emails as an owner of this package, sign in to
> the NuGet Gallery and change your email notification settings <
> https://www.nuget.org/account [https://www.nuget.org/account]>.
> Privacy Statement  https://go.microsoft.com/fwlink/?LinkId=521839]>
> Microsoft Corporation
> One Microsoft Way
> Redmond, WA 98052 USA
>
>

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

2020-09-08 Thread Matt Sicker 
The main problem with sending nuget info to the PMC is that nobody in
the PMC are working on log4net besides validating releases ;)

On Tue, 8 Sep 2020 at 04:37, Dominik Psenner  wrote:
>
> In the past security vulnerabilities were reported via nuget and it is not
> a good idea to publish those in an automated way.
>
> I suggest to update the nuget project documentation and prominently point
> to our mailing lists and discourage the communication via nuget. Users may
> continue sending messages via nuget to pmc but hopefully the volume is
> reduced. Unfortunately most users consume log4net via nuget and apparently
> do not care about the mailing list and/or the official project website.
>
> --
> Sent from my phone. Typos are a kind gift to anyone who happens to find
> them.
>
> On Tue, Sep 8, 2020, 08:34 Davyd McColl  wrote:
>
> > Ralph
> >
> > I understand that the emails provide a bit of workload, and I'm trying to
> > figure out a solution to help everyone -- obviously there are people who
> > submit mails (and wonder where they went) and people who have to handle
> > those mails.
> >
> > We use Trello at work and have built our own custom solution which bridges
> > Trello and email (called Sendboard). It looks like
> > https://community.atlassian.com/t5/Jira-questions/create-ticket-from-email-in-jira/qaq-p/806165
> > gives an idea of how to do something similar for JIRA. Would that perhaps
> > help to make things flow a bit better?
> >
> > Unlike npmjs.com, nuget.org doesn't provide a mechanism for a quick link
> > to an issues board -- the best I can see is either the project url or the
> > associated email address (which is probably why most people reach out on
> > email). So the possible solutions I see here are to
> > - automate handling the email
> > - make the issue reporting url clearer on the project page.
> >
> > The project url links to logging.apache.org/log4net -- perhaps I should
> > update the landing page to include a more obvious link to reporting issues?
> > There is already a link in the project's README.md which surfaces on
> > GitHub. At the end of the day, I'd like the situation to be better for both
> > the PMC and users. I'm open to any suggestions.
> >
> > -d
> >
> > On 2020/09/08 07:24:25, Davyd McColl  wrote:
> > Hi Ralph
> > I'll investigate this today. I'd like more information, particularly
> > configuration and, eg if the ado.net [http://ado.net] appender is used,
> > table structures.
> > Joseph, please open a ticket at
> > https://issues.apache.org/jira/browse/LOG4NET [
> > https://issues.apache.org/jira/browse/LOG4NET] to help me track this.
> > -d
> >
> > On September 7, 2020 23:35:12 Ralph Goers 
> > wrote:
> > For some reason all messages from NuGet are routed to the Apache Logging
> > PMC list. This one clearly does not need to be private. Just know that the
> > person who sent this is apparently not subscribed to the ASF mailing lists
> > so won’t see a response unless he is cc’d.
> > I’m not familiar with NuGet but it sure would be nice if they could be
> > pointed to our mailing lists. The PMC has gotten a fair number of these
> > that we have tried to respond to.
> > Ralph
> > Begin forwarded message:
> > From: NuGet Gallery 
> > Subject: [NuGet Gallery] Message for owners of the package 'log4net'
> > Date: September 7, 2020 at 2:25:32 PM MST
> > To: 
> > Reply-To: "Logging PMC" 
> > Reply-To: 
> > User jmitola  sends the following message to the
> > owners of Package 'log4net 2.0.8 <
> > https://www.nuget.org/packages/log4net/2.0.8 [
> > https://www.nuget.org/packages/log4net/2.0.8]>'.
> > Has version 2.0.9 been thoroughly tested running in .Net framework 4.6? I
> > ask because I recently upgraded from 2.0.8 which was working with no issues
> > to version 2.0.9. Now, it completely crashes the application pool in IIS
> > for any application running .Net framework v4.5 and higher which has
> > referenced the log4net library v2.0.9. Furthermore, it will not output any
> > error logs even with internal logging option turned on. Do you have any
> > suggestions as to how I could debug this?
> > Thanks, Joseph
> > To stop receiving contact emails as an owner of this package, sign in to
> > the NuGet Gallery and change your email notification settings <
> > https://www.nuget.org/account [https://www.nuget.org/account]>.
> > Privacy Statement  > https://go.microsoft.com/fwlink/?LinkId=521839]>
> > Microsoft Corporation
> > One Microsoft Way
> > Redmond, WA 98052 USA
> >
> >



-- 
Matt Sicker

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

2020-09-08 Thread Davyd McColl 
What if there was another Apache email address that messages were sent to, 
and multiple people could observe that account? I don't mind being one of 
the lucky ones if it will help (:


-d


On September 8, 2020 17:47:57 Matt Sicker  wrote:


The main problem with sending nuget info to the PMC is that nobody in
the PMC are working on log4net besides validating releases ;)

On Tue, 8 Sep 2020 at 04:37, Dominik Psenner  wrote:


In the past security vulnerabilities were reported via nuget and it is not
a good idea to publish those in an automated way.

I suggest to update the nuget project documentation and prominently point
to our mailing lists and discourage the communication via nuget. Users may
continue sending messages via nuget to pmc but hopefully the volume is
reduced. Unfortunately most users consume log4net via nuget and apparently
do not care about the mailing list and/or the official project website.

--
Sent from my phone. Typos are a kind gift to anyone who happens to find
them.

On Tue, Sep 8, 2020, 08:34 Davyd McColl  wrote:

> Ralph
>
> I understand that the emails provide a bit of workload, and I'm trying to
> figure out a solution to help everyone -- obviously there are people who
> submit mails (and wonder where they went) and people who have to handle
> those mails.
>
> We use Trello at work and have built our own custom solution which bridges
> Trello and email (called Sendboard). It looks like
> 
https://community.atlassian.com/t5/Jira-questions/create-ticket-from-email-in-jira/qaq-p/806165

> gives an idea of how to do something similar for JIRA. Would that perhaps
> help to make things flow a bit better?
>
> Unlike npmjs.com, nuget.org doesn't provide a mechanism for a quick link
> to an issues board -- the best I can see is either the project url or the
> associated email address (which is probably why most people reach out on
> email). So the possible solutions I see here are to
> - automate handling the email
> - make the issue reporting url clearer on the project page.
>
> The project url links to logging.apache.org/log4net -- perhaps I should
> update the landing page to include a more obvious link to reporting issues?
> There is already a link in the project's README.md which surfaces on
> GitHub. At the end of the day, I'd like the situation to be better for both
> the PMC and users. I'm open to any suggestions.
>
> -d
>
> On 2020/09/08 07:24:25, Davyd McColl  wrote:
> Hi Ralph
> I'll investigate this today. I'd like more information, particularly
> configuration and, eg if the ado.net [http://ado.net] appender is used,
> table structures.
> Joseph, please open a ticket at
> https://issues.apache.org/jira/browse/LOG4NET [
> https://issues.apache.org/jira/browse/LOG4NET] to help me track this.
> -d
>
> On September 7, 2020 23:35:12 Ralph Goers 
> wrote:
> For some reason all messages from NuGet are routed to the Apache Logging
> PMC list. This one clearly does not need to be private. Just know that the
> person who sent this is apparently not subscribed to the ASF mailing lists
> so won’t see a response unless he is cc’d.
> I’m not familiar with NuGet but it sure would be nice if they could be
> pointed to our mailing lists. The PMC has gotten a fair number of these
> that we have tried to respond to.
> Ralph
> Begin forwarded message:
> From: NuGet Gallery 
> Subject: [NuGet Gallery] Message for owners of the package 'log4net'
> Date: September 7, 2020 at 2:25:32 PM MST
> To: 
> Reply-To: "Logging PMC" 
> Reply-To: 
> User jmitola  sends the following message to the
> owners of Package 'log4net 2.0.8 <
> https://www.nuget.org/packages/log4net/2.0.8 [
> https://www.nuget.org/packages/log4net/2.0.8]>'.
> Has version 2.0.9 been thoroughly tested running in .Net framework 4.6? I
> ask because I recently upgraded from 2.0.8 which was working with no issues
> to version 2.0.9. Now, it completely crashes the application pool in IIS
> for any application running .Net framework v4.5 and higher which has
> referenced the log4net library v2.0.9. Furthermore, it will not output any
> error logs even with internal logging option turned on. Do you have any
> suggestions as to how I could debug this?
> Thanks, Joseph
> To stop receiving contact emails as an owner of this package, sign in to
> the NuGet Gallery and change your email notification settings <
> https://www.nuget.org/account [https://www.nuget.org/account]>.
> Privacy Statement  https://go.microsoft.com/fwlink/?LinkId=521839]>
> Microsoft Corporation
> One Microsoft Way
> Redmond, WA 98052 USA
>
>




--
Matt Sicker

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

2020-09-08 Thread Matt Sicker 
That's this dev list! Though if we need a separate mailing list, we
can always create more.

On Tue, 8 Sep 2020 at 11:54, Davyd McColl  wrote:
>
> What if there was another Apache email address that messages were sent to,
> and multiple people could observe that account? I don't mind being one of
> the lucky ones if it will help (:
>
> -d
>
>
> On September 8, 2020 17:47:57 Matt Sicker  wrote:
>
> > The main problem with sending nuget info to the PMC is that nobody in
> > the PMC are working on log4net besides validating releases ;)
> >
> > On Tue, 8 Sep 2020 at 04:37, Dominik Psenner  wrote:
> >>
> >> In the past security vulnerabilities were reported via nuget and it is not
> >> a good idea to publish those in an automated way.
> >>
> >> I suggest to update the nuget project documentation and prominently point
> >> to our mailing lists and discourage the communication via nuget. Users may
> >> continue sending messages via nuget to pmc but hopefully the volume is
> >> reduced. Unfortunately most users consume log4net via nuget and apparently
> >> do not care about the mailing list and/or the official project website.
> >>
> >> --
> >> Sent from my phone. Typos are a kind gift to anyone who happens to find
> >> them.
> >>
> >> On Tue, Sep 8, 2020, 08:34 Davyd McColl  wrote:
> >>
> >> > Ralph
> >> >
> >> > I understand that the emails provide a bit of workload, and I'm trying to
> >> > figure out a solution to help everyone -- obviously there are people who
> >> > submit mails (and wonder where they went) and people who have to handle
> >> > those mails.
> >> >
> >> > We use Trello at work and have built our own custom solution which 
> >> > bridges
> >> > Trello and email (called Sendboard). It looks like
> >> >
> >> https://community.atlassian.com/t5/Jira-questions/create-ticket-from-email-in-jira/qaq-p/806165
> >> > gives an idea of how to do something similar for JIRA. Would that perhaps
> >> > help to make things flow a bit better?
> >> >
> >> > Unlike npmjs.com, nuget.org doesn't provide a mechanism for a quick link
> >> > to an issues board -- the best I can see is either the project url or the
> >> > associated email address (which is probably why most people reach out on
> >> > email). So the possible solutions I see here are to
> >> > - automate handling the email
> >> > - make the issue reporting url clearer on the project page.
> >> >
> >> > The project url links to logging.apache.org/log4net -- perhaps I should
> >> > update the landing page to include a more obvious link to reporting 
> >> > issues?
> >> > There is already a link in the project's README.md which surfaces on
> >> > GitHub. At the end of the day, I'd like the situation to be better for 
> >> > both
> >> > the PMC and users. I'm open to any suggestions.
> >> >
> >> > -d
> >> >
> >> > On 2020/09/08 07:24:25, Davyd McColl  wrote:
> >> > Hi Ralph
> >> > I'll investigate this today. I'd like more information, particularly
> >> > configuration and, eg if the ado.net [http://ado.net] appender is used,
> >> > table structures.
> >> > Joseph, please open a ticket at
> >> > https://issues.apache.org/jira/browse/LOG4NET [
> >> > https://issues.apache.org/jira/browse/LOG4NET] to help me track this.
> >> > -d
> >> >
> >> > On September 7, 2020 23:35:12 Ralph Goers 
> >> > wrote:
> >> > For some reason all messages from NuGet are routed to the Apache Logging
> >> > PMC list. This one clearly does not need to be private. Just know that 
> >> > the
> >> > person who sent this is apparently not subscribed to the ASF mailing 
> >> > lists
> >> > so won’t see a response unless he is cc’d.
> >> > I’m not familiar with NuGet but it sure would be nice if they could be
> >> > pointed to our mailing lists. The PMC has gotten a fair number of these
> >> > that we have tried to respond to.
> >> > Ralph
> >> > Begin forwarded message:
> >> > From: NuGet Gallery 
> >> > Subject: [NuGet Gallery] Message for owners of the package 'log4net'
> >> > Date: September 7, 2020 at 2:25:32 PM MST
> >> > To: 
> >> > Reply-To: "Logging PMC" 
> >> > Reply-To: 
> >> > User jmitola  sends the following message to the
> >> > owners of Package 'log4net 2.0.8 <
> >> > https://www.nuget.org/packages/log4net/2.0.8 [
> >> > https://www.nuget.org/packages/log4net/2.0.8]>'.
> >> > Has version 2.0.9 been thoroughly tested running in .Net framework 4.6? I
> >> > ask because I recently upgraded from 2.0.8 which was working with no 
> >> > issues
> >> > to version 2.0.9. Now, it completely crashes the application pool in IIS
> >> > for any application running .Net framework v4.5 and higher which has
> >> > referenced the log4net library v2.0.9. Furthermore, it will not output 
> >> > any
> >> > error logs even with internal logging option turned on. Do you have any
> >> > suggestions as to how I could debug this?
> >> > Thanks, Joseph
> >> > To stop receiving contact emails as an owner of this package, sign in to
> >> > the NuGet Gallery and change your email notification settings <

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

2020-09-08 Thread Davyd McColl 
True that, but I tried to initiate a vote the other day from my work mail 
by mistake and the message was bounced, so I'm not sure what rules apply to 
this list. If it's fairly open, it might be a plan to update the associated 
email address on nuget to the dev list.


-d


On September 8, 2020 19:08:55 Matt Sicker  wrote:


That's this dev list! Though if we need a separate mailing list, we
can always create more.

On Tue, 8 Sep 2020 at 11:54, Davyd McColl  wrote:


What if there was another Apache email address that messages were sent to,
and multiple people could observe that account? I don't mind being one of
the lucky ones if it will help (:

-d


On September 8, 2020 17:47:57 Matt Sicker  wrote:

> The main problem with sending nuget info to the PMC is that nobody in
> the PMC are working on log4net besides validating releases ;)
>
> On Tue, 8 Sep 2020 at 04:37, Dominik Psenner  wrote:
>>
>> In the past security vulnerabilities were reported via nuget and it is not
>> a good idea to publish those in an automated way.
>>
>> I suggest to update the nuget project documentation and prominently point
>> to our mailing lists and discourage the communication via nuget. Users may
>> continue sending messages via nuget to pmc but hopefully the volume is
>> reduced. Unfortunately most users consume log4net via nuget and apparently
>> do not care about the mailing list and/or the official project website.
>>
>> --
>> Sent from my phone. Typos are a kind gift to anyone who happens to find
>> them.
>>
>> On Tue, Sep 8, 2020, 08:34 Davyd McColl  wrote:
>>
>> > Ralph
>> >
>> > I understand that the emails provide a bit of workload, and I'm trying to
>> > figure out a solution to help everyone -- obviously there are people who
>> > submit mails (and wonder where they went) and people who have to handle
>> > those mails.
>> >
>> > We use Trello at work and have built our own custom solution which bridges
>> > Trello and email (called Sendboard). It looks like
>> >
>> 
https://community.atlassian.com/t5/Jira-questions/create-ticket-from-email-in-jira/qaq-p/806165

>> > gives an idea of how to do something similar for JIRA. Would that perhaps
>> > help to make things flow a bit better?
>> >
>> > Unlike npmjs.com, nuget.org doesn't provide a mechanism for a quick link
>> > to an issues board -- the best I can see is either the project url or the
>> > associated email address (which is probably why most people reach out on
>> > email). So the possible solutions I see here are to
>> > - automate handling the email
>> > - make the issue reporting url clearer on the project page.
>> >
>> > The project url links to logging.apache.org/log4net -- perhaps I should
>> > update the landing page to include a more obvious link to reporting 
issues?

>> > There is already a link in the project's README.md which surfaces on
>> > GitHub. At the end of the day, I'd like the situation to be better for 
both

>> > the PMC and users. I'm open to any suggestions.
>> >
>> > -d
>> >
>> > On 2020/09/08 07:24:25, Davyd McColl  wrote:
>> > Hi Ralph
>> > I'll investigate this today. I'd like more information, particularly
>> > configuration and, eg if the ado.net [http://ado.net] appender is used,
>> > table structures.
>> > Joseph, please open a ticket at
>> > https://issues.apache.org/jira/browse/LOG4NET [
>> > https://issues.apache.org/jira/browse/LOG4NET] to help me track this.
>> > -d
>> >
>> > On September 7, 2020 23:35:12 Ralph Goers 
>> > wrote:
>> > For some reason all messages from NuGet are routed to the Apache Logging
>> > PMC list. This one clearly does not need to be private. Just know that the
>> > person who sent this is apparently not subscribed to the ASF mailing lists
>> > so won’t see a response unless he is cc’d.
>> > I’m not familiar with NuGet but it sure would be nice if they could be
>> > pointed to our mailing lists. The PMC has gotten a fair number of these
>> > that we have tried to respond to.
>> > Ralph
>> > Begin forwarded message:
>> > From: NuGet Gallery 
>> > Subject: [NuGet Gallery] Message for owners of the package 'log4net'
>> > Date: September 7, 2020 at 2:25:32 PM MST
>> > To: 
>> > Reply-To: "Logging PMC" 
>> > Reply-To: 
>> > User jmitola  sends the following message to the
>> > owners of Package 'log4net 2.0.8 <
>> > https://www.nuget.org/packages/log4net/2.0.8 [
>> > https://www.nuget.org/packages/log4net/2.0.8]>'.
>> > Has version 2.0.9 been thoroughly tested running in .Net framework 4.6? I
>> > ask because I recently upgraded from 2.0.8 which was working with no 
issues

>> > to version 2.0.9. Now, it completely crashes the application pool in IIS
>> > for any application running .Net framework v4.5 and higher which has
>> > referenced the log4net library v2.0.9. Furthermore, it will not output any
>> > error logs even with internal logging option turned on. Do you have any
>> > suggestions as to how I could debug this?
>> > Thanks, Joseph
>> > To stop receiving contact emails as an owner of this pa

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

2020-09-08 Thread Dominik Psenner 
This reflects my impression that the volume of individuals that do not know
the mechanics of the mailing lists has increased. I observe that with the
increased number of messages that need to be moderated. Many come from
individuals that are not subscribes. Others come from individuals that send
messages from multiple email addresses. And others come from nuget. In all
cases we can improve the situation by improving the documentation.

Despite that, I repeat that a moderator must act as an intelligent proxy
that keeps confidential information private and moves anything else to dev.
To me that choice cannot be made when moderating the message because a
reject from the moderator causes the  message to bounce and by asf rules it
would never have existed. That was the reasoning when I chose private as
the email when establishing the nuget organization.

--
Sent from my phone. Typos are a kind gift to anyone who happens to find
them.

On Tue, Sep 8, 2020, 20:04 Davyd McColl  wrote:

> True that, but I tried to initiate a vote the other day from my work mail
> by mistake and the message was bounced, so I'm not sure what rules apply
> to
> this list. If it's fairly open, it might be a plan to update the
> associated
> email address on nuget to the dev list.
>
> -d
>
>
> On September 8, 2020 19:08:55 Matt Sicker  wrote:
>
> > That's this dev list! Though if we need a separate mailing list, we
> > can always create more.
> >
> > On Tue, 8 Sep 2020 at 11:54, Davyd McColl  wrote:
> >>
> >> What if there was another Apache email address that messages were sent
> to,
> >> and multiple people could observe that account? I don't mind being one
> of
> >> the lucky ones if it will help (:
> >>
> >> -d
> >>
> >>
> >> On September 8, 2020 17:47:57 Matt Sicker  wrote:
> >>
> >> > The main problem with sending nuget info to the PMC is that nobody in
> >> > the PMC are working on log4net besides validating releases ;)
> >> >
> >> > On Tue, 8 Sep 2020 at 04:37, Dominik Psenner 
> wrote:
> >> >>
> >> >> In the past security vulnerabilities were reported via nuget and it
> is not
> >> >> a good idea to publish those in an automated way.
> >> >>
> >> >> I suggest to update the nuget project documentation and prominently
> point
> >> >> to our mailing lists and discourage the communication via nuget.
> Users may
> >> >> continue sending messages via nuget to pmc but hopefully the volume
> is
> >> >> reduced. Unfortunately most users consume log4net via nuget and
> apparently
> >> >> do not care about the mailing list and/or the official project
> website.
> >> >>
> >> >> --
> >> >> Sent from my phone. Typos are a kind gift to anyone who happens to
> find
> >> >> them.
> >> >>
> >> >> On Tue, Sep 8, 2020, 08:34 Davyd McColl  wrote:
> >> >>
> >> >> > Ralph
> >> >> >
> >> >> > I understand that the emails provide a bit of workload, and I'm
> trying to
> >> >> > figure out a solution to help everyone -- obviously there are
> people who
> >> >> > submit mails (and wonder where they went) and people who have to
> handle
> >> >> > those mails.
> >> >> >
> >> >> > We use Trello at work and have built our own custom solution which
> bridges
> >> >> > Trello and email (called Sendboard). It looks like
> >> >> >
> >> >>
> >>
> https://community.atlassian.com/t5/Jira-questions/create-ticket-from-email-in-jira/qaq-p/806165
> >> >> > gives an idea of how to do something similar for JIRA. Would that
> perhaps
> >> >> > help to make things flow a bit better?
> >> >> >
> >> >> > Unlike npmjs.com, nuget.org doesn't provide a mechanism for a
> quick link
> >> >> > to an issues board -- the best I can see is either the project url
> or the
> >> >> > associated email address (which is probably why most people reach
> out on
> >> >> > email). So the possible solutions I see here are to
> >> >> > - automate handling the email
> >> >> > - make the issue reporting url clearer on the project page.
> >> >> >
> >> >> > The project url links to logging.apache.org/log4net -- perhaps I
> should
> >> >> > update the landing page to include a more obvious link to
> reporting
> >> issues?
> >> >> > There is already a link in the project's README.md which surfaces
> on
> >> >> > GitHub. At the end of the day, I'd like the situation to be better
> for
> >> both
> >> >> > the PMC and users. I'm open to any suggestions.
> >> >> >
> >> >> > -d
> >> >> >
> >> >> > On 2020/09/08 07:24:25, Davyd McColl  wrote:
> >> >> > Hi Ralph
> >> >> > I'll investigate this today. I'd like more information,
> particularly
> >> >> > configuration and, eg if the ado.net [http://ado.net] appender is
> used,
> >> >> > table structures.
> >> >> > Joseph, please open a ticket at
> >> >> > https://issues.apache.org/jira/browse/LOG4NET [
> >> >> > https://issues.apache.org/jira/browse/LOG4NET] to help me track
> this.
> >> >> > -d
> >> >> >
> >> >> > On September 7, 2020 23:35:12 Ralph Goers <
> ralph.go...@dslextreme.com>
> >> >> > wrote:
> >> >> > For some reason all messages from NuGet are ro

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

2020-09-18 Thread Davyd McColl 
hm, that's not great ): I'll investigate. Thanks for letting me know!

-d

On 2020/09/18 13:05:58, Dominik Psenner  wrote:
See the message below. Apparently something went wrong during the last
release.
--
Sent from my phone. Typos are a kind gift to anyone who happens to find
them.

-- Forwarded message -
From: NuGet Gallery
Date: Fri, Sep 18, 2020, 12:10
Subject: [NuGet Gallery] Message for owners of the package 'log4net'
To:


*User andyfisher100 >
sends the following message to the owners of Package 'log4net 2.0.10
'.*

When 2.0.10 was released, the version of the dlls was not changed to match
the package version. All of the dlls remain at version 2.0.9
--
* To stop receiving contact emails as an owner of this package, sign in to
the NuGet Gallery and change your email notification settings
. *


Privacy Statement
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052 USA

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

2020-09-18 Thread Davyd McColl 
Ok, I've found the culprit -- there's a lot of assembly version sources which 
mention 2.0.9 -- and I'm not entirely sure why some of them are in this project 
(AssemblyVersionInfo.cpp, AssemblyVersionInfo.js, AssemblyVersionInfo.vb). And 
there are two files which set up assembly version information (AssemblyInfo.cs 
and AssemblyVersionInfo.cs)

I'll clean up, get that into master, and, after verifying that the nupkg is 
properly generated, I'll raise a vote for 2.0.11. There are some minor 
enhancements (again from NicholasNoise) in the project (specifically: a fix for 
an invalid version string for one of the client profile version strings and a 
good few places where StreamWriters weren't being disposed, so it's not for 
nought)

Thanks again for notifying me.

-d

On 2020/09/18 13:10:26, Davyd McColl  wrote:
hm, that's not great ): I'll investigate. Thanks for letting me know!

-d

On 2020/09/18 13:05:58, Dominik Psenner  wrote:
See the message below. Apparently something went wrong during the last
release.
--
Sent from my phone. Typos are a kind gift to anyone who happens to find
them.

-- Forwarded message -
From: NuGet Gallery
Date: Fri, Sep 18, 2020, 12:10
Subject: [NuGet Gallery] Message for owners of the package 'log4net'
To:


*User andyfisher100 >
sends the following message to the owners of Package 'log4net 2.0.10
'.*

When 2.0.10 was released, the version of the dlls was not changed to match
the package version. All of the dlls remain at version 2.0.9
--
* To stop receiving contact emails as an owner of this package, sign in to
the NuGet Gallery and change your email notification settings
. *


Privacy Statement
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052 USA

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

2020-10-23 Thread Davyd McColl 

Hi Dominik

iirc, this was fixed in 2.0.11. 2.0.12, with another fix for current user 
name on !win32, is waiting on one more +1 vote for release.


-d


On October 23, 2020 18:05:18 Dominik Psenner  wrote:


See the message below.
--
Sent from my phone.

-- Forwarded message -
From: NuGet Gallery 
Date: Fri, Oct 23, 2020, 07:51
Subject: [NuGet Gallery] Message for owners of the package 'log4net'
To: 


*User santoshkallatti > sends the following message to
the owners of Package 'log4net 2.0.10
'.*

Hi,

There is an assembly version mismatch in log4net 2.0.10. The assembly's
manifest definition contains 'log4net, Version=2.0.9.0'. May I know why
this version mismatch. Can I get log4net 2.0.10 nuget package with manifest
definition contains 'log4net, Version=2.0.10.0'?

Thanks & Regards Santosh K
--
* To stop receiving contact emails as an owner of this package, sign in to
the NuGet Gallery and change your email notification settings
. *


Privacy Statement 
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052 USA

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

2020-10-24 Thread Dominik Psenner 
Dear Santosh,

please see the answer to Your request below. Please note that Apache
product discussions happen on mailing lists, in this case it is
dev@logging.apache.org. NuGet messages are not an ideal way to communicate
because they reach only a limited subset of the community.

Warm regards,
Dominik

On Fri, 23 Oct 2020 at 20:52, Davyd McColl  wrote:

> Hi Dominik
>
> iirc, this was fixed in 2.0.11. 2.0.12, with another fix for current user
> name on !win32, is waiting on one more +1 vote for release.
>
> -d
>
> On October 23, 2020 18:05:18 Dominik Psenner  wrote:
>
>> See the message below.
>> --
>> Sent from my phone.
>>
>> -- Forwarded message -
>> From: NuGet Gallery 
>> Date: Fri, Oct 23, 2020, 07:51
>> Subject: [NuGet Gallery] Message for owners of the package 'log4net'
>> To: 
>>
>> *User santoshkallatti > > sends the following message
>> to
>> the owners of Package 'log4net 2.0.10
>> '.*
>>
>> Hi,
>>
>> There is an assembly version mismatch in log4net 2.0.10. The assembly's
>> manifest definition contains 'log4net, Version=2.0.9.0'. May I know why
>> this version mismatch. Can I get log4net 2.0.10 nuget package with
>> manifest
>> definition contains 'log4net, Version=2.0.10.0'?
>>
>> Thanks & Regards Santosh K
>> --
>> * To stop receiving contact emails as an owner of this package, sign in to
>> the NuGet Gallery and change your email notification settings
>> . *
>>
>> Privacy Statement 
>> Microsoft Corporation
>> One Microsoft Way
>> Redmond, WA 98052 USA
>>
>

-- 
Dominik Psenner

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

2021-11-05 Thread Davyd McColl 
Apologies - staging docs have not been set live ):

I'll have a look at it now

-d

On 2021/11/05 16:24:55, Volkan Yazıcı  wrote:
I think this message is best suited for this mailing list.
Would anybody from the log4net crew mind addressing the request of John
Bigler, please?

-- Forwarded message -
From: NuGet Gallery
Date: Thu, Nov 4, 2021 at 5:50 PM
Subject: [NuGet Gallery] Message for owners of the package 'log4net'
To:


*User JohnBig > sends the following
message to the owners of Package 'log4net 2.0.13
'.*

I see that version 2.0.13 was released around November 2, 2021, but does
not have any corresponding release notes on
https://logging.apache.org/log4net/release/release-notes.html. Would
someone from the development team be able to update those?

Kind regards,

John Bigler Pittsburgh, PA United States
--
* To stop receiving contact emails as an owner of this package, sign in to
the NuGet Gallery and change your email notification settings
. *


Privacy Statement
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052 USA

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

2021-11-05 Thread Davyd McColl 
Hi

asf-staging branch merged into asf-site and I can see the latest release notes 
are up

Apologies again for missing this.

-d
On 2021/11/05 16:31:41, Davyd McColl  wrote:
Apologies - staging docs have not been set live ):

I'll have a look at it now

-d

On 2021/11/05 16:24:55, Volkan Yazıcı  wrote:
I think this message is best suited for this mailing list.
Would anybody from the log4net crew mind addressing the request of John
Bigler, please?

-- Forwarded message -
From: NuGet Gallery
Date: Thu, Nov 4, 2021 at 5:50 PM
Subject: [NuGet Gallery] Message for owners of the package 'log4net'
To:


*User JohnBig > sends the following
message to the owners of Package 'log4net 2.0.13
'.*

I see that version 2.0.13 was released around November 2, 2021, but does
not have any corresponding release notes on
https://logging.apache.org/log4net/release/release-notes.html. Would
someone from the development team be able to update those?

Kind regards,

John Bigler Pittsburgh, PA United States
--
* To stop receiving contact emails as an owner of this package, sign in to
the NuGet Gallery and change your email notification settings
. *


Privacy Statement
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052 USA