dnsjava-users

Future of dnsjava

[Ingo B. <in...@ji...>]

Hi Brian

As you've made clear, you won't be working on dnsjava anytime soon. Would
you accept/apply patches though? There are a few lying around in the mailing
list archive, in tickets, and in forks. If they were properly redacted and
sent to you again, could you do a release?

Alternatively, would you be willing to add me as a contributor on
Sourceforge to co-maintain dnsjava? I've been maintaining the Git mirror
over at Github and the Maven Central release for a while now, and I've
previously sent patches that you've applied, so I'm no total stranger.

We could also agree on some other options how to move forward, but it would
be a real shame if this library would die completely.

Thanks,
Ingo

PS: Sorry if you read this twice, I'm not sure if you're still receiving or
reading the forums at Sourceforge.

Re: Future of dnsjava

[Brian W. <bwe...@xb...>]

Hi Ingo,

The main reason that I haven’t applied any patches recently is that I wouldn’t feel comfortable applying patches and/or doing releases without reviewing and testing the changes, and I haven’t had the time or motivation to do either of those things.  

If you (or anyone else) would like to assume maintenance of the project, I’d be in favor of that.  I haven’t used Java for anything other than maintaining dnsjava for at least 10 years, so it’s not too likely that I’m going to start doing more anytime soon.

If you do wish to be the maintainer, I’d much rather see the GitHub repo become the primary source.  There’s no compelling reason to use SourceForge (and there hasn’t been for a long time), and if I had been doing any serious development, I would have moved the project years ago.  There shouldn’t be a huge amount of state there worth saving (I think it’s just the open tickets), and I can also make you a maintainer of the project on SourceForge, in order to facilitate any redirection.

I’d definitely like to see the library continue, even if I’m not as involved.

Thanks,
Brian

> On May 12, 2019, at 4:11 AM, Ingo Bauersachs <in...@ji...> wrote:
> 
> Hi Brian
> 
> As you've made clear, you won't be working on dnsjava anytime soon. Would
> you accept/apply patches though? There are a few lying around in the mailing
> list archive, in tickets, and in forks. If they were properly redacted and
> sent to you again, could you do a release?
> 
> Alternatively, would you be willing to add me as a contributor on
> Sourceforge to co-maintain dnsjava? I've been maintaining the Git mirror
> over at Github and the Maven Central release for a while now, and I've
> previously sent patches that you've applied, so I'm no total stranger.
> 
> We could also agree on some other options how to move forward, but it would
> be a real shame if this library would die completely.
> 
> Thanks,
> Ingo
> 
> PS: Sorry if you read this twice, I'm not sure if you're still receiving or
> reading the forums at Sourceforge.
> 

RE: Future of dnsjava

[Ingo B. <in...@ji...>]

Hi Brian

Thanks for getting back!

> The main reason that I haven’t applied any patches recently is that I
> wouldn’t feel comfortable applying patches and/or doing releases without
> reviewing and testing the changes, and I haven’t had the time or motivation
> to do either of those things.

I fully understand that; priorities and interests shift.

> If you (or anyone else) would like to assume maintenance of the project, I’d
> be in favor of that.  I haven’t used Java for anything other than maintaining
> dnsjava for at least 10 years, so it’s not too likely that I’m going to start
> doing more anytime soon.
> 
> If you do wish to be the maintainer, I’d much rather see the GitHub repo
> become the primary source.  There’s no compelling reason to use SourceForge
> (and there hasn’t been for a long time), and if I had been doing any serious
> development, I would have moved the project years ago.  There shouldn’t be a
> huge amount of state there worth saving (I think it’s just the open tickets),
> and I can also make you a maintainer of the project on SourceForge, in order
> to facilitate any redirection.

I'd happily spend some time moving it forward. If the main development is on Github, I'm sure more contributions follow and there will be slightly less work for everyone involved. I can't promise that I'll be around forever either though.

First steps would be to
- Change the readme on Github
- Reopen some Github issues
- Migrate Sourceforge issues
- Leave notices at Sourceforge that future development is happening on Github
- Add a CI build using Travis and Coveralls
- Work on some issues, e.g. https://github.com/dnsjava/dnsjava/pull/17 and Java 11+

I'd like to keep the Sourceforge project for the mailing lists since Github doesn't have an equivalent. Granted, they haven't been used much lately, but IMO it's still good to have a non-personal e-mail address. I'm not sure how you want to deal with dnsjava.org. Maybe it could be changed to a simple redirect to the Github repo or Github Pages.

> I’d definitely like to see the library continue, even if I’m not as involved.

If you agree with the ideas above, could you please add me as an admin/maintainer on Sourceforge? My username there is ibauersachs. I've sent you an invite for the repo on Github.

And thank you very much for all work that you've done so far! :-)

> Thanks,
> Brian

Cheers,
Ingo

Re: Future of dnsjava

[Brian W. <bwe...@xb...>]

> On May 14, 2019, at 1:38 PM, Ingo Bauersachs <in...@ji...> wrote:
> 
> Hi Brian
> 
> Thanks for getting back!
> 
>> The main reason that I haven’t applied any patches recently is that I
>> wouldn’t feel comfortable applying patches and/or doing releases without
>> reviewing and testing the changes, and I haven’t had the time or motivation
>> to do either of those things.
> 
> I fully understand that; priorities and interests shift.
> 
>> If you (or anyone else) would like to assume maintenance of the project, I’d
>> be in favor of that.  I haven’t used Java for anything other than maintaining
>> dnsjava for at least 10 years, so it’s not too likely that I’m going to start
>> doing more anytime soon.
>> 
>> If you do wish to be the maintainer, I’d much rather see the GitHub repo
>> become the primary source.  There’s no compelling reason to use SourceForge
>> (and there hasn’t been for a long time), and if I had been doing any serious
>> development, I would have moved the project years ago.  There shouldn’t be a
>> huge amount of state there worth saving (I think it’s just the open tickets),
>> and I can also make you a maintainer of the project on SourceForge, in order
>> to facilitate any redirection.
> 
> I'd happily spend some time moving it forward. If the main development is on Github, I'm sure more contributions follow and there will be slightly less work for everyone involved. I can't promise that I'll be around forever either though.
> 
> First steps would be to
> - Change the readme on Github
> - Reopen some Github issues
> - Migrate Sourceforge issues
> - Leave notices at Sourceforge that future development is happening on Github
> - Add a CI build using Travis and Coveralls
> - Work on some issues, e.g. https://github.com/dnsjava/dnsjava/pull/17 and Java 11+

These all sound reasonable.

> I'd like to keep the Sourceforge project for the mailing lists since Github doesn't have an equivalent. Granted, they haven't been used much lately, but IMO it's still good to have a non-personal e-mail address. I'm not sure how you want to deal with dnsjava.org. Maybe it could be changed to a simple redirect to the Github repo or Github Pages.

Keeping the sourceforge page for the mailing lists sounds reasonable enough.

The front page on dnsjava.org <http://dnsjava.org/> doesn’t have much content worth saving.  All of the releases can be downloaded from there, and it might be easier to copy those to GitHub than to copy them from sourceforge.  There’s also a link to the generated docs, and I’m not sure how easy it is to replicate that with GitHub.  I expect that it’s possible, but I never figured out how to do it with sourceforge.

The dnsjava.org <http://dnsjava.org/> domain actually expires this month.  If you want to take it over, I could transfer it, otherwise I’ll renew it for a year, but probably not indefinitely.

>> I’d definitely like to see the library continue, even if I’m not as involved.
> 
> If you agree with the ideas above, could you please add me as an admin/maintainer on Sourceforge? My username there is ibauersachs. I've sent you an invite for the repo on Github.

I accepted your invitation, and added you as an admin on sourceforge.

> 
> And thank you very much for all work that you've done so far! :-)

Thanks for keeping it alive!

Brian

RE: Future of dnsjava

[Ingo B. <in...@ji...>]

Hi Brian, everyone

I have now mostly cleaned up Sourceforge and put pointers to Github there. There wasn't much that I considered worth keeping. If I missed something, please open an issue or, better yet, a pull request at Github. A Travis job builds the pull requests, and Coveralls shows changes in tested code.

> The front page on dnsjava.org <http://dnsjava.org>  doesn’t have much content
> worth saving.  All of the releases can be downloaded from there, and it might
> be easier to copy those to GitHub than to copy them from sourceforge.
> There’s also a link to the generated docs, and I’m not sure how easy it is to
> replicate that with GitHub.  I expect that it’s possible, but I never figured
> out how to do it with sourceforge.

@kingle contributed a link to a javadoc.io, which pulls the Javadoc from Maven Central provides them as a website. IMO this is actually a better replacement since it's possible to switch between the published versions.

> The dnsjava.org <http://dnsjava.org>  domain actually expires this month.  If
> you want to take it over, I could transfer it, otherwise I’ll renew it for a
> year, but probably not indefinitely.

I'd like to avoid that a domain grabber places advertisement there, or a bad actor poisoned binaries. Please contact me offlist for a potential transfer.

> Brian

Ingo

Re: Future of dnsjava

[Brian W. <bwe...@xb...>]

On May 18, 2019, at 3:40 PM, Ingo Bauersachs <in...@ji...> wrote:
> 
> Hi Brian, everyone
> 
> I have now mostly cleaned up Sourceforge and put pointers to Github there. There wasn't much that I considered worth keeping. If I missed something, please open an issue or, better yet, a pull request at Github. A Travis job builds the pull requests, and Coveralls shows changes in tested code.

Thanks!

I have a (short) list somewhere of minor bugs that I was planning to fix at some point, and if I can find it, I’ll open GitHub tickets and/or pull requests..

>> The front page on dnsjava.org <http://dnsjava.org>  doesn’t have much content
>> worth saving.  All of the releases can be downloaded from there, and it might
>> be easier to copy those to GitHub than to copy them from sourceforge.
>> There’s also a link to the generated docs, and I’m not sure how easy it is to
>> replicate that with GitHub.  I expect that it’s possible, but I never figured
>> out how to do it with sourceforge.
> 
> @kingle contributed a link to a javadoc.io, which pulls the Javadoc from Maven Central provides them as a website. IMO this is actually a better replacement since it's possible to switch between the published versions.

That definitely sounds better.  Should this get added to the README?

>> The dnsjava.org <http://dnsjava.org>  domain actually expires this month.  If
>> you want to take it over, I could transfer it, otherwise I’ll renew it for a
>> year, but probably not indefinitely.
> 
> I'd like to avoid that a domain grabber places advertisement there, or a bad actor poisoned binaries. Please contact me offlist for a potential transfer.

Will do.  Thanks!

Brian

RE: Future of dnsjava

[Ingo B. <in...@ji...>]

> I have a (short) list somewhere of minor bugs that I was planning to fix
> at some point, and if I can find it, I’ll open GitHub tickets and/or
> pull requests..

That would certainly be a good thing to have. If you're too busy splitting it up, a container-issue with checkboxes ([ ] in markdown) will do as well. These can then be ticked off or later split up into individual issues.

>>> The front page on dnsjava.org <http://dnsjava.org>  doesn’t have much
>>> content worth saving.  All of the releases can be downloaded from
>>> there, and it might be easier to copy those to GitHub than to copy
>>> them from sourceforge. There’s also a link to the generated docs, and
>>> I’m not sure how easy it is to replicate that with GitHub.  I expect
>>> that it’s possible, but I never figured out how to do it with
>>> sourceforge.
>> 
>> @kingle contributed a link to a javadoc.io, which pulls the Javadoc from
>> Maven Central provides them as a website. IMO this is actually a better
>> replacement since it's possible to switch between the published versions.
> 
> That definitely sounds better.  Should this get added to the README?

There's already the badge on top, but I just extended the Additional documentation section. Feel free to inline-edit the README on Github yourself as well for anything else you find.

Ingo