Sameboat IRC Groups

The IRC Channel Group is an abstraction of a set of related channels and is the primary and a driving use case of the Sameboat Groups mechanism and supporting domain space infrastructure. While fully general for any interest area, I am specifically targetting the category of programming language channels with the initial implementation of the group domains below.

As an exception to the general rule that group members must be AKPERSONs, social network induction and authentication in an aggregated channel that supports TLS will be sufficient for admission to these five group domains, unless and until the group membership decides otherwise.

The aggregated channel rosters below are those for alpha/rollout and are expected to be augmented during that development phase. Additional lang specifics in the context of the grand scheme of domain space are noted.

  • haskell.sameboat.network

    Unifies the haskell-* channels at libera. Haskell is the lang of choice for end application development in domain space. Additionally it has a role in middleware and (natural) lang independence in systems applications. In the AC SPA, the haskell plane operates in the context of the specious present realtime of the DCP discourse agent WorldControl and presents a haskell shell for the knowledge engineers' use in processing the Now Sentence.
  • lisp.sameboat.network

    Unifies these libera channels: #clojure,#commonlisp,#lisp,#lispcafe,#scheme . Lisp is one of two of the main systems development langs for domain space and the DCP. The lisp part of DCP is called "Lateral R" or just LR. Most function is actually in lisp, LR is larger than LL and the lisp plane of the AC SPA presents a lisp shell generalized over the four main CL implementations ACL, CCL, LW, and SBCL The adminstrative DCP agent Patternmaster has the lisp nature and is available for use in irc channels. MCP/MCS which is an operating system abstraction over individual base operating systems constitutes a Lisp OS.
  • prolog.sameboat.network

    Primarily serves ##prolog.libera.chat. Prolog is the other main systems development lang for domain space and the DCP. The logtalk/prolog part of DCP is called "Lateral L" or just LL. The prolog part of DCP has a user facing part and a operator plane in the AC SPA. While the top level of LL is logtalk, most of the rest is ordinary prolog and the prolog shell supports Ciao, Yap, and SWI. The DCP agent JuanDaugherty has the prolog nature, is available for use in IRC channels and is the general representative agent for domain space.
  • python.sameboat.network

    Unifies the #django-* and #python-*.libera.chat channels. Python is used in the backend of the domains CMS. Devops users working with DCMS can access the embedded python pkgs in that role.
  • smalltalk.sameboat.network

    Primarily serves #squeak.libera.chat. Smaltalk, specifically Squeak, is used as the GUI of choice for DCP and MCP operator interfaces.
During the first DCP/MCP ops supporting the alpha/rollout, resource quotas will initially have high limits even for non AKPERSONs. These will be reduced as load increases to their production levels on exit from alpha. This principally affects the use of videotelephony with the native jitsi backend and creation of MCP nodes. In terms of the general entitlement scheme, Y is the user class for which the quotas are normed. If the free rider load is low, it will be possible to have higher quotas for the sub Y classes and/or deeper annual subscription discounts.
Most of these group domains' are expected to choose an administrator by use of the group election mechanism. I don't expect to retain that role except possibly for smalltalk due to expected relatively low interest there. If a non AKPERSON is so nominated, a manual intervention will be made in the case where I know the nick to be that of an establisthed member of the lang channels before sameboat aggregation.