Something to think about for future use is accessibility of the build server
for those maintaining.
How we do go about sharing that information, obviously you don't want to
hand out access to the ci server to a public mailing list.
On Fri, Jan 28, 2011 at 1:41 PM, Wyatt Barnett wrote:
> Why
would the accessibility just be a configuration script? I'm not sure how CI is
set up, but I assume that we could set up something that points to our
repository for that, thus any committer could update the configuration script.
Also, I dug a bit into Hudson (I'm not familiar with it), there i
Does anyone know if the wiki will move once / if we get taken into the
incubator? I'd like to start doing a bunch of updating, but if we have to port
it all over to a new wiki space for the incubator, it's kind of pointless
~Prescott
It's unclear at this point. My recommendation in the proposal was the
move it over, because at that time the Wiki was empty.
Either way, I believe the page syntax should be the same, and so
moving the pages over wouldn't be too terrible.
Thanks,
Troy
On Sat, Jan 29, 2011 at 2:40 PM, Prescott Na
I neglected to add, I think you should go ahead and build the wiki
pages when you have time and are motivated to do so, and not let the
idea that they will be moving cause you to defer that work to later.
Migration, while troublesome, is less bad than not having that
documentation at all.
Thanks,
On 2011-01-30, Troy Howard wrote:
> I neglected to add, I think you should go ahead and build the wiki
> pages when you have time and are motivated to do so, and not let the
> idea that they will be moving cause you to defer that work to later.
> Migration, while troublesome, is less bad than not
