You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Oskar Gewalli <ge...@gmail.com> on 2017/09/06 10:49:52 UTC

Moving log4net-logviewer to apache

We currently have a project on github that might be better if it's under the stewardship of apache (since apache owns log4net)

https://github.com/wallymathieu/log4net-logviewer/issues/7#issuecomment-327421829 <https://github.com/wallymathieu/log4net-logviewer/issues/7#issuecomment-327421829>

What do you think?

Best regards from Oskar Gewalli

Re: Moving log4net-logviewer to apache

Posted by Dominik Psenner <dp...@gmail.com>.
On 2017-09-18 07:16, Ralph Goers wrote:
> https://github.com/wallymathieu/log4net-logviewer/issues/7#issuecomment-327423060 
>
>> and the following comment sounds as if "moving to Apache" was seen as a
>> way to keep logviewer maintained. I'm not convinced this would be any
>> easier here than in github so I doubt logviewer would win much by moving
>> while we (well, actually mostly you, Dominik) would have more code to
>> maintain.
>
> I would put it another way. In order for it to move to Logging Services I would want to know that there are at least 3 active committers on the project.
I agree and since there does not appear to be a community behind this to 
drive this forward it would most probably end up like chainsaw or worse.

Re: Moving log4net-logviewer to apache

Posted by Ralph Goers <ra...@dslextreme.com>.
> On Sep 17, 2017, at 9:47 PM, Stefan Bodewig <bo...@apache.org> wrote:
> 
> On 2017-09-09, Dominik Psenner wrote:
> 
>> What does the community think should happen? Are there people out there who
>> use log4net-logviewer or any of its binaries?
> 
> I don't.
> 
> https://github.com/wallymathieu/log4net-logviewer/issues/7#issuecomment-327423060
> and the following comment sounds as if "moving to Apache" was seen as a
> way to keep logviewer maintained. I'm not convinced this would be any
> easier here than in github so I doubt logviewer would win much by moving
> while we (well, actually mostly you, Dominik) would have more code to
> maintain.


I would put it another way. In order for it to move to Logging Services I would want to know that there are at least 3 active committers on the project.

Ralph



Re: Moving log4net-logviewer to apache

Posted by Stefan Bodewig <bo...@apache.org>.
On 2017-09-09, Dominik Psenner wrote:

> What does the community think should happen? Are there people out there who
> use log4net-logviewer or any of its binaries?

I don't.

https://github.com/wallymathieu/log4net-logviewer/issues/7#issuecomment-327423060
and the following comment sounds as if "moving to Apache" was seen as a
way to keep logviewer maintained. I'm not convinced this would be any
easier here than in github so I doubt logviewer would win much by moving
while we (well, actually mostly you, Dominik) would have more code to
maintain.

Stefan

Fwd: Moving log4net-logviewer to apache

Posted by Dominik Psenner <dp...@gmail.com>.
Hi fellows!

This is a call for opinions.

What does the community think should happen? Are there people out there who
use log4net-logviewer or any of its binaries?

Cheers,
Dominik


On 6 Sep 2017 3:08 p.m., "Oskar Gewalli" <ge...@gmail.com> wrote:


> On 6 Sep 2017, at 15:03, Dominik Psenner <dp...@gmail.com> wrote:
>
>
> On 2017-09-06 14:17, Oskar Gewalli wrote:
>> Hi,
>>
>> Perhaps it would be better to create a dedicated library to just the
log4net xml parsing? The GUI and CLI tools could then depend on that
package.
>>
>> Since the log parsing parts are much smaller and not very special.
>
> I don't have the insights to be able to comment on this. Would you please
explain the main difference between chainsaw, log2console and
log4net-logviewer?
>

The main benefit of using log4net-logviewer is to use the logparsing
abilities to be able to aggregate and do log statistics from the raw logs.

The GUI and CLI bits can potentially be removed, since there are already
chainsaw and log2console.

>>
>> Best regards from Oskar
>>
>>> On 6 Sep 2017, at 13:54, Dominik Psenner <dp...@gmail.com> wrote:
>>>
>>> Hi Oskar,
>>>
>>> log4net-logviewer is a tool that includes both a command line and a ui
frontend written in wpf/xaml that both can parse logfiles and provide users
a better view on log events. According to the readme this is a alternative
to log2console and chainsaw. I don't like it to have multiple tools that do
the same thing. Would you please explain the main differences between the
projects?
>>>
>>> I further noticed that there are at least a few legal issues like
unclear licensing that would definitely prevent the adoption of the
project. Further I see no personal interest to take over the maintenance of
more projects as that would definitely exceed the spare time I have
available. Therefore it would be great if we could merge the communities to
gain a larger community to maintain all of these projects.
>>>
>>> Best regards,
>>> Dominik
>>>
>>>
>>> On 2017-09-06 12:49, Oskar Gewalli wrote:
>>>> We currently have a project on github that might be better if it's
under the stewardship of apache (since apache owns log4net)
>>>>
>>>> https://github.com/wallymathieu/log4net-logviewer/issues/7#i
ssuecomment-327421829 <https://github.com/wallymathi
eu/log4net-logviewer/issues/7#issuecomment-327421829>
>>>>
>>>> What do you think?
>>>>
>>>> Best regards from Oskar Gewalli
>





-- 
Dominik Psenner

Re: Moving log4net-logviewer to apache

Posted by Dominik Psenner <dp...@gmail.com>.
Hi fellows!

This is a call for opinions.

What does the community think should happen? Are there people out there who
use log4net-logviewer or any of its binaries?

Cheers,
Dominik


On 6 Sep 2017 3:08 p.m., "Oskar Gewalli" <ge...@gmail.com> wrote:


> On 6 Sep 2017, at 15:03, Dominik Psenner <dp...@gmail.com> wrote:
>
>
> On 2017-09-06 14:17, Oskar Gewalli wrote:
>> Hi,
>>
>> Perhaps it would be better to create a dedicated library to just the
log4net xml parsing? The GUI and CLI tools could then depend on that
package.
>>
>> Since the log parsing parts are much smaller and not very special.
>
> I don't have the insights to be able to comment on this. Would you please
explain the main difference between chainsaw, log2console and
log4net-logviewer?
>

The main benefit of using log4net-logviewer is to use the logparsing
abilities to be able to aggregate and do log statistics from the raw logs.

The GUI and CLI bits can potentially be removed, since there are already
chainsaw and log2console.

>>
>> Best regards from Oskar
>>
>>> On 6 Sep 2017, at 13:54, Dominik Psenner <dp...@gmail.com> wrote:
>>>
>>> Hi Oskar,
>>>
>>> log4net-logviewer is a tool that includes both a command line and a ui
frontend written in wpf/xaml that both can parse logfiles and provide users
a better view on log events. According to the readme this is a alternative
to log2console and chainsaw. I don't like it to have multiple tools that do
the same thing. Would you please explain the main differences between the
projects?
>>>
>>> I further noticed that there are at least a few legal issues like
unclear licensing that would definitely prevent the adoption of the
project. Further I see no personal interest to take over the maintenance of
more projects as that would definitely exceed the spare time I have
available. Therefore it would be great if we could merge the communities to
gain a larger community to maintain all of these projects.
>>>
>>> Best regards,
>>> Dominik
>>>
>>>
>>> On 2017-09-06 12:49, Oskar Gewalli wrote:
>>>> We currently have a project on github that might be better if it's
under the stewardship of apache (since apache owns log4net)
>>>>
>>>> https://github.com/wallymathieu/log4net-logviewer/issues/7#
issuecomment-327421829 <https://github.com/wallymathieu/log4net-
logviewer/issues/7#issuecomment-327421829>
>>>>
>>>> What do you think?
>>>>
>>>> Best regards from Oskar Gewalli
>

Re: Moving log4net-logviewer to apache

Posted by Oskar Gewalli <ge...@gmail.com>.
> On 6 Sep 2017, at 15:03, Dominik Psenner <dp...@gmail.com> wrote:
> 
> 
> On 2017-09-06 14:17, Oskar Gewalli wrote:
>> Hi,
>> 
>> Perhaps it would be better to create a dedicated library to just the log4net xml parsing? The GUI and CLI tools could then depend on that package.
>> 
>> Since the log parsing parts are much smaller and not very special.
> 
> I don't have the insights to be able to comment on this. Would you please explain the main difference between chainsaw, log2console and log4net-logviewer?
> 

The main benefit of using log4net-logviewer is to use the logparsing abilities to be able to aggregate and do log statistics from the raw logs.   

The GUI and CLI bits can potentially be removed, since there are already chainsaw and log2console. 

>> 
>> Best regards from Oskar
>> 
>>> On 6 Sep 2017, at 13:54, Dominik Psenner <dp...@gmail.com> wrote:
>>> 
>>> Hi Oskar,
>>> 
>>> log4net-logviewer is a tool that includes both a command line and a ui frontend written in wpf/xaml that both can parse logfiles and provide users a better view on log events. According to the readme this is a alternative to log2console and chainsaw. I don't like it to have multiple tools that do the same thing. Would you please explain the main differences between the projects?
>>> 
>>> I further noticed that there are at least a few legal issues like unclear licensing that would definitely prevent the adoption of the project. Further I see no personal interest to take over the maintenance of more projects as that would definitely exceed the spare time I have available. Therefore it would be great if we could merge the communities to gain a larger community to maintain all of these projects.
>>> 
>>> Best regards,
>>> Dominik
>>> 
>>> 
>>> On 2017-09-06 12:49, Oskar Gewalli wrote:
>>>> We currently have a project on github that might be better if it's under the stewardship of apache (since apache owns log4net)
>>>> 
>>>> https://github.com/wallymathieu/log4net-logviewer/issues/7#issuecomment-327421829 <https://github.com/wallymathieu/log4net-logviewer/issues/7#issuecomment-327421829>
>>>> 
>>>> What do you think?
>>>> 
>>>> Best regards from Oskar Gewalli
> 


Re: Moving log4net-logviewer to apache

Posted by Dominik Psenner <dp...@gmail.com>.
On 2017-09-06 14:17, Oskar Gewalli wrote:
> Hi,
>
> Perhaps it would be better to create a dedicated library to just the log4net xml parsing? The GUI and CLI tools could then depend on that package.
>
> Since the log parsing parts are much smaller and not very special.

I don't have the insights to be able to comment on this. Would you 
please explain the main difference between chainsaw, log2console and 
log4net-logviewer?

>
> Best regards from Oskar
>
>> On 6 Sep 2017, at 13:54, Dominik Psenner <dp...@gmail.com> wrote:
>>
>> Hi Oskar,
>>
>> log4net-logviewer is a tool that includes both a command line and a ui frontend written in wpf/xaml that both can parse logfiles and provide users a better view on log events. According to the readme this is a alternative to log2console and chainsaw. I don't like it to have multiple tools that do the same thing. Would you please explain the main differences between the projects?
>>
>> I further noticed that there are at least a few legal issues like unclear licensing that would definitely prevent the adoption of the project. Further I see no personal interest to take over the maintenance of more projects as that would definitely exceed the spare time I have available. Therefore it would be great if we could merge the communities to gain a larger community to maintain all of these projects.
>>
>> Best regards,
>> Dominik
>>
>>
>> On 2017-09-06 12:49, Oskar Gewalli wrote:
>>> We currently have a project on github that might be better if it's under the stewardship of apache (since apache owns log4net)
>>>
>>> https://github.com/wallymathieu/log4net-logviewer/issues/7#issuecomment-327421829 <https://github.com/wallymathieu/log4net-logviewer/issues/7#issuecomment-327421829>
>>>
>>> What do you think?
>>>
>>> Best regards from Oskar Gewalli


Re: Moving log4net-logviewer to apache

Posted by Oskar Gewalli <ge...@gmail.com>.
Hi,

Perhaps it would be better to create a dedicated library to just the log4net xml parsing? The GUI and CLI tools could then depend on that package.

Since the log parsing parts are much smaller and not very special. 

Best regards from Oskar

> On 6 Sep 2017, at 13:54, Dominik Psenner <dp...@gmail.com> wrote:
> 
> Hi Oskar,
> 
> log4net-logviewer is a tool that includes both a command line and a ui frontend written in wpf/xaml that both can parse logfiles and provide users a better view on log events. According to the readme this is a alternative to log2console and chainsaw. I don't like it to have multiple tools that do the same thing. Would you please explain the main differences between the projects?
> 
> I further noticed that there are at least a few legal issues like unclear licensing that would definitely prevent the adoption of the project. Further I see no personal interest to take over the maintenance of more projects as that would definitely exceed the spare time I have available. Therefore it would be great if we could merge the communities to gain a larger community to maintain all of these projects.
> 
> Best regards,
> Dominik
> 
> 
> On 2017-09-06 12:49, Oskar Gewalli wrote:
>> We currently have a project on github that might be better if it's under the stewardship of apache (since apache owns log4net)
>> 
>> https://github.com/wallymathieu/log4net-logviewer/issues/7#issuecomment-327421829 <https://github.com/wallymathieu/log4net-logviewer/issues/7#issuecomment-327421829>
>> 
>> What do you think?
>> 
>> Best regards from Oskar Gewalli
> 


Re: Moving log4net-logviewer to apache

Posted by Dominik Psenner <dp...@gmail.com>.
Hi Oskar,

log4net-logviewer is a tool that includes both a command line and a ui 
frontend written in wpf/xaml that both can parse logfiles and provide 
users a better view on log events. According to the readme this is a 
alternative to log2console and chainsaw. I don't like it to have 
multiple tools that do the same thing. Would you please explain the main 
differences between the projects?

I further noticed that there are at least a few legal issues like 
unclear licensing that would definitely prevent the adoption of the 
project. Further I see no personal interest to take over the maintenance 
of more projects as that would definitely exceed the spare time I have 
available. Therefore it would be great if we could merge the communities 
to gain a larger community to maintain all of these projects.

Best regards,
Dominik


On 2017-09-06 12:49, Oskar Gewalli wrote:
> We currently have a project on github that might be better if it's under the stewardship of apache (since apache owns log4net)
>
> https://github.com/wallymathieu/log4net-logviewer/issues/7#issuecomment-327421829 <https://github.com/wallymathieu/log4net-logviewer/issues/7#issuecomment-327421829>
>
> What do you think?
>
> Best regards from Oskar Gewalli