[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2301: The term "filesystem" is too overloaded.

[Tahoe-LAFS]

#2301: The term "filesystem" is too overloaded.
-------------------------------+---------------------------
 Reporter:  Zancas             |          Owner:  marlowe
     Type:  defect             |         Status:  new
 Priority:  minor              |      Milestone:  undecided
Component:  documentation      |        Version:  1.10.0
 Keywords:  name names naming  |  Launchpad Bug:
-------------------------------+---------------------------
 When we describe the application as a filesystem, people anticipate it to
 have properties it does not (e.g. POSIX compliance), if I understand
 properly.

 Since the application will never have those properties, it should be
 described as something other than a filesystem.

 Here's a snippet warner and I chatting in IRC:

 {{{
 <zancas> Would it be useful to replace the term "filesystem" with
 something
          else in this (and other docs)?
 <zancas> If yes, is there an agreed upon replacement?  [13:32]
 <warner> hm, good question  [13:34]
 <warner> I suppose "storage system" is slightly less misleading
 }}}

 I'll change the word "filesystem" to "data store" in the commit I'm
 making.  Even if this doesn't pass review it'll draw welcome attention to
 the issue.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2301>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage