linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Marc MERLIN <marc@merlins.org>,
	dsterba@suse.cz, Justin Maggard <jmaggard10@gmail.com>,
	Daniel Lee <longinus00@gmail.com>,
	linux-btrfs@vger.kernel.org, clm@fb.com
Subject: Re: Which companies are using Btrfs in production?
Date: Mon, 28 Apr 2014 10:01:00 -0500	[thread overview]
Message-ID: <535E6D2C.5080404@redhat.com> (raw)
In-Reply-To: <20140425152045.GK13819@merlins.org>

On 4/25/14, 10:20 AM, Marc MERLIN wrote:
> On Fri, Apr 25, 2014 at 04:47:04PM +0200, David Sterba wrote:
>> On Thu, Apr 24, 2014 at 04:14:56PM -0700, Marc MERLIN wrote:
>>>>> Netgear uses BTRFS as the filesystem in their refreshed ReadyNAS line.
>>>>> They apparently use Oracle's linux distro so I assume they're relying on
>>>>> them to do most of the heavy lifting as far as support BTRFS and
>>>>> backporting goes since they're still on 3.0! They also have raid5/6
>>>>> support so they are probably running BTRFS on top of md.
>>>>>
>>>>
>>>> Yes, and any contributions you see coming from me so far, come from
>>>> NETGEAR.  I've been using my gmail account because I can't make our
>>>
>>> Thanks. 
>>> https://btrfs.wiki.kernel.org/index.php/Contributors
>>> Updated :)
>>
>> There are lots of contributors with the same small amout of patches
>> contributed and are not listed there.  This is first time I hear about
>> Netgear being a contributor and it looks strange to see that name among
>> the major contributors.
>>
>> If there's demand to list all the minor contributors, then let's add a
>> separate section, otherwise I'm going to remove the entry.
> 
> Mmmh. So I'm not Jon Corbet who has all those fancy honed scripts + non
> trivial time he spends doing this by hand.
> 
> That said, my goal was not to say which company gave the most
> contributions and try and rank them.
> Honestly, right now any company that is using btrfs and contributing to
> it is a great thing in my book.
> I'm not even a fan of counting number of lines or frequency of patches.
> How do you compare someone sending easy cleanup patches vs someone who
> spent a month tracking down a file corruption problem no one could find
> nor fix, and sends a 3 line patch to fix it in the end?

Just for the record, I certainly didn't mean that my git patch-counting
example was the be-all and end-all of "contribution accounting" - it's
just one metric of many; not meant to be inclusive, but might help to avoid
missing people or companies who have contributed in this particular way.

-Eric


  parent reply	other threads:[~2014-04-28 15:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24  1:18 Which companies contribute to Btrfs? Marc MERLIN
2014-04-24  1:19 ` Which companies are using Btrfs in production? Marc MERLIN
2014-04-24  7:13   ` Adam Brenner
2014-04-24 12:34   ` Austin S. Hemmelgarn
2014-04-24 12:52   ` Tomasz Torcz
2014-04-24 13:34   ` Daniel Lee
2014-04-24 21:41     ` Marc MERLIN
2014-04-24 22:03     ` Justin Maggard
2014-04-24 23:14       ` Marc MERLIN
2014-04-25 14:47         ` David Sterba
2014-04-25 15:01           ` Chris Mason
2014-04-25 15:20           ` Marc MERLIN
2014-04-25 15:32             ` ronnie sahlberg
2014-04-28 14:16             ` David Sterba
2014-04-28 15:01             ` Eric Sandeen [this message]
2014-04-24  2:29 ` Which companies contribute to Btrfs? Eric Sandeen
2014-04-24  2:30 ` Eric Sandeen
2014-04-24  3:45   ` Marc MERLIN
2014-04-24  4:32     ` Eric Sandeen
2014-04-24 10:31 ` Filipe David Manana
2014-04-24 17:07   ` Marc MERLIN
2014-04-24 11:39 ` David Sterba
2014-04-24 12:55   ` Fajar A. Nugraha
2014-04-24 21:41     ` Marc MERLIN
2014-04-28 19:00 ` Jonathan Corbet
2014-04-28 21:06   ` Chris Mason
2014-04-29  0:06   ` Chester
2014-04-29  0:08     ` Marc MERLIN
2014-04-29  0:55     ` Chris Mason

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=535E6D2C.5080404@redhat.com \
    --to=sandeen@redhat.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.cz \
    --cc=jmaggard10@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=longinus00@gmail.com \
    --cc=marc@merlins.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).