Ticket #3409 enhancement closed wontfix

Opened 6 years ago

Last modified 3 months ago

doc/ directory should contain a brief explanation of how to generate the documentation from it

Reported by: glyph Owned by:
Priority: normal Milestone:
Component: lore Keywords: documentation EndOfLore
Cc: thijs Branch: branches/lore-readme-3409
(diff, github, buildbot, log)
Author: thijs Launchpad Bug:

Description

If someone came along and wanted to help maintain the twisted documentation (wouldn't that be great?), they would probably not be able to guess the options to lore which would allow them to produce HTML or PDF documentation like the versions that we have on the website and proofread their markup.

There should be a README.txt that explains "run lore like this, in this directory".

I am assigning this to radix to make sure that this document is at least vaguely congruent, in any relevant way, with the way the documentation is generated for release.

Change History

1

Changed 5 years ago by thijs

  • cc thijs added
  • owner changed from radix to thijs
  • status changed from new to assigned
  • keywords documentation added

Yes, that would be useful indeed! Will ask someone on IRC about it.

2

Changed 5 years ago by glyph

Eventually I'd like to adjust the documented solution here to be 'cd doc; lore'.

For an example of how this might be set up, see  http://divmod.org/trac/browser/trunk/Mantissa/doc/README.txt

3

Changed 5 years ago by thijs

  • branch set to branches/lore-readme-3409
  • branch_author set to thijs

(In [26446]) Branching to 'lore-readme-3409'

4

Changed 5 years ago by thijs

  • owner thijs deleted
  • keywords documentation, review added; documentation removed
  • status changed from assigned to new

I added such a README file in doc/core/howto in r26449. Running 'lore' from the top folder (doc/) doesn't work (it returns getProcessor() failed).

5

Changed 5 years ago by glyph

  • owner set to thijs
  • keywords documentation added; documentation, review removed

The toplevel doc/ directory needs a README as well, if it is expected that anyone will actually find this file.

Perhaps for the time being it should simply refer to doc/core/howto and there should be separate tickets for simplifying this process to work across all the projects? (Presumably also fixing the doc-building scripts, such as they are, to know about this?)

6

Changed 4 years ago by thijs

  • component changed from core to lore

This is a lore-related ticket.

7

Changed 4 years ago by exarkun

  • owner changed from thijs to khorn

8

Changed 3 years ago by glyph

  • summary changed from doc/ directory should contain a brief explanation of how to run lore on it to doc/ directory should contain a brief explanation of how to generate the documentation from it

Updating description to be a little more future-proof.

9

Changed 3 years ago by <automation>

  • owner khorn deleted

10

Changed 3 months ago by khorn

  • status changed from new to closed
  • keywords EndOfLore added
  • resolution set to wontfix

Lore is no longer being used for Twisted documentation, and is being deprecated, prior to eventual removal, per #6907.

This issue will not be fixed.

Note: See TracTickets for help on using tickets.