[petsc-dev] petsc-dev on bitbucket

Matthew Knepley knepley at gmail.com
Fri Feb 10 09:41:11 CST 2012


On Fri, Feb 10, 2012 at 9:35 AM, Satish Balay <balay at mcs.anl.gov> wrote:

> On Fri, 10 Feb 2012, Barry Smith wrote:
>
> >
> > On Feb 10, 2012, at 9:13 AM, Matthew Knepley wrote:
> >
> > > The thread has become too deep for me to read, hence the top posting.
> > >
> > > Barry's question is the right one: What do we gain by changing?
> > >
> > >   1) Reliability and Availability
> > >
> > >    Barry, you should know that this crap about petsc.cs being backed
> up is farcical. We
> > >    would have the same situation we had with the first 10 years of
> PETSc history again.
> > >    BB is definitely more reliable in terms of backups, uptime, and
> connectivity (SSH issues).
> > >
> > >    2) Better management support
> > >
> > >    The infrastructure for supporting user permissions is better on BB.
> We don't edit a file,
> > >     calling a script someone hacked together. We have accounts, and
> when accounts are
> > >     shut down they go away. A user can manage his SSH key
> independently of us.
> > >
> > > Those for me make it a slam dunk. However, I will ask the question in
> reverse: What do we
> > > give up?
> >
> >    I decent way of hierarchically organizing our repositories. Tell me
> how to do this on bitbucket and you have your slam dunk.
> >
>
> Also some discussion on private repos.
>
> I guess none of you have objections for hosting private [for all kinds
> of collaboration work] at bitbucket.  [I don't claim 'iit' is better -
> for some work 'mcs' hosting was prefered]. Also lot of this work
> collabartion stuff is hosted at google docs - so I guess this isn't an
> issue.
>
> As I understand it - for more than 5 folks to be able to access a
> private repo - one needs to be on a paid plan with bitbucket. [not a
> big deal - but want to put that up front]


As Sean points out, not for us. This is already turned on in my account.


> > > I think the only thing we give up is the security blanket of being
> able to log in
> > > ourselves and mess with a machine directly.
>
> For some things its was easier to do it ourselves than wait for
> someone else [aka admin to do things.]  I think there was a
> significant benefit with this [for a lot of issues that came up in the
> past few years.]


And this exposes the best part. This is no "wait for an admin to do it
here". That is not
in the model, as it is with iit or other roll-your-own systems. This is
completely self-administrated
which is why it is great.

   Matt


>
> Satish
>



-- 
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120210/da43f896/attachment.html>


More information about the petsc-dev mailing list