Re: [myhdl-list] Reflections on a MyHDL IP library

[Jan D. <ja...@ja...>]

George Pantazopoulos wrote:
> On Fri, November 17, 2006 5:40 pm, Günter Dannoritzer wrote:
> 
>>Jan Decaluwe wrote:
>>[...]
>>
>>>>Trac looks more like it is suited for one project group. I think the
>>>>mix
>>>>of having different users that can participate in different projects
>>>>requires quite some tweaking of trac.
>>>
>>>I'm not convinced this is what we need first. Trac seems to be a
>>>sourceforge done better, in other words, a development management
>>>system. But this is a general problem, well suited to large scale
>>>dedicated hosted solutions such as sourceforge itself, or Google Code
>>>(both with subversion support), or opencores.org.
>>>
>>>I think what we need first is a content management system, well suited
>>>to
>>>create great documentation rapidly, and distribute releases by the
>>>good old method of tar files.
>>>
>>
>>I see what you are saying and I agree, with a small community as it is
>>now, there is no need to have a full fledged project management system.
>>That just adds to the administrative overhead and also can create a lot
>>of junk.
>>
>>Now what features do you see that a content management system would add,
>>that cannot be done with the docuwiki as it is now?
>>
>>
>>Guenter
>>
> 
> 
> After doing some explorations, I highly recommend looking at Zope for
> myhdl.org. I've been looking at content management systems, including
> MediaWiki, phpBB, Drupal, Wordpress, and Zope. So far, I think Zope offers
> the most potential.

Mm, but have you ever used it :-) Several year ago, I have a number of times,
and never really liked it. I found if very complicated and full of jargon.
Also, it has something unpythonic: it's large, not orthogonal and complex.
It was supposed to become the Python killer app, but from what I hear
many pythonistas simply don't like it.

I never used Plone, but I imagine it has been invented to take away
some complexity from the underlying Zope to make a more usable system.
Still, I fear that the underlying complexity still shines through.
Tom is using it for his site, so he may give good advice here.

In any case, with the migration to myhdl.org we now have the opportunity
to re-assess the CMS software issue. I think it's wise to take some
time to consider the options carefully, based on a specific list
of must-have and desirable features.

Jan

-- 
Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
Losbergenlaan 16, B-3010 Leuven, Belgium
     From Python to silicon:
     http://myhdl.jandecaluwe.com