text:
|Brian Youmans
|[gfsd]Re: Gcompris
|Mon, 21 May 2001 15:32:05 -0400
OK, you have been added to our list of maintainers, and to our address@hidden announcement list for GNU package maintainers. Here is a copy of the maintain.text file, a handbook for GNU package maintainers. A copy can be found on the web at http://www.gnu.org/prep/maintain.html. - Brian Youmans, FSF office staff --- START-INFO-DIR-ENTRY * Maintaining: (maintain). Maintaining GNU software. END-INFO-DIR-ENTRY Information for maintainers of GNU software. Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000 Free Software Foundation, Inc. Permission is granted to make and distribute verbatim copies of this document, provided the copyright notice and this permission notice are preserved on all copies. Version ******* Last updated March 13, 2001. About This Document ******************* This file contains guidelines and advice for someone who is the maintainer of a GNU program on behalf of the GNU Project. Everyone is entitled to change and redistribute GNU software; you need not pay attention to this file to get permission. But if you want to maintain a version for widespread distribution, we suggest you follow these guidelines; if you would like to be a GNU maintainer, then it is essential to follow these guidelines. Please send corrections or suggestions for this document to <address@hidden>. If you make a suggestion, please include a suggested new wording for it, to help us consider the suggestion efficiently. We prefer a context diff to the `maintain.texi' file, but if you don't have that file, you can make a context diff for some other version of this document, or propose it in any way that makes it clear. This document uses the gender-neutral third-person pronouns "person", "per", "pers" and "perself" which were promoted, and perhaps invented, by Marge Piercy in `Woman on the Edge of Time'. They are used just like "she", "her", "hers" and "herself", except that they apply equally to males and females. For example, "Person placed per new program under the GNU GPL, to let the public benefit from per work, and to enable per to feel person has done the right thing." The directory `/gd/gnuorg' is found on the GNU machines; if you are the maintainer of a GNU package, you should have an account on them. Contact <address@hidden> if you don't have one. (You can also ask for accounts for people who help you a large amount in working on the package.) `/gd/gnuorg/maintain.tar.gz' is a tar file containing all of these files in that directory which are mentioned in this file; it is updated daily. This release of the GNU Maintenance Instructions was last updated March 13, 2001. Stepping Down ************* With good fortune, you will continue maintaining your package for many decades. But sometimes for various reasons maintainers decide to step down. If you're the official maintainer of a GNU package and you decide to step down, please inform the GNU Project (<address@hidden>). We need to know that the package no longer has a maintainer, so we can look for and appoint a new maintainer. If you have an idea for who should take over, please tell <address@hidden> your suggestion. The appointment of a new maintainer needs the GNU Project's confirmation, but your judgement that a person is capable of doing the job will carry a lot of weight. Recruiting Developers ********************* Unless your package is a fairly small, you probably won't do all the work on it yourself. Most maintainers recruit other developers to help. Sometimes people will offer to help. Some of them will be capable, while others will not. It's up to you to determine who provides useful help, and encourage those people to participate more. Some of the people who offer to help will support the GNU Project, while others may be interested for other reasons. Some will support the goals of the Free Software Movement, but some may not. They are all welcome to help with the work--we don't ask people's views or motivations before they contribute to GNU packages. As a consequence, you cannot expect all contributors to support the GNU Project, or to have a concern for its policies and standards. So part of your job as maintainer is to exercise your authority on these points when they arise. No matter how much of the work other people do, you and not they are in charge of what goes in the release. When a crucial point arises, you should calmly state your decision and stick to it. Sometimes a package has several co-maintainers who share the role of maintainer. Unlike developers who help, co-maintainers have actually been appointed jointly as the maintainers of the package, and they carry out the maintainer's functions together. If you would like to propose some of your developers as co-maintainers, please contact <address@hidden>. Legal Matters ************* This chapter describes procedures you should follow for legal reasons as you maintain the program, to avoid legal difficulties. Recording Contributors ====================== *Keep correct records of which portions were written by whom.* This is very important. These records should say which files, or parts of files, were written by each person, and which files or portions were revised by each person. But they don't need to be as detailed as a change log. They don't need to distinguish work done at different times, only different people. They don't need describe changes in more detail than which files or parts of a file were changed. And they don't need to say anything about the function or purpose of a file or change-the Register of Copyrights doesn't care what the text does, just who wrote or contributed to which parts. You need not list someone who has contributed just a few lines (less than 15) of minor changes, but keep in mind that a series of minor changes can add up to a significant contribution that does need to be listed. The list should also mention if certain files distributed in the same package are really a separate program. For example, this would describe an early version of GAS: Dean Elsner first version of all files except gdb-lines.c and m68k.c. Jay Fenlason entire files gdb-lines.c and m68k.c, most of app.c, plus extensive changes in messages.c, input-file.c, write.c and revisions elsewhere. Note: GAS is distributed with the files obstack.c and obstack.h, but they are considered a separate package, not part of GAS proper. Please keep these records in a file named `AUTHORS' in the source directory for the program itself. Copyright Papers ================ If you maintain an FSF-copyrighted package, then you should follow certain legal procedures when incorporating changes written by other people. This ensures that the FSF has the legal right to distribute the package, and the right to defend its free status in court if necessary. *Before* incorporating significant changes, make sure that the person who wrote the changes has signed copyright papers and that the Free Software Foundation has received and signed them. We may also need a disclaimer from the person's employer. To check whether papers have been received, look in `/gd/gnuorg/copyright.list'. If you can't look there directly, <address@hidden> can check for you. Our clerk can also check for papers that are waiting to be entered and inform you when expected papers arrive. The directory `/gd/gnuorg' is found on the GNU machines; if you are the maintainer of a GNU package, you should have an account on them. Contact <address@hidden> if you don't have one. (You can also ask for accounts for people who help you a large amount in working on the package.) In order for the contributor to know person should sign papers, you need to ask for the necessary papers. If you don't know per well, and you don't know that person is used to our ways of handling copyright papers, then it might be a good idea to raise the subject with a message like this: Would you be willing to assign the copyright to the Free Software Foundation, so that we could install it in PROGRAM? or Would you be willing to sign a copyright disclaimer to put this change in the public domain, so that we can install it in PROGRAM? If the contributor wants more information, you can send per `/gd/gnuorg/conditions.text', which explains per options (assign vs. disclaim) and their consequences. Once the conversation is under way and the contributor is ready for more details, you should send one of the templates that are found in `/gd/gnuorg'. This section explains which templates you should use in which circumstances. *Please don't use any of the templates except for those listed here, and please don't change the wording.* Once the conversation is under way, you can send the contributor the precise wording and instructions by email. Before you do this, make sure to get the current version of the template you will use! We change these templates occasionally--don't keep using an old version. For large changes, ask the contributor for an assignment. Send per a copy of the file `/gd/gnuorg/request-assign.changes'. For medium to small changes, request a disclaimer by sending per the file `/gd/gnuorg/request-disclaim.changes'. If the contributor is likely to keep making changes, person might want to sign an assignment for all per future changes to the program. So it is useful to offer per that alternative. If person wants to do it that way, send per the `/gd/gnuorg/request-assign.future'. When you send a `request-' file, you don't need to fill in anything before sending it. Just send the file verbatim to the contributor. The file gives per instructions for how to ask the FSF to mail per the papers to sign. The `request-' file also raises the issue of getting a copyright disclaimer from the contributor's employer. For less common cases, we have template files you should send to the contributor. Be sure to fill in the name of the person and the name of the program in these templates, where it says NAME OF PERSON and NAME OF PROGRAM, before sending; otherwise person might sign without noticing them, and the papers would be useless. Note that in some templates there is more than one place to put the name of the program or the name of the person; be sure to change all of them. All the templates raise the issue of an employer's disclaimer as well. You do not need to ask for separate papers for a manual that is distributed only in the software package it describes. But if we sometimes distribute the manual separately (for instance, if we publish it as a book), then we need separate legal papers for changes in the manual. For smaller changes, use `/gd/gnuorg/disclaim.changes.manual'; for larger ones, use `/gd/gnuorg/assign.changes.manual'. To cover both past and future changes to a manual, you can use `/gd/gnuorg/assign.future.manual'. For a translation of a manual, use `/gd/gnuorg/assign.translate.manual'. If a contributor is reluctant to sign an assignment for a large change, and is willing to sign a disclaimer instead, that is acceptable, so you should offer this alternative if it helps you reach agreement. We prefer an assignment for a larger change, so that we can enforce the GNU GPL for the new text, but a disclaimer is enough to let us use the text. If you maintain a collection of programs, occasionally someone will contribute an entire separate program or manual that should be added to the collection. Then you can use the files `request-assign.program', `disclaim.program', `assign.manual', and `disclaim.manual'. We very much prefer an assignment for a new separate program or manual, unless it is quite small, but a disclaimer is acceptable if the contributor insists on handling the matter that way. *Although there are other templates besides the ones listed here, they are for special circumstances; please do not use them without getting advice from <address@hidden>.* If you are not sure what to do, then please ask <address@hidden> for advice; if the contributor asks you questions about the meaning and consequences of the legal papers, and you don't know the answers, you can forward them to <address@hidden> and we will answer. *Please do not try changing the wording of a template yourself. If you think a change is needed, please talk with <address@hidden>, and we will work with a lawyer to decide what to do.* Copyright Notices ================= You should maintain a legally valid copyright notice and a license notice in each nontrivial file in the package. (Any file more than ten lines long is nontrivial for this purpose.) This includes header files and interface definitions, makefiles, scripts, other data files used in building or running the program, documentation files, and any supporting files. If a file has been explicitly placed in the public domain, then instead of a copyright notice, it should have a notice saying explicitly that it is in the public domain. Even image files and sound files should contain copyright notices and license notices, if they can. Some formats do not have room for textual annotations; for these files, state the copyright and copying permissions in a README file in the same directory. Change log files should have a copyright notice and license notice at the end, since new material is added at the beginning but the end remains the end. When a file is automatically generated from some other file in the distribution, it is useful to copy the copyright notice and permission notice of the file it is generated from, if you can. Alternatively, put a notice at the beginning saying which file it is generated from. A copyright notice looks like this: Copyright YEAR1, YEAR2, YEAR3 COPYRIGHT-HOLDER The COPYRIGHT-HOLDER may be the Free Software Foundation, Inc., or someone else; you should know who is the copyright holder for your package. The list of year numbers should include each year in which you finished preparing a version which was actually released, and which was an ancestor of the current version. Please reread the paragraph above, slowly and carefully. It is important to understand that rule precisely, much as you would understand a complicated C statement in order to hand-simulate it. This list is _not_ a list of years in which versions were _released_. It is a list of years in which versions, later released, were _completed_. So if you finish a version on Dec 31, 1994 and release it on Jan 1, 1995, this version requires the inclusion of 1994, but doesn't require the inclusion of 1995. Do not abbreviate the year list using a range; for instance, do not write `1996--1998'; instead, write `1996, 1997, 1998'. The versions that matter, for purposes of this list, are versions that were ancestors of the current version. So if you made a temporary branch in maintenance, and worked on branches A and B in parallel, then each branch would have its own list of years, which is based on the versions released in that branch. A version in branch A need not be reflected in the list of years for branch B, and vice versa. However, if you copy code from branch A into branch B, the years for branch A (or at least, for the parts that you copied into branch B) do need to appear in the list in branch B, because now they are ancestors of branch B. This rule is complicated. If we were in charge of copyright law, we would probably change this (as well as many other aspects). For an FSF-copyrighted package, if you have followed the procedures to obtain legal papers, each file should have just one copyright holder: the Free Software Foundation, Inc. So the copyright notice should give that name. But if contributors are not all assigning their copyrights to a single copyright holder, it can easily happen that one file has several copyright holders. Each contributor of nontrivial amounts is a copyright holder. In that case, you should always include a copyright notice in the name of main copyright holder of the file. You can also include copyright notices for other copyright holders as well, and this is a good idea for those who have contributed a large amount and for those who specifically ask for notices in their names. But you don't have to include a notice for everyone who contributed to the file, and that would be rather inconvenient. License Notices =============== Every nontrivial file needs a license notice as well as the copyright notice. (Without a license notice giving permission to copy and change the file, copying and modification are legally prohibited, and that would make the file non-free.) Typically the license notice for program files (including build scripts, configure files and makefiles) should cite the GPL, like this: This file is part of GNU PROGRAM GNU PROGRAM is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version. GNU PROGRAM is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with PROGRAM; see the file COPYING. If not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. But in a small program which is just a few files, you can use this instead: This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA. Documentation files should have license notices also. Manuals should use the GNU Free Documentation License. Here is an example of the license notice to use after the copyright notice. Please adjust the list of invariant sections as appropriate for your manual. (If there are none, then say "with no invariant sections".) Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with the Invariant Sections being "GNU General Public License", the Front-Cover texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the section entitled "GNU Free Documentation License". (a) The FSF's Front-Cover Text is: A GNU Manual (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. If the FSF does not publish this manual on paper, then omit the last sentence that talks about copies published by the FSF. If the FSF is not the copyright holder, then replace `FSF' with the appropriate name. Note that when you distribute several manuals together in one software package, their on-line forms can share a single copy of the GFDL (see section 6). However, the printed (`.dvi') forms should each contain a copy of the GFDL, unless they are set up to be printed and published only together. Small supporting files, short manuals (under 300 lines long) and rough documentation (README files, INSTALL files, etc) can use simple all-permissive licenses. If you would like help with license issues or with using the GFDL, please contact <address@hidden>. External Libraries ================== When maintaining an FSF-copyrighted GNU package, sometimes you will want to use a general-purpose free software module which offers a useful functionality, as a "library" facility (though the module is not always packaged technically as a library). In a case like this, it would be unreasonable to ask the author of that module to assign the copyright to the FSF. After all, person did not write it specifically as a contribution to your package, so it would be impertinent to ask per, out of the blue, "Please give the FSF your copyright." So the thing to do in this case is to make your program use the module, but not consider it a part of your program. There are two reasonable methods of doing this: 1. Assume the module is already installed on the system, and use it when linking your program. This is only reasonable if the module really has the form of a library. 2. Include the module in your package, putting the source in a separate subdirectory whose `README' file says, "This is not part of the GNU FOO program, but is used with GNU FOO." Then set up your makefiles to build this module and link it into the executable. For this method, it is not necessary to treat the module as a library and make a `.a' file from it. You can link with the `.o' files directly in the usual manner. Both of these methods create an irregularity, and our lawyers have told us to minimize the amount of such irregularity. So consider using these methods only for general-purpose modules that were written for other programs and released separately for general use. For anything that was written as a contribution to your package, please get papers signed. Cleaning Up Changes ******************* Don't feel obligated to include every change that someone asks you to include. You must judge which changes are improvements--partly based on what you think the users will like, and partly based on your own judgement of what is an improverment. If you think a change is not good, you should reject it. If someone sends you changes which are useful, but written in an ugly way or hard to understand and maintain in the future, don't hesitate to ask person to clean up per changes before you merge them. Since the amount of work we can do is limited, the more we convince others to help us work efficiently, the faster GNU will advance. If the contributor will not or can not make the changes clean enough, then it is legitimate to say "I can't install this in its present form; I can only do so if you clean it up." Invite per to distribute per changes another way, or to find other people to make them clean enough for you to install and maintain. The only reason to do these cleanups yourself is if (1) it is easy, less work than telling the author what to clean up, or (2) the change is an important one, important enough to be worth the work of cleaning it up. The GNU Coding Standards are a good thing to send people when you ask them to clean up changes (*note Contents: (standards)Top.). The Emacs Lisp manual contains an appendix that gives coding standards for Emacs Lisp programs; it is good to urge authors to read it (*note Tips and Standards: (elisp)Tips.). Dealing With Mail ***************** Once a program is in use, you will get bug reports for it. Most GNU programs have their own special lists for sending bug reports. The advertised bug-reporting email address should always be address@hidden', to help show users that the program is a GNU package, but it is ok to set up that list to forward to another site for further forwarding. The package distribution should state the name of the bug-reporting list in a prominent place, and ask users to help us by reporting bugs there. We also have a catch-all list, <address@hidden>, which is used for all GNU programs that don't have their own specific lists. But nowadays we want to give each program its own bug-reporting list and move away from using <bug-gnu-utils>. If you are the maintainer of a GNU package, you should have an account on the GNU servers; contact <address@hidden> if you don't have one. (You can also ask for accounts for people who help you a large amount in working on the package.) With this account, you can edit `/com/mailer/aliases' to create a new unmanaged list or add yourself to an existing unmanaged list. A comment near the beginning of that file explains how to create a Mailman-managed mailing list. But if you don't want to learn how to do those things, you can alternatively ask <address@hidden> to add you to the bug-reporting list for your program. To set up a new list, contact <address@hidden>. You can subscribe to a list managed by Mailman by sending mail to the corresponding `-request' address. When you receive bug reports, keep in mind that bug reports are crucial for your work. If you don't know about problems, you cannot fix them. So always thank each person who sends a bug report. You don't have an obligation to give more response than that, though. The main purpose of bug reports is to help you contribute to the community by improving the next version of the program. Many of the people who report bugs don't realize this--they think that the point is for you to help them individually. Some will ask you to focus on that _instead of_ on making the program better. If you comply with their wishes, you will have been distracted from the job of maintaining the program. For example, people sometimes report a bug in a vague (and therefore useless) way, and when you ask for more information, they say, "I just wanted to see if you already knew the solution" (in which case the bug report would do nothing to help improve the program). When this happens, you should explain to them the real purpose of bug reports. (A canned explanation will make this more efficient.) When people ask you to put your time into helping them use the program, it may seem "helpful" to do what they ask. But it is much _less_ helpful than improving the program, which is the maintainer's real job. By all means help individual users when you feel like it, if you feel you have the time available. But be careful to limit the amount of time you spend doing this--don't let it eat away the time you need to maintain the program! Know how to say no; when you are pressed for time, just "thanks for the bug report--I will fix it" is enough response. Some GNU packages, such as Emacs and GCC, come with advice about how to make bug reports useful. If you want to copy and adapt that, it could be a very useful thing to do. Recording Old Versions ********************** It is very important to keep backup files of all source files of GNU. You can do this using RCS, CVS or PRCS if you like. The easiest way to use RCS or CVS is via the Version Control library in Emacs; *Note Concepts of Version Control: (emacs)Concepts of VC. The history of previous revisions and log entries is very important for future maintainers of the package, so even if you do not make it publicly accessible, be careful not to put anything in the repository or change log that you would not want to hand over to another maintainer some day. The GNU Project provides a CVS server that GNU software packages can use: `subversions.gnu.org'. (The name refers to the multiple versions and their subversions that are stored in a CVS repository.) You don't have to use this repository, but if you plan to allow public read-only access to your development sources, it is convenient for people to be able to find various GNU packages in a central place. The CVS Server is managed by <address@hidden>. Distributions ************* It is important to follow the GNU conventions when making GNU software distributions. Distribution tar Files ====================== The tar file for version M.N of program `foo' should be named `foo-M.N.tar'. It should unpack into a subdirectory named `foo-M.N'. Tar files should not unpack into files in the current directory, because this is inconvenient if the user happens to unpack into a directory with other files in it. Here is how the `Makefile' for Bison creates the tar file. This method is good for other programs. dist: bison.info echo bison-`sed -e '/version_string/!d' \ -e 's/[^0-9.]*\([0-9.]*\).*/\1/' -e q version.c` > .fname -rm -rf `cat .fname` mkdir `cat .fname` dst=`cat .fname`; for f in $(DISTFILES); do \ ln $(srcdir)/$$f $$dst/$$f || { echo copying $$f; \ cp -p $(srcdir)/$$f $$dst/$$f ; } \ done tar --gzip -chf `cat .fname`.tar.gz `cat .fname` -rm -rf `cat .fname` .fname Source files that are symbolic links to other file systems cannot be installed in the temporary directory using `ln', so use `cp' if `ln' fails. Using Automake is a good way to take care of writing the `dist' target. Distribution Patches ==================== If the program is large, it is useful to make a set of diffs for each release, against the previous important release. At the front of the set of diffs, put a short explanation of which version this is for and which previous version it is relative to. Also explain what else people need to do to update the sources properly (for example, delete or rename certain files before installing the diffs). The purpose of having diffs is that they are small. To keep them small, exclude files that the user can easily update. For example, exclude info files, DVI files, tags tables, output files of Bison or Flex. In Emacs diffs, we exclude compiled Lisp files, leaving it up to the installer to recompile the patched sources. When you make the diffs, each version should be in a directory suitably named--for example, `gcc-2.3.2' and `gcc-2.3.3'. This way, it will be very clear from the diffs themselves which version is which. If you use GNU `diff' to make the patch, use the options `-rc2P'. That will put any new files into the output as "entirely different." Also, the patch's context diff headers should have dates and times in Universal Time using traditional Unix format, so that patch recipients can use GNU `patch''s `-Z' option. For example, you could use the following Bourne shell command to create the patch: LC_ALL=C TZ=UTC0 diff -rc2P gcc-2.3.2 gcc-2.3.3 | \ gzip -9 >gcc-2.3.2-2.3.3.patch.gz If the distribution has subdirectories in it, then the diffs probably include some files in the subdirectories. To help users install such patches reliably, give them precise directions for how to run patch. For example, say this: To apply these patches, cd to the main directory of the program and then use `patch -p1'. `-p1' avoids guesswork in choosing which subdirectory to find each file in. It's wise to test your patch by applying it to a copy of the old version, and checking that the result exactly matches the new version. Distribution on `ftp.gnu.org' ============================= GNU packages are distributed through directory `/gnu' on `ftp.gnu.org'. Each package should have a subdirectory named after the package, and all the distribution files for the package should go in that subdirectory. Only the latest version of any program needs to be on `ftp.gnu.org'. Being an archive of old versions is not the function of `ftp.gnu.org'. Diffs are another matter. Since they are much smaller than distribution files, it is good to keep the diffs around for quite a while. Please talk with <address@hidden> in regard to putting new versions on `ftp.gnu.org'. If you have an interest in seeing the monthly download logs from the FTP site at `ftp.gnu.org' for your program, that is something that <address@hidden> can set up for you. Please contact them if you are interested. Test Releases ============= When you release a greatly changed new major version of a program, you might want to do so as a pretest. This means that you make a tar file, but send it only to a group of volunteers that you have recruited. (Use a suitable GNU mailing list/newsgroup to recruit them.) We normally use the FTP server `alpha.gnu.org' for pretests and prerelease versions. You can place items on `alpha.gnu.org' by putting them in the `~ftp/gnu' directory on `fencepost.gnu.org'. Once a program gets to be widely used and people expect it to work solidly, it is a good idea to do pretest releases before each "real" release. If you are about to release version 4.6 but you want to do a pretest first, call it 4.5.90. If you need a second pretest, call it 4.5.91, and so on. If you are really unlucky and ten pretests are not enough, after 4.5.99 you could advance to 4.5.990 and so on. One thing that you should never do is to release a pretest with the same version number as the planned real release. Many people will look only at the version number (in the tar file name, in the directory name that it unpacks into, or wherever they can find it) to determine whether a tar file is the latest version. People might look at the test release in this way and mistake it for the real release. Therefore, always change the number when you release changed code. Announcing Releases ******************* When you have a new release, please make an announcement. You can maintain your own mailing list for announcements if you like, or you can use the moderated general GNU announcements list, <address@hidden>. If you use your own list, you can decide as you see fit what events are worth announcing. If you use <address@hidden>, please do not announce pretest releases, only real releases. But real releases do include releases made just to fix bugs. Web Pages ********* Please write pages about your package for installation `www.gnu.org'. The pages should follow our usual standards for web pages (see <http://www.gnu.org/server>); we chose them in order to support a wide variety of browsers, to focus on information rather than flashy eye candy, and to keep the site simple and uniform. Please talk with <address@hidden> about the arrangements for installing and updating pages. There are various ways this can be done: you can mail them pages to install, they can make an account for you, or you can keep the pages in CVS on `subversions.gnu.org' and have them automatically checked out into the web server. Some GNU packages have just simple web pages, but the more information you provide, the better. So please write as much as you usefully can, and put all of it on `www.gnu.org'. However, pages that access databases (such as mail logs or bug tracking) are an exception; set them up wherever is convenient for you, and the pages on `www.gnu.org' can link to them. Terminology Issues ****************** This chapter explains a couple of issues of terminology which are important for correcting two widespread and important misunderstandings about GNU. Free Software and Open Source ============================= The terms "free software" and "open source" are the slogans of two different movements which differ in their basic philosophy. The Free Software Movement is idealistic, and raises issues of freedom, ethics, principle and what makes for a good society. The Open Source Movement, founded in 1998, studiously avoids such questions. For more explanation, see <http://www.gnu.org/philosophy/free-software-for-freedom.html>. The GNU Project is aligned with the Free Software Movement. This doesn't mean that all GNU contributors and maintainers have to agree; your views on these issues are up to you, and you're entitled to express them when speaking for yourself. However, due to the much greater publicity that the Open Source Movement receives, the GNU Project needs to overcome a widespread mistaken impression that GNU is _and always was_ an activity of the Open Source Movement. For this reason, please use the term "free software," rather than "open source," in GNU software releases, GNU documentation, and announcements and articles that you publish in your role as the maintainer of a GNU package. A reference to the URL given above, to explain the difference, is a useful thing to include as well. GNU and Linux ============= The GNU Project was formed to develop a free Unix-like operating system, GNU. The existence of this system is our major accomplishment. However, the widely used version of the GNU system, in which Linux is used as the kernel, is often called simply "Linux". As a result, most users don't know about the GNU Project's major accomplishment--or more precisely, they know about it, but don't realize it is the GNU Project's accomplishment and reason for existence. Even people who believe they know the real history often believe that the goal of GNU was to develop "tools" or "utilities." To correct this confusion, we have made a years-long effort to distinguish between Linux, the kernel that Linus Torvalds wrote, and GNU/Linux, the operating system that is the combination of GNU and Linux. The resulting increased awareness of what the GNU Project has already done helps every activity of the GNU Project recruit more support and contributors. Please make this distinction consistently in GNU software releases, GNU documentation, and announcements and articles that you publish in your role as the maintainer of a GNU package. If you want to explain the terminology and its reasons, you can refer to the URL <http://www.gnu.org/gnu/linux-and-gnu.html>. Hosting ******* We would like to recommend using `subversions.gnu.org' as the CVS repository for your package, and using `ftp.gnu.org' as the standard FTP site. It is ok to use other machines if you wish. If you use a company's machine to hold the repository for your program, or as its ftp site, please put this statement in a prominent place on the site, so as to prevent people from getting the wrong idea about the relationship between the package and the company: The programs <list of them> hosted here are free software packages of the GNU Project, not products of <company name>. We call them "free software" because you are free to copy and redistribute them, following the rules stated in the license of each package. For more information, see http://www.gnu.org/philosophy/free-sw.html. If you are looking for service or support for GNU software, see http://www.gnu.org/help/gethelp.html for suggestions of where to ask. If you would like to contribute to the development of one of these packages, contact the package maintainer or the bug-reporting address of the package (which should be listed in the package itself), or look on www.gnu.org for more information on how to contribute. Free Software Directory *********************** The Free Software Directory aims to be a complete list of free software packages, within certain criteria. Every GNU package should be listed there, so please contact <address@hidden> to ask for information on how to write an entry for your package. Using the Proofreaders List *************************** If you want help finding errors in documentation, or help improving the quality of writing, or if you are not a native speaker of English and want help producing good English documentation, you can use the GNU proofreaders mailing list: <address@hidden>. But be careful when you use the list, because there are over 200 people on it. If you simply ask everyone on the list to read your work, there will probably be tremendous duplication of effort by the proofreaders, and you will probably get the same errors reported 100 times. This must be avoided. Also, the people on the list do not want to get a large amount of mail from it. So do not ever ask people on the list to send mail to the list! Here are a few methods that seem reasonable to use: * For something small, mail it to the list, and ask people to pick a random number from 1 to 20, and read it if the number comes out as 10. This way, assuming 50% response, some 5 people will read the piece. * For a larger work, divide your work into around 20 equal-sized parts, tell people where to get it, and ask each person to pick randomly which part to read. Be sure to specify the random choice procedure; otherwise people will probably use a mental procedure that is not really random, such as "pick a part near the middle", and you will not get even coverage. You can either divide up the work physically, into 20 separate files, or describe a virtual division, such as by sections (if your work has approximately 20 sections). If you do the latter, be sure to be precise about it--for example, do you want the material before the first section heading to count as a section, or not? * For a job needing special skills, send an explanation of it, and ask people to send you mail if they volunteer for the job. When you get enough volunteers, send another message to the list saying "I have enough volunteers, no more please." Index ***** /gd/gnuorg directory: See ``Copyright Papers''. alpha.gnu.org, ftp site for test releases: See ``Test Releases''. AUTHORS file: See ``Recording Contributors''. automake: See ``Distribution tar Files''. beta releases: See ``Test Releases''. bug reports: See ``Dealing With Mail''. contributions, accepting: See ``Cleaning Up Changes''. copyright notices in program files: See ``Copyright Notices''. copyright papers: See ``Copyright Papers''. CVS repository: See ``Hosting''. data base of GNU copyright assignments: See ``Copyright Papers''. diff: See ``Distribution Patches''. distribution, tar files: See ``Distribution tar Files''. email, for receiving bug reports: See ``Dealing With Mail''. free software: See ``Free Software and Open Source''. Free Software Directory: See ``Free Software Directory''. FTP site: See ``Hosting''. ftp.gnu.org, the GNU ftp site: See ``Distribution on `ftp.gnu.org'''. GNU ftp site: See ``Distribution on `ftp.gnu.org'''. GNU/Linux: See ``GNU and Linux''. hosting: See ``Hosting''. legal matters: See ``Legal Matters''. legal papers for changes in manuals: See ``Copyright Papers''. license notices in program files: See ``License Notices''. Linux: See ``GNU and Linux''. mailing list for bug reports: See ``Dealing With Mail''. movements, Free Software and Open Source: See ``Free Software and Open Source''. open source: See ``Free Software and Open Source''. patch: See ``Distribution Patches''. patches, against previous releases: See ``Distribution Patches''. pretest releases: See ``Test Releases''. proofreading: See ``Using the Proofreaders List''. quality of changes suggested by others: See ``Cleaning Up Changes''. recording contributors: See ``Recording Contributors''. repository: See ``Hosting''. responding to bug reports: See ``Dealing With Mail''. terminology: See ``Terminology Issues''. test releases: See ``Test Releases''. time stamp in diffs: See ``Distribution Patches''. version control: See ``Recording Old Versions''. web pages: See ``Web Pages''. Table of Contents ***************** Version About This Document Stepping Down Recruiting Developers Legal Matters Recording Contributors Copyright Papers Copyright Notices License Notices External Libraries Cleaning Up Changes Dealing With Mail Recording Old Versions Distributions Distribution tar Files Distribution Patches Distribution on `ftp.gnu.org' Test Releases Announcing Releases Web Pages Terminology Issues Free Software and Open Source GNU and Linux Hosting Free Software Directory Using the Proofreaders List Index
|[Prev in Thread]
|Current Thread
|[Next in Thread]


text:
Gut Health 101 Series – 5 Steps to Healing the Gut
As part of the ongoing amazing Gut Summit launched in January where 35 experts from around the world presented the benefits of addressing your Gut health being at the core of many chronic health concerns.
For Dr Josh Axe, is fast becoming one of the leading experts in healing leaky gut and irritable bowel.
His journey began when his mother became ill when he was a child. They were a family who thought themselves to be healthy and fit, so this was somewhat of a surprise. His mother's health continued decline to a point where she was diagnosed with cancer at the age of 40. She commenced chemotherapy and proceeded to develop major digestive issues. According to Dr Axe his mother at one point would average 1 to 2 bowel movements a week for about 10 years.
Her health ailments ranged from constipation to autoimmune disease namely Hashimoto's thyroiditis, food sensitive's and depression.
Dr Axe introduced his mother to the concept of looking at the root cause of her illnesses instead of just treating the symptoms. They changed her diet radically and introduced vegetable juices and bone broths along with goat's milk kefir.
After 4 months of implementing a radical natural holistic approach she returned to her oncologist to find that the tumor in her lung had reduced by ½ and within a year she was in remission.
She also found that her bowel movements started to become more regular, daily, and the symptoms to her other health issues started to disappear.
As Hippocrates said "All disease begins in the gut".
In the medical world they are still denying the existence of leaky gut, so what exactly is it.
Dr Axe explains "Leaky gut is typically termed "Intestinal Permeability". There are over 11 000 different studies citing and sourcing leaky gut syndrome or should I say intestinal permeability. "
Your digestive system is basically a barrier to your bloodstream from your mouth to your anus. It allows certain nutrients and microorganisms to go through to the bloodstream and certain things out.
When you have chronic inflammation of the lining of the small intestine, it's similar to having a tear in your fishing net. Certain things start to pass through that shouldn't be able to.
If we take a protein like gluten and put it into the bloodstream where it should never be, our body sets up a inflammatory response which over time can turn into these immune or even autoimmune reactions.
Essentially, Dr Axe explains, leaky gut starts off with that inflammation of the small intestine, those junctions get larger and over time it can lead to immune issues like food sensitivities and further down the road autoimmune-like conditions as well.
So the 5 top things you can do according to Dr Axe are:
- Remove the triggers.
- Consume Healing and therapeutic foods
- Supplementation
- Change your Lifestyle
- Eat right for your Gut Type
Dr Zielinkski goes on to comment also about the onslaught of toxicity we are exposed to in our water, environments, food and personal care products.
Both Docors agreed that the first trigger is food. Food goes into our body on a daily basis, food can be our friend or our enemy.
One of the top foods to try and reduce or avoid is sugar. It is hidden in everything.
The number two food to avoid would be cows milk dairy which he suggests can be 26 times more inflammatory than gluten. In an average bottle of milk there are over 20 different medications and chemicals in our dairy supply.
3rd is gluten. We are eating foods today that are not properly prepared. Our ancestors used to sprout and ferment many foods prior to ingesting, traditionally for example sourdough and Ezekiel breads. This makes various foods easy to digest.
The last food Dr Axe believes is really adding to our leaky gut problems is GMO foods. Studies show that herbicides and pesticides do damage to the gut lining creating inflammation.
We will look next week at number 2 consuming healing and therapeutic foods to help heal the gut.
Ultimately though, we need to identify the foods that are the triggers and we believe the easiest, fastest and most effective way to do this is by taking a Bio Compatibility Test and finding out what foods your body is reacting to.
For more information on this interview or the Gut Healing Summit – click here

subset: commoncrawl


text:
I love the preaching and written ministry of Dr D.M. Lloyd-Jones. Likewise with Dr John Piper. Both men epitomise a love and desire for God's glory and majesty which is refreshing, infectious, and inspiring. Both men demonstrate a concern for fresh outpourings of God's grace by the Holy Spirit on His people. Both men are ruthlessly exegetical and expository in their style of ministry – demonstrating a commitment to allowing God's Word to speak for itself.
It comes as something of shock, then, when one finds the views of such men in collision. I am referring to an article which I have just listened to, and which can be read here, in which John Piper outlines a character sketch of the late Martyn Lloyd-Jones, and ultimately treats him with a fairly heavy hand. The title of the article is 'A Passion for Christ-Exalting Power' and Piper's main concern is to outline Lloyd-Jones position on the work and gifts of the Holy Spirit. He finds much in the life of the late Welshman that is commendable, and seems to resonate with Lloyd-Jones' position on pneumatology (which many of a Reformed persuasion struggle with), drawing quotes from some of the volumes not published by Banner of Truth, such as 'Revival' and 'Joy Unspeakable'. Piper's problem with Lloyd-Jones, however, is that he doesn't seem to go far enough in his view of the gifts, and the energy which should be expended by the Christian in pursuing them. Ultimately he writes Lloyd-Jones off as something of a bookworm who couldn't relate to people, and who wouldn't risk his reputation to follow his convictions. Piper opens this character sketch by recommending Iain H. Murray's two volume biography, but in referencing it seems to treat in a fairly derisory way.
My difficulty with Piper's approach is not necessarily his advocacy of charismatic teaching (although I do struggle with his statements on this issue) but with his poorly nuanced view of Lloyd-Jones. No time is given to exploring the latter's struggle against the onset of ecumenism or other issues threatening the evangelicalism of his day, and little is done to try to place Lloyd-Jones' views within the broader context of Puritanism and church history. In essence Lloyd-Jones' life is used as a springboard for teaching on pneumatology, and as far as he agrees with Piper's position he is commended, where his views diverge he is condemned. This comes across as unfair, and not a little sloppy in terms of research – which is surprising given Piper's normal brilliance in putting together biographical sketches. This lack of rigour is even demonstrated in simple things such as Piper's repeatedly wrong assertion that Lloyd-Jones founded the Banner of Truth Trust (although it is doubtful that the Trust would have so flourished without the foundational influence and financial assistance he afforded to Murray and Cullum).
This doesn't in any way affect my good opinion of John Piper – it just seems a shame to see such giants in collision. If anyone else has read/listened to this sketch, or has strong feelings about Lloyd-Jones' take on the work of the Holy Spirit, I'd love to hear from you.


text:
Community Advisory Committee
All AGE-WELL community partners are members of the Community Advisory Committee (CAC). The CAC is operated through an appointed Executive Committee that acts on behalf of all CAC members.
The CAC Executive Committee consists of the following members:
Susan Thorning, Chair ; AGE-WELL Board of Directors
Mary Lou Ackerman, VP Business Development, Saint Elizabeth Health Care
Ron Beleno, Independent Member, Personal Caregiver
Sue Cragg, Executive Director, Seniors Health Research Network
Don Fenn, President/CEO, Caregiver Omnimedia Inc.
Josephine Grayson, Independent Member, Care Watch
Dan Kohl, Executive Director, Health Services Organizations, Regina Qu'Appelle Health Region
Kirk Nylen, Executive Director, Ontario Brain Institute
Sandra McKay, Manager, Research & Evaluation, VHA HomeHealth Care
Alex Mihailidis, AGE-WELL Scientific Director
Bridgette Murphy, AGE-WELL Managing Director (observer)
Michelle Porter, Director of the Centre on Aging, University of Manitoba
Nalini Sen, Research Program Director, Alzheimer Society of Canada
Andrew Sixsmith, AGE-WELL Scientific Director


text:
A few days ago, I found gold in my inbox.
It was in a mass-mailing by Geometry & Topology Publications, announcing seven new papers. It was one of these, Fibered knots and potential counterexamples to the Property 2R and Slice-Ribbon Conjectures by Bob Gompf, Martin Scharlemann and Abigail Thompson, which really blew me away.
The paper is a gripping read. As I see things, its breakthrough result is the discovery of a family of slice knots which are unlikely to be ribbon, bringing my confidence in the veracity of the Slice-Ribbon Conjecture down from around 60% (what can I say? I was an optimist!) to around 5%. After more than 30 years, the Slice-Ribbon Conjecture is encircled and in imminent fear of annihilation.
A knot is slice if it bounds a disc in the 4-ball. It's ribbon if it bounds a self-intersecting disc in with only ribbon singularities. It's pretty easy to see that every ribbon knot must be slice (add one dimension and resolve the ribbon singularities using it), but there's no a-priori reason to suspect that every slice-knot would be ribbon… except that experimentally, every slice knot we know of happens to also be ribbon. We know loads of slice knots, which don't have much in common except the fact that they're slice… and they're all ribbon. All slice-knots which are 2-bridge are ribbon by a result of Lisca, and by a result of Greene and Jabucka, so are 3-stranded pretzel knots. And so, there's strong experimental support for Fox's:
Slice-Ribbon Conjecture: Every slice knot is ribbon.
The Slice-Ribbon Conjecture is a wish, which would simplify various 4-dimensional questions. In Israel one would call such a thing a pink dream. I wish it were true.
This paper (which I shall call GST for Gompf-Scharlemann-Thompson, not for Goods and Services Tax) tells us to wake up from our dream. It proposes a family of potential counterexamples to the Slice-Ribbon Conjecture, coming from proposed counterexamples to the Generalized Property R Conjecture.
Recall that David Gabai proved:
Property R: If 0-framed surgery on a knot yields $S^1\times S^2$ then is the unknot.
Generalized Proporty R is the generalization of this statement to links:
Generalized Property R Conjecture: If surgery on an -component link gives rise to a connect sum of copies of , then becomes the unlink after handle-slides.
Sadly, GST tells us that this conjecture has about as much chance of being true as the Andrews-Curtis Conjecture, which looks about as plausible as P=NP. More concretely, a square knot interleaved with the connect-sum of an torus knot with its mirror (call this 2-component link ) is a likely counterexample to the Generalized Property R Conjecture, which they show is implied by the fact that a balanced presentation of its link group is a long-known likely counterexample to the Andrews-Curtis Conjecture.
If a link were to satisfy the Generalized Property R Conjecture, then all of its band-sums (including knots) would be ribbon, but the hypothesis implies only that all such band-sums must be slice, by an (easy) result of Jonathan Hillman, quoted as Theorem 2.3 of GST. No issue arises with smooth structure in these examples, and so have no reason at all to be ribbon, although they are certainly slice. In fact, I'd be really surprised if they would turn out to be ribbon. And it wouldn't contradict the experimental evidence, because the simplest of these knots (for ) has 53 crossings (Figure 2 of GST), and so is far beyond the range of any experiments conducted up until this point in time.
There are a zillion ribbon-obstructions with which we could now bombard for , and if one of these works then the Slice-Ribbon Conjecture is toast. In fact, this is exactly what I think will happen. Somebody will write a computer programme to evaluate a ribbon obstruction on one of these (it looks horrible to do by hand!), and they'll be no reason to suspect it will vanish.
Finally, something which doesn't interest me personally as much (although it relates to the smooth 4-dimensional Poincare Conjecture): GST suggests a weaker Generalized Property R conjecture in which we're allowed to stabilize by introducing canceling Hopf pairs. It wouldn't be surprising if that were true, because 4-manifold topology behaves much more nicely after stabilization.
But what an exciting paper! If Slice-Ribbon survives this particular onslaught, I'll
eat tip my hat!


text:
My sons 7-9 in particular really dislike singing the primary songs at church. "They're all so slow, and boring," but when they're little sister got this kidz bop version of primary songs CD as a gift, guess who're the ones putting the cd on to play everyday? My boys! and they're actually singing along! These songs get the whole family dancing around! And the best part is my boys are finally learning the primary songs! I've bought this one and the Popcorn Dancing, and will keep buying every one you make! :D
My kiddos ask to listen to this cd just about every morning on the way to school, for the car ride home, and any opportunity they get to listen to music. It is fun music, great vocals, catchy rhythms, and of course amazing messages. Would recommend it to anyone. Love it!
We loved Popcorn Bopping and this one is just as great. Really liked the inclusion of "Got a dime in my pocket" as well as newer Primary program songs. This isn't for the pearl-clutchers. If you think all dance music is "evil," well, stick with your MoTab. Me, I'm happy to have music that I enjoy, that isn't babyish, that I'm happy my kids know the lyrics. They'll remember the words a lot longer!
We LOVED Popcorn Bopping so when I saw this today I immediately downloaded it. I think we're listening to it for the third time in a row right now. Wonderfully done, super fun to dance to! I turn it on and the kids and I dance (and clean) together. MUST HAVE!! And if you don't have Popcorn Bopping Yet GET IT!!
This is not your typical Primary Music! Each song has a "sound-alike" theme...it was like listening to Katie Perry or The Black Eyed Peas. My kids enjoyed dancing to this mix of CLEAN music and it has made our "Top 6" of car-rotation CDs. You won't regret this purchase!
These are the versions of the Primary songs my kids want to listen to. This album is more toned down than Popcorn Bopping- there are no block-rocking beats ala 'Follow the Prophet', but it is still fun (and respectful) with some old favorites by Janeen Brady thrown in (no relation). Everyone I have recommended this to has also raved about it.
Any family with children will love this CD and it's predecessor, "Popcorn Bopping".
"Scripture Power", "Nephi's Courage", "Army of Helaman" and others are upbeat arrangements of songs kids are familiar with and will love to sing and dance along to.
"Got a Dime in My Pocket" and "I Want to Be a Mother" are fun, nostalgic updates to popular 70's LDS songs that parents may remember.
I was disappointed to have some songs reused from Popcorn Bopping, although with new arrangements ("Saturday", "Fun to Do") and would have liked to have seen a mash-up or two like the original had.
The arrangement of "The Family Is of God" is worth the price of the album alone. It's one of the most musically-interesting and doctrinally-important songs in recent memory- Primary or otherwise- and it works remarkably well with a rock ballad arrangement. It's my favorite of the entire set.
Bottom line- any LDS child will love the fun music and uplifting messages in this album. I'm thrilled to add it to my family's playlist.
This CD is amazing!! The arrangements of the songs breathes new life into songs we're familiar with and makes them so much fun to sing. I love having music that is uplifting, fun and that everyone in my family enjoys listening to. If you liked "Popcorn Bopping", you will LOVE "Scripture Power"!
I cannot even express how much I love this cd. These mixes are AMAZING. My kids and I have been rocking out in the car to these tunes and every time they sing We'll Bring The World His Truth I start crying. Every time. Don't hesitate to buy this CD it is so great.


text:
Search Results: 'General'
The General
eBook (ePub): $0.99
The Generals
Paperback: $10.00
Prints in 3-5 business days
Come sit by my side cause you love me. Do not hasten to bid me adieu. Let's remember the Red River Valley And the love that we share that's so true.
Report of the Adjutant-General of the State of N.H.,
eBook (PDF): $8.00
A very interesting read and much info covering the wars N.H. took part in from it's settlement in 1623 up to the year 1861. It covers wars and battles up to the Civil War with many names in the... More > rosters and history. Note: No Civil War info in this book, only wars up to the Civil War. 413 pages< Less
2009 Minutes of the Cumberland Presbyterian Church
eBook (PDF): $6.49
Annual minutes of the meeting of the Cumberland Presbyterian General Assembly for 2009.
2009 Minutes of the Cumberland Presbyterian Church
Paperback: $24.95
Prints in 3-5 business days
Annual minutes of the meeting of the Cumberland Presbyterian General Assembly for 2009.
Transitory: A Creative Collecton vol. 1
Paperback: $22.99
Prints in 3-5 business days
Transitory: A Creative Collecton vol. 1
eBook (PDF): $9.99
Birney Safety Trolley Car Sales Brochure
Paperback: $13.95
Prints in 3-5 business days
In the 1910's and 20's, economic pressures and the rise of the motorbus produced dramatic changes in the streetcar industry. A promising solution to ensure profitability was the introduction of the... More > so-called "Safety Car" designed by Stone and Webster Corp. engineer Charles O. Birney. This type of small trolley featured several innovations, including deadman controls that cut power to the motors and applied brakes in an emergency. The main attraction for transit companies however was the fact that the cars' design allowed a man to both run teh car and take fares. The elimination of the conductor without any apparent compromise in safety sold the public on the cars and produced an immediate cost savings. This high quality booklet is a reprint of a brochure originally produced by General Electric to promote these cars and G.E. running gear.< Less
Life-Saving Quotations
eBook (PDF): $1.00
Quotations on the subjects of happiness and well-being.
Historique du 87me Regiment d'Infanterie: 2 Aout 1914 - 8 Mars 1915
eBook (PDF): $3.00
No description supplied
Top 10see more >
North Carolina Auto...
Paperback: $19.99
Organize for Innovation
Paperback: $3.61
Bootstrap:Algebra in...
Paperback: $10.00
The Association Exec's...
Paperback: $5.00
My Wars
Paperback: $14.36
By His Mercy 2: Living...
Paperback: $15.00
Vein Book
Paperback: $10.00
About Face
Paperback: $10.00
What May Come
Paperback: $12.71
Bootstrap:Data Science -...
Paperback: $20.00
Age Verification
The page you are attempting to access contains content that is not intended for underage readers.
Please verify your birth date to continue.


text:
Emily Gottreich is the Chair of the Center for Middle Eastern Studies at UC Berkeley. She is an Associate Adjunct Professor of History and International and Area Studies, and Chair of the undergraduate major in Middle Eastern Studies. Between 2009-2013 she served as the President of the American Institute for Maghrib Studies.
Prof. Gottreich received a Ph.D. in History and Middle Eastern Studies from Harvard University in 1999, an M.A. in Middle Eastern Studies from Harvard University in 1992, and a B.A. in Middle Eastern Studies from UC Berkeley in 1989. Her research focuses on Moroccan Jewish history and Muslim-Jewish relations in broader Arab-Islamic contexts.
Courses taught by Prof. Gottreich include: "Jews and Muslims" (MES 130/HIS 100), "North Africa: History, Culture, Society" (MES 150), "Scope and Methods of Research in MES" (MES 102) and "Senior Thesis in MES" (MES 190/H195).
Jewish Morocco: A History from Pre-Islamic to Post-Colonial Times. London: I.B. Tauris, 2018.
The Mellah of Marrakesh: Jewish and Muslim Space in Morocco's Red City. Bloomington: Indiana University Press, 2007
Jewish Culture and Society in North Africa, co-edited with Daniel Schroeter. Bloomington: Indiana University Press, 2011
Of Messiahs and Sultans: Shabbatai Zevi and Early Modernity in Morocco," in Sites of Jewish Memory: Jews in and from Islamic Lands in Modern Times. London: Routledge, 2014.
Historicizing the Concept of 'Arab Jews' in the Maghrib," Jewish Quarterly Review (98, 4) 2008


text:
Last summer, I went on a trip to the Mid-West. You're probably wondering, "Why? There is absolutely nothing there". Well, I thought that as well. I still do. But, I went to go visit someone, who is very special to me (or maybe, my memories). I guess when you go to a town that is empty, and blazing hot, it isn't so dull when you're with someone who makes you laugh. Nevertheless, this post is long overdue and a way of closure. Warning: This is not so much of a travel guide but a memoir of a fantastic weekend.Continue reading "St.Louis"
Tag: travel
Trip to Iceland
Warning: This trip was not planned beforehand. The tickets were purchased two weeks before departure and car rental was purchased the day of departure. Risky, I know.
Why Iceland?
Honestly, the only response I have is: My companion wanted to be in the dark. Darkness is exactly what I got. During the winter, there are only about 4 hours of sunlight.


text:
The Short But Sweet Ohio 213 + ADD NEW ROUTE
28 in Ohio Ohio17 Miles
By Crim/mobile/images/icons/
on September 1, 2007
- Trip Toolbox
- Add a review
- Add a photo
- Embed a video
- Watch this item
- Add to 'Routes I've Ridden'
- Add to 'Routes Wishlist'
Written Directions
The route basically starts in Steubenville, Ohio where you'll find State Route 213 (at the intersection of Ohio State Route 7 and US Route 22 just north of Steubenville). Take 213 north as it meanders north for about 20 miles. It rejoins Rt 7 just south of Wellsville Ohio at a rest stop.
This is your basic eastern Ohio country road. A few farms, hills and valleys as the route parallels the Ohio River and never strays more than 2 miles from the river, and lots of residences along the way.
Road Quality
This routes' strong point is definitely it's motorcycle road quality! It has some pretty dramatic elevation changes going from the level of the Ohio River to maybe 500' above it. At those elevation changes, the road can get pretty twisty. Near the north end, there is a nice switch back.
Roadside Amenities
The north end of 213 sports a campground and the confluence of Yellow Creek into the Ohio River.
Additional Info
- View the weather forecast for this area from Yahoo weather .
Nickname (optional) : Crim/mobile/images/icons/


text:
Most of the GRP skiers have now descended upon Soldier Hollow, Utah, to prepare for US Nationals. Nationals start on Wednesday, January 2nd with a classic sprint race, and continue through January 8th. Along with the classic sprint, there will be a 10/15k individual start skate race, a 20/30k mass start classic race, and a skate sprint.
Soldier Hollow was fortunate to receive natural snow not too long ago, and the skiing is really quite good. However, the organizers are still manufacturing a huge quantity of snow, to ensure that the snow depth is adequate for classic tracks and clean skiing. Anyone who has wanted classic tracks the past few days has been stuck with about 1k of terrain near the lodge, though the outer loops are excellent for skating and quite good for classic without tracks. The snow piles cover about half of the sprint course as well as a few other places, and they haven't been groomed smooth yet, which makes it somewhat difficult to ski certain loops of the trails. The piles are moderately skiable, but they're actually pretty icy, so its not that fun to skitter across their steep sides. We heard that the sprint course may be ready for skiing tomorrow though, so I made sure to take a few pictures of the great Snow Serpent of SoHo today. The shapes of the piles and their alignment make them look like huge fins or vertebrae of a serpent.
On a different note, after racing in the Canmore World Cups, I headed home to Alaska for the holidays.
Alaska was cold, but it was very nice to be at home. Within the first few days, I had seen at least 10 moose while driving around town or skiing. My cats were not quite sure if they remembered me at first, but they quickly came around and we played lots of games and they chased balls and feathers all over the house. On Christmas day it started snowing mid-morning and continued through much of the day, and I went on an evening ski with my parents and brother under the lights.
On December 22nd and 23rd I raced in the Besh Cups, Alaska's equivalent to Eastern Cups, and I was 2nd place in both the classic sprint and the 5k skate. We were lucky to be able to race the 2nd day, and the race was nearly cancelled due to the cold, but after a 1.5 hr delay it was supposedly above -4F.
Make sure you don't miss the Fasterskier article about Susan's race at Schalke, it sounds fascinating. (http://fasterskier.com/article/in-packed-soccer-stadium-in-germany-biathletes-put-on-a-show-burke-and-dunklee-tenth-at-schalke/)
Racing excitement here in Utah will commence in a few days, we'll try to keep you posted!


text:
Yoga About
My interest as a movement guide is to offer an embodied experience that respects each individual's process. Through years of practice I am skilled at seeing bodies and directing attention to what is quiet or unanimated. When we strengthen our ability to pay attention we open up to more possibilities and we bring an experience into existence that did not previously exist. I view asana and all movement practice as creative research involving an open flow of information. We learn more about what we think we know and are in a constant state of surprise from all that we do not know.
I have been a student of dance, yoga and Buddhism for 20 years and I've been teaching since 2004. I teach a warm and generous style of movement that is influenced by my interest in contemporary and classical dance forms, Iyengar and Vinyasa yoga and mindfulness. I currently study with Michael Stone, Lama Padma Drimed Norbu, Wendy Hambidge and Todd Jackson. I bring my love of movement, fondness of detail and my own understanding of practice into my teaching.


text:
Ensemble Studio Theatre & the Radio Drama Network present
by Abby Rosebrock, directed by Mikhaela Mahony
featuring Curran Connor*, Dalia Davi, Layla Khosh, Dawn McGee*, & Abby Rosebrock
Nora is a hard-drinking musicologist whose colleague/lover is dragging his feet about leaving his beauty-queen wife. When Nora's hijinks land her at rock bottom, she goes on a quest to get counsel from the only source she has left: her estranged, evangelical mom. Abby Rosebrock's Dido of Idaho is a horrifying comedy about love, despair and maybe, eventually, hope.
Playing March 14th through April 8th, 2018
Dido of Idaho runs two hours with one fifteen-minute intermission.
Scenic Designer: Angelica Borrero | Costume Designer: Audrey Nauman | Lighting Designer: Christina Watanabe | Sound Designer: Almeda Beynon | Stage Manager: Rachel Winfield | Assistant Stage Manager: Patricia L. Grabb | Assistant Director: Harrison Densmore
ABBY ROSEBROCK (Playwright) plays have been produced or developed at Williamstown, Cherry Lane, New York Stage and Film, Labyrinth Theater Company, Drama League, Ensemble Studio Theatre, Dixon Place, The Brick and more, as well as regionally in South Carolina, Georgia, Montana and Idaho. Abby has been a member of Playground at The Lark Play Development Center, The Tank NYC's TV- and new media-writers' collective and the Obie Award-winning playwrights' group EST/Youngblood. She is currently a member of the emerging writers' group at Clubbed Thumb and was recently selected for a Launch Commission with The Atlantic.
MIKHAELA MAHONY (Director) is a Brooklyn-based director of new plays and opera. Recent productions include 2:00, conceived by Emma McFarland, The Noise of the Future, by Anna Jazstremski, Hoshi, a new opera composed by Sato Matsui, Verdi's Rigoletto, and Chekhov's The Seagull. Mikhaela is honored to be a frequent collaborator with the playwrights of EST/Youngblood, directing short plays by Brittany Allen, Christina Quintana, and Abby Rosebrock in the past season, and helming the workshop production of Dido of Idaho in 2015. She is also deeply proud to work with the much younger playwrights at the 52nd Street Project. In her work in opera, Mikhaela has directed and assistant directed at The Juilliard School and the Chautauqua Institution. She is a co-founder of Full Moon Films and a member of the Columbia University School of the Arts Directing Class of 2019.
*Denotes EST Member Artist


text:
So what did happen to the corner store? The short answer is it became the 7-11, the Circle K – or it went out of business. Most did the latter.
The legal blogosphere is filled with speculation and news about the happenings of biglaw in the legal revolution – but about 63% of lawyers in private practice are in firms of 3 or less. So what's the future for the little guy?
What if you could suddenly benefit from national advertising – a powerful website – group health and malpractice insurance, and a continuing feed of business that would alleviate your need for marketing?
Sound like joining a big firm? Well, yes – but no.
The legal revolution that has brought about "Alternative Business Structures" offering a range of services beyond legal, and "Non-Lawyer Ownership" of law firms in Australia and Britain are blossoming with creative examples of exactly this revolution. One is a British legal franchise called Quality Solicitors. There are currently over 200 British law firms – some top ones in smaller communities – under the brand.
In Britain, financing for such endeavors is coming from outside the profession. And while that's not yet permitted in the U.S., it doesn't have to be for the franchise model. A few wealthy attorneys could fund it. And my bet is that it's already in the works.
But, you say, "no way – the franchise model has been tried, and hasn't worked very well." You're right – but that's the past. The world – and technology – has completely changed the game.
LegalZoom has created a no-lawyers model with thousands of fill-in-the-blanks-online forms. They didn't even need lawyers – although they have since expanded, to capture the market at the next level, of those who really do want to talk to a lawyer. And of course, the web has become the first place a majority of consumers look when choosing a lawyer. So when they Google "lawyer" and see a website that talks candidly about cost, it has their attention. The Quality Solicitors website headline is "When it comes to bills, we don't like surprises either."
Then it uses "artificial intelligence" to help the client determine what type of services they need, then puts them in touch with the appropriate attorney in their area. And right there, for the world to see, are prices. Reasonable – and note at the right, with a "clear price" guarantee.
Politics isn't the only place we're seeing a consumer revolt. LegalZoom has proven that.
So what can you do to solidify your market position? What can you learn from Quality Solicitors?
First – like it or not, price rules for consumers and small business.
The savvy consumer knows the difference between a straightforward problem or issue and one with a host of "if's, and's and buts." Larger corporations, not yet so much. But even that is changing. Savvy in-house legal counsel increasingly know how to take advantage of a highly competitive marketplace.
The fact is that hourly billing is a relatively new concept that began in earnest in the 1960's. Before then, most everything was flat-rate priced. (if you want the full story of how that change came about, give me a call.)
So, you're thinking I'm going to say "flat rate pricing," but you're wrong. The answer is actually a sophisticated version of that, called "unit pricing." Your agreement – and heck, maybe even your advertising (a la Quality Solicitors) has specific "flat rate" prices for stages, or levels, of work, with an open end hourly rate if needed. For instance, in estate planning:
Simple will with components A, B, and C: $750
Additional if D is needed: $300
Additional if E, F & G are needed $900
If H is requested $1200
Likewise, in litigation, pricing might look like this:
Review of matter, development of strategy,
Filing of initial suit (includes up to five client meetings) $3,000 – $5,000
Additional meetings $400
Deposition fee (travel billed separately), per deposition, per day $1000
Trial preparation $5,000 – $9,000
Trial, per attorney per day $3,000 – $5,000
This is an admittedly simple model with numbers that may not fit for you. But the concept is important. Specific prices for specific, well defined (in writing) types or stages of work. The client should be able to see what they can expect to pay for each stage of the work, and so they can make better decisions based partly on the dollar consequences.
Yes, even when your work is carefully unit-priced, sometimes your time will be more than the fee involved. But you'll prosper on the law of large numbers rather than on each matter. And after all, what better way to drive innovation and efficiency (which the legal profession has never, until recently, had to deal with) than having to analyze past work to identify better methods or better pricing?
The traditionalist objection to this "cost-based" decision tree for the client is "The client might stop me from doing something important because of cost! They'll be telling me how to practice law!" Yep, and yep. My answer to that is to yell "IT'S ALWAYS THE CLIENT'S CASE, NOT YOURS!" and to remind the attorney of their first and foremost duty in the client relationship: advice and counsel. If the client decides not to take the advice (which should, needless to say, be documented in a letter or email), then it's ultimately the client's decision. How's that really different than today's real life?
Second: Make sure your website does its job for you.
What does that mean? First, it means acknowledging that it's a web world. Even if most of your business is referrals, know that most of those prospects, after they were given your name, went to your website to check you out. So, no website? Really? Then you're missing out on lots of clients who searched for you, couldn't find you, and didn't call. Crappy, creaky 1999 website? Ditto.
So. Give in to the reality that you should pay a design expert to create an impactful, compelling website that attracts viewers to become clients. Because it's no longer your business card. It's your front door. Need a referral? Call me.
And if all of your business is referrals, and most people find you on the web by typing in your name (your website statistics can tell you this), maybe that's all you need.
If most of your business comes from strangers – walk-ins, in traditional terms (remember where your front door is), then make sure your website has all the bells and whistles that make Google light up and want to rank you highly in the listings. This is the first part of what the geeks call "website optimization," and it's a job for experts – which doesn't mean your brother-in law the computer programmer, unless he has at least three recommendations from law firms. There's a science to picking a web designer who can do both great design and great "organic" optimization. Happy to provide the details. Call me.
Next step – decide where you want to appear on the list when the consumer does a search for "family lawyer" or such. Several options here. You can pay Google to list you at the top of the page, in as many jurisdictions as you can afford. You can pay a web magician to get you listed at the top of the next group of "unpaid" listings (an arcane and less than perfect art – again, do your due diligence). You can buy a "pay-per-click" ad in the far right column that you only pay for when someone clicks on it to go to your website.
All of this means that, finally, you have to have a marketing budget of reasonable size – 10-15% of your budgeted gross revenues at least. Some for your web works, and some for your other marketing. Many personal injury firms spend far more than this.
Third – do your own marketing.
That means advertising where necessary, and most importantly, personal marketing – building and maintaining relationships with your referral sources – in other words, paying attention to the Parieto Principle – the old 80-20 rule that says 80% of your business will come from 20% or your (you name it – efforts, contacts, expenditures).
The still-true fact is that the best business comes from referrals – other professionals (especially your fellow attorneys), former clients, and personal, social and business contacts. And that's at all levels, right up to the top of the profession. CEO's don't Google "corporate lawyer." They ask their fellow CEO's or their CFO or accounting firm for a referral.
And referrals are, by far, the cheapest source of business. So, like it or not, you have to be extremely active with relationship-building. And particularly if you are in a smaller community, you have to be ubiquitous – a "leading citizen," known and respected by all. Be seen, involved and active in as many places as possible. That in itself won't make you rich, but turning all of that into a systematic, efficient and results-oriented personal marketing program will. If you need some pointers here, give me a call.
The final truth. . .
Consumer law is going away from the traditional practitioner to the LegalZooms, the RocketLawyers, the franchises, the do-it-yourself forms on the web. The lawyer's hold on the lower levels of the legal system is slipping fast, as the web offers more and more choices and opportunities. Yes, those choices may not always be the best, but sometimes, the consumer only needs a Kia, not the Bentley we want to sell them. And remember that it's always the consumer's choice, not ours.
. . . And the larger solution
Move up the ladder, away from the simple to the more complex work, whether that be corporate or high net worth individuals or successful entrepreneurs, where needs are more complex and nuanced, where matters and their solutions are unique, and where long-term relationships – those "trusted advisor" relationships exist between client and attorney.
Or get ready to buy a franchise.


text:
There are many, many foods that I like (and indeed very few that I dislike) but I really LOVE potatoes and I have never found a potato dish that I don't enjoy.
When I was growing up my dad was not a very adventurous eater so my mum was not a very adventurous cook (although she is now!). We rarely ate rice or pasta (except for rice pudding and spaghetti hoops) but we often filled up on spuds. My dad's preferred method of eating them was to have the potatoes boiled whole in their skins; he would then peel them at the table and eat them with a little knob of cold butter and some salt. I have never seen anyone else do that since but you should try it because it tastes great. The rest of the family were particularly fond of mash, homemade chips and Sunday roast potatoes.
I really started to get more adventurous with potatoes out of necessity rather than creativity: Not long after we got married Martin and I found ourselves seriously out of funds and two weeks from payday – we had a few store cupboard ingredients and no cash. We were saved by an opportune and unexpected visit from my dad who had stopped off at a local farm and bought us a 56lb bag of potatoes.
We ate potatoes, and only potatoes, for dinner fourteen nights on the run. Aware of the obvious potential for boredom we set a challenge to never eat the same meal twice during this time – I can't for the life of me remember the details but I know we succeeded. These days I prefer my spuds with meat or fish and vegetables but at the time we were just immensely grateful to be eating at all. This experience did nothing to diminish my enthusiasm for the humble spud.
Before I started writing this piece I wondered if I was alone in my passion: It would seem not – apparently we each eat an average of 102kg of potatoes per year here in the UK (around 2 kilos or more than 4lb per week). What on earth do we do with all those potatoes?
I decided to conduct a little (very unscientific) research via the bun scuffle facebook page and Twitter (@bunscuffle) where I asked you about your favourite ways of eating potatoes.
Lots of you like mash but you really are a creative lot and your ideas varied from simple mash with butter and milk (or cream) to mash with the addition of spring onions (champ), cheese or horseradish. You use mash on top of cottage pie and one or two of you turn it into an occasion such as Jacqueline's mash with butter, top of the milk, pepper, scallions (spring onions) and bacon lardons or Taya's buttery mash with red onion, leeks and peas which she then tops with cheese and pops under the grill to brown.
You also like baked potatoes; with cheese or cheese and beans for a quick, tasty meal but Liam says to vamp up a baker you should scoop out the insides of the cooked potato and mash it with crème fraiche, chives, spring onions and bacon bits, pile it back in the skin, top it with pepper and parmesan and return it to the oven for ten minutes. Sounds good to me. One thing we all agree on is that the skin should be good and crispy.
Roast potatoes also got a few mentions but once again you like to add some extra flavours; Richard roasts his with garlic and rosemary and the addition of a little leftover bacon or sausage fat, Lisa prefers to cook and crush new potatoes before roasting them with a little garlic and olive oil, Steph does similar with main crop potatoes and the further addition of some herbs whilst Pat roasts hers chopped, in their skins in little foil parcels along with chunks of sweet potato, onion and seasoning.
You would expect to find chips in any blog piece about potatoes but I thank John and Megan for reminding us that they need to be crispy on the outside and soft and fluffy on the inside – just like, as Megan points out, an armadillo!
Surprisingly there was only one mention of dauphinois potatoes – a personal favourite – rich in cream with a crispy, browned topping. My sister, Debbie, makes hers from a 1960s Good Housekeeping recipe which includes the addition of Lancashire cheese – delicious.
With all this talk of butter, cream, and cheese we should be eternally grateful to Fran and Ange for their healthier options. Potatoes are not, despite the myths, an unhealthy food. They are high in carbohydrate (an essential food group), low in fat and a great source of vitamin C (oh dear – I'm starting to sound like the potato marketing board..).
Fran suggested ricing the potatoes to make a light, fluffy mash so that no addition of fat is needed whilst Ange shared a recipe for "Slimming World chips" where you cut the potatoes into wedges and part boil them before sprinkling with celery salt, spraying with Fry Light (or similar) and baking in the oven until browned. They both sound good to me.
I would also like to thank Rob for sharing this recipe for pork belly with paprika, fennel and cider served with champ and Chloe for sharing her family favourite "Great Grandma Jane's Anglesey Eggs" which has boiled eggs, potatoes and leeks layered in a cheese sauce and baked. Chloe made this on the ITV programme "No Taste Like Home". I haven't tried either of these recipes yet but they are both high on my list…
Thank you all for your input (Rob, Andrea, Richard, Lyssa Fee, Liam, Lisa, Helen, Michelle, Rob, Laura, Ange, Sarah, Helen, Jacqueline, Debbie, Megan, Steph, Fran, John, Taya, Pat , Chloe and Lisa), this wouldn't have been half as interesting without your ideas.
If you are still looking for inspiration, check out my Top Ten Ways to Perfect Potatoes.


text:
#3 Go to a rodeo
Lindsey and I got all decked out in our cowboy gear and headed to the Cow Palace tonight for the Grand National Rodeo. So. Much. Fun!! Although I've learned that next year we will need to add some flair to our wardrobe- turns out western women love their bling. Bedazzled shirts, belts, hats, jeans, boots, saddles, bridles, coffee mugs etc... a good note for future outfits.
Started off the night with some BBQ and beer...so good but I could have easily had seconds.
Two thumbs up!! It was delish
Then we got our farmer on and 'milked a cow' ...this was so weird
The 'udders' were sticky...I was totally grossed out
After wandering around the exhibition hall (lots of rhinestone stuff) for a bit we found this little guy:
So freaking cute...trying to figure out how he can live as a third roommate in our apartment.
Look how tiny his feet are! So freaking cute
We finally pulled ourselves away from the pony and headed to our seats to watch the rodeo. There was bareback riding, steer wrestling, saddle bronc riding, team roping, barrel racing (AH-mazing), tie-down roping and last but not least bull riding. The bareback riding was the scariest by far...the second cowboy got his hand stuck and was dragged all over the area before finally yanking his hand free. He couldn't walk had to be carried out of the area...and another cowboy had trouble walking out of the area after his successful bull ride but that was because he broke his foot two weeks ago AND STILL RODE!! <--Insane. My camera was having trouble during the rodeo so I had to rely on my iphone which couldn't keep up with the riders- almost every picture is a blur they were moving so fast! So cool to watch.
Started off with the opening ceremonies- note the teeny tiny rider on the far right...she was so proud of her little pony and waved to the crowd like crazy when she did her lap.
The drill team was pretty awesome (and super American obviously)- here's a quick video of some of their moves (I was too into the show to keep filming):
Yea no big deal- I do this all the time basically. Just kidding- it was really impressive.
Finished his ride and getting ready to hop off the bucking horse and onto the horse next to him....the announcer LOVED to comment on their dismount 'try landing on your feet next time buddy' 'thank god you're judged on your ride not your dismount' etc...
Barrel racing!! So cool I was cheering too loud to take many pics.
Hot cowboys ...yup main reason to come to the rodeo.
Thanks to Lindsey for joining me and helping me check off #3 on my list- can't wait to go again next year!


text: I really can't even begin to explain the diversity of landscape we have been able to see in the past week. We have taken thousands of photos, videos and sounds and every corner we turn are tempted to collect more. Scotland is gorgeous but the highlands and western isles have my heart. This place is gorgeous. (Filming for Humanity).


text:
So, we had a great time all in all. BTW, Cabell made a successful pitch to call the trip WiMiUp, (UP for the Upper Peninsula), and that's how it's tagged in my flickr account. We've pooled our photos — 498 of them altogether — at http://www.flickr.com/groups/779759@N20/.
It was an adventure. Somehow we managed to have north winds while we were headed north on the west side of the lake, south winds while we headed south on the east side of the lake, and to end the trip, a 15-20 mph NW wind while we rode NW from Manitowoc to Green Bay on the last day. It was generally colder than I expected. I knew that mornings were going to be in the low 50s, and highs mostly in the 70s, but these cool temps in combination with the wind (and frequently a mist off the lake) made for chilly riding often. Several days we kept tights on the entire time.
The Upper Peninsula is beautiful, but often rather sad. The motels were mostly empty, and every other beach cottage was for sale. As Bob, the owner of Rosie's Family Restaurant (see below)
said, high gas prices this year are just the icing on the cake. The problems really started with the Reagan administration's union-busting in the air traffic controllers' strike. As union strength and American dominance of the car industry have declined, high-paying jobs in Detroit have quite literally gone south, and there are just not that many blue-collar workers vacationing in the UP any more.
Still, I suppose the lack of vacationers worked to our advantage, since roads were quiet
And the scenery was exquisite.
In the Lower Peninsula's northwest area, the tourist towns were doing better — not so far to drive from Chicago, etc. — and there were surprisingly many bicyclists. Several nice bike paths, as well.
Now I'm home icing my left knee, which didn't really deal with the trip very well. The doc gave me prescription-strength Naproxen, and I'm starting physical therapy on Monday. Apparently it's just irritation of the patellar tendon, but I'm not taking any chances. I don't want to be off the bike any longer than I have to. In any case, we made it.


text:
The Fokker E.V / D.VIII was the last fighter airplane put into service by Germany during WWI. The airplane was an advanced design and featured a single parasol wing.
There were some wing failures with some of the early E.V models which caused the unfortunate deaths of several pilots. The failures were traced to faulty workmanship by a subcontractor; the wing design was sound. The problems were corrected and the type was updated as the D.VIII.
By this time the war only had 18 days left so the type saw limited combat. If the war had dragged on many believe the D.VIII would have been the finest airplane of the war up to that time.
My depiction features the airplane in the markings of Leutnant Richard Wenzl during his time with Jasta 6.
This print and many other art works are available through our website: http://www.markkarvon.com. If you have any questions or want more information regarding customizing this print please contact us at: firstname.lastname@example.com.
Wednesday, May 5, 2010
Subscribe to: Posts (Atom)


text:
Turtle Island is a parable inspired by the legend that came from the heart and soul of the Native People of North America.
Combining different types of puppets, amazing light effects, and life actors and masks, the story tells how two brothers struggled to understand that people are a living part of the natural world, and to celebrate the connection of all
living things.
Books to read
Iroquois Stories. As told by Joseph Bruchac. The Crossing Press, Trumansburg, N.Y. 1985
Who Speaks for Wolf. A Native American Learning Stories by Paula Underwood. A Tribe of Two Press, San Anselmo, 1991
More Earthmaker's Tales. North American Indian Stories. Walker and Company,N.Y.,1990
Full Moon Stories. 13 Native American Legends by Eagle Walking Turtle. Hyperion Books for Children, N.Y.1997
Walk in Peace : Legends and Stories of the Michigan Indians by Simon Otto. Michigan Indian Press, 1991
Educational books
Keepers of the Earth. Native American Stories and Environmental Activities for Children. M J.Caduto andJ Bruchac. Fulcrum Inc. ,Golden, Colorado, 1997
"Keepers of Life" Discovering Plants through Native American Stories and Environmental Activities for Children. M J.Caduto andJ Bruchac. Fulcrum Inc. ,Golden, Colorado, 1997
Lightning Inside You and other Native American Riddles Edited by John Bierhorst. A Beech Tree Paperback Book, N.Y.1999
Native American Ceremony and Celebration. By Kay McGowan, Ph. D. (available at PuppetART)
Nishnawbe. A Story of Indians in Michigan by Lynne Deur. River Road Publications, Inc. 1989
Spirits of the Earth, Native American Nature Symbols. Stories and Ceremonies by Bobby Lake-Thorn (Medicine Grizzly Bear), A Plum Book,1997
Earth Signs. How to connect with the Natural Spirits of the Earth. By Grey Wolf. Daybreak Books, N.Y. 1998
Spirit Walker. Dancing Moons. Dancing Teepees. Poems by Nancy Wood. A Doubleday Book for Yong Readers, 1993
.Poems of American Indian Youth. Selected by Virginia Driving Hawk Sneve, Holiday House,N.Y.1989
The Art of Frank Howele, Doubleday,N.Y.1997
Eagles cries. Joanne Shenandoah, CD, Red Feather Music 2001
Spirit Nation Winter Moons, CD, Karuna, 2001
Ancient Voices, Nee Mah, CD, Neo Pacifica Recordings, 2001
Takini, Music and Songs of the Lakota Sioux. CD, Lo Chant Du Monde. 1994
Voices in the Stone. Leon Joseph Littlebird, email@example.com


text:
"That's very nice of you to join me for lunch, Peter. You're a good kid.
– Oh no worries, Grand Pa. It's a pleasure for me you know. I like my weekly lunch with my Grand Pa!
– I'm glad. Me too, Pete. So what's up with you?
– Oh nothing much, you know. The usual.
– Mmm. It's not what I heard from you parents.
– Ha ha. Don't listen to them. They are a bit nervous because I have a lot of interviews but no job yet.
– Oh don't worry about me. It might surprised you but I remember what it is to be young.
– Oh I know Grand Pa, I know. On this aspect, you are much more open-minded that Mum and Dad…
– So, what do you have in mind? What's your plan, now that you have resigned from your previous job. What do you want to do, Pete?
– Mmmm. Can I be honest with you, Grand Pa? Continue reading


text:
Initial release.
Launching ADAMS
- Linux/Unix/OSX: bin/run
- Windows: bin/run.bat
- OSX: open the app archive
Mac users using the app archive need to tell ADAMS where to find the example flows (see above for download). The Placeholders.props file needs to be downloaded to $HOME/.adams and the EXAMPLE_FLOWS directory in the props file pointed to the actual directory with the example flows.


text:
Hailey knows what she wants and I love, love that about her! The confidence this beautiful young lady has is so admirable especially for someone who is only 18! What a wonderful trait to have and I pray she will forever allow that to help push her forward. We met at the Botanical Gardens and just had the best time changing outfits, getting her makeup adjusted by MarLen and allowing Ms. Hailey to be a true model for the morning. She is so beautiful and I am so thrilled to finally share these with the world! Rock out your senior year Hailey, may it be a year you will always remember! <3
Location: Botanical Gardens
Makeup Artist: MarLen Hernandez