Hi!
Pardon the radio silence; it's a busy week and I'm still learning the ropes here myself. I'll get to obsolete-content policy below, and to patch 2/2 eventually, but a couple of further tips on conventions first: - On the mailing-list, please interleave replies instead of "top-posting": https://orgmode.org/worg/org-mailing-list.html#org3c940e4 - For patches, please keep commit messages close to the format: https://orgmode.org/worg/org-contribute.html#commit-messages Charles Choi <kickingve...@gmail.com> writes: > Please provide guidance on policy for archiving obsolete WORG pages. > > Also request guidance on handling obsolete content on an existing WORG page. I favor keeping things simple, cautiously deleting obsolete content without archiving when we can, using the archive sparingly, avoiding duplication, and keeping links between worg pages current. The archive directory is for obsolete *self-contained* documents that may somehow be useful for future reference. If we want to keep obsolete *snippets* of information for the same reason, they can be placed in a clearly marked section at the end of a current document. There's no need to archive everything we delete; we can always resurrect it from git. Regarding *org-protocol.org*, I think we should *not* create a backup copy in worg/archive. Org-protocol is not obsolete, and duplicate org-protocol pages might cause confusion. We should keep whatever might still be helpful and delete the rest. We don't need the archive for version control. Regarding *org-annotation-helper.org*, this page is clearly obsolete and self-contained, so it's a candidate for the archive. I struggle to articulate a reason why it might be useful for future reference, though. And its historical value is perhaps best preserved where it is, as the worg/org-contrib/index.org page is very informative about contrib history. So I lean toward leaving it in place for now, but putting an obsolescence warning and reference to org-protocol at the top. *If* we do find a reason to move it to the archive, I suggest the following: Max Nikulin wrote upthread: > Having 2 pages for org-annotation-helper is the worst option from my > point of view, especially since the archive/ page do not have the > banner suggesting org-protocol as the replacement. Agreed, we should avoid duplication, but I have a different idea how to do it: - Remove org-annotation-helper.org from worg/org-contrib and move it to worg/archive (updating relative links as needed) - Add the banner in the moved worg/archive/org-annotation-helper.org - Remove the link to org-annotation-helper.org from worg/org-contrib/index.org and add a link to worg/archive/index.org. Max Nikulin wrote: > I prefer to add permanent HTTP redirection from the current article > path, but I do not insist. Max, just checking: You mean something like this in worg/nginx.conf? rewrite ^/worg/org-contrib/org-annotation-helper\.html https://orgmode.org/worg/archive/org-annotation-helper.html permanent; That's good. I'm okay with breaking people's bookmarks for obsolete stuff, but redirecting is always more polite. Yours, Christian
