Re: [log4cxx] Contributing a CMkae build system

[Matt Sicker]

Looks like I missed saving that to the KEYS file. I've updated that now.

On Sun, 12 Jan 2020 at 12:15, Thorsten Schöning  wrote:
>
> Guten Tag Ralph Goers,
> am Sonntag, 12. Januar 2020 um 18:31 schrieben Sie:
>
> > If those were issues I would have hoped you would have asked prior to this.
>
> I did and provided my signing keys etc. already, can all be read in
> the threads which topic I mentioned in the mail before. At some point
> I simply didn't ask for further progress anymore as well and needed to
> deal with other tasks, so things have stopped.
>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>
> --
> Thorsten Schöning   E-Mail: thorsten.schoen...@am-soft.de
> AM-SoFT IT-Systeme  http://www.AM-SoFT.de/
>
> Telefon...05151-  9468- 55
> Fax...05151-  9468- 88
> Mobil..0178-8 9468- 04
>
> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
>


-- 
Matt Sicker 

Re: [log4cxx] Contributing a CMkae build system

[Thorsten Schöning]

Guten Tag Ralph Goers,
am Sonntag, 12. Januar 2020 um 18:31 schrieben Sie:

> If those were issues I would have hoped you would have asked prior to this.

I did and provided my signing keys etc. already, can all be read in
the threads which topic I mentioned in the mail before. At some point
I simply didn't ask for further progress anymore as well and needed to
deal with other tasks, so things have stopped.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning   E-Mail: thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme  http://www.AM-SoFT.de/

Telefon...05151-  9468- 55
Fax...05151-  9468- 88
Mobil..0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

Re: [log4cxx] Contributing a CMkae build system

[Ralph Goers]

> On Jan 12, 2020, at 2:00 AM, Thorsten Schöning  wrote:
> 
> Guten Tag Stephen Webb,
> am Sonntag, 12. Januar 2020 um 07:38 schrieben Sie:
> 
>> Could you tell us why the vote did not happen on these occasions?
> 
> Because things stopped at the point before for mostly two reasons: The
> first is there were still some open organisational questions to me
> like is distributing to dist-dev the proper thing to do for voting,
> who moves things to the official dist-repo in case of success, who
> adds my signing keys used for the release there and stuff like that.

If those were issues I would have hoped you would have asked prior to this.
1. The artifacts to be released need to be voted on. The ASF doesn’t require 
they be uploaded to dist-dev but, by convention, that is how Logging Services 
has been doing it.
2. Only PMC members have commit privs to the list repo, so you would need 
assistance from one of us for that. But that should be a final step in the 
release process.
3. Again, a PMC member can add your signing key. That can be done at any time, 
even now. 

> 
> The second was some technical things, like which files should the
> release contain, some version numbering issues etc. I simply tried to
> keep things as they were in older releases, but other opinions have
> occured etc. In my opinion any changes to what a release contains
> should simply be ignored in the first place and provided at most what
> has been provided in the past. I'm somewhat sure that my current
> scripts provide that.

Since it has been so long since the last release I would suggest that whatever 
the quickest path to getting a release that can be supported be taken. 
Improvements to the release process should happen with each subsequent release 
after that.

Ralph

Re: [log4cxx] Contributing a CMkae build system

[Thorsten Schöning]

Guten Tag Stephen Webb,
am Sonntag, 12. Januar 2020 um 07:38 schrieben Sie:

> Could you tell us why the vote did not happen on these occasions?

Because things stopped at the point before for mostly two reasons: The
first is there were still some open organisational questions to me
like is distributing to dist-dev the proper thing to do for voting,
who moves things to the official dist-repo in case of success, who
adds my signing keys used for the release there and stuff like that.

The second was some technical things, like which files should the
release contain, some version numbering issues etc. I simply tried to
keep things as they were in older releases, but other opinions have
occured etc. In my opinion any changes to what a release contains
should simply be ignored in the first place and provided at most what
has been provided in the past. I'm somewhat sure that my current
scripts provide that.

I guess the most relevant threads are the following:

> Re: [log4cxx] Release process releated questions
> Re: Next release
> Re: [log4cxx] Current State

Adding signing keys in the dist-repo, copying releases to that etc.
are the still open things I think.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning   E-Mail: thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme  http://www.AM-SoFT.de/

Telefon...05151-  9468- 55
Fax...05151-  9468- 88
Mobil..0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

Re: [log4cxx] Contributing a CMkae build system

[Ralph Goers]

The current PMC chair is Matt Sicker.  I believe no release vote took place 
because a release build has not successfully been completed.

Ralph

> On Jan 11, 2020, at 11:38 PM, Stephen Webb  wrote:
> 
> Hi Thorsten,
> 
> I saw in the mailing lists you have previously (July 2017, January 2018)
> attempted to get a release done, but I did not see any vote being taken.
> 
> Could you tell us why the vote did not happen on these occasions?
> 
> Also, who is the current PMC chair?
> 
> Regards
> Stephen Webb
> 
> On Tue, Jan 7, 2020 at 7:17 PM Thorsten Schöning 
> wrote:
> 
>> Guten Tag Stephen Webb,
>> am Dienstag, 7. Januar 2020 um 03:33 schrieben Sie:
>> 
>>> I am prepared to commit time to helping progress log4cxx to a release.
>> 
>> If you want to get a release done, you should first focus on that
>> instead of adding another build system necessary to maintain, which
>> might even break existing functionality and stuff. Releasing is
>> non-trivial in my opinion, took me a lot of time already and its not
>> done yet.
>> 
>> Make yourself familiar with how to tag things, where you need to
>> change version numbers, how to generate sites, where to upload what,
>> what to sign, where to put keys and stuff first. That's a lot of work
>> involving Maven, shell scripts and stuff. Afterwards you can change
>> the build system.
>> 
>> http://www.apache.org/dev/release-publishing.html
>> http://www.apache.org/legal/release-policy.html
>> 
>> Mit freundlichen Grüßen,
>> 
>> Thorsten Schöning
>> 
>> --
>> Thorsten Schöning   E-Mail: thorsten.schoen...@am-soft.de
>> AM-SoFT IT-Systeme  http://www.AM-SoFT.de/
>> 
>> Telefon...05151-  9468- 55
>> Fax...05151-  9468- 88
>> Mobil..0178-8 9468- 04
>> 
>> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
>> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
>> 
>> 

Re: [log4cxx] Contributing a CMkae build system

[Stephen Webb]

Hi Thorsten,

I saw in the mailing lists you have previously (July 2017, January 2018)
attempted to get a release done, but I did not see any vote being taken.

Could you tell us why the vote did not happen on these occasions?

Also, who is the current PMC chair?

Regards
Stephen Webb

On Tue, Jan 7, 2020 at 7:17 PM Thorsten Schöning 
wrote:

> Guten Tag Stephen Webb,
> am Dienstag, 7. Januar 2020 um 03:33 schrieben Sie:
>
> > I am prepared to commit time to helping progress log4cxx to a release.
>
> If you want to get a release done, you should first focus on that
> instead of adding another build system necessary to maintain, which
> might even break existing functionality and stuff. Releasing is
> non-trivial in my opinion, took me a lot of time already and its not
> done yet.
>
> Make yourself familiar with how to tag things, where you need to
> change version numbers, how to generate sites, where to upload what,
> what to sign, where to put keys and stuff first. That's a lot of work
> involving Maven, shell scripts and stuff. Afterwards you can change
> the build system.
>
> http://www.apache.org/dev/release-publishing.html
> http://www.apache.org/legal/release-policy.html
>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>
> --
> Thorsten Schöning   E-Mail: thorsten.schoen...@am-soft.de
> AM-SoFT IT-Systeme  http://www.AM-SoFT.de/
>
> Telefon...05151-  9468- 55
> Fax...05151-  9468- 88
> Mobil..0178-8 9468- 04
>
> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
>
>

Re: [log4cxx] Contributing a CMkae build system

[Ralph Goers]

Robert Middleton has also offered to help. I would suggest you collaborate here 
and in either a combined or individual forks.

Ralph

> On Jan 6, 2020, at 7:33 PM, Stephen Webb  wrote:
> 
> Hi All,
> I am prepared to commit time to helping progress log4cxx to a release.
> 
> I would like to add a modern CMake build option to log4cxx and then create
> a port in vcpkg (see https://github.com/microsoft/vcpkg/issues/6125). I
> have sent a signed ICLA to the secretary.
> 
> Does anyone have any comments?
> 
> Regrads
> Stephen Webb

Re: [log4cxx] Contributing a CMkae build system

[Remko Popma]

All help is welcome!

Remko



> On Jan 7, 2020, at 11:34, Stephen Webb  wrote:
> 
> Hi All,
> I am prepared to commit time to helping progress log4cxx to a release.
> 
> I would like to add a modern CMake build option to log4cxx and then create
> a port in vcpkg (see https://github.com/microsoft/vcpkg/issues/6125). I
> have sent a signed ICLA to the secretary.
> 
> Does anyone have any comments?
> 
> Regrads
> Stephen Webb

[log4cxx] Contributing a CMkae build system

[Stephen Webb]

Hi All,
I am prepared to commit time to helping progress log4cxx to a release.

I would like to add a modern CMake build option to log4cxx and then create
a port in vcpkg (see https://github.com/microsoft/vcpkg/issues/6125). I
have sent a signed ICLA to the secretary.

Does anyone have any comments?

Regrads
Stephen Webb

Re: [log4cxx] Contributing

[Robert Middleton]

On Sat, Jan 4, 2020 at 11:40 PM Ralph Goers  wrote:
>
> The project to which PMC members belong is Apache Logging Services. When a 
> committer is invited they have access to all the logging project repositories 
> except for the one area that is limited to PMC members.
>
> If you plan on making significant contributions you should sign an ICLA.
>

That makes sense; I'll look into doing that shortly.

> Yes, there are a few steps in a release that require a PMC member but most of 
> the release process can be accomplished by a committer. That said, acting as 
> a release manager is a quick way to get invited to any ASF PMC :-)
>

I have been doing a lot of releases at work lately, so working on most
of the release process should be pretty straightforward for me to do.
I should be able to take a look at the (current) release scripts in
the next few days or so.

-Robert Middleton

Re: [log4cxx] Contributing

[Ralph Goers]

The project to which PMC members belong is Apache Logging Services. When a 
committer is invited they have access to all the logging project repositories 
except for the one area that is limited to PMC members. 

If you plan on making significant contributions you should sign an ICLA. 

Yes, there are a few steps in a release that require a PMC member but most of 
the release process can be accomplished by a committer. That said, acting as a 
release manager is a quick way to get invited to any ASF PMC :-)

Ralph

> On Jan 4, 2020, at 7:42 PM, Robert Middleton  wrote:
> 
> On Wed, Jan 1, 2020 at 10:52 AM Thorsten Schöning  > wrote:
>> 
>> Guten Tag Robert Middleton,
>> am Dienstag, 31. Dezember 2019 um 21:44 schrieben Sie:
>> 
>>> [...]so what is the best way to become a contributor/committer?
>> 
>> I suggest you start reading through the following docs:
>> 
>>> A committer is a developer that was given write access to the code
>>> repository and has a signed Contributor License Agreement (CLA) on
>>> file. They have an apache.org mail address.
>> 
>> http://www.apache.org/foundation/how-it-works.html#committers
>> 
> 
> Thanks for that, I haven't seen that page before.
> 
>> https://www.apache.org/foundation/getinvolved.html 
>> 
>> https://community.apache.org/contributors/ 
>> 
>> 
> 
> After re-reading these, I wonder who are the PMC members for log4cxx
> at the moment, and is it the same people as for log4j(e.g. Ralph,
> Matt, etc.)?  And would it make sense for me to sign a CLA, or would
> that not be helpful?
> 
>> The following covers what needs to be done for releases:
>> 
>> http://www.apache.org/dev/release-publishing.html
>> http://www.apache.org/legal/release-policy.html
>> 
>> Some parts have already been automated using "release_*.sh"-scripts in
>> the root of the project, I think up to the point on which releases
>> where tagged, build and uploaded to the following staging repo:
>> 
>> https://dist.apache.org/repos/dist/dev/logging/log4cxx
>> 
>> After that point, if I remember correctly, people need to vote on the
>> release, it needs to be moved to the release-repo "somehow" and your
>> keys used to sign the release should have been added to the keys of
>> the release-repo BEFOREHAND.
> 
> From my reading of the documentation, the release repo is just an SVN
> repository that the signed packages go to.  See:
> http://www.apache.org/legal/release-policy.html#upload-ci 
> 
> Although this goes back to who exactly is PMC, since according to the
> documentation only the PMC members have the rights to upload...
> 
> -Robert Middleton

Re: [log4cxx] Contributing

[Robert Middleton]

On Wed, Jan 1, 2020 at 10:52 AM Thorsten Schöning  wrote:
>
> Guten Tag Robert Middleton,
> am Dienstag, 31. Dezember 2019 um 21:44 schrieben Sie:
>
> > [...]so what is the best way to become a contributor/committer?
>
> I suggest you start reading through the following docs:
>
> > A committer is a developer that was given write access to the code
> > repository and has a signed Contributor License Agreement (CLA) on
> > file. They have an apache.org mail address.
>
> http://www.apache.org/foundation/how-it-works.html#committers
>

Thanks for that, I haven't seen that page before.

> https://www.apache.org/foundation/getinvolved.html
> https://community.apache.org/contributors/
>

After re-reading these, I wonder who are the PMC members for log4cxx
at the moment, and is it the same people as for log4j(e.g. Ralph,
Matt, etc.)?  And would it make sense for me to sign a CLA, or would
that not be helpful?

> The following covers what needs to be done for releases:
>
> http://www.apache.org/dev/release-publishing.html
> http://www.apache.org/legal/release-policy.html
>
> Some parts have already been automated using "release_*.sh"-scripts in
> the root of the project, I think up to the point on which releases
> where tagged, build and uploaded to the following staging repo:
>
> https://dist.apache.org/repos/dist/dev/logging/log4cxx
>
> After that point, if I remember correctly, people need to vote on the
> release, it needs to be moved to the release-repo "somehow" and your
> keys used to sign the release should have been added to the keys of
> the release-repo BEFOREHAND.

>From my reading of the documentation, the release repo is just an SVN
repository that the signed packages go to.  See:
http://www.apache.org/legal/release-policy.html#upload-ci
Although this goes back to who exactly is PMC, since according to the
documentation only the PMC members have the rights to upload...

-Robert Middleton

Re: [log4cxx] Contributing

[Thorsten Schöning]

Guten Tag Robert Middleton,
am Dienstag, 31. Dezember 2019 um 21:44 schrieben Sie:

> [...]so what is the best way to become a contributor/committer?

I suggest you start reading through the following docs:

> A committer is a developer that was given write access to the code
> repository and has a signed Contributor License Agreement (CLA) on
> file. They have an apache.org mail address.

http://www.apache.org/foundation/how-it-works.html#committers

https://www.apache.org/foundation/getinvolved.html
https://community.apache.org/contributors/

The following covers what needs to be done for releases:

http://www.apache.org/dev/release-publishing.html
http://www.apache.org/legal/release-policy.html

Some parts have already been automated using "release_*.sh"-scripts in
the root of the project, I think up to the point on which releases
where tagged, build and uploaded to the following staging repo:

https://dist.apache.org/repos/dist/dev/logging/log4cxx

After that point, if I remember correctly, people need to vote on the
release, it needs to be moved to the release-repo "somehow" and your
keys used to sign the release should have been added to the keys of
the release-repo BEFOREHAND.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning   E-Mail: thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme  http://www.AM-SoFT.de/

Telefon...05151-  9468- 55
Fax...05151-  9468- 88
Mobil..0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

[log4cxx] Contributing

[Robert Middleton]

Hi all,

What's the bets way to contribute to log4cxx?  There's a comment from
a few months ago on LOG4CXX-486[1], and not much has been done since
then.  I'm willing to do the work to maintain log4cxx and do the
release, so what is the best way to become a contributor/committer?

-Robert Middleton

[1]: 
https://issues.apache.org/jira/browse/LOGCXX-486?focusedCommentId=16948277=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16948277