You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(2) |
Feb
(48) |
Mar
(17) |
Apr
(13) |
May
(102) |
Jun
(163) |
Jul
(203) |
Aug
(185) |
Sep
(16) |
Oct
(4) |
Nov
|
Dec
|
From: <s.k...@pr...> - 2003-06-04 21:40:19
|
@zoom: [...] > A user named sumank has PM'd me asking to volunteer for documentation. > I'll forward these volunteers to the list as soon as I receive them so > that the Project Leader can follow up with them. [...] sumank and geoff (and luca gioppo) are on my list. They posted in eNvo.com forum. I will publish this list (with all other names) on eNvo.com tomorrow. So we can add new members there in the future. [...] > It might be a good idea to put a contact name down somewhere in plain > view for people to contact if the do want to volunteer and participate. [...] I have opened a forum board on eNvo.de and eNvo.com There everybody has the possibility to answer to my call. Also you can find my name there and can find out my email, ICQ, etc. Mybe we can publish this kind of call on all other official eNvo sites. But I'm not good in italian, spanish, french, .... WindMeUp > > Zoom > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Etnus, makers of TotalView, The best > thread debugger on the planet. Designed with thread debugging features > you've never dreamed of, try TotalView 6 free at www.etnus.com. > _______________________________________________ > Envolution-devel mailing list > Env...@li... > https://lists.sourceforge.net/lists/listinfo/envolution-devel |
From: Scott K. <sc...@ki...> - 2003-06-04 21:36:20
|
Webmedic is a close dear friend and current business associate. Check out some of the information he has available on his site. Multisites http://www.webmedic.net/modules.php?op=modload&name=News&file=article&sid=13 Bencmarking Encompass versus others http://www.webmedic.net/webify_bench Enjoy! Zoom |
From: Scott K. <sc...@ki...> - 2003-06-04 21:16:20
|
A user named Geoff has volunteered for: 1) testing 2) Forum support (Mainly with handing default installation issues which people may have and things like that) 3) news/updates on the development of envolution. So this is a good thing to have someone volunteer to do forum support issues!!!!!!! Please someone followup with this guy and bring him on board. Zoom |
From: Scott K. <sc...@ki...> - 2003-06-04 21:10:53
|
A user named sumank has PM'd me asking to volunteer for documentation. I'll forward these volunteers to the list as soon as I receive them so that the Project Leader can follow up with them. It might be a good idea to put a contact name down somewhere in plain view for people to contact if the do want to volunteer and participate. Zoom |
From: Scott K. <sc...@ki...> - 2003-06-04 21:07:10
|
On Wed, 2003-06-04 at 11:50, Sjahrazad Alamsjah wrote: > On Wed, 4 Jun 2003 08:59:13 +0200, Luca.Gioppo wrote > > [...] > > Lets publish a roadmap since nobody starts one I'll give a first > > idea to work on: [...] > > I'm totally agreed with Luca. If we're concentrate more strengthen our team, > support, marketing etc, I'm sure our community will grow fast. We have > already envo network sites in some countries, this is also proven about the > envo added value. > A roadmap already exists as well as the philosophy Envolution was founded upon here: http://www.envolution.com/index.php?name=Subjects&file=index&req=listpages&subid=2 > Starting arguing between pn vs envo again :) will be contra productive. Let > pn has its own and vice versa. I agree that re-igniting the flames would be counter productive, but everyine should be aware that there is a lot of FUD spreading going on about Envolution on some sites and discussion lists. Wouldn't it be prudent to set the record straight and make our collective voices heard that we wish to be judged on factual information instead of outright false statements. The bottom line is Envolution development suffers because of this. The opriginal title of this thread should not have been Envolution vs PostNuke...instead it should have been: Envolution vs FUD Because Envolution is not competing against PostNuke or Xaraya or PHPNuke or Xoop's et al. We compete against our own abilities and faults and should not have to comepete against FUD from a few people who keep spreading it. Max is talking about setting the record straight and making our collective voices heard. Specifically that the Envolution community wants to be free from false and misleading statements and that we are good open source contributing netizens. Zoom |
From: TiMax - E. <web...@en...> - 2003-06-04 17:07:38
|
yes is not easy to manage that .... and i agree with Stefan But why postwrap ? try to test also StaticsDocs is not same= thing but sometimes is better TiMax On Wed, 04 Jun 2003 16:07:01 +0200, Stefan Koehler wrote: > @luca: > [...] We are going to use postwrap, and guess what, we'll need= to convert it to Oracle. > How do we usually proceed with modules not developed by the= envo community? [...] > > This is a fundamental problem. Because if we want to= distribute 3rd-party-modules including some changes for eNvo, it is not easy to hold them up-to-date, if= there are some updates and fixes published by module-owner. We have to implement them manually into the= modified files. Or we use these modules as is (based on xxx, version 123) and develop it in future under eNvo= without the support of the owner. > > [...] Do we try to get the approval of the author? can we ask= him to accept and include the modifiers on the source so that it colud be preserved for future releases and bug= fix? [...] > > This would be the better way. But it is neccessary to share= all work. This is a two-way development: > Owner -> eNvo, eNvo -> owner > Possible that not all changes would be shared. > > [...] Can we try to pull these developers in the envo= community? [...] > > And this would be the best way. But not every developer want= to work only for one community. They have some different interests, ideas, etc. to distribute their work. > But if he want to develop his modules also for eNvo, it would= be possible, that he can update his changes on our CVS. So we can share all automatically. > > Try it.... ;) > > WindMeUp > > > ------------------------------------------------------- > This SF.net email is sponsored by: Etnus, makers of= TotalView, The best > thread debugger on the planet. Designed with thread debugging= features > you've never dreamed of, try TotalView 6 free at= www.etnus.com. > _______________________________________________ > Envolution-devel mailing list > Env...@li... > https://lists.sourceforge.net/lists/listinfo/envolution-devel |
From: TiMax <ma...@em...> - 2003-06-04 17:04:16
|
I agree but now is time to finish these flames, because lot of= people and maybe lot of developers read it, beleive it and don't check eNvolution, so we loss lot of= potential developers and helpers. And me also i don't want to start flames in portalzine.de site or= other, for that me and Zoom work to write document to explain better what is eNvolution and what people can= have with eNvo. When document are ready, i submit it in this mailing list, we= revised it and we publish it, so invite people to go and read it. So we don't have flames but people can read it and understand TiMax On Wed, 4 Jun 2003 08:59:13 +0200, Luc...@cs... wrote: > > As always, I do not like loosing time warring. > It only reduce the time for coding. > Lets demonstrate the difference with fact instead of words, we= are quite > ready for the new version with lots of good points (for mine= part I believe > that when complete the Oracle compatibility will make the= difference on the > chioce for many people running intranets on business= realties) > Lets publish the roll of developers so to shed light on the= community > besides giving the merit to those behind the envo project. > Lets publish a roadmap since nobody starts one I'll give a= first idea to > work on: > > 1.2.x Compatibility with Oracle (not complete), installation= on Oracle, > benchmark (ready) > 1.2.x+1 Complete compatibility with Oracle, optimization= en code > cleaning, bug fix. (end july or september) > 1.2.x+2 LDAP integration as a native funtionality on users= (end > sectember) > 1.2.x+3 recursivity on categories for Download and groups = (end > ottobre) > > 1.3 All Oracle converted (complete compatibility), some= extra module > converted for Oracle, translation checked, accessible (W3C)= template, docs > for users and developers, an empty module and block for= tutorial and new > development [end of year?] > > these are ideas. > > I just say: let's people speak and stand on our road, ignoring= them, when > our work will be there when theirs will be just a forgotten= memory we shall > rejoice. > Bye > Luca |
From: Sjahrazad A. <sja...@ba...> - 2003-06-04 16:50:38
|
On Wed, 4 Jun 2003 08:59:13 +0200, Luca.Gioppo wrote > [...] > Lets publish a roadmap since nobody starts one I'll give a first > idea to work on: [...] I'm totally agreed with Luca. If we're concentrate more strengthen our team, support, marketing etc, I'm sure our community will grow fast. We have already envo network sites in some countries, this is also proven about the envo added value. Starting arguing between pn vs envo again :) will be contra productive. Let pn has its own and vice versa. sjah |
From: Stefan K. <Ste...@ga...> - 2003-06-04 14:40:01
|
[...] >>> bu...@di... 02.06.03 19.43 Uhr >>> There seem to be two places to get this right now. I don't see any reason = why we should maintain these defines in two different places, especially a = static file such as pnAPI.php. I suggest we move away from having these defined in the php file & only have the info available via = the database. [...] I agree. The better place for that informations would be the database. I = think we should make these changes you describe. WindMeUp ---------------------------- Currently, references to _PN_VERSION_NUM exist in: Stats module/index.php (line 462) Credits module/pnuser.php (lines: 76, 90, 104) The other two (_PN_VERSION_ID,_PN_VERSION_SUB) don't appear to ever get used. pnAPI defines: define('_PN_VERSION_NUM', "1.2"); define('_PN_VERSION_ID', "Envolution"); define('_PN_VERSION_SUB', "Michelangelo"); and database fields: /PNConfig Version_Num s:5:"1.2.0"; /PNConfig Version_ID s:10:"Envolution"; /PNConfig Version_Sub s:12:"Michelangelo"; The fields from the database are retrieved via: pnConfigGetVar('Version_Num') pnConfigGetVar('Version_ID') pnConfigGetVar('Version_Sub') ------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Envolution-devel mailing list Env...@li... https://lists.sourceforge.net/lists/listinfo/envolution-devel |
From: Stefan K. <Ste...@ga...> - 2003-06-04 14:07:44
|
@luca: [...] We are going to use postwrap, and guess what, we'll need to convert = it to Oracle. How do we usually proceed with modules not developed by the envo community?= [...] This is a fundamental problem. Because if we want to distribute 3rd-party-m= odules including some changes for eNvo, it is not easy to hold them = up-to-date, if there are some updates and fixes published by module-owner. = We have to implement them manually into the modified files. Or we use = these modules as is (based on xxx, version 123) and develop it in future = under eNvo without the support of the owner. [...] Do we try to get the approval of the author? can we ask him to = accept and include the modifiers on the source so that it colud be = preserved for future releases and bug fix? [...] This would be the better way. But it is neccessary to share all work. This = is a two-way development: Owner -> eNvo, eNvo -> owner Possible that not all changes would be shared. [...] Can we try to pull these developers in the envo community? [...] And this would be the best way. But not every developer want to work only = for one community. They have some different interests, ideas, etc. to = distribute their work. But if he want to develop his modules also for eNvo, it would be possible, = that he can update his changes on our CVS. So we can share all automaticall= y. Try it.... ;) WindMeUp |
From: <Luc...@cs...> - 2003-06-04 12:47:04
|
DQpXZSBhcmUgZ29pbmcgdG8gdXNlIHBvc3R3cmFwLCBhbmQgZ3Vlc3Mgd2hhdCwgd2UnbGwgbmVl ZCB0byBjb252ZXJ0IGl0IHRvDQpPcmFjbGUuDQpIb3cgZG8gd2UgdXN1YWxseSBwcm9jZWVkIHdp dGggbW9kdWxlcyBub3QgZGV2ZWxvcGVkIGJ5IHRoZSBlbnZvIGNvbW11bml0eT8NCkRvIHdlIHRy eSB0byBnZXQgdGhlIGFwcHJvdmFsIG9mIHRoZSBhdXRob3I/IGNhbiB3ZSBhc2sgaGltIHRvIGFj Y2VwdCBhbmQNCmluY2x1ZGUgdGhlIG1vZGlmaWVycyBvbiB0aGUgc291cmNlIHNvIHRoYXQgaXQg Y29sdWQgYmUgcHJlc2VydmVkIGZvcg0KZnV0dXJlIHJlbGVhc2VzIGFuZCBidWcgZml4Pw0KVGhp cyBpcyB0aGUgcXVlc3Rpb24gb2YgZXh0ZXJuYWwgbW9kdWxlcy4NCkNhbiB3ZSB0cnkgdG8gcHVs bCB0aGVzZSBkZXZlbG9wZXJzIGluIHRoZSBlbnZvIGNvbW11bml0eT8NCkFueSBpZGVhPw0KTHVj YQ0K |
From: <Luc...@cs...> - 2003-06-04 09:26:54
|
DQpPSywgd2UncmUgZ29pbmcgdG8gaW50ZWdyYXRlIExEQVAuDQpUaGVyZSBpcyBhIG5pY2UgbW9k dWxlIExEQVBhdXRoIHRoYXQgY291bGQgYmUgdXNlZC4NCkknZCBsaWtlIHRvIG1la2UgaXQgYSBz dGFuZGFyZCBtb2R1bGUgb2YgdGhlIG1haW4gZGlzdHJpYnV0aW9uIGJlY2F1c2UgaXQNCmNvdWxk IGJlIGEgbmljZSBtYXJrZXRpbmcgZmVhdHVyZSB0byBiZSBwcm91ZCBvZi4NClRoZSBtb2R1bGUg aXQncyB3ZWxsIGRvbmUsIGJ1dCB3ZSBuZWVkIHRvIHRlc3QgaXQuDQpJZiBldmVyeWJvZHkgYWdy ZWUgdGhpbmsgdGhhdCBzaG91bGQgYmUgY29udGFjdGVkIHRoZSBkZXZlbG9wZXIuDQpIb3cgY2Fu IHdlIGJlaGF2ZT8NCkx1Y2ENCg== |
From: <Luc...@cs...> - 2003-06-04 07:14:08
|
DQpBcyBhbHdheXMsIEkgZG8gbm90IGxpa2UgbG9vc2luZyB0aW1lIHdhcnJpbmcuDQpJdCBvbmx5 IHJlZHVjZSB0aGUgdGltZSBmb3IgY29kaW5nLg0KTGV0cyBkZW1vbnN0cmF0ZSB0aGUgZGlmZmVy ZW5jZSB3aXRoIGZhY3QgaW5zdGVhZCBvZiB3b3Jkcywgd2UgYXJlIHF1aXRlDQpyZWFkeSBmb3Ig dGhlIG5ldyB2ZXJzaW9uIHdpdGggbG90cyBvZiBnb29kIHBvaW50cyAoZm9yIG1pbmUgcGFydCBJ IGJlbGlldmUNCnRoYXQgd2hlbiBjb21wbGV0ZSB0aGUgT3JhY2xlIGNvbXBhdGliaWxpdHkgd2ls bCBtYWtlIHRoZSBkaWZmZXJlbmNlIG9uIHRoZQ0KY2hpb2NlIGZvciBtYW55IHBlb3BsZSBydW5u aW5nIGludHJhbmV0cyBvbiBidXNpbmVzcyByZWFsdGllcykNCkxldHMgcHVibGlzaCB0aGUgcm9s bCBvZiBkZXZlbG9wZXJzIHNvIHRvIHNoZWQgbGlnaHQgb24gdGhlIGNvbW11bml0eQ0KYmVzaWRl cyBnaXZpbmcgdGhlIG1lcml0IHRvIHRob3NlIGJlaGluZCB0aGUgZW52byBwcm9qZWN0Lg0KTGV0 cyBwdWJsaXNoIGEgcm9hZG1hcCBzaW5jZSBub2JvZHkgc3RhcnRzIG9uZSBJJ2xsIGdpdmUgYSBm aXJzdCBpZGVhIHRvDQp3b3JrIG9uOg0KDQoxLjIueCBDb21wYXRpYmlsaXR5IHdpdGggT3JhY2xl IChub3QgY29tcGxldGUpLCBpbnN0YWxsYXRpb24gb24gT3JhY2xlLA0KYmVuY2htYXJrICAgKHJl YWR5KQ0KMS4yLngrMSAgICAgQ29tcGxldGUgY29tcGF0aWJpbGl0eSB3aXRoIE9yYWNsZSwgb3B0 aW1pemF0aW9uIGVuIGNvZGUNCmNsZWFuaW5nLCBidWcgZml4LiAgICAgIChlbmQganVseSBvciBz ZXB0ZW1iZXIpDQoxLjIueCsyICAgICBMREFQIGludGVncmF0aW9uIGFzIGEgbmF0aXZlIGZ1bnRp b25hbGl0eSBvbiB1c2VycyAgICAoZW5kDQpzZWN0ZW1iZXIpDQoxLjIueCszICAgICByZWN1cnNp dml0eSBvbiBjYXRlZ29yaWVzIGZvciBEb3dubG9hZCBhbmQgZ3JvdXBzICAgICAoZW5kDQpvdHRv YnJlKQ0KDQoxLjMgICBBbGwgT3JhY2xlIGNvbnZlcnRlZCAoY29tcGxldGUgY29tcGF0aWJpbGl0 eSksIHNvbWUgZXh0cmEgbW9kdWxlDQpjb252ZXJ0ZWQgZm9yIE9yYWNsZSwgdHJhbnNsYXRpb24g Y2hlY2tlZCwgYWNjZXNzaWJsZSAoVzNDKSB0ZW1wbGF0ZSwgZG9jcw0KZm9yIHVzZXJzIGFuZCBk ZXZlbG9wZXJzLCBhbiBlbXB0eSBtb2R1bGUgYW5kIGJsb2NrIGZvciB0dXRvcmlhbCBhbmQgbmV3 DQpkZXZlbG9wbWVudCAgICAgICBbZW5kIG9mIHllYXI/XQ0KDQp0aGVzZSBhcmUgaWRlYXMuDQoN CkkganVzdCBzYXk6IGxldCdzIHBlb3BsZSBzcGVhayBhbmQgc3RhbmQgb24gb3VyIHJvYWQsIGln bm9yaW5nIHRoZW0sIHdoZW4NCm91ciB3b3JrIHdpbGwgYmUgdGhlcmUgd2hlbiB0aGVpcnMgd2ls bCBiZSBqdXN0IGEgZm9yZ290dGVuIG1lbW9yeSB3ZSBzaGFsbA0KcmVqb2ljZS4NCkJ5ZQ0KTHVj YQ0K |
From: TiMax <ma...@em...> - 2003-06-04 06:31:39
|
Zoom write me about this post in Portalzine, i think now is time= to explain very good to all people differences from Postnuke, so now me and Zoom work to write this document,= maybe later we send proof of this document here so you can add your suggestion before we publish= it. Feel free to go in Portalzine site and explain a little to Magicx= to check before write .... I just check that from September 2002 we start from Postnuke= 714-722 and have add lot of functions to eNvolution, Postnuke add only some little fix's ....... TiMax p.s. I m in test with some hacks and i think now envolution.com= is much fast ----------------------------------------- Hi Max, I found this post over at portalzine.de http://www.portalzine.de/XForum-tid2184.html Of specific interest is the post made by A;exander Graef so= you'll need to scroll down a bit to see his post. I'll quote it hear in case he decides to edit his posting: ---Begin Quote--- MagicX Administrator posted on 3/6/2003 at 11:54 Well I agree that envolution doesnt really provide much more functionality as postnuke. Postnuke allows the use of the native= theme system, autotheme, Xanthia or even use encompass (which is the= basis Xanthia is running on). The current user/developer community for postnuke is much bigger= then the one for envolution. And I dont see many developers jumping on= the envolution train, but in the end its a question of flavor.= Envolution decided to go their own way, which is an open source process that= is quiet popular in the open source scene (well might happen more= often with postnuke [image] ) I have been running postnuke for a long time and it always was= the basis of portalzine. I never had any performance issues. Like said= above, it all depends on your server resources. The more queries you= execute, the more power your server needs to provide. Xoops is another alternative, that provides a good stable and= fast system that can be easily erxtended and maintained. Because of= the OOP character of the system, resources are reused and execution is= optimized quiet nicely. They use a template system aswell. Well Phpnuke wouldnt be my system of choice , there are to many= things happening besides the development , which seem to center around= one person. He progressed nicely concerning features, but seeing= postnuke running completely on the new api soon, phpnuke will loose= ground. Api structure compliant modules are executed much faster and allow= the resuse of functionality across the system. Again postnuke will= allow both module types to run and allows to level your performance= better then phpnuke. Besides , the latest phpnuke release includes a= native forum, which i think slows down the core development even more.= Modules should be handled seperately from the system and should grow individually (not thinking of security issues). Hope that helps a bit. MagicX ---End Quote--- I will explain in detail how, in this post, MagicX made false= statements and perpetuates the "us versus them" mentality that some people= like to keep prominant in the "nuke" community. First paragraph: MagicX states that Envolution doesn't provide much more= functionality than PostNuke. The fact is there are glaring differences in= PostNuke and Envolution. While it is true Envolution forked from the .714= PostNuke codebase it has and still is continuing to evolve into it's own= unique code base. Just to point out the obvious MagicX did say= "Envolution doesn't provide much more functionality than PostNuke" quote,= unquote. What this means is that Envolution does provide MORE= functionality than PostNuke, juts not as much as he would prefer I guess! But I= believe his intention is to lead people to believe that Envolution is behind PostNuke in features, stability, and usfullness. Unfortunately= his FUD spreading is still based on old wounds he has from being caught= red handed stealing code and claiming it as his own original code= from true opensource and free software developers. Shame on Alexander for= at least not being a man about it and accept that the world exists outside= of portalzine and PostNuke. Second Paragraph: MagicX states that the Envolution developer community is much= smaller than PostNuke's developer community. Where has MagicX been? In= fact Envolution's developer community is larger than the current= PostNuke developer community. Our developers just don't project it's= presence like the old PostNuke developer team used to do. In fact= Envolution's official develoeper base is larger than PostNuke and Xoop's. Last= time I checked we had over 30 developers just from the English and= Italian Envolution commuinities. Add in the Asian sites, German sites,= and the new Spanish sites and I believe you'll find those numbers add up= ebven higher yet. I am also quite sure I've forgotten to mention some= other Envolution developer communities, and I apologize if I have. He also sates that, "And I dont see many developers jumping on= the envolution train, but in the end its a question of flavor..."= This is humerous. In fact since April 22, 2003 the English speaking= developer representation has increased by 6 new developers. In fact just= today we have added one more volunteer who wishes to increase the= documentation quality and library! Now ask MagicX how many developers have "jumped FROM the PostNuke= train" in the last year! I would imagine the numbers would add up to= over 100. Including MagicX himself. I know he claims to have left for time= and personal reasons..but fact is he left because he and Neo were= trying to force their wishes on the PostNuke community without regard to= what the community wanted or needs. Paragraph Three: MagicX explains that he is biased toward PostNuke. No kidding?= Maybe that explains why he continually likes to put down the Envolution= CMS and community. Now what MagicX didn't tell you is that Envolution and it's= community has had a large impact on all nuke type CMS's. In fact Envolution= was, and still is, the only community to turn over it's development= and management to the community. We consistantly solicite our= community to get involved and we frequently ask for developers to join in and= take part. Instead of sitting back like pompous fools and wait for= developers to come to us, we seek them out. Why? Because we believe in true= open development for and by the community. Email any developer at Envolution and guess what happens? You= get emailed back! Now try to email one of the developers at= PostNuke, specifically the Project Leader and see what happens! I don't mind criticism about Envolution. It is not perfect. But= it is innovative, has features PostNuke does not have, stable, and has= even affected PostNuke to explore and adopt Xantha as a theme system= for thier next release. Xantha is a fork of Encompass which has been= used in Envolution and developed by Envoilution founders. MagicX hasn't a clue what's really going on in the CMS community= he claims to be part of and serve. In fact I wouldnt be surprised if= he has other motivations besides "helping" out the communty by offering= up this kind of inaccurate and misinformed information. Zoom |
From: Burke A. <bu...@di...> - 2003-06-02 17:41:11
|
There seem to be two places to get this right now. I don't see any reason why we should maintain these defines in two different places, especially a static file such as pnAPI.php. I suggest we move away from having these defined in the php file & only have the info available via the database. Currently, references to _PN_VERSION_NUM exist in: Stats module/index.php (line 462) Credits module/pnuser.php (lines: 76, 90, 104) The other two (_PN_VERSION_ID,_PN_VERSION_SUB) don't appear to ever get used. pnAPI defines: define('_PN_VERSION_NUM', "1.2"); define('_PN_VERSION_ID', "Envolution"); define('_PN_VERSION_SUB', "Michelangelo"); and database fields: /PNConfig Version_Num s:5:"1.2.0"; /PNConfig Version_ID s:10:"Envolution"; /PNConfig Version_Sub s:12:"Michelangelo"; The fields from the database are retrieved via: pnConfigGetVar('Version_Num') pnConfigGetVar('Version_ID') pnConfigGetVar('Version_Sub') |
From: Antonio L. <an...@al...> - 2003-06-02 08:36:06
|
At 01.32 02/06/2003 -0700, you wrote: >Envolution-devel -- confirmation of subscription -- request 952321 > >We have received a request from 80.180.254.6 for subscription of your >email address, <an...@al...>, to the >env...@li... mailing list. To confirm the >request, please send a message to >env...@li..., and either: > >- maintain the subject line as is (the reply's additional "Re:" is >ok), > >- or include the following line - and only the following line - in the >message body: > >confirm 952321 > >(Simply sending a 'reply' to this message should work from most email >interfaces, since that usually leaves the subject line in the right >form.) > >If you do not wish to subscribe to this list, please simply disregard >this message. Send questions to >env...@li.... ====================================== | - Antonio Laurienzo - | www.al69.it | an...@al... | tel ++39 041 5229 579 | fax ++39 041 2417 462 | "come e' terribile conoscere quando la | conoscenza non giova a chi la possiede" (anon.) ====================================== |
From: Stefan K. <Ste...@ga...> - 2003-06-02 07:16:28
|
@arden: [...] I would like to know if anyone else does not like the default fields = for user sign up. I even see them mapped out the same way here http://mike= spub.net/xaraya/index.php?module=3Droles&func=3Dregister&phase=3Dregisterfo= rm ...[...] I agree. We have to change the default and required fields to a minimum. = And all additional fields for registration must be up to site admin. [...] http://www.suteralaut.com/user.php?op=3Dregister&module=3DNS-NewUser = [...] Is this link a modified NS-NewUser-module? Or what do you want to say? I think we can change NS-NewUser so all other fields, except Short name = and passwort, can administer in the "User settings::Dynamic data" section. = There the admin can activate the fields for the registration form. I'm not = sure, if we need it on installation time. [...] It would be very simple to change these fields in the install = routine. I don't know what other modules reference the data structure = other than NS-NewUser, NS-User and perhaps the messaging system. [...] Do you have a ready-to-use solution for testing? Perhaps you can help us = to realize it... WindMeUp |
From: Stefan K. <Ste...@ga...> - 2003-06-02 06:58:15
|
@arden: [...] I put the personal avatar hack in there but can't get the javascript correct. I think would be nice feature for = eNvolution. Maybe need function after uid is added to the database then = tie it in with moderation screen. [...] Our philosophie was, to add this feature only for registered users. They = can change after login there own settings (and include an uploaded = personal avatar). At registration time it is not sure, if site admin want to give this user = permantly membership. But I will look, if we can add this feature for NS-NewUser-module, too. [...] So out of all this I ask why does the install routine still try and = upgrade .64 mutant releases and others??? When do we draw the line. I = just finished upgrading my eNvo1.1 multi-site portals by hand to eNvo1.2 = standards and it was big big job. Many changes yes many. [...] Yes I agree. The upgrade routines are under progress. [...] I think the install routine should be the focal point for creating = installation wizards. I have and want to upload to cvs some scripts with = much reiteration and instantiation of the tables to install many sites, = stories and also change many stories and settings based on the install = routine. [...] Nice to here. Are you ready for an upload to see and test these scripts? [...] To me it seems like a good idea if a user could choose options he = would like activated before or during the install routine. If it were = possible to even configure your default stories, blocks, modules and = themes some way during the install for say corporate, personal or = organization. [...] We discussed it. But it is not an easy job to do so. But if you like, you = can code such an upgrade and additonal routine as a sub-project. [...] Also I promote eNvolution here recently: http://slideml.org/files/slidesets/495/title.html little presentation of = http://oscom.org 3rd annual conference [...] Thanks. Great job. We need more promotions like that to bring eNvolution = in front ;) WindMeUp |
From: Stefan K. <Ste...@ga...> - 2003-06-02 06:14:49
|
@GatoNero: phpGroupware is good to find out which functions are possible and a = must-have for a grouping ware solution. But it is not compatible with = eNvo. It is not possible to integrate it into eNvo as module. So we have to find and code our own solution. Possibilties are: 1. modified Addressbook 2. modified Postcalendar (or Calzone) 3. for projects: ToDo (or DQ HelpDesk) 4. a better interaction between all other modules I have coded some parts for a complete solution for our intranet. But not = all is perfect. We will see.... WindMeUp |
From: Stefan K. <Ste...@ga...> - 2003-06-02 06:01:52
|
I agree with GatoNero. He can manage this new site perfectly in addition = to our german eNvo site. So give him this new task. WindMeUp |
From: <Chr...@t-...> - 2003-06-01 07:48:53
|
TiMax - Envolution wrote: >So i need someone to help us to manage this site, to install modules, blocks and tranlsate little news in German and > > > Could be my job ;-) -- mailto:chr...@t-... personal: http://www.christoph-schwaeppe.de CMS: http://www.envolution.de ICQ: 174676647 jabber gat...@am... |
From: TiMax - E. <web...@en...> - 2003-05-31 22:20:14
|
We are ready to start with envoaddon and add modules, blocks= addons etc ... For French language Petermey help us For English language eLgie help us So i need someone to help us to manage this site, to install= modules, blocks and tranlsate little news in German and maybe in Italian language TiMax |
From: TiMax - E. <web...@en...> - 2003-05-31 18:53:52
|
who are you ? please add your signature thanks TiMax On Sat, 31 May 2003 13:56:42 -0400, Envo @ Insight wrote: > I don't see a real need for those fields either. I would like= to see the > default fields reduced and folks that want to use them could= add them via > the dynamic data fields. This would probably generate a= requirement to make > changes to some of the modules that utilize those fields or at= least an > addition to the code that ignored those functions if the data= field wasn't > defined. > > > ----- Original Message ----- > From: "Arden Wiebe" <ar...@li...> > To: "eNvolution-devel"= <env...@li...> > Sent: Saturday, May 31, 2003 4:15 AM > Subject: [Envolution-devel] NS-NewUser > > > > I would like to know if anyone else does not like the= default fields for > > user sign up. I even see them mapped out the same way here > > > = http://mikespub.net/xaraya/index.php?module=3Droles&func=3Dregister&= phase=3Dregisterform > > > > Now from a professional sense I have absolutely no *&(*&^%= use > > whatsoever for an aol, msnm, a one line location field or= otherwise. > > Now take those to a client and they chuckle. > > > > One of these days I'm hoping we see some changes to these= fields to > > something more standardized toward a business model. Then= to add other > > fields with dynamic data makes more sense. > > > > Even this as well done as it is does not make much business= sense. > > > >= http://www.suteralaut.com/user.php?op=3Dregister&module=3DNS-NewUser= > > > > Scattered throughout the forums are people unhappy with the= fields and > > always wanting to change them. I submit to you that if they= were more > > normalized at the outset that there would be less problems. = Why should > > a user suddenly after a month of using his system have to= try and hack > > dynamic data? > > > > It would be very simple to change these fields in the= install routine. > > I don't know what other modules reference the data structure= other than > > NS-NewUser, NS-User and perhaps the messaging system. > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: eBay > > Get office equipment for less on eBay! > > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > > _______________________________________________ > > Envolution-devel mailing list > > Env...@li... > >= https://lists.sourceforge.net/lists/listinfo/envolution-devel > > > ------------------------------------------------------- > This SF.net email is sponsored by: eBay > Get office equipment for less on eBay! > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Envolution-devel mailing list > Env...@li... > https://lists.sourceforge.net/lists/listinfo/envolution-devel |
From: Envo @ I. <en...@in...> - 2003-05-31 17:52:28
|
I don't see a real need for those fields either. I would like to see the default fields reduced and folks that want to use them could add them via the dynamic data fields. This would probably generate a requirement to make changes to some of the modules that utilize those fields or at least an addition to the code that ignored those functions if the data field wasn't defined. ----- Original Message ----- From: "Arden Wiebe" <ar...@li...> To: "eNvolution-devel" <env...@li...> Sent: Saturday, May 31, 2003 4:15 AM Subject: [Envolution-devel] NS-NewUser > I would like to know if anyone else does not like the default fields for > user sign up. I even see them mapped out the same way here > http://mikespub.net/xaraya/index.php?module=roles&func=register&phase=registerform > > Now from a professional sense I have absolutely no *&(*&^% use > whatsoever for an aol, msnm, a one line location field or otherwise. > Now take those to a client and they chuckle. > > One of these days I'm hoping we see some changes to these fields to > something more standardized toward a business model. Then to add other > fields with dynamic data makes more sense. > > Even this as well done as it is does not make much business sense. > > http://www.suteralaut.com/user.php?op=register&module=NS-NewUser > > Scattered throughout the forums are people unhappy with the fields and > always wanting to change them. I submit to you that if they were more > normalized at the outset that there would be less problems. Why should > a user suddenly after a month of using his system have to try and hack > dynamic data? > > It would be very simple to change these fields in the install routine. > I don't know what other modules reference the data structure other than > NS-NewUser, NS-User and perhaps the messaging system. > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: eBay > Get office equipment for less on eBay! > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Envolution-devel mailing list > Env...@li... > https://lists.sourceforge.net/lists/listinfo/envolution-devel > |
From: Arden W. <ar...@li...> - 2003-05-31 16:42:19
|
I have no write access to the tree :( On Fri, 2003-05-30 at 18:45, Christoph Schwaeppe wrote: > Arden Wiebe wrote: > > >Okay these next few days I learn better CVS skills. Right now I am > >using Cervista front end for Konqueror file manager. I can also use > >command line. > > > > > Me too, and it works pretty nice, Cervisia and command line. > > Your login messages are ok. You tried to commit some files > (NS-Mulltisites) which hasn't been added to CVS before, This is > necassary for the version management. So please use the "Add to > Repository" function from the File-menu or from the context. > > Here is a very nice link to CVS documentation > http://cvsbook.red-bean.com/, it's a very fine docu from some of the CVS > gurus (from gurus to guru ;-) ) > > -- > mailto:chr...@t-... > personal: http://www.christoph-schwaeppe.de > CMS: http://www.envolution.de > ICQ: 174676647 > jabber gat...@am... > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: eBay > Get office equipment for less on eBay! > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Envolution-devel mailing list > Env...@li... > https://lists.sourceforge.net/lists/listinfo/envolution-devel -- Add some eLGie to your eNvironment. http://www.Swingerz.ca http://www.LinuxGuru.ca http://www.WorkWanted.ca |