Re: [MooseFS-Users] Docs about master protocol and VCS

[Gandalf C. <gan...@gm...>]

Il giorno lun 28 mag 2018 alle ore 20:03 Casper Langemeijer <
cas...@pr...> ha scritto:
> Then you state that there should be documentation. You are very wrong
there. Unless you pay for something, you cannot make any demands. The guys
at MooseFS are very talented programmers building very stable software.
Because of the businessmodel they choose, it is for you to use at
absolutely no cost. I would be humble instead of making demands.

I'm sorry but I strongly disagree.
Documentation is different from support.
if you use an OSS, you don't have any support. You'll use it as-is.
But proper documentation is needed for any kind of product.
Look at any OSS project. Even on linux there are man pages. A man page is a
documentation about a product.

> Then there is the question itself. There is no documentation. This
probably is because it is an *internal* thing of the system. I've had to
change my nagios monitoring script multiple times, because sometimes the
protocol changes. Just because you *can* talk to a listening socket,
doesn't mean that you are supposed to. It simply is not a documented API.

Is not true.
What are you saying is correct for a closed source software, where you are
forced to use what is provided.
In Windows, you don't have access to internal APIs, because you are not
supposed to do that kind of things.
But AFAIK this is an open project, even if someone is willing to contribute
with some code, should know how things works.
Are you saying that to add a very simple feature (just an example), a
developer has to reverse-engineer the whole project ?
This is very time consuming and more prone to errors and as result, will
keep developers far away.

Simple example: https://github.com/gluster/glusterfs-specs