CyborgHood: Issueshttps://projects.duckcorp.org/https://projects.duckcorp.org/favicon.ico?16699090422012-01-15T00:45:32ZDuckCorp Projects
Redmine Enhancement #277 (New): Port to Ruby 1.9https://projects.duckcorp.org/issues/2772012-01-15T00:45:32ZMarc Dequènesduck@duckcorp.org
<p>It should not be very difficult, according to my experience with the mail-retrainer script using almost the same libraries.</p> Enhancement #276 (New): Rework event managementhttps://projects.duckcorp.org/issues/2762012-01-15T00:44:03ZMarc Dequènesduck@duckcorp.org
<p>We need to improve the current situation. Our DSL avoids a total mess but is not easy enough to use.</p>
We should have a look at <em>em-synchrony</em>. See:
<ul>
<li><a class="external" href="http://www.paperplanes.de/2011/4/25/eventmachine-how-does-it-work.html">http://www.paperplanes.de/2011/4/25/eventmachine-how-does-it-work.html</a></li>
<li><a class="external" href="https://github.com/igrigorik/em-synchrony">https://github.com/igrigorik/em-synchrony</a></li>
</ul> Enhancement #205 (New): Finish component dependencieshttps://projects.duckcorp.org/issues/2052011-03-12T10:38:26ZMarc Dequènesduck@duckcorp.org
<p>Work on the Config and botnet backend cases, to use DI properly.</p>
<p>Polish other remaining dependency-related work in the core.</p> Enhancement #204 (In Progress): Preliminary CLI Bothttps://projects.duckcorp.org/issues/2042011-03-12T10:34:14ZMarc Dequènesduck@duckcorp.org
<p>This bot would create a CLI interface and also help for debugging.</p> Enhancement #202 (New): Multiple services of the same typehttps://projects.duckcorp.org/issues/2022011-03-04T00:58:08ZMarc Dequènesduck@duckcorp.org
<p>We will transform the core to be able to use Guard to locate services by type and multiplex search requests in order to find the correct ressource(s). The system needs to be able to cope with similar bots and we need to change the bot naming.</p>
<p>To work on something real, we'll work on MapMaker, which is a good example of distributed resources.</p>
<p>We need a network backend, as a local one would not encounter such a situation.</p> Enhancement #201 (New): Auth/Tokens/Locator Bothttps://projects.duckcorp.org/issues/2012011-03-04T00:51:28ZMarc Dequènesduck@duckcorp.org
This bot has multiple usages:
<ul>
<li>be a trusted referee to check bots identity</li>
<li>act as a common trusted party to exchange Tokens (rights)</li>
<li>act as a name service to locate a ressource</li>
<li>anything else related to inter-bot security…</li>
</ul> Enhancement #200 (New): XMPP BEhttps://projects.duckcorp.org/issues/2002011-03-04T00:45:00ZMarc Dequènesduck@duckcorp.org
<p>Preliminary work on the XMMP communication backend</p> Enhancement #199 (New): View personnal and services informationhttps://projects.duckcorp.org/issues/1992011-03-04T00:42:51ZMarc Dequènesduck@duckcorp.org
<p>Be able to view/search infos about oneself and registered services. This is mostly (if not entirely) tied to Librarian.</p>
<p>Until a link with the LdapShadow project is done, something basic needs to be done.</p> Enhancement #198 (New): Stick logs to "areas"https://projects.duckcorp.org/issues/1982011-03-04T00:32:50ZMarc Dequènesduck@duckcorp.org
<p>Logs should be separated into areas, each one covering a certain aspect to the bot process, for example: the communication with other bots, the advertised interface, the executed tasks…</p>
<p>Log4r seems to have useful hierarchical logging features we could use.</p>
This would allow:
<ul>
<li>changing debug level for only specific aspects of the software</li>
<li>adding useful prefixes to the log messages</li>
</ul>
<p>We should also call DI to the rescue.</p> Enhancement #197 (In Progress): Preliminary Order Bothttps://projects.duckcorp.org/issues/1972011-03-04T00:00:52ZMarc Dequènesduck@duckcorp.org
<p>This bot should receive orders from Postman, store it somewhere, ACK Postman (which can then mark the mail), process orders, generate report, and send the reply to the same incoming medium back to Postman. Postman should find back the request mail using some kind of reference passed to Clerk, create a reply mail from it, insert the report, and send it.</p>
<p>So, the processing and reporting logic needs to be moved out of Postman, and it needs to be adapted for this new interraction.</p> Enhancement #196 (New): Zone editionhttps://projects.duckcorp.org/issues/1962011-03-03T23:36:32ZMarc Dequènesduck@duckcorp.org
<p>Implement the zone editor and alter() methods for zones.</p>
<p>We need some kind of micro-language to add/remove/replace RRs.</p> Enhancement #178 (New): Use LdapShadows backend in the Librarian Bothttps://projects.duckcorp.org/issues/1782010-10-31T18:16:46ZMarc Dequènesduck@duckcorp.org
<p>Use LdapShadows as a bridge to LDAP, using its abstraction without ever taking care of low-level LDAP concepts (so that we don't care about implementations and maybe one day someone would find easier to add an SQL backend). Work with LdapShadows project to have a properly designed API.</p> Enhancement #130 (New): Resource lockinghttps://projects.duckcorp.org/issues/1302010-08-16T01:28:54ZMarc Dequènesduck@duckcorp.org
A locking mechanism is necessary to ensure concurrent access don't tread on each other:
<ul>
<li>do not allow write when someone else has requested an exclusive access to the resource</li>
<li>delay read when someone is writing</li>
</ul>
<p>A lock is released when the client ask for it, or when it leaves and his session is removed.</p>
<p>We should care about dead clients to avoid deadlocks.</p> Enhancement #129 (New): Kick dead clientshttps://projects.duckcorp.org/issues/1292010-08-16T01:28:08ZMarc Dequènesduck@duckcorp.org
<p>We should have some PING/PONG mechanism to kill dead clients.</p> Enhancement #106 (New): Test suite needed -- mail chainhttps://projects.duckcorp.org/issues/1062010-06-19T21:02:56ZMarc Dequènesduck@duckcorp.org
<p>At least a few components, which should be stable, should be tested for regressions.</p>
The mail chain is very sensitive, so at least this part should be done:
<ul>
<li>craft fake mails singlepart or multipart</li>
<li>check headers/body decoding and reencoding</li>
<li>test sign/crypt combinations</li>
<li>parse result as if it was received from IMAP</li>
<li>check decrypt/sign_verify</li>
<li>check content</li>
</ul>