Cooking soup with single burner portable stoves for a crowd

As I recall, I began cooking big batches of soup (eight quarts and more) for my church’s after-service social time / coffee hour in early 2013.

On a lark, I had decided one winter Saturday afternoon that it would be a good idea to make soup the following morning during the church service and serve it during the after-service social time / coffee hour. I sought out a recipe on the internet for “big batch vegetable soup”, which sent me to a recipe on the Martha Stewart website for four quarts. The recipe suggested that it was very flexible, so I chose the ingredients I liked, ignored those I didn’t, and doubled the numbers to make eight quarts, the size of a large stainless steel pot I had. The next morning, I bought the requisite ingredients on my way to church, and upon arrival, I just started making the soup in the church kitchen during the service. During coffee hour, it was a modest hit; all of the soup was served, with none left over.

Since then, my soup recipe, having evolved somewhat from Martha Stewart’s, has become a small yet (I hope an) integral part of what has become a larger occasionally recurring food event.

This is in no small part due to a comment I received from a fellow parishioner that Sunday morning in early 2013. By the time she managed to come to my service table, the soup had cooled too much for her liking; this prompted me to invest in an inexpensive portable counter top single burner electric stove. At the least, the theory went, I could cook the soup in the church kitchen, and then upon bringing it out to the hall for serving, I could keep it hot. Since then, however, I have shifted to cooking the soup in the hall where it has been served, avoiding in the process the danger of walking through a hall with a large pot of boiling soup at a time when it starts filling with people.

I have since invested in the following:

  • a double burner counter top portable stove;
  • two more inexpensive single burner electric counter top stoves;
  • a somewhat more expensive, single burner induction counter top stove;
  • two 50 foot, 12 gauge extension cords, one of which normally does not get used;
  • and, already having had an eight quart stainless steel stock pot, I bought:
    • an eight quart stainless steel pot I found at a steal of a price at a second hand shop;
    • a slightly used 16 quart stainless steel stock pot at a steal of a price at a second hand shop;
    • a new 20 quart stainless steel pot for a steal of a price at a grocery store.

In a number of ways, portable counter top stoves are central, however indirectly, to the success of the soup I make, despite the relatively large volumes of soup I now occasionally make.

Over time, I have learned how to make large quantities of crowd-pleasing soup while also discovering some of the limits of counter top stoves, as well the upper limits of the environment in which I am using them.

My single burner, traditional coil stoves are rated at 1000 watts each (8.33A @ 120V). My double burner coil stove is rated for a total of 1500 watts (12.5A @ 120V). My single burner induction stove is rated at 1800 watts (15A @ 120V).

In my experience, it is possible to make the following capacities of my vegetable soup (your results may vary according to your soup recipe):

  • 1000 watt single burners:

I find that these units may be used for making eight quarts of soup in a two hour period, and 16 quarts if you have at least three hours to make it. (As a second burner, it also allows for the frying up of vegetables that are later added to the soup pot, although depending on your site conditions, you may not be able to operate both burners simultaneously at maximum capacity.)

  • 1500 watt, double burners:

I am able to make two eight quart pots of soup in a two hour to two and a half hour period.

  • 1800 watt, single burner induction stove:

Particularly ideal for making eight quarts of soup in less than two hours, and it will handily make 16 quarts of soup in a couple of hours. It will also bring 20 quarts of soup to a boil in just over two hours.

Planning, preparation, and logistics of “mobile cooking” for a crowd

This post is not on how to cook a full, multi-course meal or buffet for a large crowd; rather, it is about just a relatively small part of it. As described later and despite describing the portable stoves as being central to the cooking of the soup which is one of the two subjects of this post, attempting to cook a full, multi-course meal or buffet for a large crowd with consumer grade portable cookware, and in environments not set up for such cookery, is impractical at best; to do so would require planning and menu design far beyond the perview of this post.

Setting up and preparation:

Often when traveling to cook for a crowd, one is doing so in an environment that is unfamiliar, and depending on the circumstances (such as the type of hall in which I make soup for a crowd), is not set up for doing so.

From a cooking perspective, this means that I normally do more than simply collect the soup ingredients and throw them into a pot, hoping that tasty soup will come out a couple of hours later. Often, this means now that while cooking the soup takes place in the church hall, I prepare the ingredients in advance at home, typically the day before. Fresh vegetables are cleaned, chopped, and placed in containers for transport. Usually, they are mixed together, and even the olive oil is added and mixed in. Frozen vegetables are taken out of the freezer the day before in order to defrost them at least somewhat, so as to reduce the amount of time required to defrost them during cooking. I also transport all the fresh food in a cooler.

Equipment-wise, I bring most of what I need for the cooking part. (Fortunately, my church has tables, tablecloths, chairs, dishes, a commercial dishwasher, and the like.) Of course I bring the portable stoves and my pots, however I also bring my own cast iron fry pans and cooking utensils, such as spatula, ladle, and can opener. I even bring my own towels for cleaning up my area, which of course I launder myself.

Real life challenges to using portable stoves in areas not designed for cooking

I once agreed to making the soup for my church for the Fall Fair Luncheon, at which the soup would be the main dish. This was in contrast to my normally serving it informally in a mug as I usually do during Sunday coffee hour — sometimes on its own, sometimes as part of a modest luncheon — after the church service. This meant that I attempted to make a total of 44 quarts of my soup simultaneously in the same church hall. I came upon a reality of what I can only presume is a common condition of many halls not expressly designed (or recently upgraded) for high electrical demands, such as cooking for the very crowds they were designed to welcome. “That’s why there’s a kitchen, silly!”

I ended up learning definitively that the hall in which I was cooking the soup had only one electrical circuit, with what I was told (and which I later confirmed) was a 20 amp fuse. A quick addition in my head indicated that at its peak when I was trying to bring all 44 quarts of soup to a boil simultaneously, I was trying to consume between 29.6 to 31.7 amps on what proved to be a single 120V / 20A circuit!

(Note: I live in Canada, where the mains voltage is 120 volts, and unless specifically designed otherwise, circuits and circuit breakers — and in the still common situations where fuses are still used — are generally designed and set for 15 amp loads. I can only assume that the 20 amp fuse in place upon which I normally rely is there legitimately.)

It also led to what I consider to be an unfortunate conclusion, in the context of my desire to publicly (as opposed to hidden away in the kitchen) make my soup for a large crowd: The electrical outlets in many halls, designed and built decades ago, are often served by a single electrical circuit. Hall and home builders simply never envisioned nor intended for cooking, which often requires a large amount of electricity, to occur outside of a kitchen; at most, they may have assumed that someone might plug in the equivalent of a plate warmer, possibly two, to keep a casserole or two warm.

This led to my realizing that making my soup for the church had its limits. With some patience, I could still make my soup in relatively “small” quantities — usually up to 16 quarts at a time, and perhaps if I reduced the heat a bit at certain times, perhaps fry up the vegetables at the same time. However, the fuses blowing a few times confirmed that large quantities of soup — and more generally, large scale cooking — could not be cooked simultaneously in an area not set up for the loads required for cooking. This means that despite the fact that a “large hall” may have many outlets, unless the hall was designed or since upgraded for heavy electrical loads, there is a good chance that the many outlets are in fact all on a single electrical circuit.

Although I purchased all of my portable stoves for cooking in non-traditional areas, as I’ve learned, their value for cooking in certain circumstances is limited to actual cooking of relatively small amounts of food — as in, depending on which stoves are chosen for use, that which may be cooked on one or two portable stoves at a time — and only keeping warm to hot larger quantities of food that have already been heated up, only then using more of my portable stoves at once.

Which leads me to the following conclusion: Portable cookware are very useful tools for the traveling cook, but one must not have have illusions of “feeding the multitude” based solely on these tools.

Captain Obvious Update Comment: Putting aside (possibly sardonic) suggestions of “use the kitchen, silly”, it has occurred to me that some may say “well use a portable gas stove to avoid the problem with electrical limits”. To me, the obvious issue becomes one of ventilation being required to avoid the buildup of combustion gases, particularly carbon monoxide. Some may well bring a fan to prop in a nearby open window in order to assure extraction; this would require such a window can be conveniently located. Yes, I have an opinion on that subject, too, to the order of old windows that were never designed to be opened, or which have been long since painted shut. 🙂

Document Formatting When Joining Texts From Various Sources

I have mounted, on a volunteer basis and in a lay capacity, the annual reports for a community group to which I belong, since about 2008.

Up to that point, the group’s annual reports were individual committee reports delivered to the secretary, individually printed out as and when received, and then stapled together with handwritten pages numbers when it had to be distributed, with an added cover page, and an extra page listing the reports and their page numbers. This did have the charm of not requiring a herculean effort and time requirement in both mounting the report, and on “printing day”, to print literally a thousand pages or more, depending on the number of pages to the report and the number of copies to be drawn. Admittedly, it does not take into account possible collating, as per how one might print out the reports (ie. pages with colour drawings and photos vs black and white, etc.).

The year I took on mounting the annual report, I believed that the annual reports should have been in an electronic format such as PDF so that it could be placed on the group’s website. But that was barely the beginning of why I took on the job.

To fulfill the technical goal of making a PDF for download from the website was not too difficult. Two easy options would have been to either scan the report once produced the “old fashioned way” and produce a PDF from all the images, or, at least for those received in electronic format, create individual PDF documents plus scan for those received on paper, then use a PDF joiner to string the PDF files together into a single document. In fact, at the time, I gathered as many previous annual reports as I could and scanned them, making them available on the website.

However, going forward, I did not consider either option to be satisfactory.

The aesthetic appearance of the annual report irked me. It wasn’t the old school printing on paper — to this day, I still print lots of paper copies for distribution. Rather, I saw an opportunity to put to the test some angst stemming from a bit over a decade earlier when the community group’s recipe book to which I’d contributed led to my having had a few ideas on improvements to the text’s basic formatting and overall layout. (The actual recipes, variety, organization, editing, and recipe testing that I learned went on behind the scenes, and the like, were beyond the scope of my interest, although one common error, separate from my angst, was a mild nuisance.) I of course wisely kept my opinions to myself, both at the time of the recipe book in the mid 1990’s, as well as at the time of initially volunteering to mount the annual report.

As can be surmised from the above, each report came from almost as many different people as there were reports, depending on how many committee reports given individuals would take on. Each person would typically type their report on their computer and email it to the office, or perhaps print it out at home and drop it off at the group’s office personally. They used whichever word processor they had: Sometimes simple text editors, or MS Write, or MS Word, presumably ranging through Word 98, Word 2003, and Word 2006. Presumably some people had Macs with whichever word processor they might have had. I believe that the secretary, who was sometimes typing up the reports which were submitted handwritten, was using a version of Wordperfect. Finally, I was submitting my reports at that point using OpenOffice.org. Presumably, there may have been other text editors or word processors used. Each instance presented a random opportunity for default settings to be different, as well as for the user to change the settings to those that suited their own personal taste.

As a result, each report predictably had formatting unique to each author, sometimes unique to each individual report, if two or more reports were submitted by the same person.

The various differences in formatting in the reports received included the following, without being an exhaustive list:

– varying text fonts and font sizes, and occasionally, more than one of either or both in a given report;
– varying line spacing;
– varying paragraph indentation, including lack thereof;
– line jumps or lack thereof between paragraphs;
– varying page margin widths;
– varying text alignment, typically either left justified, or left and right justified;
– the occasional use of italics over the whole document, beyond that which would normally be used;
– the inclusion or lack of section titles, sometimes (or not) rendered bold and/or italicised and/or underlined and/or capitalized;
– tables listing figures in formats unique to each table and report, or simple lists with varying bullet styles;
– varying spelling conventions, ie. American vs. British vs. Canadian spellings (ie. neighbor vs. neighbour, or center vs. centre);
– varying naming conventions: Sometimes full names, sometimes initialized first names with full last names, sometimes full first names with initialized last names, or sometimes very informally with only first names;
– varying honourific format conventions: sometimes honourifics, titles, and/or ranks would not be used, with persons simply named, and sometimes referred to with variations of their title such as Reverend, Rev., The Reverend, The Rev., etc.
– varying naming conventions for committee names, multi-word names, places, and the like, which were sometimes fully spelled out, and sometimes initialized, abbreviated, and / or contracted;
– etc.

As such, as alluded to in a previous post, minor changes and differences in formatting between the individual reports created subtle (or, depending on the changes, more obvious) visual changes in how each report appeared compared to each other, when joined and printed on paper or read on a computer screen. Multiple permutations and combinations of the above formatting issues often led to creating wildly varying end results which go beyond the subtle, creating a patchwork of formatting over the multiple reports joined together into a single document. This may be jarring to the eye of some readers, particularly when it is not a subtle, unified, overarching design choice, but rather the result of a decided lack of unified design choice.

This link shows a hypothetical example of how such a report could look (you’ll need a PDF reader) — with various individual reports each having unique blends of formatting as compared to each other. Note that I intentionally use the “Lorem Ipsum” text so as to highlight the formatting.

The obligatory let’s tie it all together part at the end:

When I collect the individual reports and create one document, I cut and paste all the electronic reports (and rarely, type up handwritten reports) into a single document, imposing a uniform text formatting throughout in the form of a standard font, font size, line spacing, (lack of) paragraph indentation, page margins, and standardized and / or uniform versions of the other items above. Pages are automatically numbered, and standard page headers and footers are automatically added throughout, with date codes to distinguish between earlier and later versions. Basic spelling and typing conventions are applied and made uniform. Note that I don’t dictate or edit writing style, so one report might have section headers, while another may not, nor do I edit for turns of phrase and the like.

This link shows the above hypothetical report changed (you’ll need a PDF reader) to show the same reports with some basic text formatting across the whole document made uniform, while allowing each author’s text flow (and implicitly, were each text to be unique, writing style as well) to remain relatively untouched.

Have I addressed my angst from the mid 1990’s? Yes.

Is the document formatting on the annual reports I produce every year a work in progress, with subtle improvements, changes, and the like every year? Of course.

A text formatting riddle

I’d like to propose my version of a little visual puzzle I saw years ago. In the following table, the same text is repeated in each cell. In eight of the cells, an element of formatting has been changed from the appearance of the text using a basic set of formatting, while the ninth contains, in this case, the default settings on my wordprocessor on my system. The riddle is to find which cell has not been modified as compared to the other eight. (View a slightly larger version of the table here.)

A hint of sorts: What the basic formatting settings are, or which word processor I used on which system or OS, all represent red herrings to solving which is “the original”, or “vanilla”, version.

a text formatting puzzle

Scroll down for the solution.
Scroll down to see the solution
The solution is B2, the cell / square in the centre of the table.

All the other cells have one thing changed from the B2’s qualities.

A1) The font was changed (from a Serif font to a Sans Serif font);
A2) The font size was changed to a slightly larger point size;
A3) The cell’s background colour was changed to a light grey;
B1) The text was italicized;
B2) Standard, unchanged text using my word processor’s standard settings;
B3) The text colour was lightened from a standard black to a grey;
C1) The text was capitalized;
C2) The text was made bold;
C3) The text’s line spacing was increased.

Besides at the core being what I perceive to be a fun riddle, it demonstrates how subtle differences can be made to standard document formatting in a variety of ways. It also alludes to the challenges presented by receiving documents from multiple sources for integration into a single document, such as a community group’s newsletter, or a community group’s annual report, presenting content and / or reports from its various members, leaders, subgroups, committees, and the like. In a forthcoming post, I will further discuss basic issues of varying formatting, and the need for standard formatting in a text document from the perspective of a layman editor of a community group’s annual report.

New World Community Grid Node

I started volunteering some of my extra computers’ idle time for the World Community Grid in December, 2013.  Unfortunately, the machine in question, a used computer I’d bought about five years earlier and, after having been used as a desktop for a few years, had been converted to being a server under CentOS, died from a “thermal event” nine months later.  It had completed 713 results and earned 419,591 points.

In 2016, I found a P4 3.4GHz machine, installed CentOS 7 on it, and then the BOINC infrastructure.  I assigned it to the World Community Grid and 100% of its capacity to the project.  From when it began in September, 2016 to today, it has completed 4,540 results, and earned 2,568,590 points.

In 2017, I finally converted my old netbook (32 bit atom processor) to CentOS 6 and did the same thing.  From when it began in April until today, it has completed 261 results, and earned 133,073 points.  (What a difference in capacity that 3.4GHz 64 bit has as compared to 1.6GHz 32 bit!)

Over the past few months, I have been collecting up a number of old machines which have come my way, including some IBM ThinkCentres from the Windows Vista era.  So far, my brother and I haven’t been able to get them running properly, and we will probably end up using them for spare parts.

In the meantime, we acquired two more computers.  My brother wanted / needed a replacement computer for his aging media server, an old reclaimed IBM ThinkCentre I’d gotten for him a few years ago.  I, in the meantime, wanted to add another node to the World Community Grid (of course, working at 100% of capacity.)

I chose CentOS 7 for this build, like I did for my other nodes, for what I consider to be the obvious reason that I want to pretty much forget about the computers and just relish in the numbers on the World Community Grid website — I don’t want to be re-installing every year!

The install went well enough, although it was long enough process for the base install, as compared to my laptop and desktop.  I will rule out the comparison to my laptop since the SSD and physical drive don’t compare at all.  As for the desktop and node, I’ll chalk up the difference mainly to processor speed and general architectures:  A 2015-era four core i5 running at 3.4GHZ vs a 2010 era Pentium dual-core E6500 running at 2.93GHz (no HyperThreading).

What was really long after that was the yum update after the initial install — about 650 packages!  In the process of the updates, I tried a few things like web surfing, and the gnome desktop became unstable; I ended up with a flashing text screen.  I finally rebooted, and tried to downgrade to an older kernel in GRUB, to no avail.  I tried the rescue kernel, no avail.  Under both situations, I couldn’t pull up a terminal with Alt-Ctrl-F2.  A quick check under a Fedora live environment was a waste of time, since I didn’t really know how to diagnose things; however, I was able to mount the CentOS drive.

There was some flirting with the idea of installing Fedora 27, but I don’t want the re-installation mill on this machine (or any of my other volunteer computing nodes) every year — although, seeing my brother upgrade from Fedora 25 to 27 through the GUI go as smoothly as a routine DNF upgrade is making me wonder if the point is moot.  (Note that CentOS 7, based on Fedora 19, is still using YUM, while Fedora has been using DNF since version 22.)

Finally, I restarted the install of CentOS, this time doing a minimal text install.  Things were a touch faster.  Then I did a yum update, with only about half as many packages to update.  After that, I installed the Gnome Desktop on the machine. (Here’s my archive.)

I continued with the installation of the Fedora EPEL repository (as root “wget http://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm”, then “rpm -ivh epel-release-latest-7.noarch.rpm”).  Installing the BOINC infrastructure was easy:  As root “yum install boinc*”.

I launched the BOINC manager from one of the pull down menus, and, to my surprise, it actually worked out of the box, unlike previous installations.  Someone must have updated the packages. 🙂  I added the World Community Grid website information, and my account and password.

Voilà!  At 12:00 UTC the next morning, my machine had already submitted FIVE results, and earned 2,429 points!  And, at 00:00 UTC as I’m completing this post, a total of EIGHT results, and 4,638 points!

malak.ca updated

Since about lat 2016, my website had problems with uptime:  It was mostly down.  In the spring of 2017, it was finally up and I did a bit of restoration work.  And then … it was down again for a few months.  (And, due to the circumstances of this downtime, my restoration work was lost.)

Finally, I transferred my website to an existing home server, and it is now living out of a computer which I believe may be as old as 2003, living under CentOS 7.x series, in my bedroom.  Having fixed a faulty telephone line (squirrels!) the line is now “not noisy” and the internet is back properly.

Main work has been:

ADTE Colloque 2016

Today I attended the ADTE Colloque 2016: The annual conference in Montreal (home for me) for a Quebec association with goals to promote free software in education.

Overall, the conference and its logistics were reasonably well organized; as far as the implementation of the event went, it seemed to go hitch free. Rooms that were appropriately sized were available, enough chairs were in place, there were no problems with the sign in, the microphones worked, the lunches arrived, and so on.

My interest was to see Richard Stallman, who was the keynote speaker.

Before he started his speech, I got to see his laptop almost closeup: He has a GNU sticker on it, an FSF sticker on it, and a small Trisquel sticker on it. I managed to ask him what the model was; an IBM Thinkpad X60, reconditioned, slightly upgraded, and marketed by a company called Gluglug.

Given that the conference was in French, Mr. Stallman presented what was no doubt his standard speech on free software, in French. (Let’s clear this up now: I’m a native English speaker, but Montreal is a predominantly French-speaking city; as such, since I live in Montreal, *of*course* I speak and understand French fluently.) Although I knew in advance that his French was competent enough to make his presentation in French, I was pleasantly surprised and very impressed that technically it was better than moderate in calibre, and that he could maintain it for over two hours with barely two or three requests to provide the French equivalent of a word or expression. And despite a fairly thick non-native speaker accent, it was almost surprisingly easy to follow.

His speech, although it appeared to be one of his standard speeches, went on too long in my view; 2.5 hours had been allotted for the presentation and questions, and I thought he could have accomplished the same thing in about 100 minutes, including questions.

I found that there were three downsides to his presentation:

– The “Church of Emacs” routine was off-topic or at least beyond the scope of the conference. Given what amounted to be a public audience, it was out of place. A cute parlour routine or pub talk in its own right, but out of place there.
– His comments about not having children were completely out of place, however legitimate they may be in their own right, and at best were poorly presented.
– Mr. Stallman apparently is losing his hearing, and asks people to speak a little more slowly, and clearly enunciate all their words. This is understandable, especially when those asking questions are not speaking his mother tongue; further, Quebec French and accents can be difficult even for native French speakers not accustomed to them. At one point, someone who forgot to speak extra clear and a bit more slowly elicited his ire as he either lost his temper, or whined like a child, repeating admittedly for the umpteenth time for the person to speak clearly and more slowly.

As for the rest of the conference:

The overall conference had a few quirks. The iPads at the registration desks were funny and out of place, given the topic of the conference. The glaring and blatant use of a Microsoft Windows computer on the overhead projector was a weird oversight to the point of being shocking, regardless of the fact that for all intents and purposes it ended up only being used to display the wifi network and password, and one minor demonstration during a roundtable discussion. This was addressed in the first question period by an irate participant who venomously commented on it and expressed his feeling of being insulted, to the applause of roughly at least a third if not half the participants.

For me, the first round table, before Mr. Stallman’s speech, left something to be desired. I thought that they could have been better organized instead of being just “I’m Tom Smith and this is what I do. Oh, and this is what I know about free software.”

The second round table, after Mr. Stallman’s presentation, was a bit meatier and not quite as disappointing as the first. There was an IT person who was trying to slowly provide Free Software by placing it in their pool of software available to staff at his institution, alongside other software. Another panelist provided a good and enlightening response to a question, to the order of “Try explaining *that* to a powerful teachers’ union!”

My brother said the comments then as well as elsewhere in the day felt like we were still in 2006 instead of 2016 given their nature, such as:
– “Well GNU/Linux is hard to install” (I found it easy to install in 2008, and installing other software and fixing settings is something one does on any platform);
– “LibreOffice isn’t fully compatible with MS Word” (that’s a very nuanced conversation that strictly speaking is technically correct, but mostly trivially, IMO);
– “I’m accustomed to program X”;
– “I didn’t know that you could do that using free software”.

The lunch included in the admission fee was fine albeit a bit too frou-frou for my tastes, and totally inedible for my brother’s admittedly very narrow tastes. I would have hoped that there might have been more than three or four tables in the trade show part of the conference, which was held in the large lunch room area, but that’s neither here nor there.

The two afternoon sessions I attended were on the subject of “Accessing the Moodle Community”, and the ProjectLibre software.

The first presentation on the Moodle Community seemed a bit off and probably confusing to most of the participants, being a bit obscure and technical. However, once I re-read the title in the day’s schedule, I realized that it *was* on topic (both for the conference, and, on topic for his presentation.) Disappointingly, the presenter was delayed by a good fifteen minutes, for technical reasons: He could not use his computer for his presentation, given that for some reason he was unable to plug it into the projector. He then tried to present his slides prepared in LibreOffice with a computer using MS Powerpoint, which did not like his slides. He finally had to install LibreOffice on the supplied computer which was effectively permanently connected to the projector, or the setup otherwise effectively precluded the use of his own computer. He should have been prepared with the slides saved in PDF format, but to his credit he had placed the presentation online so that he could access it easily, in addition to having brought it on his computer.

The second presentation was a bit better as it at least was a demo of free software that can be used by educators / schools / etc. to either to manage their projects, what kind of software can be taught in schools, etc.

However, I thought that the two individual presenters I saw had two failings beyond what I mentioned earlier about the Moodle presenter:

– They only had about half an hour each; they could have done with at least another 15 minutes each. Each went over their allotted time; in any case, they should have timed things better in their presentations given that they knew of their time limitations, or should have known, given the announcements online and in the printed schedules liberally distributed during the conference.
– They should have been coached in advance with “ok, present what you want the way you want, *BUT*, please spend the first up to five minutes answering these five questions, such as a brief description of what the software / project / topic is, what its use could mean to the participants, etc. etc. etc.” In addition, I thought that each unfortunately were unprepared for people asking questions and making comments during the presentations, which could have been handled with “Could you wait until I finish my presentation, at which point I’d love to take your questions and feedback.”

Overall, however, I did love participating in the conference.

Update 27 April 2016:

Here is the link to the ADTE’s conference recap page (in French) (and here’s my archive)

In it are links to YouTube videos of Mr. Stallman’s presentation as well as a number of links to speakers’ quick resumé of what they spoke about to even sometimes slides of their presentations, again normally in French.

I’d say that Fedora has arrived!

Almost five years ago in March 2010, I stated “Ubuntu and Fedora LiveCDs — Ubuntu a clear winner!”

I’d burned two live CD’s — one of the current Fedora of the day, and one of the current Ubuntu of the day. I had wanted a group I belonged to to use one to reformat a virus-infected computer to use it again. Incidentally, they declined the honour, however that’s beyond my point: I didn’t want to give them (or anyone) the Fedora CD, while I thought that the Ubuntu CD was great out of the box, specifically including OpenOffice.org (now LibreOffice) and a cute little directory including a short video, a sample mortgage calculator, and two or three other little gems which really put the CD over the top for its immediate usefulness.

Well, I haven’t really used Live CD’s much since I’m not all that worried about having linux on the run, but at this point Fedora 21 seems to only be available by Live CD’s. But to wit, the experience with Fedora 21 seems to be quite the improvement in experience, according to at least two of my somewhere between the stated and implicit standards of comparison: The inclusion of (now) LibreOffice, what I considered a killer omission, and the ability to quickly and easily install many “productive” pieces of software through the new software installer. To be fair, at the time Fedora limited itself to CD’s and in its efforts to include as wide a base as possible for supposed widest mass appeal, Fedora was unable to include OpenOffice.org (or, as possible, any usable subset thereof) due to space restrictions, although it was able to include AbiWord.

Now, Fedora Workstation includes LibreOffice, and by typing into the search box in the “Activities Overview” (click on “Activities” on the upper left hand corner of the screen, or invoke it using the “hot corner” by bringing your cursor up there), the installed software that may help you, as well as a number of other pieces of software in the repositories which may help you, as indicated by a little shopping bag to the left of the proposed piece of software.

screenshot of proposed software

Well, I guess now I just need to find someone who needs to have their computer saved from viruses and spyware. 🙂

Ubuntu and Fedora LiveCDs — Ubuntu a clear winner!

I’m trying to convince a certain group to wipe their virus infected (and no doubt with trojan horses, key loggers, and spyware) computer over to linux, and so I’ve burned the Fedora 12 Live CD and the Ubuntu 9.10 Live CD.

I don’t want to bother giving them the Fedora Live CD. The Ubuntu CD is far too slick. And, the Fedora Live CD is far too vanilla. And that’s despite my usual rivalry with Ubuntu; at first glance, the killer is the inclusion of OpenOffice.org on the Ubuntu CD, while Fedora has the lightweight (albeit otherwise capable) AbiWord. Even the brown looks bright and welcoming, as opposed to Fedora’s more conservative, dull greyish-blue.

Add to that the directory of various files introducing Ubuntu, what it’s about, and even a sample mortgage calculator, and it’s little wonder that Ubuntu gets a whole lot of first timers straight out of the gate, or that first timers settle on Ubuntu after trying a bunch of other distros. As a marketing tool (at least for the desktop), the Ubuntu CD wins hands down; I’m not even sure that fully set up via traditional means from the DVD or full set of CD’s Fedora is this flashy.

I’ve been telling people for a while that “I use Fedora, but you’ll find Ubuntu easier”. I’ve just seen the proof. Seeing the CD, I would want to start afresh with it. I won’t of course, but I was impressed.

I’m wondering, though, which is the real killer — the inclusion of OpenOffice.org, or the directory introducing Ubuntu? I bet that were Fedora to mount a similar directory, including how to expand upon the base supplied on the CD, that people might take it up a bit more. I’m thinking of things like “Accustomed to OpenOffice.org? Go here and this is what you do.” or a “top five” “what to do once you install the Fedora base (or even just the Live-CD)” based on “Common desktop tasks”, “Setting up a home file and media server”, or the usual choices found in the standard anaconda setup.

I’m even thinking that the Ubuntu Live CD is productive — and “complete” — right away with its little directory, forget having little tutorials.

I guess that I should find out about whether or not Fedora does something like this, though … 🙂