tutos-devel Mailing List for TUTOS

Op vrijdag 29 november 2002 06:18, schreef Marc Laporte:
> The door is open!
>
> M ;-)

Well, here are my responses.....

>-----Original Message-----
From: Garland Foster [mailto:gar...@fi...] 
>Sent: November 28, 2002 10:21 AM
>To: Marc Laporte; tut...@li...;
>tik...@li...
>Subject: Re: [TUTOS-devel] Re: [Tikiwiki-devel] Tiki 1.4 brainstorming
>(groupware)

>Just in Case you are interested you can tell Jeroen
>thatthe Tiki development team completely agrees that Tutos
>is the best calendar/groupware for PHP and we'd love to
>do something together as a team.

I personnaly think that this is one of the major succes factors of the Open 
Source movement. Add some sport-like competition and the results are great!

>We don't know if integrating Tiki into tutos is a better idea
>than integrating Tutos features into Tiki. After all Tutos is
>a groupware-focused application while Tiki is an evergrowing
>project trying to add as many features as we can.

Good point and a difficult question. Let us not try to build something that 
can do everything. The last time some major institution did that we ended up 
with a text processor with a dancing paperclip.

>Garland.

>----- Original Message -----
From: "Marc Laporte" <ma...@ma...>
>To: <tut...@li...>;
><tik...@li...>
>Sent: Thursday, November 28, 2002 11:50 AM
>Subject: RE: [TUTOS-devel] Re: [Tikiwiki-devel] Tiki 1.4 brainstorming
>(groupware)


> > Marc Laporte initial text
> [JB] Jeroen Baten 1st reply
> [ML] Marc Laporte 2nd reply
>
>
> -----Original Message-----
> From: tut...@li...
> [mailto:tut...@li...] On Behalf Of Jeroen
> Baten
> Sent: November 28, 2002 2:24 AM
> To: Marc Laporte; tutos-devel
> Subject: [TUTOS-devel] Re: [Tikiwiki-devel] Tiki 1.4 brainstorming
> (groupware)


> > Tikiwiki is rapidly becoming the best GPL PHP/MySQL  CMS/wiki/portal
>
> [JB]Is it? I had a look yesterday at phpwiki and, allthough it is not
so
> fancy, it does offer a plain wiki system. Do we want all the other
> features of tikiwiki in tutos like polls etc.?
>
> [ML] What is essential is that Tutos notes can become wikipages (Or
> wikipages become a note-like modules) So many people can build a page
> together. A modularized PHPwiki would be fine. However, once decided
to
> add a wiki to Tutos, why not go for a full-fledged CMS? Links between
> these notes could then be used as a knowledgebase and be subject to
the
> permission system for view/edit/delete.

If you want to integrate a CMS than why not ezpublish (www.ez.no)?

> [ML] Currently, I am running Postnuke, PHPWiki & Tutos. PHPwiki's last
> release is 9 months old and the CVS is alive but buggy. It doesn't do
a
> great job with users, groups & permissions.
>
> [ML] Tikiwiki has released 5 times in 40 days. And another version is
in
> the works. Tikiwiki has an excellent permission system, uses Smarty
and
> for the last few weeks, has been the most active wiki and/or CMS on
SF.
> In fact, Tiki is currently #5 in Activity Percentile amongst all PHP
> projects. #1 PhpMyAdmin, #2Tutos #4 SquirrelMail, #5 Tiki,  #13
PhpWiki
> http://sourceforge.net/softwaremap/trove_list.php?form_cat=183
>
> [ML] In my case, Tikiwiki will soon replace Postnuke & PHPwiki in one
> swoop.

I had not lookad at the source or activity. In this case I have to agree that 
a more active project makes more sense,

> [ML] Any opinion on OSSuite (Nola + osCommerce + CRM)
> http://sourceforge.net/projects/ossuite/

I am downloading it now.

> > combination to web-manage pretty much any organization!!
>
> [JB] hear, hear.
>
> > I'd really like to have a workflow engine somewhere in there!
> > http://www.cmswatch.com/GlossaryTerm/?term_id=38
>
> [JB] Me too, but saying that doesn't mean it will automagically come
in
> there. Oh well, time for me to start doing some serious TUTOS work
(it's
> been to long).
>
> [ML] I'm looking forward to seeing your files in the CVS!!!!

Point taken. Would you believe me if I tell you that I can not remember that 
last time I had some free time? Except for small bits to keep the dutch TUTOS 
translation up to speed. I am looking currently at xml/xslt and fop to add 
tot tutos.

greetings to all,



-- 
  Jeroen Baten            | EMAIL :  JB...@I2...
 ____  _  __              | web   :  www.i2rs.nl
  |  )|_)(_               | tel   :  +31 (0)30 221 00 11
 _|_/_| \__)              | fax   :  +31 (0)30 220 31 91
  Kometenlaan 26, 3721 JT, Bilthoven, the Netherlands

Just in Case you are interested you can tell Jeroen
thatthe Tiki development team completely agrees that Tutos
is the best calendar/groupware for PHP and we'd love to
do something together as a team.

We don't know if integrating Tiki into tutos is a better idea
than integrating Tutos features into Tiki. After all Tutos is
a groupware-focused application while Tiki is an evergrowing
project trying to add as many features as we can.

Garland.


----- Original Message -----
From: "Marc Laporte" <ma...@ma...>
To: <tut...@li...>;
<tik...@li...>
Sent: Thursday, November 28, 2002 11:50 AM
Subject: RE: [TUTOS-devel] Re: [Tikiwiki-devel] Tiki 1.4 brainstorming
(groupware)


> > Marc Laporte initial text
> [JB] Jeroen Baten 1st reply
> [ML] Marc Laporte 2nd reply
>
>
> -----Original Message-----
> From: tut...@li...
> [mailto:tut...@li...] On Behalf Of Jeroen
> Baten
> Sent: November 28, 2002 2:24 AM
> To: Marc Laporte; tutos-devel
> Subject: [TUTOS-devel] Re: [Tikiwiki-devel] Tiki 1.4 brainstorming
> (groupware)
>
> Op donderdag 28 november 2002 05:15, schreef u:
> > Hi,
> >
> > IMHO, Tutos is currently the best GPL PHP/MySQL intranet/groupware
> > (calendar/file manager/time tracking/address book/ project-task-bug
> > manager)
>
> [JB] No argument there :-)
>
> > http://www.hotscripts.com/Detailed/6868.html
> >
> >
> > Tikiwiki is rapidly becoming the best GPL PHP/MySQL  CMS/wiki/portal
>
> [JB]Is it? I had a look yesterday at phpwiki and, allthough it is not so
> fancy, it does offer a plain wiki system. Do we want all the other
> features of tikiwiki in tutos like polls etc.?
>
> [ML] What is essential is that Tutos notes can become wikipages (Or
> wikipages become a note-like modules) So many people can build a page
> together. A modularized PHPwiki would be fine. However, once decided to
> add a wiki to Tutos, why not go for a full-fledged CMS? Links between
> these notes could then be used as a knowledgebase and be subject to the
> permission system for view/edit/delete.
>
> [ML] Currently, I am running Postnuke, PHPWiki & Tutos. PHPwiki's last
> release is 9 months old and the CVS is alive but buggy. It doesn't do a
> great job with users, groups & permissions.
>
> [ML] Tikiwiki has released 5 times in 40 days. And another version is in
> the works. Tikiwiki has an excellent permission system, uses Smarty and
> for the last few weeks, has been the most active wiki and/or CMS on SF.
> In fact, Tiki is currently #5 in Activity Percentile amongst all PHP
> projects. #1 PhpMyAdmin, #2Tutos #4 SquirrelMail, #5 Tiki,  #13 PhpWiki
> http://sourceforge.net/softwaremap/trove_list.php?form_cat=183
>
> [ML] In my case, Tikiwiki will soon replace Postnuke & PHPwiki in one
> swoop.
>
>
>
> > Tikiwiki/Tutos would make a great combination to manage a
> > portal/intranet. We're looking to integrate the two in single sign on
> > via LDAP. Anyone interested?
>
> [JB] Single sign on is relatively easy to do. It would be a real
> challenge to integrate them. So it is possible to start a wiki thread on
> a bugreport.
>
> > Looking ahead: Throw in a webmail (imp or squirrel), a CRM (relata or
> > anteil) an ERP (accounting/shopping cart) and you have a pretty
> awesome
>
> [JB] erp: nola for accounting (but remove the ugly ttf-font dependancy
> :-)
>
> [ML] Any opinion on OSSuite (Nola + osCommerce + CRM)
> http://sourceforge.net/projects/ossuite/
>
>
> > combination to web-manage pretty much any organization!!
>
> [JB] hear, hear.
>
> > I'd really like to have a workflow engine somewhere in there!
> > http://www.cmswatch.com/GlossaryTerm/?term_id=38
>
> [JB] Me too, but saying that doesn't mean it will automagically come in
> there. Oh well, time for me to start doing some serious TUTOS work (it's
> been to long).
>
> [ML] I'm looking forward to seeing your files in the CVS!!!!
>
> [ML] Best regards,
>
>
> [JB] greetings to all,
>
> --
>   Jeroen Baten            | EMAIL :  JB...@I2...
>  ____  _  __              | web   :  www.i2rs.nl
>   |  )|_)(_               | tel   :  +31 (0)30 221 00 11
>  _|_/_| \__)              | fax   :  +31 (0)30 220 31 91
>   Kometenlaan 26, 3721 JT, Bilthoven, the Netherlands
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Get the new Palm Tungsten T
> handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
> _______________________________________________
> TUTOS-devel mailing list
> TUT...@li...
> https://lists.sourceforge.net/lists/listinfo/tutos-devel
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Get the new Palm Tungsten T
> handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
> _______________________________________________
> Tikiwiki-devel mailing list
> Tik...@li...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel

> Marc Laporte initial text
[JB] Jeroen Baten 1st reply 
[ML] Marc Laporte 2nd reply


-----Original Message-----
From: tut...@li...
[mailto:tut...@li...] On Behalf Of Jeroen
Baten
Sent: November 28, 2002 2:24 AM
To: Marc Laporte; tutos-devel
Subject: [TUTOS-devel] Re: [Tikiwiki-devel] Tiki 1.4 brainstorming
(groupware)

Op donderdag 28 november 2002 05:15, schreef u:
> Hi,
>
> IMHO, Tutos is currently the best GPL PHP/MySQL intranet/groupware
> (calendar/file manager/time tracking/address book/ project-task-bug
> manager)

[JB] No argument there :-)

> http://www.hotscripts.com/Detailed/6868.html
>
>
> Tikiwiki is rapidly becoming the best GPL PHP/MySQL  CMS/wiki/portal

[JB]Is it? I had a look yesterday at phpwiki and, allthough it is not so
fancy, it does offer a plain wiki system. Do we want all the other
features of tikiwiki in tutos like polls etc.?

[ML] What is essential is that Tutos notes can become wikipages (Or
wikipages become a note-like modules) So many people can build a page
together. A modularized PHPwiki would be fine. However, once decided to
add a wiki to Tutos, why not go for a full-fledged CMS? Links between
these notes could then be used as a knowledgebase and be subject to the
permission system for view/edit/delete.

[ML] Currently, I am running Postnuke, PHPWiki & Tutos. PHPwiki's last
release is 9 months old and the CVS is alive but buggy. It doesn't do a
great job with users, groups & permissions. 

[ML] Tikiwiki has released 5 times in 40 days. And another version is in
the works. Tikiwiki has an excellent permission system, uses Smarty and
for the last few weeks, has been the most active wiki and/or CMS on SF.
In fact, Tiki is currently #5 in Activity Percentile amongst all PHP
projects. #1 PhpMyAdmin, #2Tutos #4 SquirrelMail, #5 Tiki,  #13 PhpWiki
http://sourceforge.net/softwaremap/trove_list.php?form_cat=183

[ML] In my case, Tikiwiki will soon replace Postnuke & PHPwiki in one
swoop.  



> Tikiwiki/Tutos would make a great combination to manage a
> portal/intranet. We're looking to integrate the two in single sign on
> via LDAP. Anyone interested?

[JB] Single sign on is relatively easy to do. It would be a real
challenge to integrate them. So it is possible to start a wiki thread on
a bugreport.

> Looking ahead: Throw in a webmail (imp or squirrel), a CRM (relata or
> anteil) an ERP (accounting/shopping cart) and you have a pretty
awesome

[JB] erp: nola for accounting (but remove the ugly ttf-font dependancy
:-)

[ML] Any opinion on OSSuite (Nola + osCommerce + CRM)
http://sourceforge.net/projects/ossuite/


> combination to web-manage pretty much any organization!!

[JB] hear, hear.

> I'd really like to have a workflow engine somewhere in there!
> http://www.cmswatch.com/GlossaryTerm/?term_id=38

[JB] Me too, but saying that doesn't mean it will automagically come in
there. Oh well, time for me to start doing some serious TUTOS work (it's
been to long).

[ML] I'm looking forward to seeing your files in the CVS!!!!

[ML] Best regards,


[JB] greetings to all,

-- 
  Jeroen Baten            | EMAIL :  JB...@I2...
 ____  _  __              | web   :  www.i2rs.nl
  |  )|_)(_               | tel   :  +31 (0)30 221 00 11
 _|_/_| \__)              | fax   :  +31 (0)30 220 31 91
  Kometenlaan 26, 3721 JT, Bilthoven, the Netherlands


-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T 
handheld. Power & Color in a compact size! 
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
_______________________________________________
TUTOS-devel mailing list
TUT...@li...
https://lists.sourceforge.net/lists/listinfo/tutos-devel

Op donderdag 28 november 2002 05:15, schreef u:
> Hi,
>
> IMHO, Tutos is currently the best GPL PHP/MySQL intranet/groupware
> (calendar/file manager/time tracking/address book/ project-task-bug
> manager)

No argument there :-)

> http://www.hotscripts.com/Detailed/6868.html
>
>
> Tikiwiki is rapidly becoming the best GPL PHP/MySQL  CMS/wiki/portal

Is it? I had a look yesterday at phpwiki and, allthough it is not so fancy, it 
does offer a plain wiki system. Do we want all the other features of tikiwiki 
in tutos like polls etc.?

> Tikiwiki/Tutos would make a great combination to manage a
> portal/intranet. We're looking to integrate the two in single sign on
> via LDAP. Anyone interested?

Single sign on is relatively easy to do. It would be a real challenge to 
integrate them. So it is possible to start a wiki thread on a bugreport.

> Looking ahead: Throw in a webmail (imp or squirrel), a CRM (relata or
> anteil) an ERP (accounting/shopping cart) and you have a pretty awesome

erp: nola for accounting (but remove the ugly ttf-font dependancy :-)

> combination to web-manage pretty much any organization!!

hear, hear.

> I'd really like to have a workflow engine somewhere in there!
> http://www.cmswatch.com/GlossaryTerm/?term_id=38

Me too, but saying that doesn't mean it will automagically come in there. Oh 
well, time for me to start doing some serious TUTOS work (it's been to long).

greetings to all,

-- 
  Jeroen Baten            | EMAIL :  JB...@I2...
 ____  _  __              | web   :  www.i2rs.nl
  |  )|_)(_               | tel   :  +31 (0)30 221 00 11
 _|_/_| \__)              | fax   :  +31 (0)30 220 31 91
  Kometenlaan 26, 3721 JT, Bilthoven, the Netherlands

On Wed, Nov 27, 2002 at 01:35:40AM +0100, Jerome Warnier wrote:
> > I is completely broken, to say the least!

Hello, I'm the guy who made the debian packaging !

> First of all: debconf is cycling on dba password question.

Which package version did you try ? The one to use is the
1.0.20021112-2, available here :
      http://tapoueh.org/debian

There is even an apt source !
I'm not sure which version is given on the sourceforge download page...

> Next: some problems with the postinst script, fixed in this diff.
> Take note two big problems still remain, but only for PostgreSQL, and I 
> don't have a clean fix for them, so I don't submit a patch right now.
> If you have any question on what those do, or why, just ask.

I'm not sure those lasts problems are fixed even in the last package
version. I did not have the time to make all necessary tests.

I'll be happy to integrate your patch as soon as you make it available.

Regards,
-- 
Dimitri.
http://dim.tapoueh.org

Tous les hommes naissent comédiens, sauf quelques acteurs.
	-- Sacha Guitry

Jerome Warnier wrote:
> I tried today to build and install the Debian package on Woody from CVS, 
> with PostgreSQL as database.
> 
> I is completely broken, to say the least!
> I will however submit a patch to correct this.
> Where should I submit it?
> 
> The sad part is that createdb.sh and/or shellfunc.sh have to be updated 
> to make it work (consistently).
> I'm though almost sure that no documentation update will be necessary, 
> as only internal changes are needed in those scripts as well as in the 
> Debian specific part.
> 
> I would like to have to tell good work, guys, but for now, I've not 
> succeded in the install itself! Maybe this will get fixed this evening.
> 
> Regards

First of all: debconf is cycling on dba password question.

This diff fixes the problem.

Index: debian/tutos.config
===================================================================
RCS file: /cvsroot/tutos/tutos/debian/tutos.config,v
retrieving revision 1.1
diff -r1.1 tutos.config
67c67
< 	      STATE=5
---
 > 	      STATE=6

Next: some problems with the postinst script, fixed in this diff.
Take note two big problems still remain, but only for PostgreSQL, and I 
don't have a clean fix for them, so I don't submit a patch right now.

Index: debian/tutos.postinst
===================================================================
RCS file: /cvsroot/tutos/tutos/debian/tutos.postinst,v
retrieving revision 1.2
diff -r1.2 tutos.postinst
138a139
 > 		echo Postgresql
168c169,170
< 	if [ ! $db_exists = "tutos" ]; then
---
 > 	echo $db_exists
 > 	if [ ! "x$db_exists" = "xtutos" ]; then
171c173
< 	    export $db_host $db_port $dba_name $dba_password
---
 > 	    export DBHOST=$db_host DBPORT=$db_port DBSUSER=$dba_name 
DBPASSWD=$dba_password DBUSER=$dbu_name DBNAME="tutos"
173,174c175,176
< 		"postgres")
< 		    su postgres -c "${tutosdir}/create.sh $dbase CREATE"
---
 > 		"postgresql")
 > 		    su postgres -c "${tutosdir}/createdb.sh $dbase CREATE"
177c179
< 		    ${tutosdir}/create.sh $dbase CREATE
---
 > 		    ${tutosdir}/createdb.sh $dbase CREATE


If you have any question on what those do, or why, just ask.

Regards.

I tried today to build and install the Debian package on Woody from CVS, 
with PostgreSQL as database.

I is completely broken, to say the least!
I will however submit a patch to correct this.
Where should I submit it?

The sad part is that createdb.sh and/or shellfunc.sh have to be updated 
to make it work (consistently).
I'm though almost sure that no documentation update will be necessary, 
as only internal changes are needed in those scripts as well as in the 
Debian specific part.

I would like to have to tell good work, guys, but for now, I've not 
succeded in the install itself! Maybe this will get fixed this evening.

Regards

Hi,

I noticed there is japanese-1.0.20021113.zip on sourceforge.
I forgot to send a new one. So I will attach it.
Please replace the file with this one.

Thanks,

makoto

-- 
Kikutani, Makoto

Hi Tutos folks,
	I generated some code to have tutos send an e-mail when a
task is assigned or modified, using mostly code taken from bug.pinc.
Is is worth submitting this somewhere or to someone in the form of a
patch?

Either way, I noticed some inconsistenties between the object
structures for bug and task, that if changed, I think would make the
code more readable:

1) in bug the description is "description" in task its "desc"
(I don't care sort or long, it'd just be nice to have it the same).
2) in bug the responsible person is "solver" in task its "worker"
(how about worker in both cases)

I'm not complaining, I'm just noting the things that tripped me up
in adding e-mail for tasks.

	Thanks.

	- Scott

Op vrijdag 15 november 2002 09:08, schreef Gero Kohnert:
> On Thursday 14 November 2002 01:22, Marc Laporte wrote:
> > I'd like to make it possible to modify bug reference to a different
> > project.
>
> Things are going on. The very latest CVS versions have this ability since
> yesterday evening (CET).
> There you can "move" tasks and bugs inside a project and to related
> projects. Related projects are all those projects which have a role in the
> current top project.
>
> > Does this seem like a big change to the code?
>
> It was not. Meanwhile there is a godd infrastructure in the Objects which
> allows a easy change of most things.

Also to move people to another company? :-)

>
> Gero

-- 
  Jeroen Baten            | EMAIL :  JE...@I2...
 ____  _  __              | web   :  www.i2rs.nl
  |  )|_)(_               | tel   :  +31 (0)30 221 00 11
 _|_/_| \__)              | fax   :  +31 (0)30 220 31 91
  Kometenlaan 26, 3721 JT, Bilthoven, the Netherlands

On Thursday 14 November 2002 01:22, Marc Laporte wrote:
> I'd like to make it possible to modify bug reference to a different
> project.

Things are going on. The very latest CVS versions have this ability since=
=20
yesterday evening (CET).
There you can "move" tasks and bugs inside a project and to related proje=
cts.
Related projects are all those projects which have a role in the current =
top=20
project.

> Does this seem like a big change to the code?

It was not. Meanwhile there is a godd infrastructure in the Objects which=
=20
allows a easy change of most things.

Gero
--=20
                              http://www.tutos.org

I'd like to make it possible to modify bug reference to a different
project.

Similar to:
http://sourceforge.net/tracker/index.php?func=detail&aid=635752&group_id
=8047&atid=358047

Does this seem like a big change to the code?

M ;-)

--
Marc Laporte

> My (unsorted) ideas about knowledgemangement so far are:
> * something like a searchable structured FAQ for projects
> * usable for Support/Hotline people
> * exportable in some cool formats (PDF/HTML) for use outside of TUTOS
> * (more to come)

Integrate a Wiki.

-- 
  Phlip
           http://www.greencheese.org/DontPlanDesigns
  --  "In my experience, the customer doesn't know what he wants
       until you don't give it to him." --David Brady  --

Hello all,

This is my vision of Knowledge Base architecture.

1. Primary component of KB is Solution
2. Solution has to be Project/Product based. It can be stored in
Project/Product part of database but with some attribute (it's
discutable of course)
3. Solutions can be categorized using some predefined attributes (for
example, software category, hardware category, documentation category,
something like that).
4. Solution has to be generic, e.g. it doesn't contain any address
book information or link to such information.
5. It is necessary to have a possibility to attach files to Solution.
6. There may be two ways for Solution creation: a).from scratch;
b).Solution made from some solved bug
7. Solution has to be divided by access privilegies. For example, for
internal use only, for customers, for other departments of company,
for all.
8. Solution may have status FAQ. In this case when user logins to FAQ
part of KB he has be able to see only FAQs but not other categories of
Solutions.

I will be very grateful for any comments, advices and notes

Best regards,

Hermann Zheboldov
Chief of Software Dept.
Systema LLC
Moscow, Russia
Phone: (+7095) 725-2323, 725-2325
Fax:   (+7095) 725-2322
E-Mail: Her...@sh...
        As...@sh...

Hello List, Hello Hermann,

> I have plans for adding Knowledge DataBase functionality into TUTOS.

adding a knowledgebase module is one of my plans for the future. If you
want to maintain/develop such a module it would be great.
My (unsorted) ideas about knowledgemangement so far are:
* something like a searchable structured FAQ for projects
* usable for Support/Hotline people
* exportable in some cool formats (PDF/HTML) for use outside of TUTOS
* (more to come)

What are your ideas about a knowledge base in TUTOS

> Also I can to monitor russian part of TUTOS

Very good.

Some more info about devleoping for TUTOS
* all additions must run with all supported DB systems
  (i.e NO cool MySQL or Oracle stuff that won't run with other
   databases)
* everythiung should be internationalized as far as possible
* no addition of features that are only usable for the major
  part of users (for example a funeral management modul will
  never become part of the standard release)
* you should subscribe both mailing lists
* you need a sourceforge account
* development happens in the HEAD branch of CVS
* only stable stuff should be commited to CVS
* after submitting your first efforts via mail (to me) you
  can get write access to CVS

A lot of "rules" :-)  If you can live with that you are welcome to join.


PS: I will CC this mail to the devel mailing list


Gero


-- 
http://www.tutos.org

Op maandag 11 november 2002 18:24, schreef Marc Laporte:
> To Gero and all the Tutos team,
>
> Thank you so much for such a great product.
>
> I'm looking forwarding to installing, discovering and using the latest
> version of the best open source Intranet/Groupware.

Well now, what brings on this spontaneous burst of enthousiasm? :-)

BTW, For the rest I agree completely and I thank you for your development 
efforts 

Kind regards,

Jeroen,

who is currently racing against the clock making a PHP poll/survey (no, much 
bigger than a web poll) application. Did try to find a nice php ide and 
skipped zend dev env (java program is TOOO f*cking slow), likes kate a lot, 
likes quanta [gold] a little and Komodo a lot (stabel and fast enough).

-- 
  Jeroen Baten            | EMAIL :  JE...@I2...
 ____  _  __              | web   :  www.i2rs.nl
  |  )|_)(_               | tel   :  +31 (0)30 221 00 11
 _|_/_| \__)              | fax   :  +31 (0)30 220 31 91
  Kometenlaan 26, 3721 JT, Bilthoven, the Netherlands

To Gero and all the Tutos team,

Thank you so much for such a great product.

I'm looking forwarding to installing, discovering and using the latest
version of the best open source Intranet/Groupware.

Best regards,

Marc Laporte

--->[Quoting Gero Kohnert <gok...@us...>:]

> My  idea/plan  on this  is  to  move all  (DB/LDAP/X509/PAM)
> auth functions  to seperate  classses in a  new subdirectory
> ("auth")  these   classes  will   all  be  derived   from  a
> "template/api" class.  All new autzh mechanism  only have to
> be subclasses of  this API and can do whatever  they want to
> authenticate a given username / password pair.

Good idea.

> A seperate PW  Table is not neccessary,  it already possible
> to write a own check function in permission.p3 today.

Maybe,   but   it   requires  watching   changes   in   tutos'
permission.p3 - and  keeping your own file up to  date - it is
not long distance solution.


cheers - Sergiusz
--
private: http://ibiblio.org/ser/  company: http://it-zone.org/ 
______________________________________________________________
on wallpaper: tldp.org, gnu.org, pld-linux.org, hyperreal.info

> I have  an idea: maybe  move user/password information  to the
> separate  table?  It  would  allow  authorization  from  other
> programs  which  keep auyh  info  in  other database/table  by
> simple  changing database  name/table  name  (in tutos  config
> file).

My idea/plan on this is to move all (DB/LDAP/X509/PAM) auth functions to
seperate classses in a new subdirectory ("auth") these classes will all be
derived from a "template/api" class. All new autzh mechanism only have to
be subclasses of this API and can do whatever they want to authenticate a
given username / password pair.

Another change would be that auth mechanism would be defined for every
Database connection so it will be possible to have one DB where we use
LDAP and another one where we use simple DB queries for authentification.

A good test (as soon as I have made the changes) is if someone can create
a auth module that uses some forum software like PHPNuke for
authentification of tutos users. (Just as a proof of concept)

A seperate PW Table is not neccessary, it already possible to write a own
check function in permission.p3 today.


Comments ?

Gero

-- 
http://www.tutos.org

Op maandag 11 november 2002 13:49, schreef Sergiusz Pawlowicz:
> I have  an idea: maybe  move user/password information  to the
> separate  table?  It  would  allow  authorization  from  other
> programs  which  keep auyh  info  in  other database/table  by
> simple  changing database  name/table  name  (in tutos  config
> file).

I think you can best use LDAP for this. TUTOS also supports LDAP.

>
>
> cheers - Sergiusz

kind regards,

-- 
  Jeroen Baten            | EMAIL :  JE...@I2...
 ____  _  __              | web   :  www.i2rs.nl
  |  )|_)(_               | tel   :  +31 (0)30 221 00 11
 _|_/_| \__)              | fax   :  +31 (0)30 220 31 91
  Kometenlaan 26, 3721 JT, Bilthoven, the Netherlands

I have  an idea: maybe  move user/password information  to the
separate  table?  It  would  allow  authorization  from  other
programs  which  keep auyh  info  in  other database/table  by
simple  changing database  name/table  name  (in tutos  config
file).


cheers - Sergiusz
--
private: http://ibiblio.org/ser/  company: http://it-zone.org/ 
______________________________________________________________
on wallpaper: tldp.org, gnu.org, pld-linux.org, hyperreal.info

Beste Devin B. Hedge (dev...@ya...),

> oh. ok. got it. hmmm. maybe the .htaccess file might be the trick.
In the general httpd.conf administrators can define which kind of
options you are alowed to use in the .htaccess. The system I run tutos
on does not allow me to use the 'DirectoryIndex mytutos.php' which is
solved by creating a symbolic link from the allowed index.php.
To find out what causes a problem it might be keen to start by
commenting out all options in .htaccess, and add try to uncomment all
possible items.

> > > 3) Finally, changed all but two of the uses of the
> > include() function to
> > > require() in order to improve performance and reveal where
> > errors might
> > > occur.
> > I never heard about performance issues.
> Apparently it has something to do with MySQL object instantiation or
> something. I found that tip in the SAMS "PHP and MySQL Web Development"
> book. I rate the book at a strong "B-".
There is of course a difference in the way include statements and
require statements are interpret inside PHP. When a include statement is
used inside some loop, each time the include statement is about to be
executed, the include-file should be opened, compiled and executed. This
is much more expensive than the require statement. The require statement
is replaced with the contents of the required-file and compiled with the
mainfile. 
So, especially inside loops the require function could be faster.

I didn't have problems with speed of tutos (the execution time of php
code). Because the connection (although broadband) was to slow to return
instant results I added connection-compression support by adding 2 lines
in classic_layout.pinc.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
$ cvs -d:pserver:ano...@cv...:/cvsroot/tutos diff php/layout/classic_layout.pinc 
Index: php/layout/classic_layout.pinc
===================================================================
RCS file: /cvsroot/tutos/tutos/php/layout/classic_layout.pinc,v
retrieving revision 1.19
diff -r1.19 classic_layout.pinc
10a11,12
>  include "gzdoc.inc";
> 
107c109,110
<     @ob_end_flush();
---
>     GzDocOut();
> /*    @ob_end_flush();*/

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The file 'gzdoc.inc' (or gzdoc.php) can be found in serveral places on
the internet like : 
http://php.weblogs.com/stories/http_compression
http://www.oxyscripts.com/viewcode.php?id=46

Newer versions of PHP also support http compression by options in
php.ini like:   zlib.output_compression, zlib.output_compression_level
I should probably change to these in the near future, because they are
more accurate.

Regards,
  Robert

-- 
	R.P.G.Brouwer		http://www.corine-robert.nl/
				mailto:ro...@co...

Thanks for the help. Not sure how to back out of where I am at other than
just re-untarring the files over the old after saving the configuration
files.

Devin.


> -----Original Message-----
> From: tut...@li...
> [mailto:tut...@li...]On Behalf Of Gero
> Kohnert
> Sent: Wednesday, November 06, 2002 3:32 PM
> To: tut...@li...
> Subject: Re: [TUTOS-devel] I broke it!
>
>
> Hi,
>
> On Wednesday 06 November 2002 21:46, Devin B. Hedge wrote:
> >
> > Like most Shared Hosting Providers the request to append an
> "include" to
> > the httpd.conf will get you laughed right off the phone.
> Also, having to
> > modify the "php.ini" file will achieve the same. So, in
> order for Tutos to
> > work, I would have to figure out a work-around.
>
> The include in http.conf is not really neccesary. It will
> also work without,
> but you have to take care not to serve confidential files
> like config.pinc

How bad would changing the directory structure mess things up?

>
> > 1) I changed the filenames of any file with the extension
> of .pinc to
> > .inc.php
> > This eliminates the need for the "AddType
> application/x-httpd-php .pinc"
> > directive in the apache.conf file. Also, so long as the
> development and
>
> This directive was introduced in order to "secure"
> config.pinc all other pinc
> files do not harm if served in 1:1 by apache.

oh. ok. got it. hmmm. maybe the .htaccess file might be the trick.

>
> > 2) I searched (using grep) for all of the instances of
> "filename".pinc in
> > the PHP scripts. What I found was the use of the include
> statement in
>
> No comment. This should work.

Has anyone else found problems with the variations on include? I'm not sure
if I created one problem, or just exposed one, but during the scheme.php
page=3 I had a "file not found" error on one include. I tried to recreate
the problem and couldn't.

>
> > 3) Finally, changed all but two of the uses of the
> include() function to
> > require() in order to improve performance and reveal where
> errors might
> > occur.
>
> I never heard about performance issues.

Apparently it has something to do with MySQL object instantiation or
something. I found that tip in the SAMS "PHP and MySQL Web Development"
book. I rate the book at a strong "B-".

>
> > So now I have a non-functioning Tutos site. Could someone
> point me in the
> > right direction to start repairing the code?
>
> Any error messages ?
>
>
> As you see most of the troble is caused by config.pinc and
> its sensitive
> content. Best way would be to rename it to config.php and
> only change the
> include "config.pinc"
> to
> include "config.php"
>

Thanks,
I'm going to try this. I'll let you know.

Devin.

-----------------------------------------------------------------------
"Ogres are like onions."
"Layers! Onions have layers. Ogres have layers. Onions have layers.
You get it? We both have layers."
-- Shrek
-----------------------------------------------------------------------

> -----Original Message-----
> From: tut...@li...
> [mailto:tut...@li...]On Behalf Of
> Ron McKown
> Sent: Wednesday, November 06, 2002 3:22 PM
> To: tut...@li...
> Subject: Re: [TUTOS-devel] I broke it!
>
>
> hey Devin,
> does your host provider allow for .htaccess files?

They sure do. I was wondering if adding an additional .htaccess file for
some of the dirs might help, too.

>
> On Wed, 2002-11-06 at 12:46, Devin B. Hedge wrote:
> > Why:
> >
> > Like most Shared Hosting Providers the request to append an
> "include" to the
> > httpd.conf will get you laughed right off the phone. Also,
> having to modify
> > the "php.ini" file will achieve the same. So, in order for
> Tutos to work, I
> > would have to figure out a work-around.

--------------------------------
Remaining message truncated

Hi,

On Wednesday 06 November 2002 21:46, Devin B. Hedge wrote:
>
> Like most Shared Hosting Providers the request to append an "include" t=
o
> the httpd.conf will get you laughed right off the phone. Also, having t=
o
> modify the "php.ini" file will achieve the same. So, in order for Tutos=
 to
> work, I would have to figure out a work-around.

The include in http.conf is not really neccesary. It will also work witho=
ut,=20
but you have to take care not to serve confidential files like config.pin=
c

> 1) I changed the filenames of any file with the extension of .pinc to
> .inc.php
> This eliminates the need for the "AddType application/x-httpd-php .pinc=
"
> directive in the apache.conf file. Also, so long as the development and

This directive was introduced in order to "secure" config.pinc all other =
pinc=20
files do not harm if served in 1:1 by apache.

> 2) I searched (using grep) for all of the instances of "filename".pinc =
in
> the PHP scripts. What I found was the use of the include statement in

No comment. This should work.

> 3) Finally, changed all but two of the uses of the include() function t=
o
> require() in order to improve performance and reveal where errors might
> occur.

I never heard about performance issues.=20

> So now I have a non-functioning Tutos site. Could someone point me in t=
he
> right direction to start repairing the code?

Any error messages ?


As you see most of the troble is caused by config.pinc and its sensitive=20
content. Best way would be to rename it to config.php and only change the=
=20
include "config.pinc"
to=20
include "config.php"


Gero