Skip to content. | Skip to navigation

Sections
You are here: Home content generated doc.free neda Records 201105011 Presentation articleEn

BLEE (ByStar Libre Emacs Environment):
A Deeply Integrated Emacs User Environment For the Software-Service Continuum
LinuxFest NW 2011

Document #record-201105011
April 29, 2011

Article and Presentation Available on-line at:
http://www.neda.com/Records/201105011

Mohsen BANAN
E-mail: http://mohsen.banan.1.byname.net

Copyright © 2011 Mohsen BANAN

Permission is granted to make and distribute complete (not partial)

verbatim copies of this document provided that the copyright notice

and this permission notice are preserved on all copies.

Contents

I  Introduction – What Is Blee
1 What Is Emacs?
 1.1 Emacs Is:
 1.2 Blee Is:
2 What Are ByStar Libre Services
 2.1 Libre Services: A non-proprietary Model
 2.2 From Free Software To Libre Services
 2.3 What Is ByStar
 2.4 Layering of Concepts and Results
3 Roadmap
II  Language, Definitions, Models and Concepts
4 Concepts and Definitions Summary
 4.1 Nature Of Poly-Existentials
5 Some Definitional Criteria
 5.1 Libre Services: Definitional Criteria
 5.2 Autonomous Libre Services
  5.2.1 Autonomous Libre Services: Definitional Criteria
  5.2.2 Autonomous Libre Services: Degrees of Trust and Autonomy
  5.2.3 ByStar Autonomous Libre Services
 5.3 Federated Libre Services
  5.3.1 Federated Libre Services: Definitional Criteria
6 Some Modeling Concepts
 6.1 Software - Service Continuum – Where Proprietary Looses
  6.1.1 Protocols Hour Glass – Note Convergence in the Middle
  6.1.2 ByStar Hour Glass – Importance of Convergence in the Middle
  6.1.3 Service, Desktop, Laptop, PDA Continuum Libre everywhere
7 Some Societal Concepts
 7.1 Ivan Illich’s Concept of Convivial Tools
  7.1.1 Convivial Software
 7.2 Halaal and Haraam – Ethics of Software and Service
  7.2.1 Halaal and Convivial Software Quadrant
III  The Blee Model
8 Interface Model of ByStar User Env and ByStar Services
9 ByStar Libre Emacs Environment (BLEE) Model
10 An Over Distro Model
 10.1 General Nature of Under, At and Above Distro Activities
 10.2 The ByStar Over Distro Development Model
 10.3 Design Big, Implement Gradually
IV  ByStar Vertical Slices (Feature Families)
11 ByStar Vertical Slices
 11.1 List of Vertical Slices
12 ByStar Email / Messaging Vertical Slice
13 CMS / Plone Vertical Slice
14 Self Publication Vertical Slice
 14.1 ByStar Content Publication Model
 14.2 ByStar Content Publication Workflow
 14.3 ByStar Content Publication Architecture
15 Auxiliary Vertical Slices
 15.1 ByStar Music Vertical Slice
V  Framework For Participation, Collaboration and Guardianship
16 Collaborative Development Framework
17 The Collaborative Model From Concept To Service Delivery
 17.1 Spread The Word
 17.2 Key Documents

List of Figures

Preface

Hello, Salaam.

My name is Mohsen BANAN.

I am a Software Engineer.

I offer you these thoughts as part of the Internet Engineering Profession’s responsibility to Society and Humanity.

I solicit your feedback and welcome your comments.

The title of this presentation is xxxx.

With your comments and feedback you can reach me at: contact or email me at feedback@mohsen.1.banan.byname.net.

About This Document

This document is web published as Records-201105011 at: http://www.neda.com/Records/201105011.

Part I
Introduction – What Is Blee

1 What Is Emacs?

1.1 Emacs Is:

Emacs Is:   

Emacs Is A Good Way Of Living

  • Emacs is the n’est plus ultra editor
  • Emacs is a rich lisp engine
  • Emacs is an editor centered user environment
  • Emacs is an integration platforms
  • Emacs is lots of applications
  • Emacs is Halaal – Libre/Free
  • Emacs is Convivial

1.2 Blee Is:

Blee Is:   

Bystar Libre Emacs Envirnoment

  • Blee is a layer over Emacs
  • Blee is Emacs integared with the Firefox and Gnome
  • Blee is Emacs intgrated with Bystar Autonomous Libre Service
  • Blee is Emacs made easy for out of the box usage

2 What Are ByStar Libre Services

2.1 Libre Services: A non-proprietary Model

Libre Services: A non-proprietary Model for delivery of Internet services  

A non-proprietary Model
for
delivery of Internet services

Free Software Ideology For Internet Application Services

2.2 From Free Software To Libre Services


PIC

Figure 1: From Free Software To Libre Services


2.3 What Is ByStar

  • By* is a coherent framework for enabling complex interactions among people, businesses and information.
    • Small and Medium Businesses: ForSMB.net Individuals:
    • ByName.net, ByAlias.net, ByMemory
    • Places and Events: ByWhere.net, ByEvent.net
    • Information: ByTopic.org
    • For Interactions: ByInteraction.net

2.4 Layering of Concepts and Results


PIC

Figure 2: Layering of Concepts and Results


3 Roadmap

  • Language, Definitions, Models and Concepts
  • The Blee Model
  • Blee Horizontal Capabilities
  • Blee Vertical Slices (Feature Families)
  • Getting Blee

Part II
Language, Definitions, Models and Concepts

4 Concepts and Definitions Summary

  • Libre Services
  • Autonomous Libre Services
  • Federation of Autonomous Libre Services
  • Nature of Poly-Existentials
  • Tools For Conviviality
  • Halaal and Haraam

4.1 Nature Of Poly-Existentials

  • So Called Western IPR is in conflict with Nature
  • What Are Poly-Existentials:
  • Multi-Possessabilty
  • Ownership is a one-to-one relationship
  • An Ownership Mistake With Ramifications Broader than Slavery
  • Pointer to PLPC – Full title in box

5 Some Definitional Criteria

5.1 Libre Services: Definitional Criteria

  1. The service must consist entirely of open-source & free software components
  2. The service must be based entirely on patent-free protocols
  3. The integration software must consist entirely of free software

Hence the entire service is reproducible and modifiable based on access to source code

5.2 Autonomous Libre Services

5.2.1 Autonomous Libre Services: Definitional Criteria

  1. Service Transparency – Libre Services: Definitional Criteria
  2. Service Portability – Libre Services: Definitional Criteria
  3. Data Portability (from hosting/provider to hosting/provider)
  4. Non-Retention of Data (by host/provider)
  5. End-To-End Non-Restrictivity

5.2.2 Autonomous Libre Services: Degrees of Trust and Autonomy
  • User Owned – Provider Managed
    • Libre Shared Hosting Subscriber SLA, AUP
    • Libre Shared Hosting Advertisment SLA, AUP
  • User Owned – User Managed
    • Libre Center Co-location / Dedicated Hosting
    • Cloud Based Hosting
    • At User Premise – your own machine and dedicated IP Address

While All Is Supported, The Guarantee of “At User Premise” option should always be maintained.

5.2.3 ByStar Autonomous Libre Services
  • Individual (Named, Living) – ByName.com - ByName.net
  • Individual (Alias, Living) – ByAlias.com - ByAlias.net
  • Individual (Minor) – ByFamily.com, ByFamily.net
  • Individual (Named, Deceased) – ByMemory.com - ByMemory.net
  • Individual (Information) – ByAuthor.net, ByAuthor.com
  • Families – ByFamily.com, ByFamily.net
  • Small/Medium Businesses – BySMB.net, ForSMB.net Domain is usually redirected to business’s domain
  • Locations: ByWhere.net

All of These ByStar Autonomous Services are available as Shared Hosting, Dedicated Hosting, Colocation and ByStar Appliances.

5.3 Federated Libre Services

5.3.1 Federated Libre Services: Definitional Criteria

  1. Service Transparency – Libre Services: Definitional Criteria
  2. Service Portability – Libre Services: Definitional Criteria
  3. Public Data Designated By Autonomous Libre Service
  4. Safeguards of Private Data and Non-Retention of Data on command
  5. Logs confidentiality and transparency
  6. Based on Facilitation of End-To-End Interactions

6 Some Modeling Concepts

6.1 Software - Service Continuum – Where Proprietary Looses

Service, Desktop, Laptop, PDA Continuum Free/Libre everywhere

Hour Glass= Diversity on Top – Diversity at the Bottom – Cohesion and Convergence in the middle

Consistent OS: Linux everywhere Consistent GUI: Gnome everywhere Consistent Applications: Emacs, ... everywhere Deep, Broad and Consistent Integration through Free Software and Libre Services

6.1.1 Protocols Hour Glass – Note Convergence in the Middle


PIC

Figure 3: Protocols Hour Glass – Note Convergence in the Middle


6.1.2 ByStar Hour Glass – Importance of Convergence in the Middle


PIC

Figure 4: ByStar Hour Glass – Importance of Convergence in the Middle


6.1.3 Service, Desktop, Laptop, PDA Continuum Libre everywhere
  • Consistent OS: Linux everywhere
  • Consistent GUI: Gnome everywhere
  • Consistent Applications: Emacs, ... everywhere

Deep, Broad and Consistent Integration through Free Software and Libre Services

7 Some Societal Concepts

7.1 Ivan Illich’s Concept of Convivial Tools

Tools are intrinsic to social relationships. An individual relates himself in action to his society through the use of tools that he actively masters, or by which he is passively acted upon.

To the degree that he masters his tools, he can invest the world with his meaning; to the degree that he is mastered by his tools, the shape of the tool determines his own self-image. Convivial tools are those which give each person who uses them the greatest opportunity to enrich the environment with the fruits of his or her vision. Industrial tools deny this possibility to those who use them and they allow their designers to determine the meaning and expectations of others. Most tools today cannot be used in a convivial fashion.

7.1.1 Convivial Software
  • Unix/GNU Vs Microsoft Windows
    • Unified file model, pipe, small dedicated progs, ...
  • Emacs vs Vi
    • buffers, major-modes, minor-modes, key-maps, frames, windows, regions,
  • qmail vs sendmail
    • complete separation of queuing and spooling from submission, delivery and protocols.

Enable the tool user to be creative and expressive

7.2 Halaal and Haraam – Ethics of Software and Service

  • Halaal means Moral/Ethical – Okay to do/consume
  • Haraam means Immoral/Unethical/Harmful – Should Not Be Done/Consumed

Defining Halaal Software/Internet Service:

  1. Is A Perpetual Transparent Modifiable Poly-Existential – Equivalent of “Free Software”
  2. Its Use Has Been Endorsed By The Engineering Profession
  3. Its Use Has Not Been Prohibited By Ethicists (Sources of Emulation)

7.2.1 Halaal and Convivial Software Quadrant


PIC

Figure 5: Halaal and Convivial Software Quadrant


Part III
The Blee Model

8 Interface Model of ByStar User Env and ByStar Services


PIC

Figure 6: Interface Model of ByStar User Env and ByStar Services


9 ByStar Libre Emacs Environment (BLEE) Model


PIC

Figure 7: ByStar Libre Emacs Environment (BLEE) Model


10 An Over Distro Model

10.1 General Nature of Under, At and Above Distro Activities


PIC

Figure 8: General Nature of Under, At and Above Distro Activities


10.2 The ByStar Over Distro Development Model


PIC

Figure 9: The ByStar Over Distro Development Model


10.3 Design Big, Implement Gradually

Design Big, Implement Gradually

Autonomous First

Convivial Design

Part IV
ByStar Vertical Slices (Feature Families)

11 ByStar Vertical Slices

  • Functionality’s that span
    • ByStar User Environment
    • ByStar Autonomous Libre Services
    • ByStar Federated Libre Services

11.1 List of Vertical Slices

  • Primary Vertical Slices
    • Email / Messaging (qmail) ByStar Vertical Slice
    • CMS / Plone ByStar Vertical Slice
    • Self Publication Vertical Slice
    • Integrated Public Key Infrastructure
  • Auxiliary Vertical Slices
    • Music (Audio) Vertical Slice
    • Photo / Video Gallery
    • Genealogy
    • eFax/Scanning Document Management Service
    • VoIP

12 ByStar Email / Messaging Vertical Slice

  • qmail based
  • Single Domain, Multi-Address. Multi-Mailbox Model
  • Gnus under Blee
  • embedded MTA on User Environment
  • Libre Texting, Push Email
  • NOTYET, qmail figures come after this.

13 CMS / Plone Vertical Slice

  • ploneProc.sh

14 Self Publication Vertical Slice

  • More Info at: http://www.neda.com/PLPC/110506
  • Adopted Components: TeX, XeTeX, tex4ht, Plone
  • ByStar Modules: lcntProc.sh, Libraries
  • In Blee: Menu Supported
  • Supporting Autonomous Services: ByName, ByAlias, ByMemory
  • Supporting Federated Services: ByContent, ByTopic

14.1 ByStar Content Publication Model


PIC

Figure 10: ByStar Content Publication Model


14.2 ByStar Content Publication Workflow


PIC

Figure 11: ByStar Content Publication Workflow


14.3 ByStar Content Publication Architecture


PIC

Figure 12: ByStar Content Publication Architecture


15 Auxiliary Vertical Slices

  • ByStar Music
  • ByStar Photo/Video Gallery
  • ByStar Genealogy
  • ByStar Fax/Scanning (Document Management System)
  • ByStar VoIP

15.1 ByStar Music Vertical Slice

  • Adopted Components: mpd, mpc, mplayer, emms
  • ByStar Modules:
  • In Blee: Menu Supported
  • Supporting Autonomous Services: ByName, ByAlias, ByMemory, BySMB

Part V
Framework For Participation, Collaboration and Guardianship

16 Collaborative Development Framework

  • Working Together ...

17 The Collaborative Model From Concept To Service Delivery


PIC

Figure 13: The Collaborative Model From Concept To Service Delivery


17.1 Spread The Word

  • I don’t Own By* Libre Service – You Don’t Own By* Libre Services
  • We All Own By* Libre Services
  • Use It As You Wish – Make It Be What You Want
  • Stay Autonomous
  • Spread The Word

17.2 Key Documents

  • Neda Open Business:
  • By* Libre Services Libre Services Manifesto PLPC-100105
  • ByStar full picture PLPC-110004
  • Unsolicited Proposal PLPC-110005
  • By* Libre Texting

Colophon

This document was produced with Halaal Software and is published using Halaal Internet Services.

It uses LaTeX, beamer, ByStar, Blee, Emacs, ...

Colophon

  • Totally Libre and Copyleft
  • No proprietary software used in preparation, presentation and communication of this information
  • Slides prepared with beamer-latex
  • Presented using Ubuntu-Debian-GNU-Linux and Maemo on PDA
  • Served as an Autonomous Libre Service using Debian, Apache, Plone, ...

Questions/Comments/Discussion

Document Actions
Libre/Halaal Internet Services Provided At LibreCenter By Neda

Member of By* Federation Of Autonomous Libre Services

This web site has been created based exclusively on the use of Halaal Software and Halaal Internet Application Services. It is part of the By* Federation of Autonomous Libre Services which in turn are part of the Halaal/Libre By* Digitial Ecosystem which incorporate the following software components: