Christian - Thanks for your input. My thoughts to your responses below.
> - 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 Noted for future use. > 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. Understood. That said, I do think significant pruning and revision of the content for Org Protocol on WORG is merited due to obsolescence. I advocate that “org-protocol.org” should be re-written. > > 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. > Understood. I will be less concerned about conservation of outdated content. > 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. Understood. > *If* we do find a reason to move it to the archive, I suggest the > following: > I will leave it to you to take action on any archival operation. Given the current state of this conversation, I will take the following action items: - Make a patch for “org-annotation-helper.org” - Declare it obsolete. - Link to current Org Protocol manual page. - Make a patch for “org-protocol.org” - Re-write document. Thanks again for the feedback and hopefully this will result in improved documentation for Org Protocol. Charles
