Just a couple things before people get too excited about the "other stuff" in
Github:
1. We've had extremely poor success with wiki's. I'd much rather we make
it really easy to contribute to the website and just have that content reviewed
and published rather than split the information in a wiki (and not help our
page rank, etc). I do not expect to turn on the Github wiki support for the WiX
toolset unless we really can't get updates made to the website easy.
2. I like the integration with the issue tracker on Github but their
permission model is very wrong for the WiX toolset (you have to be a
contributor to the code to take a bug which isn't the way we work in WiX). I
expect us to continue to use http://wixtoolset.org/issues/ . However, once on
Github we can take advantage of the same webhooks they use to make their issue
tracker work and get similar integration into our issue tracker. CodePlex
almost, kinda' has something like it but it's a pain to integrate with. Github
will be much easier to work with, plus we'll get to keep the workflow that is
working so well for us in triage right now.
From: Rob Winningham [mailto:originaldex...@hotmail.com]
Sent: Friday, February 7, 2014 8:23 AM
To: 'WiX toolset developer mailing list'
Subject: Re: [WiX-devs] The Great GitHub Discussion
I've only just signed my Outercurve agreement and have not yet contributed to
WiX. Like many of the other folks who have responded, I prefer moving sooner
than later.
I like the idea of moving to GitHub for a few reasons (listed below). Others
have mentioned these as well.
* Wiki
o In addition to the official documentation, I like the idea of hosting a
public (moderated) wiki on GitHub. The WiX documentation is very useful,
especially to those who already know how to use WiX. I'd like to see more
"Examples" and "How to" articles. A Wiki would be a good place for public
users to contribute that type of content outside the context of the official
documentation.
o The tutorial at http://wix.tramontana.co.hu/ is excellent. It's where I
started. Clearly many hours have been spent to create and maintain the content
there. Without that tutorial, I'm not sure I'd be as successful with WiX as I
have been. That being said, WiX 4.0 sounds like a big change. I believe new
users would benefit greatly from a similar tutorial for WiX 4.0. Why not host
one in the public (moderated) Wiki on GitHub?
* Issues
o I really like the way that GitHub associates Issues with Pull Requests,
Commits, and Changes. I know that Codeplex can do something similar. IMHO,
the integration is far better on GitHub.
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Thursday, February 6, 2014 12:52 PM
To: WiX toolset developer mailing list
Subject: [WiX-devs] The Great GitHub Discussion
In today's WiX Online Meeting http://youtu.be/4QlCTgmS33Y (about minute 10) I
spent about 15 minutes talking about the reasons to move to GitHub. At this
point, I believe it is inevitable that we will move the question is when and
what it should look like when we move.
First, in the move we'll be breaking history. We'll start from scratch to clean
up our messy history and get the crazy whitespace issues all sorted out (the
problem driving this move). That means when we do this, you'll have to go to a
different repo to go fully back in time. Keep that in mind reading on.
When.
When do you think we should move? Should we go now in the middle of v3.9 and
v4.0? Should we wait to move when each next version (v3.10 and v4.1) is ready
to start?
I already have a couple votes (thank you Blair and Bruce) for moving basically
now. I'm looking for more opinions. Even if your opinion is "It doesn't matter
to me." Voting helps me get a good idea what people want.
What.
As mentioned in the Online Meeting (if you haven't listened yet, please do),
GitHub provides a few new degrees of freedom. The biggest is that we have an
"umbrella organization" that can own multiple repositories. Today, on CodePlex,
we have to squish all of our stuff into a single repository which is
unfortunate. Some examples what GitHub would allow us to do:
1. Create a repo for the "website". I think this is a pretty obvious move
and will make it clearer where to go to improve content on
http://wixtoolset.org/.
2. Create a repo per major version of WiX toolset. In other words, there
would be "wix3" and "wix4" repos. This would allow us to use "master" branch
correctly (wix3 repo master branch would hold v3.8) and "develop" branch (wix3
repo develop branch would hold v3.9). That sounds great to me but there is a
downside. You'd no longer be able to have one repo on disk and switch between
all versions of the WiX toolset. Personally, I don't work that way anyway (I
have separate folders with wix39 and wix40 on my machine) but it's something we
should discuss here.
Anyway, please vote for when and if you have thoughts on how to organize our
code in GitHub let's discuss them.
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
