--- joko/doc/SampleTasks/joko_2003-01.html 2003/01/23 19:38:19 1.1
+++ joko/doc/SampleTasks/joko_2003-01.html 2003/01/23 20:11:39 1.3
@@ -1,3 +1,8 @@
+
+
+
+
+
joko@netfrag.org - sample stack:
o [task by joko] introduced "dispatchmail" to add mail2news-functionality to "recieveMail" (collector@netfrag.org)
@@ -60,63 +65,24 @@
o check out from cvs-repository:
o joko/doc -> /home/joko/public_html/computing/overview/topics/
- o leaded to (A):
- o write mini-howto: "howto use, document and enhance the '.cvslink'-symlinking-mechanism"
- o introduce command to 'tiki-workflow|tiki-publish'
- x introduced '.cvs'-interface (directory-style)
- x now directly accessible (but hidden) via http://netfrag.org/~joko/computing/overview/topics/.cvs/
- x here: made public by adding a "README.html" (or "HEADER.html") which either:
- x includes a html-link (a-tag) to './.cvs'
- o makes a redirect via meta-tags or javascript
- o leads to (B):
- o start 'home2web':
- x begin with having an overview of the recent topics stored in cvs
- x continue by expanding this topic-list through more details
- x use mechanisms delivered from Apache
- x HEADER.html, README.html
- x php: http-redirect
- o add more links!
- o fix proposals of how links should be expanded (maybe post RFC to news.netfrag.org first? -> create newsgroup 'nfo.rfc')
- x manually? no! (hmmm, grrrr......)
- o pod? for now!
- o DocBook? not yet!
- o some wiki? why not?
- o add links to internal tools (e.g. TUTOS, chora, etc.)
- o add external links
- o add co-worker topics
- o leads to (C):
- o write mini-howto: web publishing with cvs
- - write in pod
- - commit to cvs
- - checkout from cvs
- - build html from pod
- - publish html
- x do that regularly / in interval: use cron!
- su joko
- cd ~
- nano .cronrc-hourly
- add line(s): [...] cvs update topics [...]
- crontab -e
- add line: * 1 * * * ~/.cronrc-hourly
- o post message "About" (this) to announce@news.netfrag.org
-
-
-adduser: collector/col§$
-
-
-some sample items occoured 2003-01-17 until 2003-01-26.
-
-what to do with that?
- o have all items stored in other applications conveniently.
- o be able to have items or references to them *archived* centrally
- o be able to access informations via *one* interface.
- actually *multiple* interfaces should be possible
- - the aim here is to get everything together (INTEGRATE!) (mnoGoSearch first! Torus::Archive later?)
-
-sysadmin tasks:
+ o leaded to (A, B and C): see home2web
-joko's tasks:
+o added user@netfrag.org:
+ x adduser: collector/col§$
+o about: some sample items occoured 2003-01-17 until 2003-01-26.
+ what to do with that?
+ o have all items stored in other applications conveniently.
+ o be able to have items or references to them *archived* centrally
+ o be able to access informations via *one* interface.
+ actually *multiple* interfaces should be possible
+ - the aim here is to get everything together (INTEGRATE!) (mnoGoSearch first! Torus::Archive later?)
+
+o refactor topics:
+ o make global-accessible@netfrag.org
+ o introduce subtopics
+ o sysadmin tasks
+ o janosch's, jonen's and joko's tasks
o start project "admintools" @ nfo/perl/scripts - including
o getip.pl
@@ -158,3 +124,12 @@
o rename "thread" to "newsgroup" in all scripts!
+o what about:
+ Torus::Xyz - solution to reuse concepts of Apache 2 and Cyrus 2!!! (and OpenLDAP???) for building an open collaboration server?
+
+o word-search: "identify" and "search" for
+
+
+
+
+