Towards an Emergent Concept of Task Scheduling and Ontology

After reading an article, this morning, in the Taskwarrior documentation[1] — specifically, an article about the Taskwarrior JSON Format[2] — I thought it would be well to take pause and develop an orthogonal concept.

... an orthogonal reference to the iCalendar data record format[3], as concerning syntaxes of duration strings, in programmatic data records for regularly/periodically occurring event data expressed in iCalendar formats[4]  — to denote a thesis statement, in albeit an abstract sense, as regarding:  Internal representations of data record values, within programmed data systems.

Some Thoughts — Initial Thesis Arc

• Data registers — historically, cf. MIT CADR and the original Motorola microcontrollers
• Data record formats — cf. Common Lisp type system, and C type types system, primarily to a juxtaposition of structure data types (i.e CLtL2/CLOS/MOP structure-class implementation[s] and C 'struct')
• Data interpreters and unambiguous grammars (cf… awk? Mathematics of finite state machines, graph theory, abstract principles; a leap to BNF, parser generation, and parser applications; Common Lisp readtable, CLtL2 standard syntax; read/eval/print loop; case study, de.set.atn and de.setf.xml)
• Sidebar: Code alignment, in Common Lisp programs. cl-json
• The shiny thesis punch-line — albeit, arriving too late in the dissertation
• The pragmatic outro — tip of a hat to the development cloud?? 

Some Thoughts — Secondary Thesis Arc

• Measurement Theory
• Units of Quantity, Units of Measurement, Mathematical Interpreters, floating-point errors, and the Igneous-Math codebase
• Duration of Time as a measurable quantity
• Generic encoding for duration of time, in a format of a constant value as may be added or removed to a numeric time coordinate value encoded as Common Lisp universal time
• Juxtaposition: UNIX Epoch Time

Immediate Considerations:

• Installing Taskwarrior Server on FreeBSD
• It uses JSON, therefore probably needs an HTTP sever
• NGinx on FreeBSD
• Chroot virtual jails in FreeBSD
• Creating a virtual jail
• Virtual networking for virtual jails
• Load balancing for virtual jails, using PF
• HTTP auth methods may include: Kerberos (SPNEGO?). 
• Client support TBD
• Configuration
• Alternative: LAN/SDN/VPS config
• Denoted in the previous
• Alternative: Third Party Hosted config
• Shout out to a company with support staff for the hosted config
• Installing Taskwarrior client applications
• ... Android client  
• … client … PyGTK [FreeBSD; Debian 8; GTK on MSFT8.1?]
• … client … ncurses [FreeBSD; Cygwin; Debian 8]
• And why not right now: "Because"
1. Too immediate
2. Too many opportunists
3. Free Software Estate / Free Beer Elite ?
4. No Solution
• Chalking-Up Point and Mark
• What this began as; A search for a simple task management platform, such as might be available on the FreeBSD operating system, and as might be available without it requiring that an enterprise grade cafeteria or stew kitchen -- complimentary with kitchen sink -- be installed on a LAN server, viz a viz. brand Enterprise(TM) portal applications
• What this became, at this article: An initial design sketch -- the author fails to note clearly -- for a definition of data records as may be able to read Taskwarrior protocol messages (JSON structures) in Common Lisp
• What this will not be: 
• Will not be: A sly effort for co-opting Taskwarrior. It's not a business hacking project, this, it's a "success," in and by a technical extension project.
• Will not be: A leverage for making an academic career, "Finally and at last!" within a really terribly rough time, academically, with some "Universities" -- mitigated only by the selection of an online "School", for all the costs of it however. 
• Will not be: A pointed divergence to an entirely orthogonal design
• Will not be: Rise of the Lords of Lambda Dance, The Great and Final Emergence of Lisp Politics, the Cloned Wars, or of The OS named, Thing That Should Not Be(TM)
• But might be: A carrier for. finally and this day, a shout/out for a Metallica song, noted in the previous itemized list item. It's a darker sounding kind of hard rocking song by Metallica(TM)
• What this is, presently: This is a 'blog article. "Ciao!"
• Ed. note: The "Emergent" keyword in the title, that kinda throws it.
• There was an emergent concept - towards a view about moreso a data model for data records in a task scheduling  application, namely Taskwarrior -- albeit, initially, to no single application, in Common Lisp, therefore a data model without communications encoder, channel, decoder or receiver models, abstractly -- but including a concept: That Common Lisp may be applied in this system. It's even listed in the FreeBSD handbook, albeit not a compiler LoL.
• Between the first and second edits of this article, the concept of an emergent concept -- as was being addressed of this article -- had appeared as though to cease to emerge, as a concept.
• Presently, to a matter of ambiguity: The phrase, "Towards an Emergent Fum" might seem as if to suggest as though there was not already an existing Fum in the known universe of discourse -- a grammatical irony, certainly, in that with the instance of the original title of this article, the original title could be kerned as so, and it be more to the original point: Towards [SP] an emergent concept [SP] of task scheduling [ELLIPSIS] s/o to the Enterprise Common Lisp wizards beyond the green curtain (SNARK)
• Thus, the initial title of the article -- in all the expedience of the article's initial authorship -- the title, "Towards an Emergent Concept of Task Scheduling", did not serve denote the full concept that the author had wished to develop of the article. 
• To the author's own short recollection, this article was begun simply at the nearest concept that the author wished to develop. It was, in fact, an article begun in the Blogaway app on an Android thin client computer. 
• Not as if to shunt a development community of either empathy or culture -- as with regards to not presently developing Common Lisp altogether, if one is not, with no further discussion about the sustainability of purely academic projects -- it was rather a simple concept of a data structure, at the onset of this article -- focusing, albeit in short note at the time, about the syntax of a duration data type defined in iCalendar. 
• Not as though to indulge here on a Sunday afternoon, perhaps this lengthy discussion may now serve to bring the article, succinctly enough, back around towards its, albeit poorly stated point
• In its second major revision, this article is now titled as so: Towards an Emergent Concept of Task Scheduling and Ontology
• The phrase, "And Ontology," perhaps may serve to add a unique sense of emphasis to the title, as towards a broadening view of an applicability of ontology in data systems
• However, in such proximity to a discussion about Common Lisp, perhaps the phrase may seem as if to add a suggestion as though it was to become a thesis derailed in whatsoever, derailed of a concept of either Passive A.I or the mythical Non-Passive A.I -- both being concepts that the author prefers to simply not create stories of.
• So, the phrase "And Ontology" may need a further lexical qualification
• This article will presently diverge to a secondary thesis, in introducing a concept of ontology
• What does the author know about ontology? (ad hoc syntax)
• Knowledge expression in a tuple format: 
• Subject_1, for instance, an RDF resource denoting a lunar location, "Dark side of the moon"
• Predicate_1, for instance, and RDF property denoting a relation such as "Is the location of"
• Object_1, for instance, an RDF resource denoting a philosophical enigma, "Narrator of that song by Pink Floyd"
• Predicate_2, an RDF property, "referenced from"
• Object_2, e.g. "That one song by the band, Pink Floyd"
• We may then express the relation in the song, succinctly
• M = {Subject_1, Predicate_1, Object_1}
• Furthermore, we may make note of the source of the reference, given that available data
• N = {M, Predicate_2, Object_2} 
• Thus, object N expresses a reification of an existing tuple, namely in a relation of tuple as Subject
• The applicable role of reification as a method for bibliographical citation in ontological data structures -- is that, as yet, undiscovered concept, might it be, in so much reflection of all the Huge Data? 
• Given the "Given axioms" as presented:
• Anyone whom may legally access both of objects N and M -- as data objects, with no present review of objects denoted by the data -- essentially anyone then should be able to review the definition of M for its reference denoted in N, and likewise to review object N for the statement that it is drawn to, in the bibliographical reference, namely object M
• Thus; This describes a method for making albeit a non-narrative data reference with a peer-reviewable reification format, in a manner of a bibliography
• How could this be relevant? In reviewing details of a crisis, it avoids all of a coroner's view of the data.
• Inasmuch as it being a non-narrative statement -- not an article, not a report, not a book in itself -- the author sincerely does not want to decompose all of language into tuples. If it seems that there are methods for such deomposition, certainly it may serve as to comment to the essentially communicative nature of language. Presently, author is presently unwilling to decompose -- if any arbitrary regards -- to arbitrarily decompose language into any smaller expressions than of the individual list items of an individual itemized list, in the hope that it may serve as a reading aid to the inevitably busy reader whom might otherwise entirely dismiss this article from the reader's own attention, as with a remark, "TL;DR". The irony.
• Of course, in developing this article now as albeit a lengthy itemized list, it might seem to approach the limits of the itemized list as a format for human communication.
• Furthermore, ontologies may be applied in study of non-crisis-oriented resources
• Literary applications
• Applications in archaeology
• Applications in aiding with consumer selection of mass-produced commercial goods
• Applications in aiding any number of  service help desk personnel for selection of knowledge base articles, for resolution of consumers' personal if not primarily technical concerns -- even if the knowledge base itself is as wide as the entire The Internet, at any single instance of time -- though likewise preserving something with regards to privacy in any single consumer-support relation, as per any support personnel's own sense of professionalism, if not moreover the structure of a support system in itself.
• ...likely ever in assisting to ensure that any crisis N will not emerge, even if a crisis M may be already underway.
• Perhaps, ontologies may be applied even in a study of an abstract concept of crisis, in itself
• It might seem as though to entail a sort of coroner's view, however
• Thus, objectivity.
• ...and moving on, literally?
• Shout-out to the coal miners and metallurgists of Donbass.

Footnotes

[1] http://taskwarrior.org/docs/
[2] http://taskwarrior.org/docs/design/task.html
[3] http://tools.ietf.org/html/rfc5545

[4] http://tools.ietf.org/html/rfc5545#section-3.3.6

On locating Taskwarrior - An Overview of Projects

Earlier this morning — here on the very day after Independence Day, 2015 — I had decided to run a web search as to inquire, in a sense, about the availability of web resources concerning any single concept of a supoort for project management, on the FreeBSD operating system. In addition to a short page about project management within the FreeBSD Project, itself — with an observation, as by contrast, that one may only hope as though there could be such any single page published, as in any ways analogously, of the entire Debian project, today[1] — I also found a short index of projects hosted at SourceForge.net[2]. I'm writing this article with the Blogaway app, this morning — I will provide a note to any corresponding web resource locators, in footnote form, along with any prosaic footnotes. As ever, #GIYF.

What I have found — as resources corresponding with this morning's web search — firstly, there is the Taskwarrior project[3], as hosted at SourceForge.net, and there is the corresponding Taskwarrior web site[4]. (Presently, I'll continue this article with the Blogger web client.)

Towards a Comment in Contextual Computing - FreeBSD on LAN

Personally, as immediately previous to this morning's web resource search, I have been developing a small set of notes, around a study of the PF firewall -- as was forked from its original development in OpenBSD, then introduced into the FreeBSD base system.[5] In a manner chronologically previous to that study, I'd developed an albeit ad hoc and nearly arbitrary configuration for the IPFW firewall[6], in configuring a simple network address translation service for a LAN gateway.

As something of an orthogonal comment, perhaps towards a sense of context: The single laptop-based server now providing the LAN gateway, in its FreeBSD root (UFS) and swap partitions, it comprises what's been my own first installation of FreeBSD, in a "Bare metal" regards. Previous to the installation to the PC, I'd installed FreeBSD into a VirtualBox guest system, using the FreeBSD virtual machine VMDK image .The VirutalBox Guest system, however, howas running on a proprietary desktop operating system. Though I had thought that it could make for something of a comfortable desktop arrangement, but I thought I would be more comfortable with a "Bare metal" installation.

Following to the installation of FreeBSD (amd64) in developing a LAN gateway appliance for my small GraniteLAN, I've now installed FreeBSD on the laptop where the other proprietary operating system is installed. That laptop, now, is also booted continuously to FreeBSD. It's tasked out, on my LAN, as it providing a small set of filesystem services and software compilation services for the LAN. Though, candidly, I've yet to configure a complete package repository of on that laptop, but I'm certain that such a service would correspond well to the package build automation service.  In the latter regards, I've begun to work out something for a configuration in applying the FreeBSD Poudriere tool, for building sets of packages as corresponding to individual host profiles -- building thee same, all with /etc/make.conf configured as follows, namely in regards for a machine-specific compiler optimization and (viz a viz -j4) parallel build configuration:

## cf. /usr/share/examples/etc/make.conf

CPUTYPE?=core2
# See also: /usr/src/share/mk/bsd.cpu.mk

#BDECFLAGS=     -W -Wall -ansi -pedantic -Wbad-function-cast -Wcast-align \
#               -Wcast-qual -Wchar-subscripts -Winline \
#               -Wmissing-prototypes -Wnested-externs -Wpointer-arith \
#               -Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings

CFLAGS+=        -msse3
CXXFLAGS+=      -msse3

COPTFLAGS?= -O -pipe -j4

Essentially, that serves in creating a certain species of platform definition, namely in creating a set of packages compiled for amd64 architectures, core2 CPU type, moreover appyling those specific compiler optimizations. Though it was a rather functionally easy thing, to begin to develop that configuration, but I have not wanted to rush around to the point of applying it together with Poudriere and HTTP, even on my own small LAN. My being of an impression that there must certainly be some things that I've yet to completely work out, as with regards to such a framework, in its present configuration-- focusing about the package builder and hypothetical package distribution services, namely -- I've not wanted to get the cart situated before the horse, in those services. Perhaps the matter of it defining a species of architecture may be the next thing that I may take to consideration, at that -- towards then defining a second species of architecture for package-building with a cross-compilers configuration and package distribution on the same LAN, namely for an armv6/granite architecture. The "Granite" tag -- essentially, synonymous with "Prototype", in that application -- it would denote that it is a local architectural configuration for GraniteNet,

So, but previous to any further development for a package build/distribution service, I've wanted to adapt the GraniteLAN gateway appliance to use PF instead of IPFW. Not as though to make any sort of a negative impression about IPFW, it was simply a first choice for the LAN gateway appliance. At the time of my having just recently installed FreeBSD to the LAN gateway, I wasn't altogether certain of whether to apply PF, IPFW, or IPF for the initial network address translation services for the gateway.  As I recall, the IPFW documentation had simply seemed a little easier for me to understand, at the time. Now after having found some repeated concerns with regards to FTP PASV transfers across the LAN gateway, in its present IPFW  configuration -- even inasmuch as to retrieve, simply, a PDF edition of the FreeBSD handbook -- I've begun to read the further documentation about PF,

As corresponding to that matter of a simple study, this week -- and and not as though to crowd out any manner of attention from any of the existing projects for firewall appliance operating systems deriving of FreeBSD, such as OPNsense and, comparatively, pfSense -- I'm now of an impression, candidly, that PF may be one of the most advanced firewall systems available for a free/open source operating system. After reading the pf.conf manual page[7] with it converted into a PDF format for PDF annotation, furthermore in keeping abreast of my own observations, with a single note in my Evenote notes, I've begun to develop a small number of firewall appliance profiles, as in bouncing some ideas off of the pf.conf documentation, and in consideration of my own present range of studies -- such as, towards a concept of applying pf.conf for a hospitality network firewall, and towards applying pf.conf in a firewall for a WAN-to-Hughesnet gateway correspondingly.  The idea, to my thinking, is to be able to support the convenience of wireless access points, at rural recreational destinations -- ideally, as in coordinating with hospitality service providers, if having previously arrived to any opportune arrangements with hardware and network service providers and distributors, in endeavoring to make it a commercial opportunity, realized with steady management, -- as rather than it becoming any kind of a a radically emergent manner of thing, as if removed from management at any single hospitality location. I mean, it's a business idea, not a "Flash mob" thing.

It will, of course, will need be made with some careful coordination over time, if it may ever become a well managed business idea. It being nothing of any proprietary manner of design, moreover, it's just as well to me, to share these comments about that -- one of my own business ideas, as such -- here in my own tech notes web log, online.

In regards to a quality of service, in a commercial sense: Personally, I've seen how very harsh the comments are, from some many of the critics of free Android applications, in their comments about Android applications at Google Play. I think, it kind of presents a sort of a an immediate barrier, moreover, as with regards to Android application development altogether. Personally, there is not a chance on or beyond earth that I would ever be willing to develop any manner of a free application if it could be in any ways as if to flatter such an ungrateful lot of users. I'm not even of an idea to develop any sort of a for-fee application, to such a community of fundamentally immature, essentially mean Android users, if it may in any ways entail that I should have to encounter such a lot of impulsive, if not abusive rubbish in any manner of providing customer support.  Perhaps it may have something to do with how convenient the Google web experience is, to such critics?

I am not of an impression as if it ruins all of the Google Android platform, though I am quite sure it serves to ask for some further consideration -- such as to how one may endeavor to provide any manner of a professional user support, for any professional manner of user community. Certainly, I hope Google will continue to "Leave the door open to us," to choose among any number of available options in such regards, for those of "us" who would be Android application developers -- assuming that I would make a commitment, of my own  voluntary consideration, to develop applications on the Android platform. Of course, there's also Firefox OS, from the Mozilla foundation -- Linux and Gecko, essentially -- and there's Tizen, from Samsung, essentially Linux and the EFL toolkit from the Enlightenment project -- Tizen being, ostensibly, something of a "Clone" of Android, or so it's been said, if it is not instead a clone of Maemo, or any number of other mobile operating systems built on a Linux kernel. Secondly, then, there's the FreeBSD kernel, the BeagleBone platform, and some number of concepts in "mobile to mobile" i.e "M2M" computing.  Certainly, it may need something of more of a a professional style -- by far, more professional than what I may ever estimate of so much of the Android userbase, now -- if it could be a platform.

So, then, there's the matter of task management -- no small sidebar to nod a tip of the hat for all the "Apple-ness" of the Apple computing company.


TaskWarrior and the Shell Terminal Portal

In trying to develop a simple manner of a back to basics approach to business and broader commerce, moreover in a view as with regards to academia and the fundamental mathematics and sciences of things, and though I've been struggling personally to understand how that could ever be factored into any sort of a cultural climate, in California specifically -- and it be all of nationally legal, economically sustainable, personally ethical, and socially practical, to all of my best abilities to reasonably estimate of such qualities of a business endeavor and furthermore, qualities of any single, regional social climate in California --  firstly, I've been of an impression that I should plan to move to another state. I cannot begin to estimate, in full, what anyone may consider to be socially practical in California, where all I'm seeing is, on one hand, a millenial radicalism and secondly, a sort of managed statism, such that it resembles -- to my best ability to estimate and to comment, succinctly -- a liberal nanny state, such that moreover I cannot imagine the state's contemporary society be actually sustainable, beyond the state's own apparent codependency on so many existing modes of corporate industry -- and certainly, to much of an albeit relatively small range of contemporary, if not wholly commercialized entertainment. If I had ever thought that was "All the world," but after my experiences in a few years enlisted in the US Army, but then on moving back to California, I know it is by no means "All the world."

To my point of view, California is developing much of a grossly immature society -- a society becoming more markedly immature, every year -- a state essentially, then, becoming repulsive to any further, genuine sense of innovation. So, to my point of view, it is by no means an economically sustainable society -- perhaps, much to a further sense of irony, for how awfully narcissistic the people are. That I do know of a broader world, now, it's not such that I may ever voluntarily forget.

So, but in my little niche in all of this state's broad geological diversity and ironic commercial hegemony, I've been trying to develop an idea for how to put together some simple software tools to make anything manageable original, sustainable, and commercially productive, beside my own senses of interest about archaeology, ecological conservation, tourism, and typically low-horsepower, small-footprint recreation in the outdoors. Those interests, I consider, those interests can travel with me.

Of course, there's also my ongoing study about social developments in the Middle East regions effectively overlayed by Kurdistan, and the level of support heretofore provided to Kurdistan, in the Kurdish engagement to the conflict against the singular brand of militant extremism waving the false flag so know of ISIS -- lately, also the Taliban militants' attacks as conducted against the Afghan state -- lastly, then, so much grossly frivolous misguidance from President Obama and the broader The Administration(TM).

This morning, I had simply thought to search for a matter about task management, in a sense of project management, for an idea as with regards to managing a local area network. I would not wish to let that be sensationalized, however, of my own views with regards to executive leadership and/or gross federal executive mismanagement. As to my own views of all of these topics, of course it all may serve to shape my own sense of context about even this relatively small endeavor of having searched for a task management application for a local area network.

In another sense, if there is a presidential administration so endeavoring to make a federal fire sale out of a federal government, perhaps this small endeavor might seem too timely, and though much I am a fan of Bruce Willis' own work in the performing arts -- likewise, Steve Buscemi -- but this is by no means to emulate a Die Hard film. Not is it either as though to emulate any films depicting of any single, human guided landings on any asteroids, comets, or minor planets. If there's anything it must be said to emulate, in science fiction, I would rather wish to draw a metaphor of The Heritage Universe, by Charles Sheffield. That story begins on a planet named Opal. The author would not wish to spoil the reader's view of such a story, however, if it may spoil as to comment as with regards to any manner of a sense of elasticity in any single theory or concept of a time/space continuum.

This article, I hope, does it got all the things, then? There's even a passing reference to the Deep Imapct and Rosetta/Philae programs, with a nod to a recent speech by Buzz Alrdin, for a sense of semantic closure in regards to space exploration process in crewed and uncrewed spaceflight.

So, this morning I'd found a task management application for servers, Taskwarrior. listed among some other other task management, if not broader project management projects hosted by SourceForge.net[2]. On noticing some short documentation about structures of data record sets in TaskWarrior[8] -- and, in a breadcrumbs sense, I had been reading about OpenSLP, then DNSCurve, shortly previous to the search -- I thought, essentially: That I've finally found a task management application, such that might integrate well with my own perosnal range of expertise, experiences, and resources, at this time.

Proceeding from that observation, I began to sketch up an idea with regards to integrating Taskwarrior and Modeshape JCR services -- I had blogged about that, this morning, in my Google+ social networking blog[9] -- as well as observing that there is an NCurses TTY/terminal shell client for Taskwarrior, tasknc, listed at the Taskwarrior tools page[10]. Considering how much I've been working with shell terminal interfaces in managing my LAN's gateway and build host appliances, moreover considering the dolefully corporate managed interface of Cisco IOS -- such that I am familiar with, to an extent -- and although I cannot even imagine to install Taskwarrior on a Cisco networking appliance, I think I may now denote what impresses me the most about Taskwarrior: That it can serve to both prettify and organize the shell environment -- moreover, effectively including a shell environment in a broader hypothetical management information system (MIS) network applying Taskwarrior for task management -- without it drawing all of Emacs into any manner of a console located however semantically approximate to any manner of a superuser access, moreover.

What thing might it resemble, whether or not unlike the Little Shop of Horrors, if Emacs was run as Root, on a network routing server? Certainly, it may be, "Not a Great Idea(TM)," in some short terms. One might wish to expect that if a terminal-mode application may be run on a network routing server, that it would not ever load the server's microcontroller, however it may be applied as to correspond to data on the server.

Of course -- as towards a concept of furthermore developing a concept of applying Taskwarrior as a support tool, in as may be applied in a development of a server management architecture -- one could run Taskwarrior in a terminal beside any terminal connected to any manner of a network routing appliance. However, with Taskwarrior installed directly on the network routing appliance, it would then be able to access resources of the network routing appliance, directly, such as to provide any manner of task content data or task verification data, in any data records as may be developed in the progress of a task.

So, broadly, I think that one of the nicest features of Taskwarrior is that it has a clearly non-imposing design, that the Taskwarrior API can be applied in even a light-duty terminal environment. In that itts design might require only a a small footprint for a task-management protocol and application, it may not be any sort of any too resource-intensive task management service to apply. It might integrate well with other applications, too -- perhaps, in a sense, much analogous to a classic text stream piping methodology, for processing textual data with shell terminal applications in a UNIX environment.

Likewise, perhaps it may not essentially need any manner of a proprietary focus, to carry its architecture by -- comparatively, not requiring all of an enterprise proprietary J2EE services stack for its implementation. Of course, the JCR integration would be another matter, at that. Towards integrating Taskwarrior withing a documentary content management service, however, perhaps it may be worth the effort.

Towards integrating Taskwarrior with a desktop development environment, of course an Emacs Lisp interface may be easily developed for Taskwarrior -- towards something of an IDE-like integration, moreover then in an application of Emacs Lisp, as a relatively light-duty programming language -- however in parallel to the the NCurses client, considering Emacs' dual-mode applicability for desktop windowing systems and terminals.


Footnotes

[1] In FreeBSD, there are ports, packages and package repositories, and the FreeBSD base system — juxtaposed to package maintenance, packages and package repositories, and perhaps, the Debian installer, if the latter may be denoted as it being in any ways analogous to a base system, in Debian. The package maintenance concern, in FreeBSD, as it deriving of ports — perhaps as may be contrasted,  in an  immediate and perhaps naive sense, contrasted to Debian source packages —  a concept, rather, of any single manner of package management with a FreeBSD installation, if any single concept may be developed, as such, perhaps it may be developed as with a sense of supporting a manner of decentralized software distribution. Perhaps one may consider whether it could be sufficient, to simply configure and batch-build a set of FreeBSD ports with the FreeBSD Poudiere tool, then to host the resulting packages in an organization-local softwate package repository. Though it might suffice, in some terms of convenience, however it may not — in itself — obviate a concern for user support, within same organization.
[2] http://sourceforge.net/directory/business-enterprise/project-management/os%3Awindows/os%3Afreebsd/
[3] http://sourceforge.net/projects/taskwarrior/
[4] http://taskwarrior.org/

[5] https://www.freebsd.org/doc/handbook/firewalls-pf.html
[6] https://www.freebsd.org/doc/handbook/firewalls-ipfw.html
[7] pf.conf(5)
[8] http://taskwarrior.org/docs/dom.html
[9] https://plus.google.com/110843395386227107116/posts/coUbJnWWmT7 in HTTP[S] URL sytnax
[10] http://taskwarrior.org/tools/

Active Projects – Hardpan Technologies Workspace

• Compile a FreeBSD image for a BeagleBone Black single-board computer, then netboot a BeagleBone Black A6 to FreeBSD, from a FreeBSD Virtual Appliance, using Crochet, FreeBSD 10.1 VMDK, Virtualbox, Debian GNU/Linux (?) for the PXE services, and a Netgear wireless router with Ethernet hub. HP Laptop (UEFI) with Microsoft Windows 8 as host OS to the Virtualbox VMDK appliance. Toshiba laptop for USB boot to PXE service on Debian (?) or FreeBSD.

• Development of a fork of McCLIM, extending of the original CLIM model for human-computer interface design and implementation, independent of graphical or audible appliance interface or textual media

• Develop HPan Ex Libris services – JCR and CORBA; Bookshelves interface in CORBA; Notebooks interface in CORBA; editor interfaces and viewer interfaces, in human-computer interface (HCI) design, focusing on the Android Mobile platform and one or more desktop computing platforms.

• Develop an automotive crew information system onto Ex Libris, Android mobile,  and ELM interfaces onto OBD-II as interface for automotive sensor information,  corresponding to normative mechanical diagnostic methods,  automotive maintenance models,  and procedures in automotive repair. Additional focus about environmental characteristics of automotive/mechanical work environments and corresponding demands for physical and structural resilience of digital electronic systems

• Politics? Nope, the author is not babysitting myths.

• Not getting lost in a vortex of prolific cryptocurrencies — keyword: Mathematics

• Bitcoin miner implementation in Common Lisp,  as primarily focusing on CMUCL-style VOPs as furthermore implemented in SBCL, furthermore referencing implementations and optimizations of ECDSA system elements in C and in specialized microcontroller elements as accessible via direct machine instructions (Intel,  ARM, and Nvidia instruction set architectures) (See also: Texas Instruments AM35xx Sitara MCU;  design documents for the CryptoCape peripheral to BeagleBone SBC platforms)

• Development and applications of an interface for SHA-256, RIPEMD-160, and other mathematical systems relevant to cryptographic computations, with optimizations for features of the BeagleBone Black platform,  as extensible with the peripheral CryptoCape, and other machine architectures.

• Parallelization in applications of mathematical computations denoted in the previous outline elements.

• CORBA GIOP extended for serial communications,  project OLLIEOP

• CORBA GIOP extended for I²C, project OLLIEOP

• CORBA implementation in Common Lisp,  updating a fork of CLORB.

• Applications of the TPM element of the peripheral CryproCape, using the BeagleBone single board computer (SBC) within a FreeBSD
kernel and correlated operating system, focusing on PKI architecture, LDAP directories for principal identity, Keberos for principal authentication,  and OpenSSL as a feature of a TLS system applying X.509 certificates — focusing on the TPM's roles for trusted storage of cryptographic keys.

• Various things CORBA and BSD-style "Open"

• Formal Business Models

Maintenance as Project

Here at the author's DSP42 web log ('blog), this week, the author has begun to develop a concept of project management. Rather than launching onto an orthogonal thesis with regards to the Interface Definition Language (IDL) of the Common Object Request Broker Architecture (CORBA), the author is prsently preferring to develop something of a broader view of project management, as namely towards a broader sense of types of project. Thus far, the author has denoted three primary types of project, at this web log, and some corresponding concepts.

• Thesis Development Project [xref]
• Subsumed by Literary Project
• Subsumes
• Thesis project for academic institution, i.e. graduate thesis
• Thesis project for journal publisher, i.e. journal article
• Those subsumed types of thesis development project may differ as per style and format of published bibliography, such that would be entailed of a given publisher's requirements
• Software Development Project [xref]
• Subsumes
• FPGA programming project
• Software programming project
• Subsumed by Digital media project [not denoted in earlier thesis work]
• Construction Project [xref]
• See also: Structural Archaeology

The author would not venture to define any further detail of the third of those types of project, if without further reflection as with regards to scale and context, and no long thesis for orthogonal and typically legal concepts of intellectual property, as well as concepts of physical property and, essentially, ownership. Candidly, the author is personally familiar with concerns faced by owners of properties having historic structures on premises, insofar as concerns resulting of property theft and property vandalism. In both respects, it would seem to entail a certain lack of understanding with regards to concepts of physical property. One might think as if a historic structure would not need a guard dog on premises, and that be proved to be altogether a naive concept.

With no too cute comment from the author for the author's own ears, and the author's own defensive posture with regards to family properties, presently this web log will proceed to develop a concept of a fourth type of project, namely, the maintenance project. This concept, too, may require some careful introspection, as towards developing a concept: What is the beauty of maintenance?

Similar to the manner of the author's previous articles, in this series, the author will endeavor to focus  the author's consideration on a practical matter, essentially towards a single reification of each type of project. In regards to maintenance project, on this weekend day, the author endeavors to produce a sense of personal focus, namely towards personal physical health maintenance and personal intellectual health maintenance, both subsumed by a concept of health maintenance -- not quite insofar as with regards to central health management institutions and the fine distinction of capitalist principles as viz a viz any essentially socialist principles, aside to any concept of how science is managed, institutionally. No too contentions topics in this web log -- those would be left aside for the author's politically concerned web log, Bring Back Lady Liberty.

So, the author has now denoted one further type of project, subsuming two more exacting types of project. In those two instances, however, the author does not formally apply the term, Project.

• Health Maintenance Project [Type 2]
• Subsumed by Maintenance Project
• Properties
• Intellectual Health Maintenance
• Physical Health Maintenance

Concerning that -- moreover -- at first, the author does not denote that particular type of Health Maintenance Project as a Personal Health Maintenance type, it is not the author's wish to invite any speculation with regards to Group Health Maintenance, such that would reside in parallel to personal health maintenance. In a sense, public schools might be thought to be institutions implementing of manners of group health maintenance. However, in light of the concerns presented by the Common Core, as it being essentially a socialist agenda being imposed in public schools, it would seem to be far too contentious a topic to introduce in any hasty regards whatsoever. If, however, the outline would be expanded on further, it might be written thusly:

• Health Maintenance Project [Type 1]
• Subsumed by Maintenance Project
• Subsumes
• Health Maintenance Project [Type 2]
• Health Maintenance Project [Type 3]
• Properties
• Intellectual Health Maintenance
• Physical Health Maintenance
• Health Maintenance Project [Type 3]
• Subsumed by Health Maintenance Project [Type 1]
• Subsumes
• School

The author has there revised the Intellectual Health Maintenance and Physical Health Maintenance qualities as to denote those qualities as being properties of such type of project. That would be instead of denoting those as being subsumed by the Health Maintenance Project [Type 1].

Some examples of Health Maintenance Project [Type 2] may include:

• Reading a book
• Exercising with a bungee band
• Excercising with free weights
• Exercising in a study of the martial arts (external equipment sometimes applied, but not required), for example
• Exercising in a study of Tai Chi
• Exercising in a study of Wing Chun
• Exercising in a study of Judo
• Exercising in a study of Jeet Kune Do
• Riding a bicycle
• Going on a hike, along a managed trail
• Climbing a mountain
• Swimming in a public body of water.
• Recreations of a physically exerting manner and -- characteristically -- recreations entailing some type of a non-self-propelled material equipment, such as a mechanical snowmobile, a powered motorcycle, a four-wheeled ATV, or a living creature such as a horse, (Please, Tread Lightly on land, water, or asphalt)
• Walking with dog along a road or trail

It is the author's sinceremost opinion that any examples of Health Maintenance Project [Type 3] would be best be left to officials of the institutions managing such projects. 

Presently, the author observes that this article has not yet addressed all too much of a sense of maintenance project, that -- namely -- this article has not described much of a sense of structural facilities maintenance, such as with regards to maintaining known geographical properties in a civil manner, and maintaining any structural constructions developed on any known geographical properties. Perhaps the reader may endeavor to consider that the author does not wish to paint a neon sign over "Home."

In considering a third type of structural maintenance project, moreover, the author observes that there is a type of project in an automotive maintenance project -- essentially a type of equipment maintenance project for a type of equipment that provides a means of external locomotion, paralleled also by watercraft maintenance, further paralleled by types of equipment maintenance project not entailing a maintenance of a means of external locomotion -- such types of equipment maintenance project as include firearm maintenance, footwear maintenance, and manners of other indoor and outdoor equipment maintenance.

The reader might be advised that this article is not a property of a tax board. This article is a property of the author's own writing, in a thesis development project, broadly so. Though a survivalist type of view about politics might seem quite apropos to the time, the author does not subscribe to any concepts of a hasty escalationism.

Concerning Construction and Project Management for Countryside Climates

The author has recently moved to a ranch type acreage in a quiet country locale. At same locale, the author has begun an ad hoc project, firstly in regards to automotive repair. In a linear manner, the author is also keeping up with vocational planning and software development -- at this time, insofar as ideas management. To avoid casting any short or long shadow onto concepts of patent ownership and patent litigation, the author has been endeavoring to avoid developing any projects that may be too far semantically similar or too much practically similar to any of the body of existing work in software and academia. Beyond concerns with regards to patent ownership, patent licensing, and litigation about laws concerning intellectual property, the author has begun to develop an orthogonal thesis with regards to managed knowledge sharing, as viz a viz the respective technology transfer methods developed by the ESA and by NASA -- as to a point, a concept of managed technology transfer. In a manner, that concept resides in parallel to a concept of informal knowledge sharing.

In the previous article at the author's DSP42 tech web log, the author had developed a number of concepts -- albeit, none too formally expressed -- with regards to thesis projects, software projects, and the simple observation that to develop a software project's documentation, it may entail something like a thesis project -- citing the FreeBSD Handbook, then, as a literary precedent to which effect. In that article, the author also developed -- in a short time -- a concept of programming language as programming media, and a corresponding concept of FPGA programming being similar to, or rather being correlated to software programming only insofar as that an FPGA program is applied essentially as to configure a digital circuit, whereas a software program is developed essentially as to control a computing machine -- such manner of machine, including a microprocessor, perhaps having been implemented with an FPGA program, onto a single FPGA circuit.  Initially, the author's thesis was that a thesis development project, in itself, would entail an original work in ideas management, as would correspond to content development and formal bibliographical reference.

Presently, the author would like to develop a widely orthogonal thesis, with regards to project management for country projects, citing the classic wood working projects regularly published by the periodical, Popular Mechanics. Certainly, Popular Mechanics is one of the original "DIY" resources, at least for projects at a small residential scale, such as -- in a formal sense -- single-facility construction projects, automotive study, and electronics study. By no oversimplified comparison, it might seem vaguely similar to the extensive work developed about digital and analog electronics, specifically, such as of modular projects and studies published by the Adafruit Learning System and at Sparkfun. In short, the Adafruit Learning System itself might seem to be something like a Popular Mechanics of the modern digital electronics domain.

Returning to a concept of country projects -- the author presently relying on the author's own memory of a few of the construction projects published by Popular Mechanics, namely those applying wood as a building material -- in a sense, such construction projects would need at least four things as in order to be produced. No riddle:

• Materials
• Tools
• Labor
• A Plan

Insofar as budgeting for materials purchases, tools purchases or tool rentals, labor time, and development or licensing of plans, that in itself may entail something of a managerial quality. It being something of an implicit quality of such projects -- in some projects, moreover to a decentralized quality, essentially of a group-oriented project management, for projects managed of all of a group's knowledge, contrasted to a monolithic or centralized style of management -- the author will not denote it separately.

Insofar as concerning the media of project plans, and a corresponding concern as with regards to terms of licensing, certainly the digital tablet is not the first medium on which a plan would be produced, though it may afford an opportunity for licensing and control of media files. In an older sense, paper often suffices as a medium.

Orthogonally, the author is presently mulling about a concept with regards to developing a manner of structural archaeology, as around a single thesis concept: That if a structure exists, that structure was built by someone, at a time in the history of the known cosmos.

Toward a Functional Overview of Thesis Development and Software Development

My being a student of electronics and computer networking, in an associates level program, and -- for some time -- a fan of free/open source Linux software platforms such as Debian GNU Linux, and broadly a fan of academic literature about computing, I understand that there is an existing body of work with regards to project management, at least insofar as with regards to software projects. My being furthermore of some experience with regards to the arts aspects of the humanities, including visual creative arts and the performing arts, I'm of a point of view that software projects are not the only kinds of projects under the sun.

Personally, I haven't encountered a lot of literature in academia, insofar as project management. I've read some little about the Capability Maturity Model (CMM), perhaps a sort of monolithic or centralized project management model, and some little about Scrum. I've not read a lot about "Extreme Programming" (XP) -- sort of an older agile project management trend, in a sense -- but I understand that it involves an iterative process. I've also read a little about the ideas management method proposed by Scott Belsky, in the book, Making Ideas Happen. Belsky's Action Method addresses more of a creative approach, juxtaposed to what one might expect that an implementation of monolithic CMM might be like, at a personal level. Of course, a large project might need a large management information system (MIS) to manage it by, entailing a certain degree of formalism throughout.

Personally -- as my being a student, at this time in my life -- I'm more interested about management methods for small-scale, original projects, rather than for projects developed under monolithic requirements. As a person of any manner of a creative bent, and a student of a technical field, with some self-managed knowledge of computer programming language, personally I'm interested in developing a project management system for small-scale thesis development projects, and for small free/open source software (FOSS) projects -- in an abstract sense, two types of project. In juxtaposition to monolithic project management methods, personally  I'm of an impression that each of a thesis type of project and a FOSS type of project might be -- in the most of which -- each managed individually, and by a small number of contributors.

To inquire, "How does a FOSS project begin?" or similarly, "How does a thesis project begin?" perhaps the Action Method might present the most readily applicable practical model for such a context -- as towards an ideas management phase of project development.

Towards a View of Idea Management

Aside to the metaphysical aspects of positive intention,  ideas are some of the raw stuff of academic work. Parenthetically, the reader is offered the author's sincerest apology for a lack of formal citation, to that effect. Perhaps the reader may agree that it is a valid assertion. Broadly, it may be a matter of philosophy -- namely, towards a relevance of ideas, in academic work -- furthermore, a practical matter of a functional application of intellect to a formal or informal task. Whether or not that may satisfy all of a model of "Left brain" and "Right brain" knowledge, perhaps it at least serves to present two juxtaposed views about -- in broad sense -- a relevance of ideas.

Aside to this thesis, the reader -- at any time -- might wish to criticize the author's style of writing, if it may serve as a convenient alternative to an addressing of any of the content of the discussion. The author has an idea that the ad hominem mode of discussion occurs in numerous forms. Inevitably, there will be another biting ad hominem criticism over my own writing. At that, I might wish to only address the topic: Philosophy.

Ideas and Theses

In a capital sense, ideas cannot be exchanged for raw currency. Thesis articles -- insofar as being works made as expressions of ideas -- thesis articles may not seem to be terribly profitable, either, not in any manner of an immediate economic sense. In a practical sense, a thesis article about barns does not in itself build a barn, though a thesis article may ever attract some manner of attention from a barn builder. In a literate society, thesis articles -- as literate works -- thesis articles are one manner of a textual medium on which ideas may be communicated.

Without any too lengthy reference to the Business Process Management Notation (BPMN), hypothetically, a model can be developed for a process of thesis article development. Certainly, thesis articles are works developed in chronologically linear manner, from a discrete "Start point" to a discrete "Stop point," at which time the work is published or filed away, if not altogether abandoned.  The process of developing a thesis paper, essentially, is a process of developing ideas, and expressing those ideas on a written medium. In that sense, it may be analogous to a development of any of other forms of prose, and forms of written verse, such as poetry.

Thesis articles, as ideal media,  thesis articles may not seem to serve any single, exacting functional role in society, except insofar as being required of some academic programs. If all of the world is a functional world, thesis articles may not seem to have any obvious relevance -- at least, outside of any manners of academic cultures as in which thesis articles would be any manner of a common fare. Ideally, even in proceeding from academic cultures in which learning itself would seem to be presupposed to be something akin to "Just press play", there may be a relevance recognized of thesis articles as discursive works, in a literary medium, works communicating ideas, and serving in further development of ideas. Hypothetically, a diagram of the ideas content of a single set of thesis works and the ideal derivatives of thesis articles may be all made in a single directed graph. In a practical sense, there is at least the bibliographical cross-reference, incidental to the actual content of individual thesis articles.

That a thesis article represents a communicative medium, in communicating ideas in a literal manner, that in itself does not describe how to write an idea down.

Presently, the linear thread of this article's textual content will diverge onto software development.

Logical Software Development

In a functional manner, a software program represents a linear application of digital data and control structures, such as to produce some manner of a functional result in a microprocessor for which the software program is compiled into machine code. Prototypically, the microprocessor is the central element of a software program, Once compiled to machine code, a software program performs a linear series of applications of digital functions and digital data shift procedures, in any number of linear, processor-level threads of execution. Excepting procedures applied for data shift, as in memory access and in transmission and receiving of data onto digital communication interfaces, the digital functions provided of a microprocessor architecture may include mathematical functions, for scalar and floating point values.

Firmware programming, as a manner of software programming -- as in an instance of FPGA programming -- firmware programming, insofar as FPGA programming, represents a configuration of circuit elements, such that those circuit elements would either produce a direct implementation of a discrete functional model, or that the circuit as implemented of an FPGA program would, itself, be a programmable element of a computer.

Insofar as that a software program and an FPGA program -- in a categorical manner -- would both represent an application of software for application of a digital system, then a certain philosophical parallel may be illustrated between the two categories, in some abstraction. Essentially, an FPGA program configures a digital machine. A software program applies a digital machine, whether a microprocessor implemented as an FPGA program or a microprocessor implemented directly in a semiconductor design.

Software programming, as a practice, would represent a work of developing of a software program. A software program, itself, represents -- essentially -- a medium for application and control of a digital system.

If there may be a single topic denoted of the stylistic qualities of applications of individual programming languages, perhaps it would be a contentious topic to develop. For instance, what manner of a Java collection class is preferred for which applications? What is the deeper meaning of a Common Lisp iterative macro? How often should C pointer arithmetic be applied? Opinions might vary.

To differentiate programming languages on a basis of programming media, broadly, there are text-based programming languages -- such as C, C++, Java, and the numerous dialects of Lisp -- and some visual programming languages -- at which topic, the author refers the reader to an article at Wikipedia: Visual Programming Language,  The author would wish to categorize the older punched--card and punched-tape programs as being some earlier text-based languages -- presumably, those not having been designed expressly for the visual qualities of the chad-betokened storage surfaces on which the historic punched-paper programs would be conveyed to their respective machines.

Again in a social context, the choice of a licensing model for a software program -- there is another possibly contentious topic, in software programming, certainly a topic much related to any number of topics in social, commercial, and legal views of a concept of software program as property.

So, this article has developed a succinct view of two distinct qualities of a software program: The programming language, and the license under which the software program is developed. Again viewing a software program as a categorical item distinct to a thesis paper, there is also the distinct quality of documentation for a software program. Consulting the FreeBSD Handbook. at a level of a view of project meta-data, a software project itself may essentially contain any one or more thesis projects, insofar as the documentation quality of a software project.

In a view of resources and resource containers, the whole set of documentation resources of a software project may not be represented singularly of any single source tree in which the software project is formally developed. That is, documentation may be available about a software project, such that the documentation is not developed by the software project developers, or at least is not contained in the same source tree as the software project itself.

Again, that is not to say how a software project is developed. It is to suggest a sense of a model of what a software project represents, in a sense of three fundamental qualities: A selection of a programming language; a software license for the content of the software program, altogether; documentation. Finally, there is the content of the software program itself -- as the software program being represented in a sense of source code or compiled code and correlated data elements -- the latter not being, expressly, "Program code," though supporting the execution of the program code, for instance as with firmware data for driving an external peripheral, or visual graphics data for the layout of a graphical program interface.

Certainly, the relevance of logic in software development, as a topic, may not be  as easily illustrated as the relevance of ideas in development of thesis articles. A software program -- as a product of a software project -- may represent a multi-faceted kind of work, including some literary work in a form of documentation.

As in order to develop a concept of a relevance of ideas in software development, a concept of topic maps may be presented.

Insofar as to answer a question, "How is a software program developed?" perhaps that may be illustrated with any single "Proof of concept." A concept of requirements, and of styles for best practice in application of any single programming language -- perhaps, again, some  contentious topics.

The concept, "For attention" may not be sufficient as a goal or a requirement for software program development. Incentive -- there, another complex and perhaps contentious quality of software program development.

Why?

If it may be possible to develop a system applying CORBA for project management, and that system support an individual, decentralized, by-in-large independent manner of management -- as in development of thesis articles and, in a separate sense, software -- of course, one would want to have determined, "What is that CORBA application going to support?" At that, of course it should be implemented with a license making a clear statement of indemnity.

#YMMV