Thread: [myhdl-list] Reflections on a MyHDL IP library
Brought to you by:
jandecaluwe
Menu
▾
▴
myhdl-list
|
From: Jan D. <ja...@ja...> - 2006-11-16 20:26:13
|
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:oss_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? -- Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com Losbergenlaan 16, B-3010 Leuven, Belgium From Python to silicon: http://myhdl.jandecaluwe.com |
|
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? |
|
From: <ni...@gm...> - 2006-11-16 20:44:22
|
VGhlIHRoaXJkIG9wdGlvbiBpcyBncmVhdC4gDQpTZW50IGZyb20gbXkgQmxhY2tCZXJyea4gd2ly ZWxlc3MgaGFuZGhlbGQgIA0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogVG9t IERpbGxvbiA8VERpbGxvbkBkaWxsb25lbmcuY29tPg0KRGF0ZTogVGh1LCAxNiBOb3YgMjAwNiAx NDozODozMSANClRvOkdlbmVyYWwgZGlzY3Vzc2lvbnMgb24gTXlIREwgPG15aGRsLWxpc3RAbGlz dHMuc291cmNlZm9yZ2UubmV0Pg0KU3ViamVjdDogUmU6IFtteWhkbC1saXN0XSBSZWZsZWN0aW9u cyBvbiBhIE15SERMIElQIGxpYnJhcnkNCg0KSmFuLA0KDQpJZiB5b3UgY2hvb3NlIG9wdGlvbiAz LCBJIHdvdWxkIGJlIHdpbGxpbmcgdG8gaG9zdCB0aGUgc2l0ZSBvbiBvdXIgc2VydmVycyBhbmQg DQppbnN0YWxsIHdoYXRldmVyIHlvdSBuZWVkIHRvIHJ1biB5b3VyIGN1cnJlbnQgc2l0ZSAoYXMg bG9uZyBhcyBpdCBpcyANCmF2YWlsYWJsZSBhbmQgcnVucyBvbiBMaW51eCkuDQoNClRvbQ0KDQoN Ck9uIFRodXJzZGF5IDE2IE5vdmVtYmVyIDIwMDYgMTU6MDAsIEphbiBEZWNhbHV3ZSB3cm90ZToN Cj4gSGkgYWxsOg0KPg0KPiBBbiBvcGVuLXNvdXJjZSBNeUhETCBJUCBsaWJyYXJ5IHdvdWxkIHBy b2JhYmx5IGJlIGEgZ3JlYXQNCj4gYm9vc3QgdG8gdGhlIHByb2plY3QuIFlvdSBtYXkgaGF2ZSBu b3RpY2VkIHRoYXQgR2VvcmdlIGlzDQo+IG1ha2luZyBhIHN0YXJ0IHdpdGggdGhpczoNCj4NCj4g aHR0cDovL215aGRsLmphbmRlY2FsdXdlLmNvbS9kb2t1LnBocC9wcm9qZWN0czpkc3gxMDAwDQo+ IGh0dHA6Ly9teWhkbC5qYW5kZWNhbHV3ZS5jb20vZG9rdS5waHAvdXNlcnM6Z2VvcmdlX3BhbnRh em9wb3Vsb3M6cHJvamVjdHM6bw0KPnNzX2lwX2NvcmVzOmxmc3Jfc2lkDQo+DQo+IFNvIGl0J3Mg YSBnb29kIHRpbWUgdG8gcmVmbGVjdCBvbiB0aGlzIGEgbGl0dGxlLCBtb3JlIHNwZWNpZmljYWxs eQ0KPiBvbiB3aGF0IHdvdWxkIGJlIHRoZSBiZXN0IHdheSB0byBzZXQgdGhpcyB1cC4NCj4NCj4g SSBjYW4gdGhpbmsgb2YgMyBwb3NzaWJpbGl0aWVzOg0KPg0KPiAxKSBzaW1wbHkgdXNlIHRoZSB3 aWtpIG9uIHRoZSBleGlzdGluZyBzaXRlIG15aGRsLmphbmRlY2FsdXdlLmNvbQ0KPg0KPiBQcm86 IHdlIGNhbiBzaW1wbHkgY29udGludWUgdG8gd29yayBhcyB3ZSBkbyBub3cNCj4NCj4gQ29uOiB3 ZSB3YW50IHRvIGF0dHJhY3QgSVAgZG9uYXRpb25zIGZyb20gYXMgbWFueSBwZW9wbGUgYXMgcG9z c2libGUuDQo+IEEgc2l0ZSBsaW5rZWQgdG8gbXkgcGVyc29uYWwgbmFtZSBtYXkgbm90IGJlIHRo ZSByaWdodCB3YXkgdG8gZG8NCj4gdGhpcy4gSW4gZmFjdCwgaXQgbWF5IGhhdmUgYmVlbiBhbiBv YnN0YWNsZSBpbiB0aGUgcGFzdCB0byBvdGhlcg0KPiB0eXBlcyBvZiBjb250cmlidXRpb25zLg0K Pg0KPiAyKSBwdWJsaXNoIE15SERMIElQIG9uIG9wZW5jb3Jlcy5vcmcNCj4NCj4gUHJvOiBXZSBt YXkgY3JlYXRlIHZpc2liaWxpdHkgYW5kIGdvb2R3aWxsIHdpdGggb3BlbiBzb3VyY2UgSVANCj4g ZGV2ZWxvcGVycy4gVGhlIGluZnJhc3RydWN0dXJlIGlzIHJlYWR5IHRvIHVzZSwgYW5kIGlzIHR1 bmVkIHRvDQo+IElQIGRpc3RyaWJ1dGlvbi4NCj4NCj4gQ29uOiBJIGRvbid0IHJlYWxseSBsaWtl IHRoZSBpbnRlcmZhY2UgOi0pIEl0IHdvdWxkIGJlIG1vcmUNCj4gZGlmZmljdWx0IHRvIGhpZ2hs aWdodCBNeUhETCdzIHNwZWNpZmljIGNhcGFiaWxpdGllcy4gVGhlDQo+IHdheSB0byBwcmVzZW50 IHRoZSBJUCBpcyBxdWl0ZSBzdHJpY3QsIGFuZCB3ZSBjYW5ub3QgcmVhbGx5DQo+IGluZmx1ZW5j ZSB0aGF0Lg0KPg0KPiAzKSBjcmVhdGUgYSBuZXcgc2l0ZSwgZS5nLiBteWhkbC5vcmcNCj4NCj4g UHJvOiBXZSBoYXZlIGEgIm5ldXRyYWwiIGJ1dCBNeUhETC1kZWRpY2F0ZWQgc2l0ZSB0aGF0IHBl b3BsZQ0KPiBtYXkgYmUgbW9yZSB3aWxsaW5nIHRvIGNvbnRyaWJ1dGUgdG8sIHdoaWxlIHN0aWxs IGhhdmluZyBhIGxvdA0KPiBvZiBmbGV4aWJpbGl0eS4gV2UgY2FuIGludmVzdGlnYXRlIGFuZCBj aG9vc2UgbmV3IG9wdGlvbnMgZm9yIGhvc3RpbmcNCj4gYW5kIGNvbnRlbnQgbWFuYWdlbWVudC4N Cj4NCj4gQ29uOiBJdCBtYXkgdGFrZSBzb21lIHRpbWUgdG8gZGVjaWRlIG9uIHRoZSBvcHRpb25z IGFuZCB0bw0KPiBzZXQgdGhpbmdzIHVwLg0KPg0KPiBOb3RlOiBpbiB0aGlzIGNhc2UgSSB3b3Vs ZCBzdGlsbCBsaWtlIHRvIG93biB0aGUgZG9tYWluIG5hbWUsDQo+IGFuZCBJIHdvdWxkIGJlIHdp bGxpbmcgdG8gcGF5IGZvciB0aGUgaG9zdGluZyBjb3N0cyBhbmQgdG8NCj4gKGNvKW1hbmFnZSB0 aGUgc2l0ZS4NCj4NCj4NCj4NCj4gV2hhdCBkbyB5b3UgdGhpbms/DQoNCi0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0NClRha2UgU3VydmV5cy4gRWFybiBDYXNoLiBJbmZsdWVuY2UgdGhlIEZ1dHVyZSBvZiBJVA0K Sm9pbiBTb3VyY2VGb3JnZS5uZXQncyBUZWNoc2F5IHBhbmVsIGFuZCB5b3UnbGwgZ2V0IHRoZSBj aGFuY2UgdG8gc2hhcmUgeW91cg0Kb3BpbmlvbnMgb24gSVQgJiBidXNpbmVzcyB0b3BpY3MgdGhy b3VnaCBicmllZiBzdXJ2ZXlzIC0gYW5kIGVhcm4gY2FzaA0KaHR0cDovL3d3dy50ZWNoc2F5LmNv bS9kZWZhdWx0LnBocD9wYWdlPWpvaW4ucGhwJnA9c291cmNlZm9yZ2UmQ0lEPURFVkRFVg0KX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm15aGRsLWxpc3Qg bWFpbGluZyBsaXN0DQpteWhkbC1saXN0QGxpc3RzLnNvdXJjZWZvcmdlLm5ldA0KaHR0cHM6Ly9s aXN0cy5zb3VyY2Vmb3JnZS5uZXQvbGlzdHMvbGlzdGluZm8vbXloZGwtbGlzdA0K |
|
From: George P. <ge...@ga...> - 2006-11-16 20:48:26
|
> > 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. > > > > I like option 3 the best. At the same time, I have a bunch of links out there to the current site and I'd prefer some kind of redirection to happen for a good while. I still like docuwiki a great deal. Also, I don't see a problem with taking selected IP cores from myhdl.org and creating opencores.org projects on their site. Thanks, George http://www.gammaburst.net |
|
From: <dan...@we...> - 2006-11-16 22:39:31
|
Jan Decaluwe wrote: > > 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. I agree, seems like they did everything on their own and they are reluctant to changes. There are some nice features though, like highlighting on the front page which project got updated recently. I also don't like how much "me too" has gathered in that community. First it was only on the mailing lists. Now it comes that far that people write bug reports the type of "plz send mp3 vhdl code". > > 3) create a new site, e.g. myhdl.org I like that option too. I have been working with trac recently http://trac.edgewall.org/, it has a web interface for svn, ticket system and wiki. Now the focus on that software is more single project type. It would be good if there is something like an umbrella to that, that has the features like sourceforge or opencores, listing the projects, categorizing them, etc. Guenter |
|
From: George P. <ge...@ga...> - 2006-11-16 22:47:37
|
>> 3) create a new site, e.g. myhdl.org >> > > I like that option too. > > I have been working with trac recently http://trac.edgewall.org/, it has > a web interface for svn, ticket system and wiki. Now the focus on that > software is more single project type. It would be good if there is > something like an umbrella to that, that has the features like > sourceforge or opencores, listing the projects, categorizing them, etc. > > Guenter > > I'd love to have subversion support. That's what I use here at home and I love it. Besides what I've published so far, I have my own personal IP library and it's in the form of a subversion tree. Some of the modules depend on others, and I'm still working out the best way to deal with that, but it's working fairly well as it is. Trac looks very interesting in that it supports svn and the ticket system, and is also a wiki. How does the wiki part compare to docuwiki? Are there any nice docuwiki features we'd have to give up? Thanks, George > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > myhdl-list mailing list > myh...@li... > https://lists.sourceforge.net/lists/listinfo/myhdl-list > |
|
From: <dan...@we...> - 2006-11-17 00:29:04
|
George Pantazopoulos wrote: [...] > > Trac looks very interesting in that it supports svn and the ticket > system, and is also a wiki. How does the wiki part compare to docuwiki? > Are there any nice docuwiki features we'd have to give up? I haven't done too much with docuwiki. I think the wiki syntax is pretty much the same. From the first sight it looks like that docuwiki has a nicer interface with the menu at the left side. Though I wonder whether that can be done with trac too. 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. Looking through the trac users page I found an interesting project that seems to be the umbrella that I mentioned: www.kforgeproject.com. Guenter |
|
From: Jan D. <ja...@ja...> - 2006-11-17 20:56:22
|
Günter Dannoritzer wrote: > George Pantazopoulos wrote: > [...] > >>Trac looks very interesting in that it supports svn and the ticket >>system, and is also a wiki. How does the wiki part compare to docuwiki? >>Are there any nice docuwiki features we'd have to give up? > > > I haven't done too much with docuwiki. I think the wiki syntax is pretty > much the same. From the first sight it looks like that docuwiki has a > nicer interface with the menu at the left side. That was my personal contribution to the dokuwiki project :-) By now there are many other templates, several with sidebars that you could use to change the dokuwiki look instantaneously. > Though I wonder whether > that can be done with trac too. > > 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. Jan -- Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com Losbergenlaan 16, B-3010 Leuven, Belgium From Python to silicon: http://myhdl.jandecaluwe.com |
|
From: <dan...@we...> - 2006-11-17 22:40:45
|
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 |
|
From: George P. <ge...@ga...> - 2006-12-13 14:16:50
|
On Fri, November 17, 2006 5:40 pm, G=FCnter 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 offer= s the most potential. Zope seems more fundamental than all the others. Since modules can be downloaded and/or created for it, it can incorporate all their functionality. In fact, my friend told me a Zope-based site could even run all those other pre-existing components under one umbrella. Last, but certainly not least, Zope is based on Python, and not nasty, C-like PHP. Here's but one site someone did using Zope as a backend: http://www.issuetrackerproduct.com/ His main site: http://www.peterbe.com/ Zope webpage: http://www.zope.org/ Rock on, George http://www.gammaburst.net |
|
From:
<joa...@em...> - 2006-12-13 15:15:26
|
George Pantazopoulos schrieb: > 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. > > Zope seems more fundamental than all the others. Since modules can be > downloaded and/or created for it, it can incorporate all their > functionality. > > In fact, my friend told me a Zope-based site could even run all those > other pre-existing components under one umbrella. Last, but certainly not > least, Zope is based on Python, and not nasty, C-like PHP. > I'm working with Plone (CMS based on Zope) as my day job, so in case that some help and support is needed, I can contribute (e.g. if a MyHDL skin is needed). Be aware that the learning curve is rather steep, but Plone and Zope are mature and worth the efforts IMO. Joachim |
|
From: Tom D. <TD...@di...> - 2006-12-13 15:32:00
|
> I'm working with Plone (CMS based on Zope) as my day job, so in case > that some > help and support is needed, I can contribute (e.g. if a MyHDL skin is > needed). Be aware > that the learning curve is rather steep, but Plone and Zope are mature > and worth the > efforts IMO. > We use plone to host our website and since we have offered to host the myhdl.org site, that may be a good option. We are by no means plone experts, but can do enough to get a site setup so it is easy to add content. Tom |
|
From: George P. <ge...@ga...> - 2006-12-13 15:48:03
|
On Wed, December 13, 2006 10:15 am, Joachim K=F6nig-Baltes wrote: > George Pantazopoulos schrieb: >> 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. >> >> Zope seems more fundamental than all the others. Since modules can be >> downloaded and/or created for it, it can incorporate all their >> functionality. >> >> In fact, my friend told me a Zope-based site could even run all those >> other pre-existing components under one umbrella. Last, but certainly >> not >> least, Zope is based on Python, and not nasty, C-like PHP. >> > I'm working with Plone (CMS based on Zope) as my day job, so in case > that some > help and support is needed, I can contribute (e.g. if a MyHDL skin is > needed). Be aware > that the learning curve is rather steep, but Plone and Zope are mature > and worth the > efforts IMO. > > Joachim > Plone looks like exactly what I've wanted all along! Thanks Joachim! I was very impressed with their website and demostration videos. I think experiencing something like this as a lot better than reading about it. Plone demonstration videos: http://plone.org/about/movies Rock on, George > -----------------------------------------------------------------------= -- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > myhdl-list mailing list > myh...@li... > https://lists.sourceforge.net/lists/listinfo/myhdl-list > --=20 George Pantazopoulos http://www.gammaburst.net |
|
From: dannoritzer <dan...@we...> - 2006-12-13 16:08:18
|
Joachim König-Baltes wrote: > I'm working with Plone (CMS based on Zope) as my day job, so in case > that some > help and support is needed, I can contribute (e.g. if a MyHDL skin is > needed). Be aware > that the learning curve is rather steep, but Plone and Zope are mature > and worth the > efforts IMO. > > Joachim > That sounds good to have an experienced Plone user/developer. I had some frustrating experience with adding Products to Plone that caused a lot of maintenance when doing a site update. -- Products are add ons to the basic installation that add functions like issue tracking for example. http://plone.org/products -- One I had problems with was PloneCollectorNG, an issue tracking system. Another was a Product with some additional file types -- forgot its name -- that could be added and had nicer icons and better indexing support for PDF documents for example. I think before committing to Plone it would be good to make a list of what features should be provided by the page and then look how much is provided by Plone and what can be added through Products. Cheers, Guenter |
|
From: Jan D. <ja...@ja...> - 2006-12-13 16:02:36
|
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 |
|
From: Brendan R. <bre...@gm...> - 2006-12-14 00:04:34
|
Jan Decaluwe <jan <at> jandecaluwe.com> writes: > > George Pantazopoulos wrote: > > 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 > I'm definitely not a fan of Zope and, through relation, Plone. It's just too complex. There are a few new python-based CMSs, however, and of these I think that skeletonz (http://orangoo.com/skeletonz/) looks pretty promising, though there's bound to be one for Turbogears or Django as well. Just my $0.02. - Brendan |
|
From: dannoritzer <dan...@we...> - 2006-12-14 18:05:21
|
Brendan Rankin wrote: > > I'm definitely not a fan of Zope and, through relation, Plone. It's just too > complex. There are a few new python-based CMSs, however, and of these I think > that skeletonz (http://orangoo.com/skeletonz/) looks pretty promising, though > there's bound to be one for Turbogears or Django as well. How would you compare Skeletonz, TurboGears, and Django in terms of how much development has been done to it? I got the feeling that Django exists already for quite some time, where as TurboGears and Skeletonz are newer, but there seems to be quite some activity in development going on with the two later ones? Cheers, Guenter |
|
From: Tom D. <TD...@di...> - 2006-12-14 06:53:40
|
> 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. > I agree it is complicated. Newer versions of plone keep you further away from zope but there is still more to know than you would like to. I had to buy a book to help me understand how to use it. On the other hand, it provides a lot. All the site structure is just there. There are add on products for just about anything you could need, including a wiki. All in all, it is probably overkill for a small site, if something easier to use was available that provided all the features required for the site that would be a better option. Maybe the thing to do is so compile a list of features needed to properly host the site. Tom |
|
From: George P. <ge...@ga...> - 2006-12-14 13:53:23
|
Tom Dillon wrote: >> 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. >> >> > > I agree it is complicated. Newer versions of plone keep you further away from > zope but there is still more to know than you would like to. I had to buy a > book to help me understand how to use it. > > On the other hand, it provides a lot. All the site structure is just there. > There are add on products for just about anything you could need, including a > wiki. > > All in all, it is probably overkill for a small site, if something easier to > use was available that provided all the features required for the site that > would be a better option. > > Maybe the thing to do is so compile a list of features needed to properly host > the site. > > Tom > > FYI I just found a python-oriented hosting provider that already has Zope AND Plone installed and ready to create websites on. I was really impressed by their features, and I signed up for month to month, so all I risk is $34.95 right now. Haven't set it up just yet, but I'll let you all know how it goes. Another interesting tidbit from their site: "As both python and open-source lovers we're happy to offer free trac/subversion hosting for open-source python projects. We already host more than 400 of them." Here's the site. http://www.webfaction.com/ Rock on, George |
|
From: dannoritzer <dan...@we...> - 2006-12-14 14:10:42
|
George Pantazopoulos wrote: >> >> > FYI I just found a python-oriented hosting provider that already has > Zope AND Plone installed and ready to create websites on. I was really > impressed by their features, and I signed up for month to month, so all > I risk is $34.95 right now. Haven't set it up just yet, but I'll let you > all know how it goes. You should spend that money on a hard drive and install Linux on it ;) Most distributions come at least with zope and you can install plone on top of that. But hey, what am I saying, there used to be a windows installer for plone. Might be another way for testing. Guenter |
|
From: George P. <ge...@ga...> - 2006-12-14 14:12:50
|
dannoritzer wrote: > George Pantazopoulos wrote: > > >>> >>> >> FYI I just found a python-oriented hosting provider that already has >> Zope AND Plone installed and ready to create websites on. I was really >> impressed by their features, and I signed up for month to month, so all >> I risk is $34.95 right now. Haven't set it up just yet, but I'll let you >> all know how it goes. >> > > You should spend that money on a hard drive and install Linux on it ;) > Most distributions come at least with zope and you can install plone on > top of that. > > But hey, what am I saying, there used to be a windows installer for > plone. Might be another way for testing. > > Guenter > Been there, done that (Gentoo and Ubuntu), too busy to deal with all that right now. I want it to Just Work(tm) ;-) George |
|
From: Tom D. <TD...@di...> - 2006-12-14 15:33:28
|
On Thursday 14 December 2006 07:53, George Pantazopoulos wrote: > FYI I just found a python-oriented hosting provider that already has > Zope AND Plone installed and ready to create websites on. I was really > impressed by their features, and I signed up for month to month, so all > I risk is $34.95 right now. Haven't set it up just yet, but I'll let you > all know how it goes. > > Another interesting tidbit from their site: > "As both python and open-source lovers we're happy to offer free > trac/subversion hosting for open-source python projects. We already host > more than 400 of them." We have offered to host the myhdl.org site on our servers. We have plone, subversion, and trac all running. Trac and subversion at this point are only used internally, but those could be extended for public access. I would recommend making sure plone is not overkill for this site. Again think we should come up with a list of features required, and find the simplest solution as nobody wants to spend more time on web development than they need to. Tom |
|
From: George P. <ge...@ga...> - 2006-12-14 15:44:32
|
Tom Dillon wrote: > On Thursday 14 December 2006 07:53, George Pantazopoulos wrote: > >> FYI I just found a python-oriented hosting provider that already has >> Zope AND Plone installed and ready to create websites on. I was really >> impressed by their features, and I signed up for month to month, so all >> I risk is $34.95 right now. Haven't set it up just yet, but I'll let you >> all know how it goes. >> >> Another interesting tidbit from their site: >> "As both python and open-source lovers we're happy to offer free >> trac/subversion hosting for open-source python projects. We already host >> more than 400 of them." >> > > We have offered to host the myhdl.org site on our servers. We have plone, > subversion, and trac all running. Trac and subversion at this point are only > used internally, but those could be extended for public access. > > I would recommend making sure plone is not overkill for this site. Again think > we should come up with a list of features required, and find the simplest > solution as nobody wants to spend more time on web development than they need > to. > > Tom > Hi Tom, I agree wholeheartedly on putting together a list of features for myhdl.org. I'm grateful that you've offered all those features. I bought a hosting plan because I have substantial needs for my own website, which is not directly related to myhdl.org. What is your site? Desired Features (so far): -------------------------- * Version control for IP * Easily editable web content (no HTML required) * Versioned web content (as in Wiki's) * LaTeX support would be nice (for light use of equations). * Ability to seamlessly integrate links to member pages (and/or host member sites) * Ability to do Wiki-style pages and not just blog posts. Rock on, George |
|
From: Jan D. <ja...@ja...> - 2006-12-14 16:54:23
|
George Pantazopoulos wrote: > > Desired Features (so far): > -------------------------- > > * Version control for IP All your other points have to do with documentation, and I agree with all of them. But this one is about (open-source) development. What do you see as the value of hosting that ourselves, as opposed to simply opening a project in sourceforge or google code or perhaps others? > * Easily editable web content (no HTML required) > * Versioned web content (as in Wiki's) > * LaTeX support would be nice (for light use of equations). > * Ability to seamlessly integrate links to member pages (and/or host > member sites) > * Ability to do Wiki-style pages and not just blog posts. -- Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com Losbergenlaan 16, B-3010 Leuven, Belgium From Python to silicon: http://myhdl.jandecaluwe.com |
|
From: George P. <ge...@ga...> - 2006-12-14 17:35:16
|
Jan Decaluwe wrote: > George Pantazopoulos wrote: > > >> Desired Features (so far): >> -------------------------- >> >> * Version control for IP >> > > All your other points have to do with documentation, > and I agree with all of them. > > But this one is about (open-source) development. What > do you see as the value of hosting that ourselves, as opposed to > simply opening a project in sourceforge or google code > or perhaps others? > > Hi Jan, I didn't necessarily mean that we had to host it ourselves, just that we need it somehow. I think writing down our requirements, even if they're obvious can help us see the big picture better. I think it's best at this stage to focus on what we need and not on how we're to get it (that comes later). Regards, George >> * Easily editable web content (no HTML required) >> * Versioned web content (as in Wiki's) >> * LaTeX support would be nice (for light use of equations). >> * Ability to seamlessly integrate links to member pages (and/or host >> member sites) >> * Ability to do Wiki-style pages and not just blog posts. >> > > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X