Menu
▾
▴
perfparse-devel-int
|
From: Ben C. <BCl...@pe...> - 2004-11-23 08:39:58
|
Garry, One thing that Yves talked about was a tiki system. Have you ever set one up? This could be really useful for, as Yves suggested, an FAQ and a private document of agreed bits. sf.net give access to the database, but not looked any further at it... Ben Cook, Garry wrote: > Sorry, I haven't been following this thread very closely, I'll have to > go back and read it all the way through. However, to add a page, this is > not too hard. I'm sure Flo can do it, as he has been working with PHP a > bit, the pages are written in PHP. Ben has been maintaining them in my > absence as well, so he could probably handle this too. If you would > like, I can probably spare a few minutes to get this done today. > However, the name "development crypt" sounds a little, um, cryptic. > Maybe we can find something to describe it a little better? > > Garry W. Cook, CCNA > Network Infrastructure Manager > MACTEC, Inc. - http://www.mactec.com/ > 303.273.5050 (Office) - 720.220.1862 (Mobile) > > Yves wrote: > >>OK, good. >> >>Ben or Garry, could you make a page "development crypt" and >>put this and other good >>stuff that we sometimes write in mails and then forget ? >> >>------------------------------------------------------------ >><h1>How to use Nightly CVS Tarball</h1> >><pre> >>One possibility would be to use the "Nightly CVS Tarball" >>from sf. This >>can be found at >>http://cvs.sourceforge.net/cvstarballs/perfparse-cvsroot.tar.bz2 >>This tarball is a complete cvs repository including all historical >>versions. This should work: >>- untar it >>- use "cvs -d/path/where/untared/perfparse checkout perfparse-phpgui" >> to get the latest revisions. >></pre> >>------------------------------------------------------------ >>If you have time, I also suggest a wiki. One for the user FAQ >>And one where we could easily write such things instead of >>downloading the file, edit it, upload. >> >>Thanks Flo for the tip :) >> >>Yves > > > |
|
From: Cook, G. <GW...@ma...> - 2004-11-29 15:43:58
|
I've not used a WIKI/TIKI, but I hear that they are not too difficult to setup. Think it requires a backend DB, although not positive. Like you mentioned below, sf.net will give access to MySQL, but I believe we need to make a formal request for this. Garry W. Cook, CCNA Network Infrastructure Manager MACTEC, Inc. - http://www.mactec.com/ 303.273.5050 (Office) - 720.220.1862 (Mobile) Ben Clewett wrote: > Garry, >=20 > One thing that Yves talked about was a tiki system. Have you ever set > one up? This could be really useful for, as Yves suggested, an FAQ > and a private document of agreed bits. sf.net give access to the > database, but not looked any further at it... >=20 > Ben >=20 > Cook, Garry wrote: >=20 >> Sorry, I haven't been following this thread very closely, I'll have >> to go back and read it all the way through. However, to add a page, >> this is not too hard. I'm sure Flo can do it, as he has been working >> with PHP a bit, the pages are written in PHP. Ben has been >> maintaining them in my absence as well, so he could probably handle >> this too. If you would like, I can probably spare a few minutes to >> get this done today. However, the name "development crypt" sounds a >> little, um, cryptic. Maybe we can find something to describe it a >> little better?=20 >>=20 >> Garry W. Cook, CCNA >> Network Infrastructure Manager >> MACTEC, Inc. - http://www.mactec.com/ >> 303.273.5050 (Office) - 720.220.1862 (Mobile) >>=20 >> Yves wrote: >>=20 >>> OK, good. >>>=20 >>> Ben or Garry, could you make a page "development crypt" and >>> put this and other good >>> stuff that we sometimes write in mails and then forget ? >>>=20 >>> ------------------------------------------------------------ >>> <h1>How to use Nightly CVS Tarball</h1> >>> <pre> >>> One possibility would be to use the "Nightly CVS Tarball" >>> from sf. This >>> can be found at >>> http://cvs.sourceforge.net/cvstarballs/perfparse-cvsroot.tar.bz2 >>> This tarball is a complete cvs repository including all historical >>> versions. This should work:=20 >>> - untar it >>> - use "cvs -d/path/where/untared/perfparse checkout >>> perfparse-phpgui" to get the latest revisions. >>> </pre> >>> ------------------------------------------------------------ >>> If you have time, I also suggest a wiki. One for the user FAQ >>> And one where we could easily write such things instead of >>> downloading the file, edit it, upload. >>>=20 >>> Thanks Flo for the tip :) >>>=20 >>> Yves |
|
From: Ben C. <BCl...@pe...> - 2004-11-29 16:28:45
|
Cook, Garry wrote: > I've not used a WIKI/TIKI, but I hear that they are not too difficult to > setup. Think it requires a backend DB, although not positive. Like you > mentioned below, sf.net will give access to MySQL, but I believe we need > to make a formal request for this. I will see what database we need, and what services sf.net offer. Tiki does use MySQL which I know sf offer. I just have to work out how :) I've not installed tiki before, so I'm in the dark as well. Some fun for the weekend maybe :) To all developers: What structure would you like to see in a wiki/tiki system? For my self I would like to see editable specifications of new work we are going to undertake. Where comments as well as actual changes can be made. Yves also mentioned a public FAQ, private edit. Now the software is gaining in ability, this sounds like an excellent idea. Thanks to Tim and Yves for finding and fixing a bug so quickly. Regards, Ben > > Garry W. Cook, CCNA > Network Infrastructure Manager > MACTEC, Inc. - http://www.mactec.com/ > 303.273.5050 (Office) - 720.220.1862 (Mobile) > > Ben Clewett wrote: > >>Garry, >> >>One thing that Yves talked about was a tiki system. Have you ever set >>one up? This could be really useful for, as Yves suggested, an FAQ >>and a private document of agreed bits. sf.net give access to the >>database, but not looked any further at it... >> >>Ben >> >>Cook, Garry wrote: >> >> >>>Sorry, I haven't been following this thread very closely, I'll have >>>to go back and read it all the way through. However, to add a page, >>>this is not too hard. I'm sure Flo can do it, as he has been working >>>with PHP a bit, the pages are written in PHP. Ben has been >>>maintaining them in my absence as well, so he could probably handle >>>this too. If you would like, I can probably spare a few minutes to >>>get this done today. However, the name "development crypt" sounds a >>>little, um, cryptic. Maybe we can find something to describe it a >>>little better? >>> >>>Garry W. Cook, CCNA >>>Network Infrastructure Manager >>>MACTEC, Inc. - http://www.mactec.com/ >>>303.273.5050 (Office) - 720.220.1862 (Mobile) >>> >>>Yves wrote: >>> >>> >>>>OK, good. >>>> >>>>Ben or Garry, could you make a page "development crypt" and >>>>put this and other good >>>>stuff that we sometimes write in mails and then forget ? >>>> >>>>------------------------------------------------------------ >>>><h1>How to use Nightly CVS Tarball</h1> >>>><pre> >>>>One possibility would be to use the "Nightly CVS Tarball" >>>>from sf. This >>>>can be found at >>>>http://cvs.sourceforge.net/cvstarballs/perfparse-cvsroot.tar.bz2 >>>>This tarball is a complete cvs repository including all historical >>>>versions. This should work: >>>>- untar it >>>>- use "cvs -d/path/where/untared/perfparse checkout >>>> perfparse-phpgui" to get the latest revisions. >>>></pre> >>>>------------------------------------------------------------ >>>>If you have time, I also suggest a wiki. One for the user FAQ >>>>And one where we could easily write such things instead of >>>>downloading the file, edit it, upload. >>>> >>>>Thanks Flo for the tip :) >>>> >>>>Yves > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Perfparse-devel-int mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int > |
|
From: Yves <yme...@pe...> - 2004-11-29 17:10:15
|
> What structure would you like to see in a wiki/tiki system? > > For my self I would like to see editable specifications of new work we > are going to undertake. Where comments as well as actual changes can b= e > made. Specifications, when there are some. Yes (I'm thinking about the next dat= abase schema for mysql, and API for modules that I will define soon). But don't take them as the reference. The reference is always the code : - create_mysql.sh for mysql database schema (Ben, do you have better idea= than that file ?) - storage.h for storage modules. But I like the idea to have a public draft for specifications. > Yves also mentioned a public FAQ, private edit. Now the software is > gaining in ability, this sounds like an excellent idea. have a look on that : http://www.squirrelmail.org/wiki/UserFAQ Answering the question at the beginning of this mail, I have 2 suggestion= s : - have one wiki with entries for the main stuff (spec drafts, faq, ...) - have one wiki per main stuff (one for spec drafts, one for faq, ...) I suggest one wiki because we can link some FAQ entries inside our drafts= ? btw, if you don't know what wiki to use, have a look on the wiki that squ= irrelmail uses, and have a look on what wikipedia uses. I don't know which is the best. > Thanks to Tim and Yves for finding and fixing a bug so quickly. Thanks to Tim : he noticed the problem, found the bug, well, yes, that's = me who found the bug, and he found the solution while I was actively searching for it = :) Yves --=20 - Homepage - http://ymettier.free.fr - http://www.logicacmg.com - - GPG key - http://ymettier.free.fr/gpg.txt - - Maitretarot - http://www.nongnu.org/maitretarot/ - - Perfparse - http://perfparse.sf.net/ - |
|
From: Flo G. <fl...@bi...> - 2004-11-29 22:16:55
|
Had a relaying problem right now so the mail was rejected - have to switch private mail to my own mailserver :-) So, i'm back now from basketball - how about a tiki tomorrow? Flo On Mon, 29 Nov 2004, Flo Gleixner wrote: > > > hey, just almost missed the wiki discussion :-) > > Since i'm a project admin of tikiwiki, i'd surely vote for tikiwiki. I also > have a server with root access and 500GB traffic fast ethernet connection > (100MBit), own dns server, mailserver, ... whatever one can do with a root > account. I'd be pleased to host a perfparse site (or part of it). I can > install can configure a tikiwiki in less than 10 mins :-) But at the momenet > i have to go to play basketball. I'll be back in 3-4 hours... > > Flo > > > On Mon, 29 Nov 2004, Yves wrote: > >> >>> What structure would you like to see in a wiki/tiki system? >>> >>> For my self I would like to see editable specifications of new work we >>> are going to undertake. Where comments as well as actual changes can be >>> made. >> >> Specifications, when there are some. Yes (I'm thinking about the next >> database schema >> for mysql, and API for modules that I will define soon). >> But don't take them as the reference. The reference is always the code : >> - create_mysql.sh for mysql database schema (Ben, do you have better idea >> than that file ?) >> - storage.h for storage modules. >> >> But I like the idea to have a public draft for specifications. >> >> >>> Yves also mentioned a public FAQ, private edit. Now the software is >>> gaining in ability, this sounds like an excellent idea. >> >> have a look on that : http://www.squirrelmail.org/wiki/UserFAQ >> >> Answering the question at the beginning of this mail, I have 2 suggestions >> : >> - have one wiki with entries for the main stuff (spec drafts, faq, ...) >> - have one wiki per main stuff (one for spec drafts, one for faq, ...) >> >> I suggest one wiki because we can link some FAQ entries inside our drafts >> ? >> >> btw, if you don't know what wiki to use, have a look on the wiki that >> squirrelmail uses, >> and have a look on what wikipedia uses. I don't know which is the best. >> >>> Thanks to Tim and Yves for finding and fixing a bug so quickly. >> >> Thanks to Tim : he noticed the problem, found the bug, well, yes, that's >> me who found >> the bug, and he found the solution while I was actively searching for it >> :) >> >> Yves >> >> -- >> - Homepage - http://ymettier.free.fr - http://www.logicacmg.com - >> - GPG key - http://ymettier.free.fr/gpg.txt - >> - Maitretarot - http://www.nongnu.org/maitretarot/ - >> - Perfparse - http://perfparse.sf.net/ - >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real users. >> Discover which products truly live up to the hype. Start reading now. >> http://productguide.itmanagersjournal.com/ >> _______________________________________________ >> Perfparse-devel-int mailing list >> Per...@li... >> https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int >> > |
|
From: Ben C. <BCl...@pe...> - 2004-11-30 09:37:25
|
Flo, I think this is an excellent idea! Thanks. I will arrange a domain name for this, something like wiki.perfparse.org. Can you work with this? If I look through email I think the main idea was specifications. There is one on the sf.net project page for deletion policies: http://sourceforge.net/docman/display_doc.php?docid=23729&group_id=109355 Another I emailed around for new database, will upload directly to wiki when possible :) Yves wrote: > Specifications, when there are some. Yes (I'm thinking about the next database schema > for mysql, and API for modules that I will define soon). > But don't take them as the reference. The reference is always the code : > - create_mysql.sh for mysql database schema (Ben, do you have better idea than that file ?) > - storage.h for storage modules. No I don't have a better idea. The file is to create the schema when using MySQL. (I took the name from Nagios version of the same so that users with both projects would find this familiar.) Have you a better idea? > Answering the question at the beginning of this mail, I have 2 suggestions : > - have one wiki with entries for the main stuff (spec drafts, faq, ...) > - have one wiki per main stuff (one for spec drafts, one for faq, ...) I would like to see one clean page for each specification. Keeps things simple and readable... (Like RFCs. It works for them :) The FAQ is a public entity and should therefore have it's own page to replace the current FAQ. Current I hope will be start of new: http://perfparse.sourceforge.net/faq.php Garry has also given us a good clear style for this FAQ which works with this main site, so I think we should try and maintain this if possible :) Have I missed anything? Ben Flo Gleixner wrote: > > Had a relaying problem right now so the mail was rejected - have to > switch private mail to my own mailserver :-) > > So, i'm back now from basketball - how about a tiki tomorrow? > > Flo > > > On Mon, 29 Nov 2004, Flo Gleixner wrote: > >> >> >> hey, just almost missed the wiki discussion :-) >> >> Since i'm a project admin of tikiwiki, i'd surely vote for tikiwiki. I >> also have a server with root access and 500GB traffic fast ethernet >> connection (100MBit), own dns server, mailserver, ... whatever one can >> do with a root account. I'd be pleased to host a perfparse site (or >> part of it). I can install can configure a tikiwiki in less than 10 >> mins :-) But at the momenet i have to go to play basketball. I'll be >> back in 3-4 hours... >> >> Flo >> >> >> On Mon, 29 Nov 2004, Yves wrote: >> >>> >>>> What structure would you like to see in a wiki/tiki system? >>>> >>>> For my self I would like to see editable specifications of new work we >>>> are going to undertake. Where comments as well as actual changes >>>> can be >>>> made. >>> >>> >>> Specifications, when there are some. Yes (I'm thinking about the next >>> database schema >>> for mysql, and API for modules that I will define soon). >>> But don't take them as the reference. The reference is always the code : >>> - create_mysql.sh for mysql database schema (Ben, do you have better >>> idea than that file ?) >>> - storage.h for storage modules. >>> >>> But I like the idea to have a public draft for specifications. >>> >>> >>>> Yves also mentioned a public FAQ, private edit. Now the software is >>>> gaining in ability, this sounds like an excellent idea. >>> >>> >>> have a look on that : http://www.squirrelmail.org/wiki/UserFAQ >>> >>> Answering the question at the beginning of this mail, I have 2 >>> suggestions : >>> - have one wiki with entries for the main stuff (spec drafts, faq, ...) >>> - have one wiki per main stuff (one for spec drafts, one for faq, ...) >>> >>> I suggest one wiki because we can link some FAQ entries inside our >>> drafts ? >>> >>> btw, if you don't know what wiki to use, have a look on the wiki that >>> squirrelmail uses, >>> and have a look on what wikipedia uses. I don't know which is the best. >>> >>>> Thanks to Tim and Yves for finding and fixing a bug so quickly. >>> >>> >>> Thanks to Tim : he noticed the problem, found the bug, well, yes, >>> that's me who found >>> the bug, and he found the solution while I was actively searching for >>> it :) >>> >>> Yves >>> >>> -- >>> - Homepage - http://ymettier.free.fr - http://www.logicacmg.com - >>> - GPG key - http://ymettier.free.fr/gpg.txt - >>> - Maitretarot - http://www.nongnu.org/maitretarot/ - >>> - Perfparse - http://perfparse.sf.net/ - >>> >>> >>> >>> ------------------------------------------------------- >>> SF email is sponsored by - The IT Product Guide >>> Read honest & candid reviews on hundreds of IT Products from real users. >>> Discover which products truly live up to the hype. Start reading now. >>> http://productguide.itmanagersjournal.com/ >>> _______________________________________________ >>> Perfparse-devel-int mailing list >>> Per...@li... >>> https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int >>> >> > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Perfparse-devel-int mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int > |
|
From: Flo G. <fl...@bi...> - 2004-11-30 12:21:43
|
Hi Ben, yes, The IP of my server is 62.75.177.180. I'll prepare all for a tiki install. Flo On Tue, 30 Nov 2004, Ben Clewett wrote: > Flo, > > I think this is an excellent idea! Thanks. > > I will arrange a domain name for this, something like wiki.perfparse.org. > Can you work with this? > > If I look through email I think the main idea was specifications. There is > one on the sf.net project page for deletion policies: > > http://sourceforge.net/docman/display_doc.php?docid=23729&group_id=109355 > > Another I emailed around for new database, will upload directly to wiki when > possible :) > > Yves wrote: >> Specifications, when there are some. Yes (I'm thinking about the next >> database schema >> for mysql, and API for modules that I will define soon). >> But don't take them as the reference. The reference is always the code : >> - create_mysql.sh for mysql database schema (Ben, do you have better idea >> than that file ?) >> - storage.h for storage modules. > > No I don't have a better idea. The file is to create the schema when using > MySQL. (I took the name from Nagios version of the same so that users with > both projects would find this familiar.) Have you a better idea? > >> Answering the question at the beginning of this mail, I have 2 suggestions >> : >> - have one wiki with entries for the main stuff (spec drafts, faq, ...) >> - have one wiki per main stuff (one for spec drafts, one for faq, ...) > > I would like to see one clean page for each specification. Keeps things > simple and readable... (Like RFCs. It works for them :) > > The FAQ is a public entity and should therefore have it's own page to replace > the current FAQ. Current I hope will be start of new: > > http://perfparse.sourceforge.net/faq.php > > Garry has also given us a good clear style for this FAQ which works with this > main site, so I think we should try and maintain this if possible :) > > Have I missed anything? > > Ben > > > > > Flo Gleixner wrote: >> >> Had a relaying problem right now so the mail was rejected - have to >> switch private mail to my own mailserver :-) >> >> So, i'm back now from basketball - how about a tiki tomorrow? >> >> Flo >> >> >> On Mon, 29 Nov 2004, Flo Gleixner wrote: >> >>> >>> >>> hey, just almost missed the wiki discussion :-) >>> >>> Since i'm a project admin of tikiwiki, i'd surely vote for tikiwiki. I >>> also have a server with root access and 500GB traffic fast ethernet >>> connection (100MBit), own dns server, mailserver, ... whatever one can >>> do with a root account. I'd be pleased to host a perfparse site (or part >>> of it). I can install can configure a tikiwiki in less than 10 mins :-) >>> But at the momenet i have to go to play basketball. I'll be back in 3-4 >>> hours... >>> >>> Flo >>> >>> >>> On Mon, 29 Nov 2004, Yves wrote: >>> >>>> >>>>> What structure would you like to see in a wiki/tiki system? >>>>> >>>>> For my self I would like to see editable specifications of new work >>>>> we >>>>> are going to undertake. Where comments as well as actual changes >>>>> can be >>>>> made. >>>> >>>> >>>> Specifications, when there are some. Yes (I'm thinking about the next >>>> database schema >>>> for mysql, and API for modules that I will define soon). >>>> But don't take them as the reference. The reference is always the code >>>> : >>>> - create_mysql.sh for mysql database schema (Ben, do you have better >>>> idea than that file ?) >>>> - storage.h for storage modules. >>>> >>>> But I like the idea to have a public draft for specifications. >>>> >>>> >>>>> Yves also mentioned a public FAQ, private edit. Now the software is >>>>> gaining in ability, this sounds like an excellent idea. >>>> >>>> >>>> have a look on that : http://www.squirrelmail.org/wiki/UserFAQ >>>> >>>> Answering the question at the beginning of this mail, I have 2 >>>> suggestions : >>>> - have one wiki with entries for the main stuff (spec drafts, faq, >>>> ...) >>>> - have one wiki per main stuff (one for spec drafts, one for faq, ...) >>>> >>>> I suggest one wiki because we can link some FAQ entries inside our >>>> drafts ? >>>> >>>> btw, if you don't know what wiki to use, have a look on the wiki that >>>> squirrelmail uses, >>>> and have a look on what wikipedia uses. I don't know which is the >>>> best. >>>> >>>>> Thanks to Tim and Yves for finding and fixing a bug so quickly. >>>> >>>> >>>> Thanks to Tim : he noticed the problem, found the bug, well, yes, >>>> that's me who found >>>> the bug, and he found the solution while I was actively searching for >>>> it :) >>>> >>>> Yves >>>> >>>> -- >>>> - Homepage - http://ymettier.free.fr - http://www.logicacmg.com - >>>> - GPG key - http://ymettier.free.fr/gpg.txt - >>>> - Maitretarot - http://www.nongnu.org/maitretarot/ - >>>> - Perfparse - http://perfparse.sf.net/ - >>>> >>>> >>>> >>>> ------------------------------------------------------- >>>> SF email is sponsored by - The IT Product Guide >>>> Read honest & candid reviews on hundreds of IT Products from real >>>> users. >>>> Discover which products truly live up to the hype. Start reading now. >>>> http://productguide.itmanagersjournal.com/ >>>> _______________________________________________ >>>> Perfparse-devel-int mailing list >>>> Per...@li... >>>> https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int >>>> >>> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real users. >> Discover which products truly live up to the hype. Start reading now. >> http://productguide.itmanagersjournal.com/ >> _______________________________________________ >> Perfparse-devel-int mailing list >> Per...@li... >> https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int >> > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Perfparse-devel-int mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int > |
|
From: Ben C. <BCl...@pe...> - 2004-11-30 13:44:04
|
Flo, The perfparse domain is kindly donated to us by Jeff Scott. I am in contact with him about changes to the new DNS. I look forward to seeing the tiki! Ben Flo Gleixner wrote: > > Hi Ben, > > yes, The IP of my server is 62.75.177.180. I'll prepare all for a tiki > install. > > Flo > > On Tue, 30 Nov 2004, Ben Clewett wrote: > >> Flo, >> >> I think this is an excellent idea! Thanks. >> >> I will arrange a domain name for this, something like >> wiki.perfparse.org. Can you work with this? >> >> If I look through email I think the main idea was specifications. >> There is one on the sf.net project page for deletion policies: >> >> http://sourceforge.net/docman/display_doc.php?docid=23729&group_id=109355 >> >> Another I emailed around for new database, will upload directly to >> wiki when possible :) >> >> Yves wrote: >> >>> Specifications, when there are some. Yes (I'm thinking about the next >>> database schema >>> for mysql, and API for modules that I will define soon). >>> But don't take them as the reference. The reference is always the code : >>> - create_mysql.sh for mysql database schema (Ben, do you have better >>> idea than that file ?) >>> - storage.h for storage modules. >> >> >> No I don't have a better idea. The file is to create the schema when >> using MySQL. (I took the name from Nagios version of the same so that >> users with both projects would find this familiar.) Have you a better >> idea? >> >>> Answering the question at the beginning of this mail, I have 2 >>> suggestions : >>> - have one wiki with entries for the main stuff (spec drafts, faq, ...) >>> - have one wiki per main stuff (one for spec drafts, one for faq, ...) >> >> >> I would like to see one clean page for each specification. Keeps >> things simple and readable... (Like RFCs. It works for them :) >> >> The FAQ is a public entity and should therefore have it's own page to >> replace the current FAQ. Current I hope will be start of new: >> >> http://perfparse.sourceforge.net/faq.php >> >> Garry has also given us a good clear style for this FAQ which works >> with this main site, so I think we should try and maintain this if >> possible :) >> >> Have I missed anything? >> >> Ben >> >> >> >> >> Flo Gleixner wrote: >> >>> >>> Had a relaying problem right now so the mail was rejected - have to >>> switch private mail to my own mailserver :-) >>> >>> So, i'm back now from basketball - how about a tiki tomorrow? >>> >>> Flo >>> >>> >>> On Mon, 29 Nov 2004, Flo Gleixner wrote: >>> >>>> >>>> >>>> hey, just almost missed the wiki discussion :-) >>>> >>>> Since i'm a project admin of tikiwiki, i'd surely vote for tikiwiki. >>>> I also have a server with root access and 500GB traffic fast >>>> ethernet connection (100MBit), own dns server, mailserver, ... >>>> whatever one can do with a root account. I'd be pleased to host a >>>> perfparse site (or part of it). I can install can configure a >>>> tikiwiki in less than 10 mins :-) But at the momenet i have to go to >>>> play basketball. I'll be back in 3-4 hours... >>>> >>>> Flo >>>> >>>> >>>> On Mon, 29 Nov 2004, Yves wrote: >>>> >>>>> >>>>>> What structure would you like to see in a wiki/tiki system? >>>>>> >>>>>> For my self I would like to see editable specifications of new >>>>>> work we >>>>>> are going to undertake. Where comments as well as actual changes >>>>>> can be >>>>>> made. >>>>> >>>>> >>>>> >>>>> Specifications, when there are some. Yes (I'm thinking about the >>>>> next database schema >>>>> for mysql, and API for modules that I will define soon). >>>>> But don't take them as the reference. The reference is always the >>>>> code : >>>>> - create_mysql.sh for mysql database schema (Ben, do you have >>>>> better idea than that file ?) >>>>> - storage.h for storage modules. >>>>> >>>>> But I like the idea to have a public draft for specifications. >>>>> >>>>> >>>>>> Yves also mentioned a public FAQ, private edit. Now the software is >>>>>> gaining in ability, this sounds like an excellent idea. >>>>> >>>>> >>>>> >>>>> have a look on that : http://www.squirrelmail.org/wiki/UserFAQ >>>>> >>>>> Answering the question at the beginning of this mail, I have 2 >>>>> suggestions : >>>>> - have one wiki with entries for the main stuff (spec drafts, faq, >>>>> ...) >>>>> - have one wiki per main stuff (one for spec drafts, one for faq, ...) >>>>> >>>>> I suggest one wiki because we can link some FAQ entries inside our >>>>> drafts ? >>>>> >>>>> btw, if you don't know what wiki to use, have a look on the wiki >>>>> that squirrelmail uses, >>>>> and have a look on what wikipedia uses. I don't know which is the >>>>> best. >>>>> >>>>>> Thanks to Tim and Yves for finding and fixing a bug so quickly. >>>>> >>>>> >>>>> >>>>> Thanks to Tim : he noticed the problem, found the bug, well, yes, >>>>> that's me who found >>>>> the bug, and he found the solution while I was actively searching >>>>> for it :) >>>>> >>>>> Yves >>>>> >>>>> -- >>>>> - Homepage - http://ymettier.free.fr - http://www.logicacmg.com - >>>>> - GPG key - http://ymettier.free.fr/gpg.txt - >>>>> - Maitretarot - http://www.nongnu.org/maitretarot/ - >>>>> - Perfparse - http://perfparse.sf.net/ - >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------- >>>>> SF email is sponsored by - The IT Product Guide >>>>> Read honest & candid reviews on hundreds of IT Products from real >>>>> users. >>>>> Discover which products truly live up to the hype. Start reading now. >>>>> http://productguide.itmanagersjournal.com/ >>>>> _______________________________________________ >>>>> Perfparse-devel-int mailing list >>>>> Per...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int >>>>> >>>> >>> >>> >>> ------------------------------------------------------- >>> SF email is sponsored by - The IT Product Guide >>> Read honest & candid reviews on hundreds of IT Products from real users. >>> Discover which products truly live up to the hype. Start reading now. >>> http://productguide.itmanagersjournal.com/ >>> _______________________________________________ >>> Perfparse-devel-int mailing list >>> Per...@li... >>> https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int >>> >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real users. >> Discover which products truly live up to the hype. Start reading now. >> http://productguide.itmanagersjournal.com/ >> _______________________________________________ >> Perfparse-devel-int mailing list >> Per...@li... >> https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int >> > |
|
From: Flo G. <fl...@bi...> - 2004-11-30 15:09:07
|
Hi, if you edit your local /etc/hosts and add the line 62.75.177.180 wiki.perfparse.org you can start to test tikiwiki. I did some configs. If you have registered, i can give the core team admin permissions. tikiwiki is somewhat overpowered, but you can switch on/off almost everything. At the moment anonymous users have only read permissions except submitting faq's for further review. Registred users may edit/create pages, blogs image galleries (do we need them?) ... Core team get full admin permissions. Flo On Tue, 30 Nov 2004, Ben Clewett wrote: > Flo, > > The perfparse domain is kindly donated to us by Jeff Scott. I am in contact > with him about changes to the new DNS. > > I look forward to seeing the tiki! > > Ben > > Flo Gleixner wrote: > >> >> Hi Ben, >> >> yes, The IP of my server is 62.75.177.180. I'll prepare all for a tiki >> install. >> >> Flo >> >> On Tue, 30 Nov 2004, Ben Clewett wrote: >> >>> Flo, >>> >>> I think this is an excellent idea! Thanks. >>> >>> I will arrange a domain name for this, something like >>> wiki.perfparse.org. Can you work with this? >>> >>> If I look through email I think the main idea was specifications. There >>> is one on the sf.net project page for deletion policies: >>> >>> http://sourceforge.net/docman/display_doc.php?docid=23729&group_id=109355 >>> >>> Another I emailed around for new database, will upload directly to wiki >>> when possible :) >>> >>> Yves wrote: >>> >>>> Specifications, when there are some. Yes (I'm thinking about the next >>>> database schema >>>> for mysql, and API for modules that I will define soon). >>>> But don't take them as the reference. The reference is always the code >>>> : >>>> - create_mysql.sh for mysql database schema (Ben, do you have better >>>> idea than that file ?) >>>> - storage.h for storage modules. >>> >>> >>> No I don't have a better idea. The file is to create the schema when >>> using MySQL. (I took the name from Nagios version of the same so that >>> users with both projects would find this familiar.) Have you a better >>> idea? >>> >>>> Answering the question at the beginning of this mail, I have 2 >>>> suggestions : >>>> - have one wiki with entries for the main stuff (spec drafts, faq, >>>> ...) >>>> - have one wiki per main stuff (one for spec drafts, one for faq, ...) >>> >>> >>> I would like to see one clean page for each specification. Keeps things >>> simple and readable... (Like RFCs. It works for them :) >>> >>> The FAQ is a public entity and should therefore have it's own page to >>> replace the current FAQ. Current I hope will be start of new: >>> >>> http://perfparse.sourceforge.net/faq.php >>> >>> Garry has also given us a good clear style for this FAQ which works with >>> this main site, so I think we should try and maintain this if possible >>> :) >>> >>> Have I missed anything? >>> >>> Ben >>> >>> >>> >>> >>> Flo Gleixner wrote: >>> >>>> >>>> Had a relaying problem right now so the mail was rejected - have to >>>> switch private mail to my own mailserver :-) >>>> >>>> So, i'm back now from basketball - how about a tiki tomorrow? >>>> >>>> Flo >>>> >>>> >>>> On Mon, 29 Nov 2004, Flo Gleixner wrote: >>>> >>>>> >>>>> >>>>> hey, just almost missed the wiki discussion :-) >>>>> >>>>> Since i'm a project admin of tikiwiki, i'd surely vote for tikiwiki. >>>>> I also have a server with root access and 500GB traffic fast >>>>> ethernet connection (100MBit), own dns server, mailserver, ... >>>>> whatever one can do with a root account. I'd be pleased to host a >>>>> perfparse site (or part of it). I can install can configure a >>>>> tikiwiki in less than 10 mins :-) But at the momenet i have to go to >>>>> play basketball. I'll be back in 3-4 hours... >>>>> >>>>> Flo >>>>> >>>>> >>>>> On Mon, 29 Nov 2004, Yves wrote: >>>>> >>>>>> >>>>>>> What structure would you like to see in a wiki/tiki system? >>>>>>> >>>>>>> For my self I would like to see editable specifications of new >>>>>>> work we >>>>>>> are going to undertake. Where comments as well as actual >>>>>>> changes can be >>>>>>> made. >>>>>> >>>>>> >>>>>> >>>>>> Specifications, when there are some. Yes (I'm thinking about the >>>>>> next database schema >>>>>> for mysql, and API for modules that I will define soon). >>>>>> But don't take them as the reference. The reference is always the >>>>>> code : >>>>>> - create_mysql.sh for mysql database schema (Ben, do you have >>>>>> better idea than that file ?) >>>>>> - storage.h for storage modules. >>>>>> >>>>>> But I like the idea to have a public draft for specifications. >>>>>> >>>>>> >>>>>>> Yves also mentioned a public FAQ, private edit. Now the >>>>>>> software is >>>>>>> gaining in ability, this sounds like an excellent idea. >>>>>> >>>>>> >>>>>> >>>>>> have a look on that : http://www.squirrelmail.org/wiki/UserFAQ >>>>>> >>>>>> Answering the question at the beginning of this mail, I have 2 >>>>>> suggestions : >>>>>> - have one wiki with entries for the main stuff (spec drafts, faq, >>>>>> ...) >>>>>> - have one wiki per main stuff (one for spec drafts, one for faq, >>>>>> ...) >>>>>> >>>>>> I suggest one wiki because we can link some FAQ entries inside our >>>>>> drafts ? >>>>>> >>>>>> btw, if you don't know what wiki to use, have a look on the wiki >>>>>> that squirrelmail uses, >>>>>> and have a look on what wikipedia uses. I don't know which is the >>>>>> best. >>>>>> >>>>>>> Thanks to Tim and Yves for finding and fixing a bug so quickly. >>>>>> >>>>>> >>>>>> >>>>>> Thanks to Tim : he noticed the problem, found the bug, well, yes, >>>>>> that's me who found >>>>>> the bug, and he found the solution while I was actively searching >>>>>> for it :) >>>>>> >>>>>> Yves >>>>>> >>>>>> -- >>>>>> - Homepage - http://ymettier.free.fr - http://www.logicacmg.com >>>>>> - >>>>>> - GPG key - http://ymettier.free.fr/gpg.txt >>>>>> - >>>>>> - Maitretarot - http://www.nongnu.org/maitretarot/ >>>>>> - >>>>>> - Perfparse - http://perfparse.sf.net/ >>>>>> - >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------- >>>>>> SF email is sponsored by - The IT Product Guide >>>>>> Read honest & candid reviews on hundreds of IT Products from real >>>>>> users. >>>>>> Discover which products truly live up to the hype. Start reading >>>>>> now. >>>>>> http://productguide.itmanagersjournal.com/ >>>>>> _______________________________________________ >>>>>> Perfparse-devel-int mailing list >>>>>> Per...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int >>>>>> >>>>> >>>> >>>> >>>> ------------------------------------------------------- >>>> SF email is sponsored by - The IT Product Guide >>>> Read honest & candid reviews on hundreds of IT Products from real >>>> users. >>>> Discover which products truly live up to the hype. Start reading now. >>>> http://productguide.itmanagersjournal.com/ >>>> _______________________________________________ >>>> Perfparse-devel-int mailing list >>>> Per...@li... >>>> https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int >>>> >>> >>> >>> >>> ------------------------------------------------------- >>> SF email is sponsored by - The IT Product Guide >>> Read honest & candid reviews on hundreds of IT Products from real users. >>> Discover which products truly live up to the hype. Start reading now. >>> http://productguide.itmanagersjournal.com/ >>> _______________________________________________ >>> Perfparse-devel-int mailing list >>> Per...@li... >>> https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int >>> >> > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Perfparse-devel-int mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int > |
|
From: Yves M. <yme...@li...> - 2004-11-30 15:51:32
|
I will wait that wiki.perfparse.org work here (I cannot edit /etc/hosts). Then, I think that registering should be enough for me :) I'm better at C coding... Yves > > Hi, > > if you edit your local /etc/hosts and add the line > 62.75.177.180 wiki.perfparse.org > > you can start to test tikiwiki. I did some configs. If you have > registered, i can give the core team admin permissions. > > tikiwiki is somewhat overpowered, but you can switch on/off almost > everything. > At the moment anonymous users have only read permissions except submitt= ing > faq's for further review. Registred users may edit/create pages, blogs > image galleries (do we need them?) ... Core team get full admin > permissions. > > Flo > > > On Tue, 30 Nov 2004, Ben Clewett wrote: > >> Flo, >> >> The perfparse domain is kindly donated to us by Jeff Scott. I am in c= ontact >> with him about changes to the new DNS. >> >> I look forward to seeing the tiki! >> >> Ben >> >> Flo Gleixner wrote: >> >>> >>> Hi Ben, >>> >>> yes, The IP of my server is 62.75.177.180. I'll prepare all for a tik= i >>> install. >>> >>> Flo >>> >>> On Tue, 30 Nov 2004, Ben Clewett wrote: >>> >>>> Flo, >>>> >>>> I think this is an excellent idea! Thanks. >>>> >>>> I will arrange a domain name for this, something like >>>> wiki.perfparse.org. Can you work with this? >>>> >>>> If I look through email I think the main idea was specifications. T= here >>>> is one on the sf.net project page for deletion policies: >>>> >>>> http://sourceforge.net/docman/display_doc.php?docid=3D23729&group_id= =3D109355 >>>> >>>> Another I emailed around for new database, will upload directly to w= iki >>>> when possible :) >>>> >>>> Yves wrote: >>>> >>>>> Specifications, when there are some. Yes (I'm thinking about the ne= xt >>>>> database schema >>>>> for mysql, and API for modules that I will define soon). >>>>> But don't take them as the reference. The reference is always the c= ode >>>>> : >>>>> - create_mysql.sh for mysql database schema (Ben, do you have bette= r >>>>> idea than that file ?) >>>>> - storage.h for storage modules. >>>> >>>> >>>> No I don't have a better idea. The file is to create the schema whe= n >>>> using MySQL. (I took the name from Nagios version of the same so th= at >>>> users with both projects would find this familiar.) Have you a bett= er >>>> idea? >>>> >>>>> Answering the question at the beginning of this mail, I have 2 >>>>> suggestions : >>>>> - have one wiki with entries for the main stuff (spec drafts, faq, >>>>> ...) >>>>> - have one wiki per main stuff (one for spec drafts, one for faq, .= ..) >>>> >>>> >>>> I would like to see one clean page for each specification. Keeps th= ings >>>> simple and readable... (Like RFCs. It works for them :) >>>> >>>> The FAQ is a public entity and should therefore have it's own page t= o >>>> replace the current FAQ. Current I hope will be start of new: >>>> >>>> http://perfparse.sourceforge.net/faq.php >>>> >>>> Garry has also given us a good clear style for this FAQ which works = with >>>> this main site, so I think we should try and maintain this if possib= le >>>> :) >>>> >>>> Have I missed anything? >>>> >>>> Ben >>>> >>>> >>>> >>>> >>>> Flo Gleixner wrote: >>>> >>>>> >>>>> Had a relaying problem right now so the mail was rejected - have t= o >>>>> switch private mail to my own mailserver :-) >>>>> >>>>> So, i'm back now from basketball - how about a tiki tomorrow? >>>>> >>>>> Flo >>>>> >>>>> >>>>> On Mon, 29 Nov 2004, Flo Gleixner wrote: >>>>> >>>>>> >>>>>> >>>>>> hey, just almost missed the wiki discussion :-) >>>>>> >>>>>> Since i'm a project admin of tikiwiki, i'd surely vote for tikiwik= i. >>>>>> I also have a server with root access and 500GB traffic fast >>>>>> ethernet connection (100MBit), own dns server, mailserver, ... >>>>>> whatever one can do with a root account. I'd be pleased to host a >>>>>> perfparse site (or part of it). I can install can configure a >>>>>> tikiwiki in less than 10 mins :-) But at the momenet i have to go = to >>>>>> play basketball. I'll be back in 3-4 hours... >>>>>> >>>>>> Flo >>>>>> >>>>>> >>>>>> On Mon, 29 Nov 2004, Yves wrote: >>>>>> >>>>>>> >>>>>>>> What structure would you like to see in a wiki/tiki system? >>>>>>>> >>>>>>>> For my self I would like to see editable specifications of new >>>>>>>> work we >>>>>>>> are going to undertake. Where comments as well as actual >>>>>>>> changes can be >>>>>>>> made. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Specifications, when there are some. Yes (I'm thinking about the >>>>>>> next database schema >>>>>>> for mysql, and API for modules that I will define soon). >>>>>>> But don't take them as the reference. The reference is always the >>>>>>> code : >>>>>>> - create_mysql.sh for mysql database schema (Ben, do you have >>>>>>> better idea than that file ?) >>>>>>> - storage.h for storage modules. >>>>>>> >>>>>>> But I like the idea to have a public draft for specifications. >>>>>>> >>>>>>> >>>>>>>> Yves also mentioned a public FAQ, private edit. Now the >>>>>>>> software is >>>>>>>> gaining in ability, this sounds like an excellent idea. >>>>>>> >>>>>>> >>>>>>> >>>>>>> have a look on that : http://www.squirrelmail.org/wiki/UserFAQ >>>>>>> >>>>>>> Answering the question at the beginning of this mail, I have 2 >>>>>>> suggestions : >>>>>>> - have one wiki with entries for the main stuff (spec drafts, faq= , >>>>>>> ...) >>>>>>> - have one wiki per main stuff (one for spec drafts, one for faq, >>>>>>> ...) >>>>>>> >>>>>>> I suggest one wiki because we can link some FAQ entries inside ou= r >>>>>>> drafts ? >>>>>>> >>>>>>> btw, if you don't know what wiki to use, have a look on the wiki >>>>>>> that squirrelmail uses, >>>>>>> and have a look on what wikipedia uses. I don't know which is the >>>>>>> best. >>>>>>> >>>>>>>> Thanks to Tim and Yves for finding and fixing a bug so quickly. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Thanks to Tim : he noticed the problem, found the bug, well, yes, >>>>>>> that's me who found >>>>>>> the bug, and he found the solution while I was actively searching >>>>>>> for it :) >>>>>>> >>>>>>> Yves >>>>>>> >>>>>>> -- >>>>>>> - Homepage - http://ymettier.free.fr - http://www.logicacmg.co= m >>>>>>> - >>>>>>> - GPG key - http://ymettier.free.fr/gpg.txt >>>>>>> - >>>>>>> - Maitretarot - http://www.nongnu.org/maitretarot/ >>>>>>> - >>>>>>> - Perfparse - http://perfparse.sf.net/ >>>>>>> - >>>>>>> >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------- >>>>>>> SF email is sponsored by - The IT Product Guide >>>>>>> Read honest & candid reviews on hundreds of IT Products from real >>>>>>> users. >>>>>>> Discover which products truly live up to the hype. Start reading >>>>>>> now. >>>>>>> http://productguide.itmanagersjournal.com/ >>>>>>> _______________________________________________ >>>>>>> Perfparse-devel-int mailing list >>>>>>> Per...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int >>>>>>> >>>>>> >>>>> >>>>> >>>>> ------------------------------------------------------- >>>>> SF email is sponsored by - The IT Product Guide >>>>> Read honest & candid reviews on hundreds of IT Products from real >>>>> users. >>>>> Discover which products truly live up to the hype. Start reading no= w. >>>>> http://productguide.itmanagersjournal.com/ >>>>> _______________________________________________ >>>>> Perfparse-devel-int mailing list >>>>> Per...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int >>>>> >>>> >>>> >>>> >>>> ------------------------------------------------------- >>>> SF email is sponsored by - The IT Product Guide >>>> Read honest & candid reviews on hundreds of IT Products from real us= ers. >>>> Discover which products truly live up to the hype. Start reading now= . >>>> http://productguide.itmanagersjournal.com/ >>>> _______________________________________________ >>>> Perfparse-devel-int mailing list >>>> Per...@li... >>>> https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int >>>> >>> >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real user= s. >> Discover which products truly live up to the hype. Start reading now. >> http://productguide.itmanagersjournal.com/ >> _______________________________________________ >> Perfparse-devel-int mailing list >> Per...@li... >> https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int >> > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users= . > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Perfparse-devel-int mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int > > --=20 - Homepage - http://ymettier.free.fr - http://www.logicacmg.com - - GPG key - http://ymettier.free.fr/gpg.txt - - Maitretarot - http://www.nongnu.org/maitretarot/ - - Perfparse - http://perfparse.sf.net/ - |
|
From: Ben C. <BCl...@pe...> - 2004-12-01 13:13:29
|
Hi Flo, I had a look at the wiki system last. I was very impressed. I need to have look in more detail. I have not registered yet, my task for this evening. The look/feel of the site is also great. Who provides the HTML? Ben Flo Gleixner wrote: > > Hi, > > if you edit your local /etc/hosts and add the line > 62.75.177.180 wiki.perfparse.org > > you can start to test tikiwiki. I did some configs. If you have > registered, i can give the core team admin permissions. > > tikiwiki is somewhat overpowered, but you can switch on/off almost > everything. > At the moment anonymous users have only read permissions except > submitting faq's for further review. Registred users may edit/create > pages, blogs image galleries (do we need them?) ... Core team get full > admin permissions. > > Flo > > > On Tue, 30 Nov 2004, Ben Clewett wrote: > >> Flo, >> >> The perfparse domain is kindly donated to us by Jeff Scott. I am in >> contact with him about changes to the new DNS. >> >> I look forward to seeing the tiki! >> >> Ben >> >> Flo Gleixner wrote: >> >>> >>> Hi Ben, >>> >>> yes, The IP of my server is 62.75.177.180. I'll prepare all for a >>> tiki install. >>> >>> Flo >>> >>> On Tue, 30 Nov 2004, Ben Clewett wrote: >>> >>>> Flo, >>>> >>>> I think this is an excellent idea! Thanks. >>>> >>>> I will arrange a domain name for this, something like >>>> wiki.perfparse.org. Can you work with this? >>>> >>>> If I look through email I think the main idea was specifications. >>>> There is one on the sf.net project page for deletion policies: >>>> >>>> http://sourceforge.net/docman/display_doc.php?docid=23729&group_id=109355 >>>> >>>> >>>> Another I emailed around for new database, will upload directly to >>>> wiki when possible :) >>>> >>>> Yves wrote: >>>> >>>>> Specifications, when there are some. Yes (I'm thinking about the >>>>> next database schema >>>>> for mysql, and API for modules that I will define soon). >>>>> But don't take them as the reference. The reference is always the >>>>> code : >>>>> - create_mysql.sh for mysql database schema (Ben, do you have >>>>> better idea than that file ?) >>>>> - storage.h for storage modules. >>>> >>>> >>>> >>>> No I don't have a better idea. The file is to create the schema >>>> when using MySQL. (I took the name from Nagios version of the same >>>> so that users with both projects would find this familiar.) Have >>>> you a better idea? >>>> >>>>> Answering the question at the beginning of this mail, I have 2 >>>>> suggestions : >>>>> - have one wiki with entries for the main stuff (spec drafts, faq, >>>>> ...) >>>>> - have one wiki per main stuff (one for spec drafts, one for faq, ...) >>>> >>>> >>>> >>>> I would like to see one clean page for each specification. Keeps >>>> things simple and readable... (Like RFCs. It works for them :) >>>> >>>> The FAQ is a public entity and should therefore have it's own page >>>> to replace the current FAQ. Current I hope will be start of new: >>>> >>>> http://perfparse.sourceforge.net/faq.php >>>> >>>> Garry has also given us a good clear style for this FAQ which works >>>> with this main site, so I think we should try and maintain this if >>>> possible :) >>>> >>>> Have I missed anything? >>>> >>>> Ben >>>> >>>> >>>> >>>> >>>> Flo Gleixner wrote: >>>> >>>>> >>>>> Had a relaying problem right now so the mail was rejected - have >>>>> to switch private mail to my own mailserver :-) >>>>> >>>>> So, i'm back now from basketball - how about a tiki tomorrow? >>>>> >>>>> Flo >>>>> >>>>> >>>>> On Mon, 29 Nov 2004, Flo Gleixner wrote: >>>>> >>>>>> >>>>>> >>>>>> hey, just almost missed the wiki discussion :-) >>>>>> >>>>>> Since i'm a project admin of tikiwiki, i'd surely vote for >>>>>> tikiwiki. I also have a server with root access and 500GB traffic >>>>>> fast ethernet connection (100MBit), own dns server, mailserver, >>>>>> ... whatever one can do with a root account. I'd be pleased to >>>>>> host a perfparse site (or part of it). I can install can configure >>>>>> a tikiwiki in less than 10 mins :-) But at the momenet i have to >>>>>> go to play basketball. I'll be back in 3-4 hours... >>>>>> >>>>>> Flo >>>>>> >>>>>> >>>>>> On Mon, 29 Nov 2004, Yves wrote: >>>>>> >>>>>>> >>>>>>>> What structure would you like to see in a wiki/tiki system? >>>>>>>> >>>>>>>> For my self I would like to see editable specifications of new >>>>>>>> work we >>>>>>>> are going to undertake. Where comments as well as actual >>>>>>>> changes can be >>>>>>>> made. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Specifications, when there are some. Yes (I'm thinking about the >>>>>>> next database schema >>>>>>> for mysql, and API for modules that I will define soon). >>>>>>> But don't take them as the reference. The reference is always the >>>>>>> code : >>>>>>> - create_mysql.sh for mysql database schema (Ben, do you have >>>>>>> better idea than that file ?) >>>>>>> - storage.h for storage modules. >>>>>>> >>>>>>> But I like the idea to have a public draft for specifications. >>>>>>> >>>>>>> >>>>>>>> Yves also mentioned a public FAQ, private edit. Now the >>>>>>>> software is >>>>>>>> gaining in ability, this sounds like an excellent idea. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> have a look on that : http://www.squirrelmail.org/wiki/UserFAQ >>>>>>> >>>>>>> Answering the question at the beginning of this mail, I have 2 >>>>>>> suggestions : >>>>>>> - have one wiki with entries for the main stuff (spec drafts, >>>>>>> faq, ...) >>>>>>> - have one wiki per main stuff (one for spec drafts, one for faq, >>>>>>> ...) >>>>>>> >>>>>>> I suggest one wiki because we can link some FAQ entries inside >>>>>>> our drafts ? >>>>>>> >>>>>>> btw, if you don't know what wiki to use, have a look on the wiki >>>>>>> that squirrelmail uses, >>>>>>> and have a look on what wikipedia uses. I don't know which is the >>>>>>> best. >>>>>>> >>>>>>>> Thanks to Tim and Yves for finding and fixing a bug so quickly. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Thanks to Tim : he noticed the problem, found the bug, well, yes, >>>>>>> that's me who found >>>>>>> the bug, and he found the solution while I was actively searching >>>>>>> for it :) >>>>>>> >>>>>>> Yves >>>>>>> >>>>>>> -- >>>>>>> - Homepage - http://ymettier.free.fr - http://www.logicacmg.com - >>>>>>> - GPG key - http://ymettier.free.fr/gpg.txt - >>>>>>> - Maitretarot - http://www.nongnu.org/maitretarot/ - >>>>>>> - Perfparse - http://perfparse.sf.net/ - >>>>>>> >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------- >>>>>>> SF email is sponsored by - The IT Product Guide >>>>>>> Read honest & candid reviews on hundreds of IT Products from real >>>>>>> users. >>>>>>> Discover which products truly live up to the hype. Start reading >>>>>>> now. >>>>>>> http://productguide.itmanagersjournal.com/ >>>>>>> _______________________________________________ >>>>>>> Perfparse-devel-int mailing list >>>>>>> Per...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int >>>>>>> >>>>>> >>>>> >>>>> >>>>> ------------------------------------------------------- >>>>> SF email is sponsored by - The IT Product Guide >>>>> Read honest & candid reviews on hundreds of IT Products from real >>>>> users. >>>>> Discover which products truly live up to the hype. Start reading >>>>> now. http://productguide.itmanagersjournal.com/ >>>>> _______________________________________________ >>>>> Perfparse-devel-int mailing list >>>>> Per...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int >>>>> >>>> >>>> >>>> >>>> ------------------------------------------------------- >>>> SF email is sponsored by - The IT Product Guide >>>> Read honest & candid reviews on hundreds of IT Products from real >>>> users. >>>> Discover which products truly live up to the hype. Start reading >>>> now. http://productguide.itmanagersjournal.com/ >>>> _______________________________________________ >>>> Perfparse-devel-int mailing list >>>> Per...@li... >>>> https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int >>>> >>> >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real users. >> Discover which products truly live up to the hype. Start reading now. >> http://productguide.itmanagersjournal.com/ >> _______________________________________________ >> Perfparse-devel-int mailing list >> Per...@li... >> https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int >> > |
|
From: Flo G. <fl...@bi...> - 2004-12-01 13:51:30
|
On Wed, 1 Dec 2004, Ben Clewett wrote: > Hi Flo, > > I had a look at the wiki system last. I was very impressed. I need to have > look in more detail. I have not registered yet, my task for this evening. > > The look/feel of the site is also great. Who provides the HTML? > > Ben > Thanks. For explanation: tikiwiki is completely based on templates/css. So the look is changed by editing the templates/css and the content is edited online - like with every wiki system. Flo |
×
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