[Gluster-devel] [Gluster-users] Gluster Community Weekly Meeting

[Vijay Bellur]

On 12/12/2013 10:42 AM, James wrote:
> RE: meeting, sorry I couldn't make it, but I have some comments:

No problem. It would be really good to have everybody in the meeting, 
but if you cannot comments are definitely welcome :).

>
> 1) About the pre-packaged VM comment's. I've gotten Vagrant working on
> Fedora. I'm using this to rapidly spin up and test GlusterFS.
> https://ttboj.wordpress.com/2013/12/09/vagrant-on-fedora-with-libvirt/
> In the coming week or so, I'll be publishing the Vagrant file for my
> GlusterFS setup, but if you really want it now I can send you an early
> version. This obviously integrates with Puppet-Gluster, but whether
> you use that or not is optional. I think this is the best way to test
> GlusterFS. If someone gives me hosting, I could publish "pre-built"
> images very easily. Let me know what you think.

Niels - do you have any thoughts here?

>
> 2) I never heard back from any action items from 2 weeks ago. I think
> someone was going to connect me with a way to get access to some VM's
> for testing stuff !

I see that there is an ongoing offline thread now. I think that should 
result in you getting those VMs.

>
> 3) Hagarth:  RE: typos, I have at least one spell check patch against
> 3.4.1 I sent it to list before, but someone told me to enroll in the
> jenkins thing, which wasn't worth it for a small patch. Let me know if
> you want it.

There are more typos now. I ran a cursory check with misspell-check [1] 
and found quite a few. Having that cleaned up on master and release-3.5 
would be great. Since the number is more, I am sure the patch would be 
non-trivial and having that routed through gerrit would be great. If you 
need a how to on getting to gerrit, it is available at [2].

>
> 4a) Someone mentioned documentation. Please feel free to merge in
> https://github.com/purpleidea/puppet-gluster/blob/master/DOCUMENTATION.md
> (markdown format). I have gone to great lengths to format this so that
> it displays properly in github markdown, and standard (pandoc)
> markdown. This way it works on github, and can also be rendered to a
> pdf easily. Example:
> https://github.com/purpleidea/puppet-gluster/raw/master/puppet-gluster-documentation.pdf
>   You can use the file as a template!

Again having this in gerrit would be useful for merging the puppet 
documentation.

>
> 4b) I think the documentation should be kept in the same repo as
> GlusterFS. This way, when you submit a feature branch, it can also
> come with documentation. Lots of people work this way. It helps you
> get minimal docs there, and/or at least some example code or a few
> sentences. Also, looking at the docs, you can see what commits came
> with this

I am with you on this one. After we are done with the planned 
documentation hackathon, let us open a new thread on this to get more 
opinions.

-Vijay

[1] https://github.com/lyda/misspell-check

[2] 
http://www.gluster.org/community/documentation/index.php/Development_Work_Flow

>
> Thanks!
>
> James
>
>