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 > |