comunity source server

COMMENT PLEASE

I checked the Google hosting project today

http://code.google.com/hosting/ (http://code.google.com/hosting/)

Since Google does not offer the ability to create sub-projects, we may opt to start a new Google project for each component.

It uses subversion, which is good for a project with a developing directory structure. It has its own issue tracking system and seems easy to use.

I propose LGPL as the license for the project, since opencores uses this license.

http://en.wikipedia.org/wiki/lgpl (http://en.wikipedia.org/wiki/lgpl)

http://www.opencores.org/faq.cgi/section/4/4 (http://www.opencores.org/faq.cgi/section/4/4)

I propose to group SOC components into the next groups (with example components):

1. system

- button debouncing

- led_blinker (http://en.wikipedia.org/wiki/blinkenlights)

- general purpose clock dividers

2. DSP

- FIR filter

- CIC filter

3. SOC (for SOPC builder)

- I2C (from opencores)

- SPI

- UART with fifo

- onewire

- ...

Iztok Jeras