Re: [myhdl-list] Reflections on a MyHDL IP library
Brought to you by:
jandecaluwe
From: Tom D. <TD...@di...> - 2006-11-16 20:38:47
|
Jan, If you choose option 3, I would be willing to host the site on our servers and install whatever you need to run your current site (as long as it is available and runs on Linux). Tom On Thursday 16 November 2006 15:00, Jan Decaluwe wrote: > Hi all: > > An open-source MyHDL IP library would probably be a great > boost to the project. You may have noticed that George is > making a start with this: > > http://myhdl.jandecaluwe.com/doku.php/projects:dsx1000 > http://myhdl.jandecaluwe.com/doku.php/users:george_pantazopoulos:projects:o >ss_ip_cores:lfsr_sid > > So it's a good time to reflect on this a little, more specifically > on what would be the best way to set this up. > > I can think of 3 possibilities: > > 1) simply use the wiki on the existing site myhdl.jandecaluwe.com > > Pro: we can simply continue to work as we do now > > Con: we want to attract IP donations from as many people as possible. > A site linked to my personal name may not be the right way to do > this. In fact, it may have been an obstacle in the past to other > types of contributions. > > 2) publish MyHDL IP on opencores.org > > Pro: We may create visibility and goodwill with open source IP > developers. The infrastructure is ready to use, and is tuned to > IP distribution. > > Con: I don't really like the interface :-) It would be more > difficult to highlight MyHDL's specific capabilities. The > way to present the IP is quite strict, and we cannot really > influence that. > > 3) create a new site, e.g. myhdl.org > > Pro: We have a "neutral" but MyHDL-dedicated site that people > may be more willing to contribute to, while still having a lot > of flexibility. We can investigate and choose new options for hosting > and content management. > > Con: It may take some time to decide on the options and to > set things up. > > Note: in this case I would still like to own the domain name, > and I would be willing to pay for the hosting costs and to > (co)manage the site. > > > > What do you think? |