Re: [Iverilog-devel] Google SoC 2008!

[Stephen W. <st...@ic...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Nick Gasson wrote:
> Hi all,
> 
> I'm interested in working on Icarus Verilog as part of Summer of Code. 
> In particular I'm interested in building a VHDL plug-in code generator 
> to get a Verilog to VHDL translator (as per the projects wiki). This is 
> actually a problem I've encountered in real life -- when I've wanted to 
> use Verilog components in a VHDL system. Since it'll be a back-end code 
> generator, it should stay clear of a lot of the more complex VHDL 
> constructs, so hopefully this will be manageable as a summer project. 
> I'd like to focus on getting the synthesisable subset working first, as 
> I think this would be the most useful.
> 
> I'm a final-year Computer Systems and Software Engineering student at 
> the University of York (UK). I've got quite a bit of experience in VHDL 
> (mostly designs for Xilinx FPGAs) and the usual C/C++ (I have some 
> industrial experience with these). Unfortunately I don't really have any 
> Verilog knowledge beyond the usual introduction/tutorials, but I should 
> be able to pick it up pretty rapidly (and this project doesn't seem too 
> Verilog-y).
> 
> If this sounds reasonable I'll have a go at drafting a project proposal. 
> Is there anything you're looking for in particular on the application?

We're looking for an indication that you really can do what you propose
to do. We will use clues such as your apparent understanding of what
the project you propose actually *is*.

Some idea of a schedule, that looks reasonable to us, will help. Include
a schedule of your availability so that we can judge that your plan
fits. Note that some interruption in your GSoC is OK if we know it up
front, but is *not* OK if we find out about it later.

Because payments are involved, it would be good to clearly state
proposed "victory conditions": A sample program that you want to
work, a verifiable set of features, something like that. That helps
us mentors come evaluation time.

> I also volunteer to do the git version strings project :-)

We're also expecting a candidate to understand (or learn in a
hurry) git. Looks like you got a jump there.

We're also hoping to use the GSoC process to attract long-term
developers. We want people to come here to learn, participate,
and _remain_ with us in the long term. Google's stated purpose for
throwing money at us is to attract people to the open source community
who will then stay. This is about learning how the open source
"system" works, with a little motivation to get over the hump.

- --
Steve Williams                "The woods are lovely, dark and deep.
steve at icarus.com           But I have promises to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFH4TENrPt1Sc2b3ikRArz+AKCIJJZZocOtHCzncYtlpWFJ5AjGdACfXL11
ZPXlxfkaPI2udFkEQNLNVhE=
=GtNw
-----END PGP SIGNATURE-----