Due to a recent change in employment, I'm not going to be able to make it
to Code4Lib this year (much to my disappointment). That means I won't be
able to facilitate the Git -r Done preconference session. It looks like
there are enough other interested Git users attending, though, to make a
pretty good show of it.
I look forward to attending in 2013, once I've established myself at my new
institution.
Cheers,
-Ian
On Tue, Sep 27, 2011 at 11:47 AM, Carl Wiedemann
<[log in to unmask]>wrote:
> I've been using Git extensively for a library's Drupal sites and may have
> some relevant items to share about deployment strategy and managing
> branches
> across dev/test/prod environments. Would be very interested to hear how
> others have approached these issues, especially on different platforms.
>
> Carl Wiedemann
> Website design and development consulting
> [log in to unmask] | skype: c4rlww
>
>
>
> On Mon, Sep 26, 2011 at 11:04 AM, Ian Walls
> <[log in to unmask]>wrote:
>
> > Yup, for better or worse, I'll help shepherd this preconference along.
> > Anyone interested in sharing their knowledge and experience is welcome to
> > contact me directly, or put something up on the wiki when it returns.
> I'm
> > personally quite interested in the different workflows groups have set up
> > around Git; the way we do it for Koha may be completely different than,
> > say,
> > for Drupal or Summon.
> >
> > Cheers,
> >
> >
> > -Ian
> >
> > On Mon, Sep 26, 2011 at 12:58 PM, Kevin S. Clarke <[log in to unmask]
> > >wrote:
> >
> > > On Mon, Sep 26, 2011 at 12:33 PM, Andrew Nagy <[log in to unmask]>
> wrote:
> > > > Is anyone leading this session or is a free for all? Code4lib site
> is
> > > down
> > > > - so I can't see whats on the wiki.
> > >
> > > I believe [log in to unmask] volunteered to lead it. Have
> > > your engineer contact him(?)
> > >
> > > Kevin
> > >
> >
> >
> >
> > --
> > Ian Walls
> > Lead Development Specialist
> > ByWater Solutions
> > Phone # (888) 900-8944
> > http://bywatersolutions.com
> > [log in to unmask]
> > Twitter: @sekjal
> >
>
|