Jan 12, 2011 at 6:14 PM
Edited Jan 12, 2011 at 6:24 PM
First thank you for responding.
I went ahead and looked at several of the work items and the attached comments...but wasn't able to find an high level understanding of what exactly the goals are of this project and what type of materials you guys are planning on delivering. And I'd like
to get an understanding of the audience you're targeting...I've got 3 audiences. Developers(who want to go deep into the Team Build API)... build masters(who just wants to drag in workflows and do limited C# customizations)...and release managers(who just
wants to change parameters on the visual designer...like copying to multiple servers).
I can understand that the code is being self documented but that seems like a less than ideal way to deliver a solid technical reference. If you are just going to be documenting the source...please publish the source in the same way on the web with additional
context (similiar to MSDN)...possible on tfsbuild.com? I'd like to have an easy way for my folks to be able to reference the material without having to tell each of them to download and crack open a bunch of random c# files.
I also understand this is a volunteer effort...but I keep hearing from my folks that "Microsoft's build guru's say Team Build is the way to go...it'd be so much easier if we use Team Build"
And when I ask about the fact that 2010 isn't anywhere as easy as 2008 to customize the developers come back and say:
"Microsoft is going to be publishing a bunch of Team Build extensions/activities and we'll be able to easily add in these activities into our build script xaml files."
Each time I hear this I ask "who'd you hear it from?" And I get links to Brian Harry's blog, William Bartholomew's blog, TFS 2010 SP1 links, and then I hear about this specific codeplex project."
Then I have to tell my team that they are wrong and reset their expectations.
And while several of them complain that our internal build tooling+final builder is complicated...I've yet to be proven that Team build (with whatever community customizations) will in fact be easier.
I've heard somewhere that Microsoft folks...buck hodges and grant holiday...may be invovled in this project...but if Microsoft isn't commited to supporting and delivering future value (like the ASP.NET AJax control toolkit team) via this codeplex project...then
I'm doubtful that this project will be of any lasting benefit to the community...so your efforts may be more helpful elsewhere. If this project is somesort of an MVP and Microsoft effort to explore Team Build customization...then you may be better served by
using some private hosting infastructure like bit bucket to store your source....and not making it public until it will be of value to the entire community.
Thanks for what your trying to do...and I look forward to better understanding whatever it is you are trying to accomplish.