/[cvs]/joko/doc/SampleTasks/joko_2003-01.html
ViewVC logotype

Contents of /joko/doc/SampleTasks/joko_2003-01.html

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.3 - (show annotations)
Thu Jan 23 20:11:39 2003 UTC (21 years, 9 months ago) by joko
Branch: MAIN
Changes since 1.2: +29 -15 lines
File MIME type: text/html
+ updated
+ added reference to sample task

1 <html>
2 <body>
3
4 <pre>
5
6 joko@netfrag.org - sample stack:
7
8 o [task by joko] introduced "dispatchmail" to add mail2news-functionality to "recieveMail" (collector@netfrag.org)
9 x [task by joko] migrated joko_mail from "receiveMail" to "dispatchmail"
10 x [bug from joko] what about mailing from the cli / mails sent from the system (e.g. via CVSSpam):
11 mail is sent out coming from <username>@quepasa.netfrag.org
12 --> how to configure just having <username>@netfrag.org right here???
13 x [resolved by jonen] CVSSpam: janosch@netfrag.org:
14 x cd /etc/mail
15 x nano sendmail.mc
16 x add/replace line: MASQUERADE_AS(`netfrag.org')
17 x make
18 x /etc/init.d/sendmail reload
19 o [bug from joko] "su root" is needed sometimes
20 else PATH is not set correctly
21 and maybe something other
22 compiling fails always
23 x [task by joko] these items already have been refactored into other Tasks, Notes and/or Bug Requests - this Note is just FYI.
24 o [task by joko] dispatchmail - project work
25 x README.pod -> README.html
26 x link with "topics.html" properly
27 x write something about data-/control-flow to README.pod
28
29 o look (in detail) at Cyrus Netnews
30 [...]
31 The IMAP server can export netnews newsgroups as IMAP mailboxes.
32 [...]
33 o collectnews, rmnews, syncnews
34 x seems to make an external web-based newsreader unneccessary!!!
35
36 o tie together mail, news and html
37 o write mini-howto
38
39 o link with erfrakon
40
41 o sieve?
42
43 o post some old mails to news.netfrag.org!
44
45 o what about "dev@netfrag.org"?
46
47 o nfo/perl/libs
48 x ts
49 x outlook2ldap
50 x dispatchmail
51 o get the essence (project- and development work - the whole workflow) out of it! write it down! in detail!
52
53 o netfrag.org-workflow:
54 o technical questions to support@netfrag.org?
55 o publish them via news!
56 o queue them into / integrate with TUTOS somehow!!!
57
58 o new threads@news.netfrag.org:
59 x ctlinnd newgroup nfo.support.queue
60 x ctlinnd newgroup nfo.support.faq
61
62 x new account for janosch@news.netfrag.org
63 x nano /etc/news/nnrp.access
64 x added line: *:Read Post:janosch:janosch:*
65
66 o check out from cvs-repository:
67 o joko/doc -> /home/joko/public_html/computing/overview/topics/
68 o leaded to (A, B and C): see <a href="../topics/home2web.html">home2web</a>
69
70 o added user@netfrag.org:
71 x adduser: collector/colĀ§$
72
73 o about: some sample items occoured 2003-01-17 until 2003-01-26.
74 what to do with that?
75 o have all items stored in other applications conveniently.
76 o be able to have items or references to them *archived* centrally
77 o be able to access informations via *one* interface.
78 actually *multiple* interfaces should be possible
79 - the aim here is to get everything together (INTEGRATE!) (mnoGoSearch first! Torus::Archive later?)
80
81 o refactor topics:
82 o make global-accessible@netfrag.org
83 o introduce subtopics
84 o sysadmin tasks
85 o janosch's, jonen's and joko's tasks
86
87 o start project "admintools" @ nfo/perl/scripts - including
88 o getip.pl
89 o notify.pl
90 x on uml-event: up/down/reboot
91 o on news-post (dispatchmail: mail2news)
92 o on cvs-checkout (done on interval with joko/doc - see above)
93 o on build (build.pl)
94 o some tools from dispatchmail
95 o dispatchmail itself!
96 o
97
98 o [idea] ;-) for symbols (in general)
99 - o = Open Task
100 - x = Closed Task
101 (- [<TopicName>] = name of topic - fixed/proposed)
102 - [<TopicType> by|for <UserName>] =
103 - type of topic - fixed/proposed
104 - username who submitted this item / should this item be assigned to
105 - this could become a language for describing the workflow
106 - this proposal should be the shortcut-form in wiki-style: (e.g. make 'tiki-workflow' from that?)
107 - more verbose (e.g. XML) - forms could/should become possible (e.g. 'WFML') (WorkFlow Markup|Modeling Language)
108 - TODO: refactor this document after further commits to show off refactoring process through cvs-revisioning!
109 o required for this: link to a page which shows the history of a document not as verbose as (e.g.) chora does
110 - d = from 'tbd': to-be-discussed
111 - c = cancelled
112
113 o [idea] ;-) for symbols (in _this_ document here) (parser|engine behaviour modification)
114 - R = from 'tbr': to-be-refactored
115 - r = already refactored elsewhere
116 - an "r" may also mean "reference" ;-)
117 - make 'r-http://netfrag.org/to/another/reference/wrapped/via/http/' possible in documentation
118 - also the shortcut form: [r:/to/another/reference/wrapped/via/http/]
119 - this - and only this - should be the minimalst requried definition of a "reference"
120 - an internet "link" - however needs some more metadata around it: an "url" and a "caption" - what about these?
121 - either fetch them from archive-metadata of this reference ...
122 - ... or use the name directly as caption and build the url against a known redirector handler which
123 accesses the archive-metadata
124
125 o rename "thread" to "newsgroup" in all scripts!
126
127 o what about:
128 Torus::Xyz - solution to reuse concepts of Apache 2 and Cyrus 2!!! (and OpenLDAP???) for building an open collaboration server?
129
130 o word-search: "identify" and "search" for
131
132 </pre>
133
134 </body>
135 </html>

MailToCvsAdmin">MailToCvsAdmin
ViewVC Help
Powered by ViewVC 1.1.26 RSS 2.0 feed