public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell Cattelan <cattelan@thebarn.com>
To: "Linda A. Walsh" <xfs@tlinx.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: future of xfs, oss.sgi.com after sgi purchased?
Date: Thu, 16 Apr 2009 10:54:08 -0500	[thread overview]
Message-ID: <49E754A0.30608@thebarn.com> (raw)
In-Reply-To: <49E65044.8080802@tlinx.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Linda A. Walsh wrote:
> Not one to beat about the bush, but curious from a practical sense,
>
> If sgi is being bought by another company, is there any idea about
> the plans
> for the xfs file system or the source code on 'oss.sgi.com'?
>
> I'm _guessing_ that there is some interest in users and developers
> to keep xfs alive after the 'sgi' moniker is purchased, but that
> begs the question about the new company wanting to support the old
> 'sgi.com' websites including
> oss.sgi.com.
It is probably to soon to actually speculate as to what is going to
happen with oss.sgi.com once the sale of SGI happens.

But is it probably worth while to understand oss has been primarily a
volunteer effort for probably the last 5 years or more.
There is nobody at SGI officially responsible for oss, most of the
system maintenance is handled by Trevor Hurst (who does work at sgi)
and myself (who does not), and the efforts of other external
volunteers. The system itself is 2 processor Altix owned and housed by
SGI in one of their data
centers in Chippewa Falls Wisconsin.

The XFS project also has xfs.org, which I also maintain independent of
SGI systems and I will continue to do so for as long
as XFS is alive and kicking.
>
> Is there a danger of oss.sgi.com suddenly being yanked offline with
> little to no warning, such that community members should start
> keeping up-to-date, or is it already mirrored?  I'm assuming that
> the current source code repository only exists on oss.sgi.com?
> Should it be mirrored on some other external open-source site?
> sourceforge? google? mozilla?
Most things (git, cvs, mail list/archives etc)  are being mirrored at
xfs.org as a precautionary measure against any sort of outage for
quite some time now.

I highly doubt there will be any sudden "yanking" of systems.

>
> Is completely worthless to discuss new, desired features in some of
> the utils? Will it be possible to support the xfs codebase if its
> development no longer becomes necessary to sgi (or its parent company)?
Well that is up to you I suppose, but given the number of external
people willing to keep XFS going I suspect you will be able
to find more than enough conversation about future development.

>
> *sigh*,
> -linda
>
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJ51SgNRmM+OaGhBgRAl42AJ9E1KHX90q7rhqWMJBv9rFAImB2agCcCbuQ
/0PfKtwNbNeGz3xR7CY5SsU=
=5Vv2
-----END PGP SIGNATURE-----

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      parent reply	other threads:[~2009-04-16 15:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15 21:23 future of xfs, oss.sgi.com after sgi purchased? Linda A. Walsh
2009-04-16  4:41 ` Eric Sandeen
2009-04-16  8:34   ` Linda A. Walsh
2009-04-16 14:54     ` Eric Sandeen
2009-04-16 18:36       ` getting changes (fixes or enhancements) to xfs-tools Linda A. Walsh
2009-04-16 20:50         ` Eric Sandeen
2009-04-16 21:15         ` Felix Blyakher
2009-04-16  6:05 ` future of xfs, oss.sgi.com after sgi purchased? Felix Blyakher
2009-04-16 15:54 ` Russell Cattelan [this message]

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=49E754A0.30608@thebarn.com \
    --to=cattelan@thebarn.com \
    --cc=xfs@oss.sgi.com \
    --cc=xfs@tlinx.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