RE: Compiling log4net with strong name and 3rd party dependencies (also is log4net in a cul-du-sac)
I have volunteered my services before, but unfortunately, I don't know how to use ANY of the tools required to interface with Jira and the source control. I fear that I am Microsoft centric and will, for the most part, probably stay that way. If someone could give me good guidance, I could learn enough to be productive. -- Roy Chastain SOHO Technology Solutions, LLC (770) 426-4708 http://www.sohotech.biz If you do not wish to receive future email from SOHO Technology Solutions, please reply to this message with the subject line of Remove Me. -Original Message- From: Jim Scott [mailto:jsc...@infoconex.com] Sent: Tuesday, August 09, 2011 19:16 To: log4net-dev@logging.apache.org Subject: Re: Compiling log4net with strong name and 3rd party dependencies (also is log4net in a cul-du-sac) On 8/8/2011 8:34 PM, Curt Arnold wrote: I'd be happy to perform the release build or reencrypt the strong signing key to another PMC member who wants to help. However, to get to that point, it will take people who are motivated to pitch in and get things ready for release. Further discussion should be on log4net-dev. Curt, I am more than interested in helping this project move forward. However I am not 100% confident that I would be able to do things exactly to the standard expected so would need some guidance in providing help if you are interested in having me participate.
Re: Compiling log4net with strong name and 3rd party dependencies (also is log4net in a cul-du-sac)
Good to have both of you here. Hopefully the content under Contribute back to the community at http://www.apache.org/foundation/getinvolved.html can get you started. Write access to the ASF source code repository is granted by a process that requires some history of contribution to a project, so for the time being, anyone new to contributing to log4net that doesn't already have an Apache account will need to work by reviewing bugs and submitting patches (checkout the source code using Subversion, look at a bug, add test cases, write a fix, do a svn diff to produce a difference between your final and starting version and upload) to JIRA which is basically how almost all people with Apache accounts earned their Apache accounts. If bugs in JIRA have good test cases and patches, we will come up with some set of people with existing Apache credentials to act as mentors who will review the patches and commit them. Our current situation is those with the itch don't have the keys and those with the keys don't have the itch (or they have too many other itches and haven't been able to get around to this particular itch). On Aug 9, 2011, at 6:19 PM, Roy Chastain wrote: I have volunteered my services before, but unfortunately, I don't know how to use ANY of the tools required to interface with Jira and the source control. I fear that I am Microsoft centric and will, for the most part, probably stay that way. If someone could give me good guidance, I could learn enough to be productive. On Aug 9, 2011, at 6:15 PM, Jim Scott wrote: Curt, I am more than interested in helping this project move forward. However I am not 100% confident that I would be able to do things exactly to the standard expected so would need some guidance in providing help if you are interested in having me participate.
Re: Compiling log4net with strong name and 3rd party dependencies (also is log4net in a cul-du-sac)
By the way, no need to apologize. The ASF is an educational foundation and community which happens to produce software. On Aug 9, 2011, at 6:15 PM, Jim Scott wrote: On 8/8/2011 8:34 PM, Curt Arnold wrote: I'd be happy to perform the release build or reencrypt the strong signing key to another PMC member who wants to help. However, to get to that point, it will take people who are motivated to pitch in and get things ready for release. Further discussion should be on log4net-dev. Curt, I am more than interested in helping this project move forward. However I am not 100% confident that I would be able to do things exactly to the standard expected so would need some guidance in providing help if you are interested in having me participate.
Re: Compiling log4net with strong name and 3rd party dependencies (also is log4net in a cul-du-sac)
Hi Jim, On 2011-08-10, Jim Scott wrote: On 8/8/2011 8:34 PM, Curt Arnold wrote: I'd be happy to perform the release build or reencrypt the strong signing key to another PMC member who wants to help. However, to get to that point, it will take people who are motivated to pitch in and get things ready for release. Further discussion should be on log4net-dev. Curt, I am more than interested in helping this project move forward. This sounds great. However I am not 100% confident that I would be able to do things exactly to the standard expected so would need some guidance in providing help if you are interested in having me participate. Don't worry. Most people around here won't know me as I'm just a user of log4net myself and haven't contributed much to it. In 2000 I became involved with the Apache Software Foundation as a committer to Apache Ant - some small build tool nobody knew back then that initially was used to build Tomcat and was later spun out as a separate project. Those familiar with the Java space will know what has grown out of it. After that I've helped out here and there and still am a committer and PMC member at Ant (and a few other places). But when I started I was sure I could never meet the standards of the ASF. One of my first contributions to Ant was some helper code that allowed me to use the small - by then - unknown testing library from inside my builds, the junit task. The initial code was quite limited and even a bit hackish in places, it did what I needed and others expanded upon it. What I'm trying to say here is that it is better to have some start, even if not perfect, than nothing at all. A bad implementation may even be a good way to get the community involved. I think Cocoon's founder Stefano Mazzocci once coined great ideas and crappy code as the best fertilizer for open source communities. When I wrote the initial version of the code that maps XML elements and attributes to Java objects in Ant using lots of reflection this was the first time I used any class from the Java reflection package. I learned a lot from it and I learned even more from the improvements others made to my code. There is a lot of value in developing in the open. Each time anybody provides a patch to code you've written you learn something new and become a better developer. And the discussions in most communities are very very fruitful, there are very few jerks around the ASF. Again, don't worry, just jump in, the water is fine. Stefan
Re: Compiling log4net with strong name and 3rd party dependencies (also is log4net in a cul-du-sac)
Hi Roy On 2011-08-10, Roy Chastain wrote: I have volunteered my services before, but unfortunately, I don't know how to use ANY of the tools required to interface with Jira and the source control. Interfacing with JIRA really doesn't involve anything but a browser. I know there are some integrations into Eclipse, maybe even Visual Studio, but I've never used anything but Firefox for it myself. The recent JIRA releases are pretty JavaScript-heavy so I wouldn't recommend using older IEs. Subversion is the main tool and likely the biggest hurdle. I come from a Unix background myself and am a command line kind of person so I'm not sure about the options but there are GUI frontends to Subversion as well (TurtoiseSVN or something like that). The command line svn diff creates exactly the kind of output that people expect as patches attached to JIRA. I'm sure the GUI frontends will provide a way to get exactly that as well. The ideal workflow if you think you've found a bug would then be: (1) check out source code from svn (2) write a unit test that verifies the bug (3) fix the bug (4) open a JIRA ticket (5) create a patch by using svn diff (6) attach the patch to the ticket (7) revert your changes in your local copy and tackle the next bug You may need to svn add new files before creating the patch. If you do that often enough, you'll eventually gain write access and can forget about the patch, at which point the flow continues as (5) commit your changes (6) resolve the JIRA issue and there will be nothing to revert. Cheers Stefan
Re: Compiling log4net with strong name and 3rd party dependencies (also is log4net in a cul-du-sac)
I wrote this message last night in response to the is log4net in a cul-du-sac thread, but it got bounced due to a spam guard which I've hopefully satisfied this time. The strong naming key that has been used to sign log4net releases has been encrypted and can be decrypted using the private keys of several people including myself. I'd be happy to perform the release build or reencrypt the strong signing key to another PMC member who wants to help. However, to get to that point, it will take people who are motivated to pitch in and get things ready for release. Further discussion should be on log4net-dev. My message from last night: I'm not sure if this message got an adequate answer. For those who want to drive a release forward, I would suggest: Create a bug report for the next release (check if there is already one) Make that bug dependent on any issue that you think needs to be resolved before the next release If there are any debatable issues (like dropping support for earlier .NET versions), start a vote on the mailing list. If there are interrelated issues, perhaps create a page on the logging wiki and have a vote on all the issues in the same time. If there are bugs without test cases or patches, create test cases and patches. If there are bugs with test case and patches that should be committed, make a comment on the bug that it appears ready to go. Hopefully through this process, we can develop the track record that will allow adding some new committers or PMC members. On Aug 8, 2011, at 4:27 PM, Jim Scott wrote: From: Johannes Gustafsson Sent: Monday, August 08, 2011 1:20 PM To: log4net-u...@logging.apache.org Subject: Compiling log4net with strong name and 3rd party dependencies Hi, There are a few bugfixes in the trunk that I need and since there has been no new release for a very long time, I tried to compile it myself. I created a key and have successfully compiled it with no problems. However, I have quite a few 3rd party dependencies that themselves are dependent on log4net. These dependencies can't find load the new assembly that I have created because they require that it is signed with a key that I dont have access to. So this means that I can't use my own version of log4net without recompiling all my dependencies. Do you have any suggestions to how I can solve this? Regards, /Johannes Yes, this is the same issue we have. I have a few features I would like to add but the thought of having to recompile everything has kept me from doing so.
Re: Compiling log4net with strong name and 3rd party dependencies (also is log4net in a cul-du-sac)
On 2011-08-09, Curt Arnold wrote: For those who want to drive a release forward, I would suggest: Create a bug report for the next release (check if there is already one) JIRA already has 1.2.11 as release version and tons of issues assigned to it. 20 are still open 34 are already in the resolved state. Some triage may be in order. 34 fixed issues sounds huge and it may very well be worth pushing back some issues without patches and release the rest now rather than waiting for the rest. I'm not sure we need a separate issue for the release itself when JIRA provides the roadmap view. If there are any debatable issues (like dropping support for earlier .NET versions), start a vote on the mailing list. If there are interrelated issues, perhaps create a page on the logging wiki and have a vote on all the issues in the same time. If there are bugs without test cases or patches, create test cases and patches. If there are bugs with test case and patches that should be committed, make a comment on the bug that it appears ready to go. Hopefully through this process, we can develop the track record that will allow adding some new committers or PMC members. Sounds like a plan. Stefan
