On Thu, Jan 06, 2011 at 10:30:52PM -0500, rail shafigulin wrote: > i would like to become one of the developers for ghdl, but unfortunately i > don't know enough about programming, vhdl and tool development. what kind of > skills and experience would i need to become one of the developers? any tips > are appreciated.
I cannot answer in name of any of the developers; I only use ghdl, and I thank them a lot. I think that in Open Source projects, people should get involved in development first by sending patches to the mailing list, implementing some features that could be of benefit for all. I think that a ticketing system having both bugs to be solved and desired features can be a good start for newcomers to learn about what can be useful for the ghdl users, and what developers agree on "it should be done some day". For what I know, GHDL lacks any ticket system that can convey such information to a newcomer. I don't know if "what should be done some day" is only on the heads of developrs, or it is published somewhere else. As for me, ghdl works quite well for me. So I would get benefits mostly if it made simulations faster, as to show something to be improved. If it is at the expense of nothing, it even does not need discussion then. :) Regards, Lluís. _______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
