[Flightgear-devel] Google Summer Of Code

2012-01-29 Thread Pedro Morgan
Now its a new year an warmer for us lot in the north of the equator..

Can I suggest now the project proposal.. for year marking and done...

I suggest we need a project manager and for this I project Geoff... GBH

As GBH is chared with the jobs uncoming in the aero industry and student
its recommended we come up with the projects..

What is the project for Google Summer of Code...

For a pilot it starts with OAT,
For atc  its SID and STAR

So I can see no reason, or bannana or chesnut that we shoudld elect..

GBH for this wole i the first yeaar

GBH talen is a massive ddebuggong exersie..

Onece we agree on a fixed chair, wwhen I believe that all of us can rotate
abbbout the relms..

Lets Bullshit Goggle...
Hello I am from germany, I am and Open source advocado..

get  in the hot seat with rules and regulation...
--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Google Summer of Code

2010-03-19 Thread Curtis Olson
On Tue, Mar 9, 2010 at 9:08 AM, Pete Morgan wrote:

 Has/Does FlightGear participate ?


 http://google-opensource.blogspot.com/2010/03/google-summer-of-code-applications-now.html


Just to put some closure on this thread.  I had one person reply (Tim) with
an offer to be a possible mentor.  That was pretty much it ... other than a
couple peripheral emails (Stuart wrote about our bug tracking system, Vivian
wrote in to remind us of the short time frame, Alex offered possible support
as co-admin if no one else would do it, and that he'd be open to considering
mentorship if something really came through with his name all over it.)

I was hoping for a bunch of good project ideas.  I was hoping for some help
filling out the application form and answer the questions.  Mostly I was
hoping for a couple really enthusiastic volunteers at the mentor level to
jump in and help get this going and push it through.  I am unfortunately not
able to commit to carrying this whole thing entirely on my own shoulders.
 The necessary components unfortunately did not materialize this year, but
I'd love to revisit this subject again (before the deadline) for next year.

I do think that mentorship (whether official or unofficial) is a very
important thing.  It's a great way for the younger generation to learn a lot
of practical lessons about life (beyond just facts and ideas, but there is a
lot of that which can be learned too.)  There is much to be learned about
process, and attitude, and interpersonal interactions, and what it takes to
be successful.  Of course non of us are experts or know everything.  The
older generation is not always a shining example of what the younger
generation should aspire too.  But if the younger generation is willing to
slow down and listen, there is a lot to be learned ... if we have mentors on
the other side willing to share.

Best regards,

Curt.
-- 
Curtis Olson: http://baron.flightgear.org/~curt/
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Google Summer of Code

2010-03-19 Thread Gene Buckle
On Fri, 19 Mar 2010, Curtis Olson wrote:

 On Tue, Mar 9, 2010 at 9:08 AM, Pete Morgan wrote:

 Has/Does FlightGear participate ?


 http://google-opensource.blogspot.com/2010/03/google-summer-of-code-applications-now.html


Curt, could the lack of enthusiasm been more due to the short timeframe 
than anything else?  AFAIK, the GSoC participants are thinking about their 
entry *months* in advance.

Why not make a note to revist a GSoC entry about 2-3 months before the 
2011 entry deadline?  That gives you guys plenty of time to identify the 
best use of the GSoC resources for FlightGear and a well prepared proposal 
would go a long way towards getting it accepted.

just sayin'. :)

g.



-- 
Proud owner of F-15C 80-0007
http://www.f15sim.com - The only one of its kind.
http://www.simpits.org/geneb - The Me-109F/X Project

ScarletDME - The red hot Data Management Environment
A Multi-Value database for the masses, not the classes.
http://www.scarletdme.org - Get it _today_!

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Google Summer of Code

2010-03-19 Thread Curtis Olson
On Fri, Mar 19, 2010 at 10:45 AM, Gene Buckle ge...@deltasoft.com wrote:

 Curt, could the lack of enthusiasm been more due to the short timeframe
 than anything else?  AFAIK, the GSoC participants are thinking about their
 entry *months* in advance.

 Why not make a note to revist a GSoC entry about 2-3 months before the
 2011 entry deadline?  That gives you guys plenty of time to identify the
 best use of the GSoC resources for FlightGear and a well prepared proposal
 would go a long way towards getting it accepted.


Hi Gene,

What you are sayin' makes sense.

Why don't we form a GSOC committee for lack of a better name.  This
committee could start thinking and preparing right now, or at least a couple
months in advance.  I'm willing to participate, but I can't commit to
pulling lead and carrying all the load myself.  Do we have anyone who would
want to take charge of this effort, get things rolling, get things
organized, keep track of deadlines, and just do whatever it takes to push
this through for next year?  We need a couple dedicated people  to step
forward and take charge here.  Otherwise we'll be sayin' the same things at
this time next year. :-)

Regards,

Curt.
-- 
Curtis Olson: http://baron.flightgear.org/~curt/
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Google Summer of Code

2010-03-19 Thread Gene Buckle
On Fri, 19 Mar 2010, Curtis Olson wrote:

 On Fri, Mar 19, 2010 at 10:45 AM, Gene Buckle ge...@deltasoft.com wrote:

 Curt, could the lack of enthusiasm been more due to the short timeframe
 than anything else?  AFAIK, the GSoC participants are thinking about their
 entry *months* in advance.

 Why not make a note to revist a GSoC entry about 2-3 months before the
 2011 entry deadline?  That gives you guys plenty of time to identify the
 best use of the GSoC resources for FlightGear and a well prepared proposal
 would go a long way towards getting it accepted.


 Hi Gene,

 What you are sayin' makes sense.

 Why don't we form a GSOC committee for lack of a better name.  This
 committee could start thinking and preparing right now, or at least a couple
 months in advance.  I'm willing to participate, but I can't commit to
 pulling lead and carrying all the load myself.  Do we have anyone who would
 want to take charge of this effort, get things rolling, get things
 organized, keep track of deadlines, and just do whatever it takes to push
 this through for next year?  We need a couple dedicated people  to step
 forward and take charge here.  Otherwise we'll be sayin' the same things at
 this time next year. :-)

I guess the first thing to identify is what date would be appropriate to 
start this process for the 2011 GSoC run?

I don't have the time to take lead on this either, but I'm a pretty good 
cat herder. :)

g.

-- 
Proud owner of F-15C 80-0007
http://www.f15sim.com - The only one of its kind.
http://www.simpits.org/geneb - The Me-109F/X Project

ScarletDME - The red hot Data Management Environment
A Multi-Value database for the masses, not the classes.
http://www.scarletdme.org - Get it _today_!

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Google Summer of Code

2010-03-19 Thread Reagan Thomas
Curtis Olson wrote:
 On Fri, Mar 19, 2010 at 10:45 AM, Gene Buckle ge...@deltasoft.com 
 mailto:ge...@deltasoft.com wrote:

 Curt, could the lack of enthusiasm been more due to the short
 timeframe
 than anything else?  AFAIK, the GSoC participants are thinking
 about their
 entry *months* in advance.

 Why not make a note to revist a GSoC entry about 2-3 months before the
 2011 entry deadline?  That gives you guys plenty of time to
 identify the
 best use of the GSoC resources for FlightGear and a well prepared
 proposal
 would go a long way towards getting it accepted.


 Hi Gene,

 What you are sayin' makes sense.

 Why don't we form a GSOC committee for lack of a better name.  This 
 committee could start thinking and preparing right now, or at least a 
 couple months in advance.  I'm willing to participate, but I can't 
 commit to pulling lead and carrying all the load myself.  Do we have 
 anyone who would want to take charge of this effort, get things 
 rolling, get things organized, keep track of deadlines, and just do 
 whatever it takes to push this through for next year?  We need a 
 couple dedicated people  to step forward and take charge here. 
  Otherwise we'll be sayin' the same things at this time next year. :-)

 Regards,

 Curt.
 -- 
 Curtis Olson: http://baron.flightgear.org/~curt/ 
 http://baron.flightgear.org/%7Ecurt/
Hi, Curt.

Another F/OSS project I've been watching for years is BZFlag.  They've 
participated in GSoC three years in a row and seem to have been pretty 
successful each time. They've also been quite good at documenting their 
efforts; reading their GSoC wiki pages could be a great guide for future 
FG GSoC efforts (see http://my.bzflag.org/w/Google_Summer_of_Code ).  
One thing that's pretty clear is that the first burden of success is on 
the mentors to be available for the students.  Using IRC seems to have 
worked out pretty well, even with many time zones between the student 
and mentor.

I think FG is an excellent candidate project for GSoC because it 
involves so many different and interesting disciplines. It should be 
easy to attract bright and enthusiastic students.  To pull it off, 
though, requires advance planning and a genuine commitment of time on 
the part of seasoned developers who are to be mentors.  As an example, 
in spite of previous successes with GSoC, BZFlag is not participating 
this year... because they need to get their next release out!

-Reagan

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Google Summer of Code

2010-03-19 Thread Reagan Thomas
Reagan Thomas wrote:
 Curtis Olson wrote:
 On Fri, Mar 19, 2010 at 10:45 AM, Gene Buckle ge...@deltasoft.com 
 mailto:ge...@deltasoft.com wrote:

 Curt, could the lack of enthusiasm been more due to the short
 timeframe
 than anything else?  AFAIK, the GSoC participants are thinking
 about their
 entry *months* in advance.

 Why not make a note to revist a GSoC entry about 2-3 months 
 before the
 2011 entry deadline?  That gives you guys plenty of time to
 identify the
 best use of the GSoC resources for FlightGear and a well prepared
 proposal
 would go a long way towards getting it accepted.


 Hi Gene,

 What you are sayin' makes sense.

 Why don't we form a GSOC committee for lack of a better name.  This 
 committee could start thinking and preparing right now, or at least a 
 couple months in advance.  I'm willing to participate, but I can't 
 commit to pulling lead and carrying all the load myself.  Do we have 
 anyone who would want to take charge of this effort, get things 
 rolling, get things organized, keep track of deadlines, and just do 
 whatever it takes to push this through for next year?  We need a 
 couple dedicated people  to step forward and take charge here. 
  Otherwise we'll be sayin' the same things at this time next year. :-)

 Regards,

 Curt.
 -- 
 Curtis Olson: http://baron.flightgear.org/~curt/ 
 http://baron.flightgear.org/%7Ecurt/
 Hi, Curt.

 Another F/OSS project I've been watching for years is BZFlag.  They've 
 participated in GSoC three years in a row and seem to have been pretty 
 successful each time. They've also been quite good at documenting 
 their efforts; reading their GSoC wiki pages could be a great guide 
 for future FG GSoC efforts (see 
 http://my.bzflag.org/w/Google_Summer_of_Code ).  One thing that's 
 pretty clear is that the first burden of success is on the mentors to 
 be available for the students.  Using IRC seems to have worked out 
 pretty well, even with many time zones between the student and mentor.

 I think FG is an excellent candidate project for GSoC because it 
 involves so many different and interesting disciplines. It should be 
 easy to attract bright and enthusiastic students.  To pull it off, 
 though, requires advance planning and a genuine commitment of time on 
 the part of seasoned developers who are to be mentors.  As an example, 
 in spite of previous successes with GSoC, BZFlag is not participating 
 this year... because they need to get their next release out!

 -Reagan

I should have included this link to their 2007 GSoC post mortem:
http://my.bzflag.org/gsoc/bzflag_gsoc2007_post_mortem.pdf


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Google Summer of Code

2010-03-19 Thread Curtis Olson
Is it worth setting up a GOSC wiki page to start organizing our thoughts and
possible volunteers?  If we wait on this we'll very likely have a repeat of
this year when next year's deadline comes around.  Several people have
written expressing support that this is a good idea, but we need actual
warm bodies to step up to the plate and do something here if we are going to
move forward with this.  The point is to help mentor some younger kids, so
we need to be organized and have our mentoring act together before I'd feel
comfortable putting in an application.  I don't want to waste a couple kids
summers.

Regards,

Curt.


On Fri, Mar 19, 2010 at 11:08 AM, Gene Buckle ge...@deltasoft.com wrote:

 On Fri, 19 Mar 2010, Curtis Olson wrote:

  On Fri, Mar 19, 2010 at 10:45 AM, Gene Buckle ge...@deltasoft.com
 wrote:
 
  Curt, could the lack of enthusiasm been more due to the short timeframe
  than anything else?  AFAIK, the GSoC participants are thinking about
 their
  entry *months* in advance.
 
  Why not make a note to revist a GSoC entry about 2-3 months before the
  2011 entry deadline?  That gives you guys plenty of time to identify the
  best use of the GSoC resources for FlightGear and a well prepared
 proposal
  would go a long way towards getting it accepted.
 
 
  Hi Gene,
 
  What you are sayin' makes sense.
 
  Why don't we form a GSOC committee for lack of a better name.  This
  committee could start thinking and preparing right now, or at least a
 couple
  months in advance.  I'm willing to participate, but I can't commit to
  pulling lead and carrying all the load myself.  Do we have anyone who
 would
  want to take charge of this effort, get things rolling, get things
  organized, keep track of deadlines, and just do whatever it takes to push
  this through for next year?  We need a couple dedicated people  to step
  forward and take charge here.  Otherwise we'll be sayin' the same things
 at
  this time next year. :-)
 
 I guess the first thing to identify is what date would be appropriate to
 start this process for the 2011 GSoC run?

 I don't have the time to take lead on this either, but I'm a pretty good
 cat herder. :)

 g.

 --
 Proud owner of F-15C 80-0007
 http://www.f15sim.com - The only one of its kind.
 http://www.simpits.org/geneb - The Me-109F/X Project

 ScarletDME - The red hot Data Management Environment
 A Multi-Value database for the masses, not the classes.
 http://www.scarletdme.org - Get it _today_!


 --
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel




-- 
Curtis Olson: http://baron.flightgear.org/~curt/
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Google Summer of Code

2010-03-19 Thread Gene Buckle
On Fri, 19 Mar 2010, Curtis Olson wrote:

 Is it worth setting up a GOSC wiki page to start organizing our thoughts and
 possible volunteers?  If we wait on this we'll very likely have a repeat of
 this year when next year's deadline comes around.  Several people have
 written expressing support that this is a good idea, but we need actual
 warm bodies to step up to the plate and do something here if we are going to
 move forward with this.  The point is to help mentor some younger kids, so
 we need to be organized and have our mentoring act together before I'd feel
 comfortable putting in an application.  I don't want to waste a couple kids
 summers.


I would think so, yes.

The first thing we can teach them is how not to top post. :)

g.

-- 
Proud owner of F-15C 80-0007
http://www.f15sim.com - The only one of its kind.
http://www.simpits.org/geneb - The Me-109F/X Project

ScarletDME - The red hot Data Management Environment
A Multi-Value database for the masses, not the classes.
http://www.scarletdme.org - Get it _today_!

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Google Summer of Code

2010-03-19 Thread Curtis Olson
A good mail reader can straighten it all out ... :-)

On Fri, Mar 19, 2010 at 2:47 PM, Gene Buckle wrote:

 I would think so, yes.

 The first thing we can teach them is how not to top post. :)


-- 
Curtis Olson: http://baron.flightgear.org/~curt/
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Google Summer of Code

2010-03-19 Thread Gene Buckle
On Fri, 19 Mar 2010, Curtis Olson wrote:

 A good mail reader can straighten it all out ... :-)

 On Fri, Mar 19, 2010 at 2:47 PM, Gene Buckle wrote:

 I would think so, yes.

 The first thing we can teach them is how not to top post. :)




*facepalm*

g.

-- 
Proud owner of F-15C 80-0007
http://www.f15sim.com - The only one of its kind.
http://www.simpits.org/geneb - The Me-109F/X Project

ScarletDME - The red hot Data Management Environment
A Multi-Value database for the masses, not the classes.
http://www.scarletdme.org - Get it _today_!

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Google Summer of Code

2010-03-19 Thread willie
Curtis Olson wrote:
 On Fri, Mar 19, 2010 at 10:45 AM, Gene Buckle ge...@deltasoft.com
 mailto:ge...@deltasoft.com wrote:
 
 Curt, could the lack of enthusiasm been more due to the short timeframe
 than anything else?  AFAIK, the GSoC participants are thinking about
 their
 entry *months* in advance.
 
 Why not make a note to revist a GSoC entry about 2-3 months before the
 2011 entry deadline?  That gives you guys plenty of time to identify the
 best use of the GSoC resources for FlightGear and a well prepared
 proposal
 would go a long way towards getting it accepted.
 
 
 Hi Gene,
 
 What you are sayin' makes sense.
 
 Why don't we form a GSOC committee for lack of a better name.  This
 committee could start thinking and preparing right now, or at least a
 couple months in advance.  I'm willing to participate, but I can't
 commit to pulling lead and carrying all the load myself.  Do we have
 anyone who would want to take charge of this effort, get things rolling,
 get things organized, keep track of deadlines, and just do whatever it
 takes to push this through for next year?  We need a couple dedicated
 people  to step forward and take charge here.  Otherwise we'll be sayin'
 the same things at this time next year. :-)
 
 Regards,
 
 Curt.
 -- 
 Curtis Olson: http://baron.flightgear.org/~curt/
 
OK I'll volunteer to be on that committee. I am no coder so I'm probably
unsuited as an individual mentor, but I do have some project mgmt skills.

I kicked off #FG-GSoC on irc.flightgear.org so we don't distract the
normal chatter on #flightgear.

I'll put together a list of proposed milestones that I think we should
be aiming for. One very important milestone will be the finalising of
the short-list of projects and their associated mentors. This should be
in place by Jan 1 2011. We need to be realistic about projects though
and remember that the features we really really want added to FG  will
not have a line of code written until May 2011 at the very earliest. So
we need long-term thinking on this.
An important early task MUST be to get commitment from a range of
mentors so we can properly support these kids.

I have made some minor changes to

http://wiki.flightgear.org/index.php/Google_Summer_of_Code_Candidate_Projects

Please add your own thoughts. Perhaps we could have a GSoC section on
the spiffy new (pref django-powered) website that will be along anytime
soon?

Best Regards
Willie Fleming




--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Google Summer of Code

2010-03-10 Thread Pete Morgan
Curtis Olson wrote:
 One more thing we need.  I need someone to sign up on the google 
 summer of code page and create an ID for themselves.  The applications 
 requires a backup admin link id and it will not let me enter myself.

 Thanks,

 Curt.
Have files this issue

#101 - Google Summer Of Code

Deasline for mentors = us is Fri 12th at 23:00 UTC.. so everthing needs 
to be done pretty well a few hours before.. in determingning ideas etc..

Its an issue for everyone PLEASE to stick in the ideas NOW.. so they can 
be reviewed and eliminated..

http://code.google.com/p/flightgear-bugs/issues/detail?id=101

pete




 On Tue, Mar 9, 2010 at 9:39 AM, Curtis Olson  wrote:

 On Tue, Mar 9, 2010 at 8:08 AM, Pete Morgan  wrote:

 Has/Does FlightGear participate ?

 
 http://google-opensource.blogspot.com/2010/03/google-summer-of-code-applications-now.html


 We have never participated before, but I see the deadline for
 organizations to apply is March 12 ... coming right up.  It's not
 like I've got nothing else to do, but I like the idea of
 mentoring.  I can think of many individuals who have played a
 mentor roll from time to time for me and I am very appreciative of
 that.  So I am submitting an application for FlightGear (assuming
 no one else has already.)

 Here are some things we need:

 1. Mentors
 2. Student applicants (mentorees).
 3. A web page listing project/mentoring ideas

 1  3 are the most important to have lined up before March 12
 (Friday.)

 The organization application has some questions that I'd love to
 have some help thinking about and answering:

 1. What criteria did you use to select the individuals who will
 act as mentors for your organization? Please be as specific as
 possible.

 2. What is your plan for dealing with disappearing students?

 3. What is your plan for dealing with disappearing mentors?

 4. What steps will you take to encourage students to interact with
 your project's community before, during and after the program?

 5. What will you do to ensure that your accepted students stick
 with the project after GSoC concludes?

 6. What would our organization expect to gain from this experience?

 As you can see, this would not be a trivial undertaking for the
 FlightGear project, and it's not something I can carry entirely on
 my own shoulders.  Do we have others in the project that would be
 willing to volunteer their time and participate in a mentoring and
 organizational roll?

 We also need to quickly assemble a list of possible student
 project ideas ... and these need to be well measured ... like you
 would measure a pass in soccer/futbol.  We want to avoid things
 that are too hard or too easy.  The ball needs to arrive with the
 correct pace so the student can handle it.  We want suggestions
 that could be attainable by a *student* in the allotted time frame
 (summer?) and realize that a student may have to spend a good
 chunk of their time learning about the FlightGear structure before
 they can advance with their project.

 I think we should avoid suggesting projects that are in
 FlightGear's critical path.  I.e. add aircraft shadows might be
 an tempting project to suggest, but is this student level work
 that could be finished in a summer?  Do we want to pin all our
 hopes for aircraft shadows in FlightGear on a google summer of
 code student who may bugout mid stream if it starts looking too
 hard?  If it does get too hard, does that student fail or is it
 us that failed as a mentoring organization?

 So for project suggestions I think we should focus on projects
 that have the best chance of teaching student level people, have
 the best chance of being attainable in a summer of effort, have
 the best chance of helping a student to gain confidence,
 knowledge, experience, etc.  We should be careful/resistant to
 suggesting projects that are simply FlightGear feature wishlist
 items.  We should suggest projects that the mentors have some idea
 of a clear path to a solution (i.e. not so much research into new
 and unknown things.)

 I think to be successful, we need to keep our focus on the
 mentoring aspect of this.  The focus is to help bring some of the
 younger generation up to speed more quickly by sharing our
 experiences and knowledge.  It's something we do already to some
 extent in a casual context.  The google program just makes it
 official.  The mentors commit some time to sharing their
 experience and knowledge and the students commit to actually
 listening and respecting what is shared. :-)

 Those are my thoughts.  I can get the ball rolling, but I can't do
 it all myself.

 Thanks,

 Curt.
 -- 
 Curtis Olson: http://baron.flightgear.org/~curt/
 

Re: [Flightgear-devel] Google Summer of Code

2010-03-10 Thread Stuart Buchanan
On Wed, Mar 10, 2010 at 12:01 PM, Pete Morgan wrote:

 Curtis Olson wrote:
  One more thing we need.  I need someone to sign up on the google
  summer of code page and create an ID for themselves.  The applications
  requires a backup admin link id and it will not let me enter myself.
 
  Thanks,
 
  Curt.
 Have files this issue

 #101 - Google Summer Of Code

 Deasline for mentors = us is Fri 12th at 23:00 UTC.. so everthing needs
 to be done pretty well a few hours before.. in determingning ideas etc..

 Its an issue for everyone PLEASE to stick in the ideas NOW.. so they can
 be reviewed and eliminated..

 http://code.google.com/p/flightgear-bugs/issues/detail?id=101

 pete

Pete,

This really isn't a bug, is it?

Having made a great start with putting together a bug tracker, you're
in real danger of
ruining it by adding things like this to it.  The bug tracker really
has to have a focus on
bugs,  not feature requests, nor random issues.

As a developer I need a database of the known bugs that I can look over easily.
Having to manually parse out stuff like this is just going to make me
less likely to
use it, and therefore make it useless.

I'd suggest that the wiki is a better place for this sort of information.

-Stuart Buchanan

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Google Summer of Code

2010-03-10 Thread Vivian Meazza
Stuart Buchanan wrote

 
 On Wed, Mar 10, 2010 at 12:01 PM, Pete Morgan wrote:
 
  Curtis Olson wrote:
   One more thing we need.  I need someone to sign up on the google
   summer of code page and create an ID for themselves.  The applications
   requires a backup admin link id and it will not let me enter myself.
  
   Thanks,
  
   Curt.
  Have files this issue
 
  #101 - Google Summer Of Code
 
  Deasline for mentors = us is Fri 12th at 23:00 UTC.. so everthing needs
  to be done pretty well a few hours before.. in determingning ideas etc..
 
  Its an issue for everyone PLEASE to stick in the ideas NOW.. so they can
  be reviewed and eliminated..
 
  http://code.google.com/p/flightgear-bugs/issues/detail?id=101
 
  pete
 
 Pete,
 
 This really isn't a bug, is it?
 
 Having made a great start with putting together a bug tracker, you're
 in real danger of
 ruining it by adding things like this to it.  The bug tracker really
 has to have a focus on
 bugs,  not feature requests, nor random issues.
 
 As a developer I need a database of the known bugs that I can look over
 easily.
 Having to manually parse out stuff like this is just going to make me
 less likely to
 use it, and therefore make it useless.
 
 I'd suggest that the wiki is a better place for this sort of information.
 

Time is of the essence for this issue, if we are not to fail yet again.
While you are quite right, let's not be too picky about this one.

Vivian



--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Google Summer of Code

2010-03-10 Thread Tim Moore
On Tue, Mar 9, 2010 at 4:39 PM, Curtis Olson curtol...@gmail.com wrote:

 On Tue, Mar 9, 2010 at 8:08 AM, Pete Morgan ac...@daffodil.uk.com wrote:

 Has/Does FlightGear participate ?


 http://google-opensource.blogspot.com/2010/03/google-summer-of-code-applications-now.html


 We have never participated before, but I see the deadline for organizations
 to apply is March 12 ... coming right up.  It's not like I've got nothing
 else to do, but I like the idea of mentoring.  I can think of many
 individuals who have played a mentor roll from time to time for me and I am
 very appreciative of that.  So I am submitting an application for FlightGear
 (assuming no one else has already.)

 Here are some things we need:

 1. Mentors

I agree to be a mentor for graphics projects.

 2. Student applicants (mentorees).
 3. A web page listing project/mentoring ideas

 1  3 are the most important to have lined up before March 12 (Friday.)

 3. What is your plan for dealing with disappearing mentors?

Backup mentors.


 I think we should avoid suggesting projects that are in FlightGear's
 critical path.  I.e. add aircraft shadows might be an tempting project to
 suggest, but is this student level work that could be finished in a summer?
  Do we want to pin all our hopes for aircraft shadows in FlightGear on a
 google summer of code student who may bugout mid stream if it starts looking
 too hard?  If it does get too hard, does that student fail or is it us
 that failed as a mentoring organization?

I'll respond to shadows specifically, as I know it's a sought-after feature
and I've sat on it for more than a year.

The problem can be stated as Use the Open Scene Graph Light Space
Perspective Shadow technique to implement shadows in FlightGear. There are
several well-defined steps, along with some milestones, on the way. For
example:

* Using OSG demo code, get shadows working by overriding all existing
shaders;
* adapt our shaders to use a function call to do lighting calculations;
* change effects code to link different lighting library to shaders if
shadows are enabled;
* enable a special shader in an effect when the shadow pass is run;
* modify the OSG shadow technique to interact with our effects code;
* get this working for the aircraft;
* get it working for the whole scene.

Yeah, it's ambitious, but it should be achievable in a summer by someone who
already has 3D graphics knowledge.

Tim
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Google Summer of Code

2010-03-09 Thread Curtis Olson
On Tue, Mar 9, 2010 at 8:08 AM, Pete Morgan ac...@daffodil.uk.com wrote:

 Has/Does FlightGear participate ?


 http://google-opensource.blogspot.com/2010/03/google-summer-of-code-applications-now.html


We have never participated before, but I see the deadline for organizations
to apply is March 12 ... coming right up.  It's not like I've got nothing
else to do, but I like the idea of mentoring.  I can think of many
individuals who have played a mentor roll from time to time for me and I am
very appreciative of that.  So I am submitting an application for FlightGear
(assuming no one else has already.)

Here are some things we need:

1. Mentors
2. Student applicants (mentorees).
3. A web page listing project/mentoring ideas

1  3 are the most important to have lined up before March 12 (Friday.)

The organization application has some questions that I'd love to have some
help thinking about and answering:

1. What criteria did you use to select the individuals who will act as
mentors for your organization? Please be as specific as possible.

2. What is your plan for dealing with disappearing students?

3. What is your plan for dealing with disappearing mentors?

4. What steps will you take to encourage students to interact with your
project's community before, during and after the program?

5. What will you do to ensure that your accepted students stick with the
project after GSoC concludes?

6. What would our organization expect to gain from this experience?

As you can see, this would not be a trivial undertaking for the FlightGear
project, and it's not something I can carry entirely on my own shoulders.
 Do we have others in the project that would be willing to volunteer their
time and participate in a mentoring and organizational roll?

We also need to quickly assemble a list of possible student project ideas
... and these need to be well measured ... like you would measure a pass in
soccer/futbol.  We want to avoid things that are too hard or too easy.  The
ball needs to arrive with the correct pace so the student can handle it.  We
want suggestions that could be attainable by a *student* in the allotted
time frame (summer?) and realize that a student may have to spend a good
chunk of their time learning about the FlightGear structure before they can
advance with their project.

I think we should avoid suggesting projects that are in FlightGear's
critical path.  I.e. add aircraft shadows might be an tempting project to
suggest, but is this student level work that could be finished in a summer?
 Do we want to pin all our hopes for aircraft shadows in FlightGear on a
google summer of code student who may bugout mid stream if it starts looking
too hard?  If it does get too hard, does that student fail or is it us
that failed as a mentoring organization?

So for project suggestions I think we should focus on projects that have the
best chance of teaching student level people, have the best chance of being
attainable in a summer of effort, have the best chance of helping a student
to gain confidence, knowledge, experience, etc.  We should be
careful/resistant to suggesting projects that are simply FlightGear feature
wishlist items.  We should suggest projects that the mentors have some idea
of a clear path to a solution (i.e. not so much research into new and
unknown things.)

I think to be successful, we need to keep our focus on the mentoring aspect
of this.  The focus is to help bring some of the younger generation up to
speed more quickly by sharing our experiences and knowledge.  It's something
we do already to some extent in a casual context.  The google program just
makes it official.  The mentors commit some time to sharing their experience
and knowledge and the students commit to actually listening and respecting
what is shared. :-)

Those are my thoughts.  I can get the ball rolling, but I can't do it all
myself.

Thanks,

Curt.
-- 
Curtis Olson: http://baron.flightgear.org/~curt/
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Google Summer of Code

2010-03-09 Thread Curtis Olson
One more thing we need.  I need someone to sign up on the google summer of
code page and create an ID for themselves.  The applications requires a
backup admin link id and it will not let me enter myself.

Thanks,

Curt.


On Tue, Mar 9, 2010 at 9:39 AM, Curtis Olson  wrote:

 On Tue, Mar 9, 2010 at 8:08 AM, Pete Morgan  wrote:

 Has/Does FlightGear participate ?


 http://google-opensource.blogspot.com/2010/03/google-summer-of-code-applications-now.html


 We have never participated before, but I see the deadline for organizations
 to apply is March 12 ... coming right up.  It's not like I've got nothing
 else to do, but I like the idea of mentoring.  I can think of many
 individuals who have played a mentor roll from time to time for me and I am
 very appreciative of that.  So I am submitting an application for FlightGear
 (assuming no one else has already.)

 Here are some things we need:

 1. Mentors
 2. Student applicants (mentorees).
 3. A web page listing project/mentoring ideas

 1  3 are the most important to have lined up before March 12 (Friday.)

 The organization application has some questions that I'd love to have some
 help thinking about and answering:

 1. What criteria did you use to select the individuals who will act as
 mentors for your organization? Please be as specific as possible.

 2. What is your plan for dealing with disappearing students?

 3. What is your plan for dealing with disappearing mentors?

 4. What steps will you take to encourage students to interact with your
 project's community before, during and after the program?

 5. What will you do to ensure that your accepted students stick with the
 project after GSoC concludes?

 6. What would our organization expect to gain from this experience?

 As you can see, this would not be a trivial undertaking for the FlightGear
 project, and it's not something I can carry entirely on my own shoulders.
  Do we have others in the project that would be willing to volunteer their
 time and participate in a mentoring and organizational roll?

 We also need to quickly assemble a list of possible student project ideas
 ... and these need to be well measured ... like you would measure a pass in
 soccer/futbol.  We want to avoid things that are too hard or too easy.  The
 ball needs to arrive with the correct pace so the student can handle it.  We
 want suggestions that could be attainable by a *student* in the allotted
 time frame (summer?) and realize that a student may have to spend a good
 chunk of their time learning about the FlightGear structure before they can
 advance with their project.

 I think we should avoid suggesting projects that are in FlightGear's
 critical path.  I.e. add aircraft shadows might be an tempting project to
 suggest, but is this student level work that could be finished in a summer?
  Do we want to pin all our hopes for aircraft shadows in FlightGear on a
 google summer of code student who may bugout mid stream if it starts looking
 too hard?  If it does get too hard, does that student fail or is it us
 that failed as a mentoring organization?

 So for project suggestions I think we should focus on projects that have
 the best chance of teaching student level people, have the best chance of
 being attainable in a summer of effort, have the best chance of helping a
 student to gain confidence, knowledge, experience, etc.  We should be
 careful/resistant to suggesting projects that are simply FlightGear feature
 wishlist items.  We should suggest projects that the mentors have some idea
 of a clear path to a solution (i.e. not so much research into new and
 unknown things.)

 I think to be successful, we need to keep our focus on the mentoring aspect
 of this.  The focus is to help bring some of the younger generation up to
 speed more quickly by sharing our experiences and knowledge.  It's something
 we do already to some extent in a casual context.  The google program just
 makes it official.  The mentors commit some time to sharing their experience
 and knowledge and the students commit to actually listening and respecting
 what is shared. :-)

 Those are my thoughts.  I can get the ball rolling, but I can't do it all
 myself.

 Thanks,

 Curt.
 --
 Curtis Olson: http://baron.flightgear.org/~curt/




-- 
Curtis Olson: http://baron.flightgear.org/~curt/
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] Google Summer of Code

2010-03-09 Thread Pete Morgan
Has/Does FlightGear participate ?

http://google-opensource.blogspot.com/2010/03/google-summer-of-code-applications-now.html

pete

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] Google Summer of Code -- opportunity for project?

2008-02-26 Thread Chris Metzler


For the last few years, Google has been running a program called the
Summer of Code.  Many/most of you are probably familiar with it.  For
those who aren't, it attempts to pair up students with open source
projects to mentor that student as they make contributions to the
project over the summer.  The students receive a stipend for the
time spent working on the open source project.

An FAQ about the program can be found at:

http://code.google.com/soc/2008/faqs.html

Early on in that FAQ, you can follow links to past years' lists of open
source projects that have mentored a student/students, and received
contributions as a result.

Given that we have plenty of hard problems to work on, in areas that
students might find interesting and applicable to future work, I would
guess that FG could really benefit from involvement in GSOC.

Thoughts?  The period for mentoring organizations to apply is March 3
through March 12.


-c

-- 
Chris Metzler   [EMAIL PROTECTED]
(remove snip-me. to email)

As a child I understood how to give; I have forgotten this grace since I
have become civilized. - Chief Luther Standing Bear


signature.asc
Description: PGP signature
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel