Is this great project dead?

[karldodd]

No commits on master branch for more than half a year... And nobody is merging pull requests...

Thanks,

[ThermIt]

@sbohlen is now "Technical Evangelist at Microsoft" and is no more working on Spring.Net or Common.Logging... So I assume yes, this project is dead. There are active forks though.

[karldodd]

@sbohlen Joining Microsoft should be good news rather than bad new for Common.Logging, right? :) Microsoft is much more open-minded than before.

I wonder why the project owner, if they don't have time to merge pull requests, don't add maintainers of active forks to the list of contributors of this project so that they can continue the master branch.

Thanks,

[ThermIt]

"Technical Evangelist at Microsoft" actually means "He is no more working with code". There are no more (active) developers or maintainers for Common.Logging (and Spring.Net).

[karldodd]

Thanks @ThermIt .

It is a pity, isn't it? Spring.net is a bit out of date but Common.Logging is still very useful.

I wish the project will involve new contributors (say, allow people to apply for being a new contributor. I think many including me would love to apply and join). @sbohlen

[ThermIt]

Make a fork, apply pull requests, test extensively, develop new features, send new pull requests. You actually don't need @net-commons for that.

[karldodd]

Thanks for your suggestion @ThermIt. It makes sense to me and will be my choice.

Well, I still think it will be great if @net-commons /common-logging don't die, which is a perfect centralized place to push the project forward. It is hard for fork maintainers to know about/share their work and hard for users to judge which fork is better.

[sbohlen]

Hey, guys, good to see the interest in the project! Although I've indeed changed both employers and titles, I wanted to assure you of a few things:

1. this project is NOT dead, though I admit that I've been a bit neglectful of it as I ramped up on my new job responsibilities
2. A significant part of my day job indeed still includes writing code, though for different people and in a very different context than in the past :)
3. One of the things that I requested of MSFT (and received!) before I accepted the job was approval to continue to contribute to a variety of OSS projects, this one included

FWIW, the notifications of the pending pull requests have (apparently) been going to my old, non-functional email address and so I'd not seen any of them since departing VMware/Springsource in early-January of this year. Its only just now that I've updated my github profile with my private address that I've begun to receive notifications of this thread and that has pointed me to realize that there are pull-requests pending here :(

One of the worst things you can do to an OSS project is to let contributions languish, and for that I wholeheartedly apologize to everyone -- I honestly had no idea these were pending.

As mentioned, I've been a bit distracted from other obligations while I ramped up into my new position, and that's taken most of my 'spare' time. However, if you have a desire to contribute, please do fork this repo and issue additional pull requests. I'll try to review the pending pull requests this coming weekend and get them re-integrated into the project ASAP so that this can get back on track.

While its technically feasible to fork the project and abandon making pull requests back into this repo, its probably neither practical nor beneficial to the project for that to happen. The challenge with that approach is decreased discoverability as the 'possible' official repos for this project balloon outward. Its also the case that this project's official committers are the 'owners' of the existing Common.Logging.* NuGet packages and that this also argues for trying to maintain a single 'authoritative' repo for the project (so that all valid contributions manage to make their way into NuGet successfully so that they are most-broadly made accessible to all).

Part of the point in moving this project to github in the first place was to lower the barriers to others to contribute, so if you have ideas for features and/or bugfixes for issues, please fork this repo and issue relevant pull requests if possible.

Thanks for your interest in the project and we look forward to your contributions!

[karldodd]

Wow, great to hear from you and have you back @sbohlen ! This is very good news for everyone who is using/interested in this project!

[FroggieFrog]

What is the current status (over 1 year later)?

[cesarmm]

@FroggieFrog: from Nuget you can find version 2.2.0 published at 01/03/2014.

[neutmute]

@sbohlen "One of the worst things you can do to an OSS project is to let contributions languish"
+1

So about these 34 open issues and 10 open pull requests... :)

is this project still active? I want to pull NLog dependencies out of my libraries and applications and reference common logging instead but the activity (or lack there of) on this project is making me nervous.
Any thoughts as to future directions for this project?
More contributors need write access to repo and nuget?

[sbohlen]

Mea Culpa; a number of issues (some technical and other personal) have conspired to keep me from being able to apply the level of attention on this project that I'd wished I could provide. I'm working on the backlog of both issues and pull-requests now and should expect to have a new release ready for NUGET by mid-NOV at the latest.

Thanks for your (and everyone else's) continued patience in this.

[sbohlen]

Just FYI, the 2.3.0-RC1 packages are in NuGet now (https://www.nuget.org/packages/Common.Logging/2.3.0-RC1). Assuming no surprises from people's testing this week, expect 2.3.0-GA to be posted to NuGet on or about 1 November 2014.