boostbook documentation is at serious risk of becoming impossible to use
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- java
- Domain
- build-system, documentation
Research direction
Start by reviewing the BoostBook setup scripts duplicated into the Ubuntu Bionic Docker environment and the listed docbook-xsl, docbook-xml, and FOP dependencies. Determine whether supported versions can replace them or whether another documentation system is needed; done means the documentation build no longer depends on the identified obsolete tools.
Written by the indexing model from the issue text.
Description
I would have opened an "issue" on the boostorg/boostbook project, however, that is not enabled.
I have been duplicating the boostbook setup scripts into the docker setup environment for Ubuntu Bionic and I have found that all of the packages that boostbook depends on are ancient.
| Package | Version | Last Modified | Host |
|---|---|---|---|
| docbook-xsl | 1.75.2 | 2009 | SourceForge |
| docbook-xml | 4.2 | 2002 | oasis-open.org |
| fop | 0.94 | 2007 | Apache |
These tools are quite old and it is only a matter of time before the older versions could be removed. These external sites are under no particular requirement to keep these older versions of software available. At some point some of these tools may no longer work with current operating system tools, for example fop says that it is for "JDK 1.4".
Each of these tools has a newer version. A project should be initiated to modernize the documentation build to use the latest versions of these tools, or switch to another documentation system perhaps (I saw a discussion on the mailing list).
- Dominant language
- No language data
- Stars
- 4
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from boostorg/admin
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
area:engineering priority:p2 type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jejjohnson/pyrox#234 ·
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 85/100
ros2/ros2_tracing#266 · 1 comment ·