[Pulp-list] Synchronize Git Repositories: Crazy?

[Scott McCarty]

Randy,
    I FINALLY had a chance to file this as a user story. Holy cow, you guys have 200 open stories :-)  So, I thought I was busy, but I have no idea how you guys would ever have time to implement this ;-)

Nick,
    I added your idea of the Builder Image too :-)

[1]: https://pulp.plan.io/issues/1526

Best Regards
Scott M

Scott McCarty, RHCA
Technical Product Marketing: Containers
Email: smccarty at redhat.com
Phone: 312-660-3535
Cell: 330-807-1043
Web: http://crunchtools.com

Containerizing? Why does the user space matter? http://red.ht/1Kl0mpx

----- Original Message -----
> From: "Randy Barlow" <rbarlow at redhat.com>
> To: pulp-list at redhat.com
> Sent: Thursday, September 3, 2015 2:11:39 PM
> Subject: Re: [Pulp-list] Synchronize Git Repositories: Crazy?
> 
> Scott McCarty wrote:
> > - Absolutely, is there a guide somewhere on how to start this off?
> 
> I don't believe we have any formal process documented for writing a
> story, so I'll write some high level stuff here:
> 
> 0) Use Redmine to file a new issue:
> https://pulp.plan.io/projects/pulp/issues/new
> 
> 1) Choose "Story" as the type.
> 
> 2) Try to word the title of the story with "As a user, I can do such
> and
> such" so that the story is focused on what problem the user wants to
> solve, not necessarily on the technical details on how to solve it.
> 
> 3) Use the body to describe the use case in detail.
> 
> 4) The comments can then be used by people to discuss possible
> solutions, to ask questions, or for conversation that further defines
> the user story. The description can be updated as people go if
> desired.
> 
> 5) Once the story seems to be "ready to be worked on" (and has a set
> of
> clear deliverables), there is a checkbox called "sprint candidate".
> Once
> this is checked, the team will look at it and decide whether the
> description is well defined. If it is, it will get marked as
> "groomed".
> 
> 6) Alternatively, you can lead the development effort yourself and
> not
> worry too much about the "sprint candidate"/"groomed" workflow, so
> long
> as the story seems to be well vetted. We accept pull requests so long
> as
> they meet our quality standards (and we will help you get to the
> expected quality standards during code review).
> 
> Does that help? Thanks!
> 
> 
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list