Re: [Gluster-devel] Recognizing contributors and displaying other useful bits?

[Kaleb KEITHLEY]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 12/17/2015 10:05 AM, Niels de Vos wrote:
> On Wed, Dec 16, 2015 at 10:05:04PM +0530, Ravishankar N wrote:
> 
>> But yes, if  we do want to expose this information via the mount 
>> point, then maybe /mount/.meta is a good place.
> 
> Indeed, .meta would be better :)

Can you be certain there isn't some application somewhere that uses
/mount/.meta ?

I would prefer that we not litter the namespace with magic filenames.
Any more than it's already littered.

I'd prefer an xattr over a file. And something that's sufficiently
random that it won't collide (high probability) with an application
file. E.g. a uuid created with `uuidgen -r`

- --

Kaleb

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJWctNJAAoJEDcw3UmJzK6LqBwH/AxqUtxvn8fWF/SqlLc4GekA
Ukpa/4i/VBjoLQLFLkS6HJw3e60ZaE5QnDWXyYPZPQXseQuxIC971rVI7JQgsOCA
HbrkNirkZ45LHLD1g7XO9+hJkObXF3aXAvsugmQByt4QZpVY3Rmz9gUjsH33WTCF
BFlOeYoGK75onWtK3haCYUJqEqlgXQmPXS0lCOJt+yXzznpF86G6ShKuf1GQvGzy
ugVQx8HRLsqY7Zvbf9n7ve8tLtCV22xR1uU3lUBqJFbVo9aum1rRX4H6QMb7M6qj
aFld1na0YeQOYG6HoRIdgQzwzbRzQZi1i3z8JJXRj8XQOdmA+XzvzP2JXOEPusA=
=V/id
-END PGP SIGNATURE-


0x89CCAE8B.asc
Description: application/pgp-keys
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Recognizing contributors and displaying other useful bits?

[Niels de Vos]

On Thu, Dec 17, 2015 at 10:22:56AM -0500, Kaleb KEITHLEY wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> On 12/17/2015 10:05 AM, Niels de Vos wrote:
> > On Wed, Dec 16, 2015 at 10:05:04PM +0530, Ravishankar N wrote:
> > 
> >> But yes, if  we do want to expose this information via the mount 
> >> point, then maybe /mount/.meta is a good place.
> > 
> > Indeed, .meta would be better :)
> 
> Can you be certain there isn't some application somewhere that uses
> /mount/.meta ?
> 
> I would prefer that we not litter the namespace with magic filenames.
> Any more than it's already littered.

That is why I was suggesting .glusterfs. There would not be many
applications that use this directory. However, .meta would be more
suitable because we already have the meta xlator:

  https://github.com/gluster/glusterfs-specs/blob/master/done/Features/meta.md

I'm thinking of extending this to include at least an AUTHORS file.

Niels


> 
> I'd prefer an xattr over a file. And something that's sufficiently
> random that it won't collide (high probability) with an application
> file. E.g. a uuid created with `uuidgen -r`
> 
> - --
> 
> Kaleb
> 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
> 
> iQEcBAEBCAAGBQJWctNJAAoJEDcw3UmJzK6LqBwH/AxqUtxvn8fWF/SqlLc4GekA
> Ukpa/4i/VBjoLQLFLkS6HJw3e60ZaE5QnDWXyYPZPQXseQuxIC971rVI7JQgsOCA
> HbrkNirkZ45LHLD1g7XO9+hJkObXF3aXAvsugmQByt4QZpVY3Rmz9gUjsH33WTCF
> BFlOeYoGK75onWtK3haCYUJqEqlgXQmPXS0lCOJt+yXzznpF86G6ShKuf1GQvGzy
> ugVQx8HRLsqY7Zvbf9n7ve8tLtCV22xR1uU3lUBqJFbVo9aum1rRX4H6QMb7M6qj
> aFld1na0YeQOYG6HoRIdgQzwzbRzQZi1i3z8JJXRj8XQOdmA+XzvzP2JXOEPusA=
> =V/id
> -END PGP SIGNATURE-

> pub  2048R/89CCAE8B 2011-10-04 Kaleb S. KEITHLEY 
> sub  2048R/AFFECD68 2011-10-04

> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel



signature.asc
Description: PGP signature
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Recognizing contributors and displaying other useful bits?

[Niels de Vos]

On Wed, Dec 16, 2015 at 10:05:04PM +0530, Ravishankar N wrote:
> On 12/16/2015 07:36 PM, Niels de Vos wrote:
> >Hi,
> >
> >Many GUI tools provide an "About" box that displays some information
> >about the project. Some applications (Wireshark for example) go an extra
> >step by including a list of all people that contributed patches. That is
> >quite a nice way for contributors to see the appreciation of their work.
> >
> >I think it would be really awesome if we could do something similar. We
> >have our reserved+hidden ".glusterfs" directory where all access is
> >denied. We could populate this directory with static compiled-in
> >contents. When accessed from a client, the licenses, versions, authors
> >and other bits could be displayed. A normal readdir should still not
> >list the directory at all (no change from current behaviour).
> >
> >Any thoughts?
> 
> I think It would be better to revive the who-wrote-glusterfs reports that
> Vijay used to send on the mailing list instead of statically adding
> contributor names to code.

Well, I would like to see an AUTHORS list automatically generated by
'make dist' or the such.

> We could have a `gluster --credits` or `gluster--help`  cli that points to
> gluster.org and maybe add a button thingy on the website which when clicked
> runs the who-wrote-glusterfs.sh  on   and displays the
> result. Things like version numbers and licenses are/should be covered in
> gluster--version.

I think it would be nice to be able to see some information through a
client mount point. Not everyone that uses Gluster has access to the
storage servers, and it can benefit them to see some info.

> But yes, if  we do want to expose this information via the mount point, then
> maybe /mount/.meta is a good place.

Indeed, .meta would be better :)

Thanks,
Niels

> 
> My 2 cents.
> Ravi
> 
> 
> 
> >Niels
> >
> >
> >___
> >Gluster-devel mailing list
> >Gluster-devel@gluster.org
> >http://www.gluster.org/mailman/listinfo/gluster-devel
> 
> 
> -- 
> > : Any porters out there should feel happier knowing that DEC is shipping >
> : me an AlphaPC that I intend to try getting linux running on: this will > :
> definitely help flush out some of the most flagrant unportable stuff. > :
> The Alpha is much more different from the i386 than the 68k stuff is, so > :
> it's likely to get most of the stuff fixed. > > It's posts like this that
> almost convince us non-believers that there > really is a god. (A follow-up
> by alov...@kerberos.demon.co.uk, Anthony Lovell, to Linus's remarks about
> porting)


signature.asc
Description: PGP signature
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Recognizing contributors and displaying other useful bits?

[Niels de Vos]

On Wed, Dec 16, 2015 at 10:13:01PM +0530, Venky Shankar wrote:
> 
> 
> Ravishankar N wrote:
> >On 12/16/2015 07:36 PM, Niels de Vos wrote:
> >>Hi,
> >>
> >>Many GUI tools provide an "About" box that displays some information
> >>about the project. Some applications (Wireshark for example) go an extra
> >>step by including a list of all people that contributed patches. That is
> >>quite a nice way for contributors to see the appreciation of their work.
> >>
> >>I think it would be really awesome if we could do something similar. We
> >>have our reserved+hidden ".glusterfs" directory where all access is
> >>denied. We could populate this directory with static compiled-in
> >>contents. When accessed from a client, the licenses, versions, authors
> >>and other bits could be displayed. A normal readdir should still not
> >>list the directory at all (no change from current behaviour).
> >>
> >>Any thoughts?
> >
> >I think It would be better to revive the who-wrote-glusterfs reports
> >that Vijay used to send on the mailing list instead of statically adding
> >contributor names to code.
> >We could have a `gluster --credits` or `gluster--help`  cli that points
> >to gluster.org and maybe add a button thingy on the website which when
> >clicked runs the who-wrote-glusterfs.sh  on   and
> >displays the result. Things like version numbers and licenses are/should
> >be covered in gluster--version.
> 
> or a tshirt with contributors list on the back :)

That was a plan once, but I do not think this actually happened. Maybe
we should try to get that done for 3.8, or 4.0.

Niels

> 
> >
> >But yes, if  we do want to expose this information via the mount point,
> >then maybe /mount/.meta is a good place.
> 
> Ummm.. makes sense.
> 
> >
> >My 2 cents.
> >Ravi
> >
> >
> >
> >>Niels
> >>
> >>
> >>___
> >>Gluster-devel mailing list
> >>Gluster-devel@gluster.org
> >>http://www.gluster.org/mailman/listinfo/gluster-devel
> >
> >
> >--
> > > : Any porters out there should feel happier knowing that DEC is
> >shipping > : me an AlphaPC that I intend to try getting linux running
> >on: this will > : definitely help flush out some of the most flagrant
> >unportable stuff. > : The Alpha is much more different from the i386
> >than the 68k stuff is, so > : it's likely to get most of the stuff
> >fixed. > > It's posts like this that almost convince us non-believers
> >that there > really is a god. (A follow-up by
> >alov...@kerberos.demon.co.uk, Anthony Lovell, to Linus's remarks about
> >porting)
> >
> >___
> >Gluster-devel mailing list
> >Gluster-devel@gluster.org
> >http://www.gluster.org/mailman/listinfo/gluster-devel


signature.asc
Description: PGP signature
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Recognizing contributors and displaying other useful bits?

[Ravishankar N]

On 12/16/2015 07:36 PM, Niels de Vos wrote:

Hi,

Many GUI tools provide an "About" box that displays some information
about the project. Some applications (Wireshark for example) go an extra
step by including a list of all people that contributed patches. That is
quite a nice way for contributors to see the appreciation of their work.

I think it would be really awesome if we could do something similar. We
have our reserved+hidden ".glusterfs" directory where all access is
denied. We could populate this directory with static compiled-in
contents. When accessed from a client, the licenses, versions, authors
and other bits could be displayed. A normal readdir should still not
list the directory at all (no change from current behaviour).

Any thoughts?


I think It would be better to revive the who-wrote-glusterfs reports 
that Vijay used to send on the mailing list instead of statically adding 
contributor names to code.
We could have a `gluster --credits` or `gluster--help`  cli that points 
to gluster.org and maybe add a button thingy on the website which when 
clicked runs the who-wrote-glusterfs.sh  on   and 
displays the result. Things like version numbers and licenses are/should 
be covered in gluster--version.


But yes, if  we do want to expose this information via the mount point, 
then maybe /mount/.meta is a good place.


My 2 cents.
Ravi




Niels


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel



--
> : Any porters out there should feel happier knowing that DEC is 
shipping > : me an AlphaPC that I intend to try getting linux running 
on: this will > : definitely help flush out some of the most flagrant 
unportable stuff. > : The Alpha is much more different from the i386 
than the 68k stuff is, so > : it's likely to get most of the stuff 
fixed. > > It's posts like this that almost convince us non-believers 
that there > really is a god. (A follow-up by 
alov...@kerberos.demon.co.uk, Anthony Lovell, to Linus's remarks about 
porting)
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Recognizing contributors and displaying other useful bits?

[Venky Shankar]

Ravishankar N wrote:

On 12/16/2015 07:36 PM, Niels de Vos wrote:

Hi,

Many GUI tools provide an "About" box that displays some information
about the project. Some applications (Wireshark for example) go an extra
step by including a list of all people that contributed patches. That is
quite a nice way for contributors to see the appreciation of their work.

I think it would be really awesome if we could do something similar. We
have our reserved+hidden ".glusterfs" directory where all access is
denied. We could populate this directory with static compiled-in
contents. When accessed from a client, the licenses, versions, authors
and other bits could be displayed. A normal readdir should still not
list the directory at all (no change from current behaviour).

Any thoughts?


I think It would be better to revive the who-wrote-glusterfs reports
that Vijay used to send on the mailing list instead of statically adding
contributor names to code.
We could have a `gluster --credits` or `gluster--help`  cli that points
to gluster.org and maybe add a button thingy on the website which when
clicked runs the who-wrote-glusterfs.sh  on   and
displays the result. Things like version numbers and licenses are/should
be covered in gluster--version.


or a tshirt with contributors list on the back :)



But yes, if  we do want to expose this information via the mount point,
then maybe /mount/.meta is a good place.


Ummm.. makes sense.



My 2 cents.
Ravi




Niels


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel



--
 > : Any porters out there should feel happier knowing that DEC is
shipping > : me an AlphaPC that I intend to try getting linux running
on: this will > : definitely help flush out some of the most flagrant
unportable stuff. > : The Alpha is much more different from the i386
than the 68k stuff is, so > : it's likely to get most of the stuff
fixed. > > It's posts like this that almost convince us non-believers
that there > really is a god. (A follow-up by
alov...@kerberos.demon.co.uk, Anthony Lovell, to Linus's remarks about
porting)

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel