Sunday, July 5, 2015

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[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, 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

# See also: /usr/src/share/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 opportunityrealized 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[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 OpenSLPthen 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.


[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.
[7] pf.conf(5)
[9] in HTTP[S] URL sytnax