GSoC

[konijn_]

Greetings,

part of 'the rant' mentioned the Google Code of Summer as a means to get more system work done on Vanilla.

The maintainer ( or someone he designates ) should write up a proposal for the next GSoC.

My preference would be to either expand or rewrite make files ( acorn ? amiga ? VMS ? ) , clean up code without changing functionality and getting angband on portables.

[Magnate]

Originally Posted by konijn_

Greetings,

part of 'the rant' mentioned the Google Code of Summer as a means to get more system work done on Vanilla.

The maintainer ( or someone he designates ) should write up a proposal for the next GSoC.

My preference would be to either expand or rewrite make files ( acorn ? amiga ? VMS ? ) , clean up code without changing functionality and getting angband on portables.

Sounds like an excellent idea - I'd go for a Symbian SDL port.

Excuse my ignorance, but can you tell us a bit about GSoC works? If we submit a successful proposal, does Google pay someone to write code for us? Or do they pay one of us to take a sabbatical and write it ourselves? The latter is still limited by our existing knowledge!

CC

[pav]

I have participated in SoC for a project of quite a large magnitude (FreeBSD) as a mentor. I would say Angband is too small project to justify even a single slot in SoC programme. But you may try.

You will need to provide Google with an official point of contact (takkaria). Then potential students will be submitting project propositions to Google. Then our people (accredited with Google beforehand) will score the proposals. Then Google will make up it's mind how many students they want to sponsor. Then top ranked proposals are accepted. The summer starts. At the end of the time period, mentors will submit an evaluation of their student's work back to Google. Google will then pay $4500 to a successfull student and $500 to takkaria. The mentor gets a t-shirt.

Don't expect SoC to give you a useful source code. That happens in minority of assignments. It might gain you a devoted contributor for the future, thou.

[konijn_]

Originally Posted by pav

I have participated in SoC for a project of quite a large magnitude (FreeBSD) as a mentor. I would say Angband is too small project to justify even a single slot in SoC programme. But you may try.

You will need to provide Google with an official point of contact (takkaria). Then potential students will be submitting project propositions to Google. Then our people (accredited with Google beforehand) will score the proposals. Then Google will make up it's mind how many students they want to sponsor. Then top ranked proposals are accepted. The summer starts. At the end of the time period, mentors will submit an evaluation of their student's work back to Google. Google will then pay $4500 to a successfull student and $500 to takkaria. The mentor gets a t-shirt.

Don't expect SoC to give you a useful source code. That happens in minority of assignments. It might gain you a devoted contributor for the future, thou.

Do we end up on their site either way ?

T.

[takkaria]

Originally Posted by konijn_

Greetings,

part of 'the rant' mentioned the Google Code of Summer as a means to get more system work done on Vanilla.

The maintainer ( or someone he designates ) should write up a proposal for the next GSoC.

My preference would be to either expand or rewrite make files ( acorn ? amiga ? VMS ? ) , clean up code without changing functionality and getting angband on portables.

I don't have the bandwidth to spare on GSoC this summer—and I don't think we'd get accepted as an organisation anyway. Maybe next year?