Message-
From: scons-dev-boun...@scons.org [mailto:scons-dev-boun...@scons.org] On
Behalf Of William Deegan
Sent: Thursday, March 28, 2013 3:40 PM
To: SCons developer list
Subject: Re: [Scons-dev] GSOC this year?
We need to submit by end of day tomorrow.
So of you can take a few minutes and flesh
sday, March 28, 2013 1:52 PM
> To: SCons developer list
> Subject: Re: [Scons-dev] GSOC this year?
>
> Jason,
>
> Perhaps a GSoC student can help migrate some of your monkey patches from
> parts into the core where we can agree that such wouldn't be too complex for
&g
-dev] GSOC this year?
Jason,
Perhaps a GSoC student can help migrate some of your monkey patches from parts
into the core where we can agree that such wouldn't be too complex for a
student to understand?
-Bill
On Mar 28, 2013, at 11:50 AM, William Deegan wrote:
> All,
>
> We n
Dirk,
On Mar 28, 2013, at 12:13 PM, Dirk Bächle wrote:
> Hi Bill,
>
> On 28.03.2013 19:50, William Deegan wrote:
>> All,
>>
>> We need to turn in the proposal by tomorrow.
>>
>> ...
>> Here's some other thoughts I have:
>> * Change SCons code to be runnable on py2.7 and py3.0
>> * Get SCons t
Hi Bill,
On 28.03.2013 19:50, William Deegan wrote:
All,
We need to turn in the proposal by tomorrow.
...
Here's some other thoughts I have:
* Change SCons code to be runnable on py2.7 and py3.0
* Get SCons to work better/at all on cygwin
* Change code to use more modern constructs (slots, gen
Jason,
Perhaps a GSoC student can help migrate some of your monkey patches from parts
into the core where we can agree that such wouldn't be too complex for a
student to understand?
-Bill
On Mar 28, 2013, at 11:50 AM, William Deegan wrote:
> All,
>
> We need to turn in the proposal by tomorr
All,
We need to turn in the proposal by tomorrow.
I've put up a google doc for the proposal here:
https://docs.google.com/document/d/1wOQGgUfdLlY355IC24YyB74i5Kg7uw-35A1Lsdos5aE/edit?usp=sharing
I've copied/pasted from the FAQ on what we should put in our proposal:
http://www.google-melange.com/g
Russel,
Today's the last day to file.
I'll go ahead and do that.
-Bill
On Mar 28, 2013, at 4:08 AM, Russel Winder wrote:
> Bill,
>
> Did you put an entry in? I can be a mentor if you would like me to.
>
> --
> Russel.
>
Bill,
Did you put an entry in? I can be a mentor if you would like me to.
--
Russel.
=
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net
41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus..
dev-boun...@scons.org] *On
> Behalf Of *Gary Oberbrunner
> *Sent:* Wednesday, March 20, 2013 10:38 AM
> *To:* SCons developer list
> *Subject:* Re: [Scons-dev] GSOC this year?
> ** **
> ** **
> On Wed, Mar 20, 2013 at 10:34 AM, anatoly techtonik
> wrote:
> On Tue,
e.
>
> Jason
>
> From: scons-dev-boun...@scons.org [mailto:scons-dev-boun...@scons.org] On
> Behalf Of Gary Oberbrunner
> Sent: Wednesday, March 20, 2013 10:38 AM
> To: SCons developer list
> Subject: Re: [Scons-dev] GSOC this year?
>
>
> On Wed, Mar 20, 2013 at 10:34 A
stuff is not simple. The details can
become a real issue.
Jason
From: scons-dev-boun...@scons.org [mailto:scons-dev-boun...@scons.org] On
Behalf Of Gary Oberbrunner
Sent: Wednesday, March 20, 2013 10:38 AM
To: SCons developer list
Subject: Re: [Scons-dev] GSOC this year?
On Wed, Mar 20, 2013
On Wed, Mar 20, 2013 at 10:34 AM, anatoly techtonik wrote:
> On Tue, Mar 19, 2013 at 9:59 PM, William Deegan > wrote:
>
>> Folks,
>>
>> Anyone interested in mentoring for GSOC for SCons this year?
>> Any appropriate projects ?
>>
>
> Build SCons diagrams, and tools, yes. Research current, define
On Tue, Mar 19, 2013 at 9:59 PM, William Deegan
wrote:
> Folks,
>
> Anyone interested in mentoring for GSOC for SCons this year?
> Any appropriate projects ?
>
Build SCons diagrams, and tools, yes. Research current, define and
implement next mechanisms for:
1. Tool discovery
2. Tool initializatio
Folks,
Anyone interested in mentoring for GSOC for SCons this year?
Any appropriate projects ?
-Bill
___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev
15 matches
Mail list logo