search

n-t-roff / heirloom-doctools

The Heirloom Documentation Tools: troff, nroff, and related utilities
http://n-t-roff.github.io/heirloom/doctools.html
Other
127 stars 23 forks source link

Heirloom doctools maintenance #87

Open n-t-roff opened 5 years ago

n-t-roff commented 5 years ago

Unfortunately I don't have the time to do any further work on GitHub projects. It had already been agreed to continue the Heirloom-doctools development @reffort 's GitHub account. The project at the account here (@n-t-roff) could either be replaced by a link to the new location or it could be freezed with a noticeable remark regarding the new location (I'd prefere that since there are automatic packaging tools around which know the current location. Of course these packages need to be updated to point to the new location some day.)

Alhadis commented 5 years ago

When transferring ownership of a repository on GitHub, any old links will redirect to the new owner's URL.

n-t-roff commented 5 years ago

Ok, then this would be the preferred way.

reffort commented 5 years ago

This is sad news. I've substantially cut back on GitHub participation, as well, but if there is a need to park the project somewhere, my account should work as well as any.

The further development I had in mind was to advance the typographical capabilities without any particular consideration for badly coded man pages or groff compatibility. Both of those things will necessarily break, which would make the developmental repository unsuitable for backward-looking applications that require them. As a result, the current track (support for man pages, etc.) will need to exist separately.

n-t-roff commented 5 years ago

The current code here need not be deleted (at least until someone else is interested in maintaining the traditional nroff etc. functionality). Applying pull requests here is also still possible.

So we can continue as we had decided that you do the further development at your account without regard on compatibility. If you give the project a new name or not is up to you.

mohd-akram commented 4 years ago

Could there be a new release? There hasn't been one for a while.

n-t-roff commented 4 years ago

I'll try to find the time for it next week.

Alhadis commented 4 years ago

@n-t-roff Do you want a hand setting up continuous integration? Releases (even cross-platform) can be automatically built and attached as assets when tagged releases get published.

Even test-results can be displayed in the readme file using shields.io.

n-t-roff commented 4 years ago

You would need unit and application level tests with sufficient coverage for this. This could be a topic for the next project maintainer.