Re: [myhdl-list] Proposal: New class, ClockDomain

[Christopher F. <chr...@gm...>]

On 5/17/13 12:23 PM, Oscar Daniel Diaz wrote:
> El Wed, 15 May 2013 09:29:15 +0200
> Jan Decaluwe <ja...@ja...> escribió:
>
>> On 05/15/2013 03:47 AM, Christopher Lozinski wrote:
>>>    Clock domain is a great idea.
>>>
>>> There should be a rich and interesting library of Hardware modules
>>> available as a library in MyHDL.
>>
>> Of course there should not.
>>
>> Unlike Python, it is totally unclear how a "standard" library for
>> MyHDL should look like.
>>
>> Guido himself recently explained how the concept of the Python
>> standard library is frequently misunderstood. The Python standard
>> library is like a minimum set of generally useful functionality,
>> on which there is basically a consensus.
>>
>> However, being in the standard library is not a blessing. It takes
>> ages, and you have comply with all kinds of Python-release related
>> restrictions. I certainly would not want MyHDL to be in the
>> Python standard library. For innovation, you don't want a
>> standard library.
>>
>> For the record, I am of course all of for "rich and interesting
>> libraries of MyHDL hardware modules" - plenty of them, including
>> competing ones. Just do not look at me or the MyHDL library itself for
>> that - I am doing my share and I have many other plans.
>
> Totally agree. Lately I though about how to gather different
> contributions into one (or several) modules.
>
> I was thinking on making a module index on the wiki; with module
> descriptions and some search keywords. The current mechanism is the
> user's pages and its own descriptions of their projects.

There is a little bit of this in the user-space, but to have
a dedicated page with a module link and short description
and, maybe, a few checkboxes like open-cores (model,
convertible, ect) would be an straightforward way to get
going.  There have been a few useful modules posted to
the mailing-list (I think only exist on the mailing list).

>
> Also, I think we should define some coding guidelines for the modules
> to be included on the index, so we have basic quality standard.

There has been past discussions if it would be possible
to create an open-cores like site with a bunch of myhdl
modules.  If you have a site with this goal you can have
guidelines etc (I would like to see complete tests more
than syntax guidelines as a requirement).  But you would
need someone fairly dedicated to build the site.

>
> Another option is to use bitbucket features for group develop, I'm
> checking what bitbucket offers for multi-users.

You can look at other projects like pypy hosted on bitbucket,
bitbucket does have "groups", I think this is a simple way
to control permissions/access.  Example, you could create
a group, /myhdl_cores/ (or whatever) and have myhdl_cores_public
repository that you give permissions to a large group.

The documentation for the cores can be in sphinx and you can
post/host it on "readthedocs".  It would be useful/interesting
to have nightly builds where the cores are checked for changes
and if so the tests are run against the cores.  You can have a
real-time status of which cores are stable (ish).

But it is easy to talk about this stuff and throw some ideas
around but it is some work to actually put it all together.  I
would be supportive and could move a bunch of my stuff to the
repo, if one was put together and it looked promising.

Regards,
Chris