| 73 |
b) human-readable material (e.g.: generated indexes, overviews, details, descent-documents) |
b) human-readable material (e.g.: generated indexes, overviews, details, descent-documents) |
| 74 |
o add collaboration on top of that! |
o add collaboration on top of that! |
| 75 |
o (technical) annotations, pbb, etc. |
o (technical) annotations, pbb, etc. |
| 76 |
|
o what is already there? |
| 77 |
|
x found: ProArc, OpenArc - but nothing seems to be truly *open*! |
| 78 |
|
|
| 79 |
o Gtk Rules | phpRules - an abstract rule chain editor |
o Gtk Rules | phpRules - an abstract rule chain editor |
| 80 |
o modes: dispatchmail, dispatchrequest, ipchains? |
o modes: dispatchmail, dispatchrequest, ipchains? |
| 95 |
flat-file databases (csv, etc.), structured files (INPADOC, XML) and |
flat-file databases (csv, etc.), structured files (INPADOC, XML) and |
| 96 |
oo-rdbms-mappers (orms) - in our case "Tangram" (from CPAN). |
oo-rdbms-mappers (orms) - in our case "Tangram" (from CPAN). |
| 97 |
|
|
| 98 |
|
o Resources, Ontologies, Information Delivery |
| 99 |
|
o RSS, RDF, RDFS |
| 100 |
|
|
| 101 |
o modifier.pl |
o modifier.pl |
| 102 |
o soap <-> rpc-xml |
o soap <-> rpc-xml |
| 103 |
o Tangram-Schema <-> RDF Schema (RDFS) |
o Tangram-Schema <-> RDF Schema (RDFS) |
| 104 |
|
|
|
o Resources, Ontologies, Information Delivery |
|
|
o RSS, RDF, RDFS |
|
|
|
|
| 105 |
o use nntp//rss!!! |
o use nntp//rss!!! |
| 106 |
|
|
| 107 |
o cvssync |
o cvssync |
| 109 |
o option AUTOADD |
o option AUTOADD |
| 110 |
o mode GUI |
o mode GUI |
| 111 |
|
|
| 112 |
|
o sieve & XML??? |
| 113 |
|
|
| 114 |
|
o cvs & kerberos??? |
| 115 |
|
|
| 116 |
|
o enhance Mail::Audit::Dispatch |
| 117 |
|
x recieveMail -> dispatchmail & Mail::Audit::Dispatch |
| 118 |
|
o Mail::Audit::Dispatch::Folder::Mbox (by joko, the main part of the former recieveMail, just uses Mail::Audit) |
| 119 |
|
o Mail::Audit::Dispatch::Spool (by joko, a little part of the former recieveMail, just uses Mail::Audit) |
| 120 |
|
x Mail::Audit::Dispatch::Newsgate (by joko, uses Net::NNTP) |
| 121 |
|
o Mail::Audit::Dispatch::Folder::Cyrus1 (by jonen, acts as sendmail MDA instead of /usr/sbin/cyrdeliver, but re-dispatches to it again after resolving addresses against an arbitrary data source, see 'Data::Map' stuff....) |
| 122 |
|
o Mail::Audit::Dispatch::Faxgate (by janosch, uses /usr/bin/sendfax; still inside 'mail-handler', tbr) |
| 123 |
|
o Mail::Audit::Dispatch::Smsgate (by janosch, uses /usr/bin/yaps; still inside 'mail-handler', tbr) |
| 124 |
|
o could also use /usr/bin/smssend or some module from CPAN |
| 125 |
|
o Mail::Audit::Dispatch::Response (by joko, notifies sender that his/her mail was processed by arbitrary system) |
| 126 |
|
o send autoresponse with subject: "Your bug-request was filed." when mailing to bugs@netfrag.org (done by gateway@netfrag.org) |
| 127 |
|
o actually do file the message at nfo.support.queue (done by gateway@netfrag.org) |
| 128 |
|
o maybe cc: to or integrate with tutos or other ticketing system (bugzilla)???) |
| 129 |
|
o this should be the basic functionality needed to implement known features as "autoresponder" or "vacation" on top of this |
| 130 |
|
|
| 131 |
|
|
| 132 |
|
|
| 133 |
|
|
| 134 |
|
|
| 135 |
</pre> |
</pre> |
Parent Directory
| 
Revision Log
| 
Patch
