[Sheepdog] Next version and user documentation

[Matthew Law]

Hi,

in my humble opinion, it is always good to have a users list.  The dev
list is fairly busy with patch submissions and dev chat which could put
off new or casual users from asking questions and those that do may have
their questions lost in the dev threads.

Kazutaka's point that there may be useful information on the user list
which would be useful to developers is a good one and other successful
projects tend to address this by having a few people who sit on both lists
and pass information between them.

For example, it is good to summarise complex patch submissions or the
issues addressed by a release into more user-readable info and post to the
users list.

For me, the vast majority of potential sheepdog users are not going to be
able to and really should not have to read the source to figure out how
some things work.  We are only as good as the quality of our documentation
and the help and support we give to our users.  Sheepdog is great.  We
just need to be better at making sure the world and all of the potential
users who can benefit from it know how good it is and can make use of it
as easily as possible.


Matt.

On Tue, May 15, 2012 12:07 pm, Tomasz Chmielewski wrote:
> On 05/11/2012 02:01 AM, MORITA Kazutaka wrote:
>
>>> Kazutaka, can we have a sheepdog-users list please? -either at
>>> lists.wpkg.org, or somewhere else suitable.
>>
>> Tomasz, is it possible to create sheepdog-users list on
>> lists.wpkg.org?  However, I wonder it's better to discuss user-side
>> issues on this list too because such inputs would be really important
>> for our developers.
>
> Hi,
>
> sorry for a late reply.
>
> We can of course create it - but what do we want to achieve?
>
> There aren't really that many user threads in the list already, so it
> could be that sheepdog-users list would be a bit empty at times.
>
> On the other hand, it would be easier to search sheepdog-users archives,
> without all [PATCH] emails.
>
> Should I proceed and create it?
>
>
> --
> Tomasz Chmielewski
>
>