Re: [Condor-devel] github revisited.

[Matthew Farrellee <matt@xxxxxxxxxx>]

As promised, the pad notes are captured below.

Additionally, the idea of incremental steps is popular.

If anyone wants to try out github just setup an account at,

	https://github.com/signup/free

I've also -
 . setup a backup of the github repository in AFS
 . setup a mirror of the github repository suitable for use by gittrac
 . setup a simple Org at github to explore account management
 . setup the github IRC bot to send information to #distcomp
 .. it should also be possible to integrate condorbot

If you have a github account and want to toy with the Org interface, 
just send me your details.

Things left to explore -
 . demonstrate ability of NMI to build from github (remote URL change)
 . ability to notify upon illegal actions (devel -> stable merges)
 . interaction with security embargo policy (waiting to see the policy)

I'll check back during FW next Monday to see what exploration has 
happened and ideas have gestated.

Best,


matt

=== http://sync.in/FzqZA01IVA ===

iWho: Todd, Greg, Jaime, Alan, Tim, Rob, Matt, TJ, Dan, Nate, Zach, Sam, 
Brooklin, Brian, Ian
What -
 . Host canonical Condor Project repository at github.com
What not -
 . Migrating from gittrac to github
Why -
 . Request from the community
 . Setup to enhance openness and inclusiveness of the project
 . Enhance visibility of project in developer community
 . Benefit from enhanced workflow techniques discovered in the community
 .. Specifically pull-requests can be valuable
 . Utilize development and community tools
Obstacles -
 . Technical -
 .. NMI - builds from github?
 .. gittrac - trac github repository?
 .. backups - backup from github?
 .. embargo branches - visibility control?
 .. repository hooks
 ... commit rejection - devel -> stable merge?
 ... condorbot
 . Process -
 .. github stability
 .. Account management
 ... account owners/admin
 ... add/remove committers
 . Others -
 .. ??
 .. Additional workload of managing potentially more patches/pull-requests
Greg - incremental steps?
===

On 09/25/2012 02:33 PM, Brian Bockelman wrote:
> Hi,
>
> Another action item would be to:
> 1) do a pull request on github,
> 2) write down the workflow for committing the pull request to the UW repo,
> 3) see how the github UI behaves when the commit shows up.
>
> Brian
>
> On Sep 25, 2012, at 1:22 PM, Tim St Clair <tstclair@xxxxxxxxxx> wrote:
>
> > Maybe a good action item from yesterdays discussion would be to create a account on github and give it a test drive for those who are not already on it.
> >
> > It's very low cost.
> >
> > Cheers,
> > Tim
> >
> > ----- Original Message -----
> > > From: "Matthew Farrellee" <matt@xxxxxxxxxx>
> > > To: "Condor Developers" <condor-devel@xxxxxxxxxxx>
> > > Sent: Monday, September 24, 2012 2:43:44 PM
> > > Subject: Re: [Condor-devel] github revisited.
> > >
> > > On 09/17/2012 05:08 PM, Matthew Farrellee wrote:
> > > > This is all good feedback. Please keep it coming.
> > > >
> > > > I'll summarize it and report back next week.
> > > >
> > > > If you want to reply off list, feel free to contact me directly.
> > >
> > > Here's an etherpad for the meeting today - http://sync.in/FzqZA01IVA
> > >
> > > Best,
> > >
> > >
> > > matt
> > > _______________________________________________
> > > Condor-devel mailing list
> > > Condor-devel@xxxxxxxxxxx
> > > https://lists.cs.wisc.edu/mailman/listinfo/condor-devel
> > _______________________________________________
> > Condor-devel mailing list
> > Condor-devel@xxxxxxxxxxx
> > https://lists.cs.wisc.edu/mailman/listinfo/condor-devel
>
>
>
> _______________________________________________
> Condor-devel mailing list
> Condor-devel@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/condor-devel