Hangout::Intro

Summary notes from Hangout #1.

Moq v4

• Move SVN source over to GitHub
  • New repo moq4
  • Move pending issues over
    • Triage first
    • Quantify effort, rather than priority
• Setup CI?
• Schedule moq4 Hangout
  • Design walk through
  • Code walk through
    • Fix one or two bugs?

Moq v5

• Maintainability
• Extensibility
• Contributions
  • Fully documenting the SDK API
  • Install-Package Moq.Source
    • Use generic private key to branch/push/send pull request for patches?
    • Embed github? -> not in 2 months
    • Limit what a key can do? Investigate (don't wanna lose the repo!)

Project Infrastructure/Communication Choices:

• Hangouts for design/coding/feedback
• GitHub
  • moq4
  • moq
    • /master => stable
    • /dev => current work
  • To Contribute:
    • fork moq
    • work on /dev branch. then either:
      • send pull request for 1 commit (option 1): subsequent teaks require new pull requests
      • branch /dev when ready for pull request (i.e. “FixMockingDelegates”)
        • send pull request (entire branch): allows evolving the pull request code iteratively. We prefer this (option 2).
• AgileZen (story tracking)
• TeamCity CI

Comments

A test comment. Not the same as the discussion tab on media wiki though.

@kzu: Nate (from AgileZen) mentioned you can link to a story AND a github issue by using different notation. zen-123 (story card) and #123 (github issue, as usual). This is pretty great :)