text:
This document describes the Development Process for the Eclipse Foundation. In particular, it describes how the Membership at Large, the Board of Directors, other constituents of the Ecosystem, and the Eclipse Management Organization (EMO) lead, influence, and collaborate with Eclipse Projects to achieve these Eclipse purposes:
The Eclipse technology is a vendor-neutral, open development platform supplying frameworks and exemplary, extensible tools (the 'Eclipse Platform'). Eclipse Platform tools are exemplary in that they verify the utility of the Eclipse frameworks, illustrate the appropriate use of those frameworks, and support the development and maintenance of the Eclipse Platform itself; Eclipse Platform tools are extensible in that their functionality is accessible via documented programmatic interfaces. The purpose of Eclipse Foundation Inc., is to advance the creation, evolution, promotion, and support of the Eclipse Platform and to cultivate both an open source community and an ecosystem of complementary products, capabilities, and services.
Explanatory comments, guidelines, and checklists - as well as additional requirements added by the EMO per section 3 - are noted in yellow boxes.
This document has five sections:
The following describes the guiding principles used in developing this Development Process.
Eclipse as a brand is the sum of its parts (all of the Projects), and Projects should strive for the highest possible quality in extensible frameworks, exemplary tools, transparent processes, and project openness.
The Eclipse Foundation has the responsibility to ...cultivate...an ecosystem of complementary products, capabilities, and services.... It is therefore a key principle that the Eclipse Development Process ensures that the projects are managed for the benefit of both the open source community and the ecosystem members. To this end, all Eclipse projects are required to:
Essential to the Purposes of the Eclipse Foundation is the development of three inter-related communities around each Project:
The Eclipse community considers the absence of any one or more of these communities as proof that the Project is not sufficiently open, transparent, and inviting, and/or that it has emphasized tools at the expense of extensible frameworks or vice versa.
It is an explicit goal of the Development Process to be as clear and concise as possible so as to help the Project teams navigate the complexities, avoid the pitfalls, and become successful as quickly as possible.
This document imposes requirements and constraints on the operation of the Projects, and it does so on behalf of the larger Eclipse community. It is an explicit goal of the Development Process to provide as much freedom and autonomy to the Projects as possible while ensuring the collective qualities benefit the entire Eclipse community.
Similarly, this document should not place undue constraints on the EMO or the Board that prevent them from governing the process as necessary. We cannot foresee all circumstances and as such should be cautious of being overly prescriptive and/or requiring certain fixed metrics.
The frameworks, tools, projects, processes, community, and even the definition of Quality continues to, and will continue to, evolve. Creating rules or processes that force a static snapshot of any of these is detrimental to the health, growth, and ecosystem impact of Eclipse.
Part of the strength of this document is in what it does not say, and thus opens for community definition through convention, guidelines, and public consultation. A document with too much structure becomes too rigid and prevents the kind of innovation and change we desire for Eclipse. In areas where this document is vague, we expect the Projects and Members to engage the community-at-large to clarify the current norms and expectations.
This document and any additional criteria as established by the EMO contains requirements, recommendations, and suggestions.
RRequired - Certain responsibilities and behaviors are required of participants in Eclipse open source projects. Projects that fail to perform the required behaviors will be terminated by the EMO. In keeping with the Guiding Principles, the number of requirements must be kept to an absolute minimum.
GGuideline - Other responsibilities and behaviors are recommended best practices. Collectively, we have learned that Projects are more likely to be successful if the team members and leaders follow these recommendations. Projects are strongly encouraged to follow these recommendations, but will not be penalized by this Process if they do not.
This document is entirely composed of requirements. In addition to the requirements specified in this Development Process, the EMO is instructed to clarify, expand, and extend this Process by creating a set of Eclipse Project Development Guidelines to advance the creation, evolution, promotion, and support of the Eclipse Platform and to cultivate both an open source community and an ecosystem of complementary products and services.
The EMO is not permitted to override or ignore the requirements listed in this document without the express written endorsement of the Board of Directors.
This version of the document adds the word "Project" to the title of this section to better qualify that it discusses the structure and organization of projects. The previous version of this document defined notions of "Operating" and "Container" Projects. These notions have been abandoned in favour of a more generalized notion of Project. Under this new structure, projects can opt to function as Operating Projects by choosing not to maintain a code repository.
See Bug 301065.
A Project is the main operational unit at Eclipse. Specifically, all open source software development at Eclipse occurs within the context of a Project. Projects have leaders, developers, code, builds, downloads, websites, and more. Projects are more than just the sum of their many parts, they are the means by which open source work is organized when presented to the communities of developers, adopters, and users. Projects provide structure that helps developers expose their hard work to a broad audience of consumers.
Eclipse Projects are organized hierarchically. A special type of Project, Top-Level Projects, sit at the top of the hierarchy. Each Top-Level Project contains one or more Projects. Each Project may itself contain zero or more Projects. A project that has one or more Projects is said to be the "parent" of those Projects. A Project that has a parent is oftentimes referred to as a Sub-Project. The term Project refers to either a Top-Level Project or a Sub-Project. Projects may be referred to as Sub-Projects or Components, but the choice of common name does not change the characteristics of the Project.
The descendants of a Project are the Project itself and transitive closure of its child Projects. The top parent of a Project is the Top-Level Project at the top of the hierarchy.
Projects are the unit entity for:
As defined by the Eclipse Bylaws - Article VII, the Eclipse Management Organization (EMO) consists of the Foundation staff and the Councils. The term EMO(ED), when discussing an approval process, refers to the subset of the EMO consisting of the Executive Director and whomever he or she may delegate that specific approval authority to.
The previous version of this document introduced a notion of a "union" of committers that was never fully defined or utilized. That notion has been removed.
We attempt to make it clear that each project has exactly one set of committers. This has been driven by the negative experiences of the past in attempting to manage multiple committer groups in a single project. We further attempt to make it clear that there is no roll-up of committers; a committer in a sub-project is not automatically a committer in a parent project.
Each project has exactly one set of committers. Each Project's set of Committers is distinct from that of any other Project, including Sub-Projects or parent Projects. All Project Committers have equal rights and responsibilities within the Project. Partitioning of responsibility within a Project is managed using social convention. A Project may, for example, divide itself into logical partitions of functionality; it is social convention that prevents Committers from one logical partition from doing inappropriate work in another. If finer-grained management of committer responsibilities is required, a project should consider partitioning (via a Restructuring Review) into two or more Sub-Projects.
The Committers of a project have the exclusive right to elect new Committers to their Project–no other group, including a parent Project, can force a Project to accept a new Committer.
There is no roll-up of committers: the set of committers on a project is exactly that set of people who have been explicitly elected into that role for the project (i.e. being a committer on a sub-project does not give you any automatic rights on the "parent" project).
In practical terms, each Project has a single Unix group of its Committers that provides write-access to the Project's resources. Pictorially below, we see that a Project, in addition to the various resources and Committers it has, can also have zero or more Sub-Projects. Each of these Sub-Projects has its own distinct set of Committers and resources.
The previous version of this document restricted code ownership to the former notion of "Operating" projects. With the generalization of projects, it is now possible for a project at any level in the hierarchy to have (or not have) code.
This version of the document clarifies that a project in the incubation phase may make pre-1.0 releases only.
Each Project owns and maintains a collection of resources.
Resources may include source code, a project website, space on the downloads server, access to build resources, and other services provided by the Eclipse Foundation infrastructure. The exact infrastructure provided by the Eclipse Foundation varies over time and is defined outside this process document.
A project is not strictly required to make use of all the resources made available; a project might, for example, opt to not maintain a source code repository. Such a Project might operate as an organizational unit, or container, for several Sub-Projects. Similarly, a Project might opt to provide a consolidated website, build and/or download site for its Sub-Projects (the Sub-Projects would then not require those resources for themselves).
Each Project has a single Bugzilla component for its bugs.
Any Project in the Mature Phase may make a Release. A Project in the Incubation Phase with two Mentors may make a pre-1.0 Release. A Release may include the code from any subset of the Project's descendants.
A Project at any level may receive IP clearance for contributions and third-party libraries. IP approval will often include the same approval for all descendant Projects. However, IP clearance will only be granted at the most appropriate technical level.
Projects are the level of communication with the larger Eclipse community and ecosystem. Projects may either have their own communications (website, mailing lists, forums/newsgroups, etc) or they may be part of a parent Project's communications (website, mailing list, forums/newsgroups, etc). In either case, the Project is required to maintain an open and public communication channel with the Eclipse community including, but not limited to, project plans, schedules, design discussions, and so on.
All Projects must make the communication channels easy to find. Projects are further required to make the separate communication channels of their child Projects (if any) easy to find.
Any Project in the Incubation Phase must correctly identify its website and Releases. A Project with at least one descendant Project in Incubation Phase must correctly annotate its own website so as to notify the Eclipse community that incubating Projects exist in its hierarchy. Any Release containing code from an Incubation Phase project must be correctly labeled, i.e., the Incubation Phase is viral and expands to cover all Releases in which it is included.
Each Top-Level Project has a Charter which describes the purpose, Scope, and operational rules for the Top-Level Project. The Charter should refer to, and describe any refinements to, the provisions of this Development Process. The Board approves the Charter of each Top-Level Project.
Sub-Projects do not have separate Charters; Sub-Projects operate under the Charter of their parent Top-Level Project.
All Projects have a defined Scope and all initiatives within that Project are required to reside within that Scope. Initiatives and code that is found to be outside the Scope of a Project may result in the termination of the Project. The Scope of Top-Level Projects is part of the Charter, as approved by the Board of Directors of the Eclipse Foundation.
The Scope of a Sub-Project is defined by the initial project proposal as reviewed and approved by the Project Management Committee (PMC) (as further defined below) of the Project's Project's top parent and by the EMO. A Project's Scope must be a subset of its parent's Scope.
The previous version of this document used confusing language in an attempt to combine the discussion of PMCs and Project Leads. This version separates these discussions in an attempt to make more explicit the process of bringing leaders on board and the role that the two different types of leaders play. Sections 4.6.1 and 4.6.2 are new with this version of the document.
See Bug 300002 and Bug 300006.
There are two different types of Project leadership at Eclipse: The Project Management Committee (PMC) and Project Leads. Both forms of leadership are required to:
The leadership for a Project is composed of the Project's Project Lead(s), the leadership of the parent Project (if any) and the PMC Leads and PMC Members for the Top-Level Project.
Top-level projects are managed by a Project Management Committee (PMC). A PMC has one or more PMC Leads and zero or more PMC Members. Together the PMC provides oversight and overall leadership for the projects that fall under their top-level project. The PMC as a whole, and the PMC Leads in particular, are ultimately responsible for ensuring that the Eclipse Development Process is understood and followed by their projects. The PMC is additionally responsible for maintaining the top-level project's charter.
PMC Leads are approved by the Board; PMC members are elected by the existing PMC Leads and Members, and approved by the EMO(ED).
Eclipse Projects are managed by one or more Project Leads. Project Leads are responsible for ensuring that their Project's Committers are following the Eclipse Development Process, and that the project is engaging in the right sorts of activities to develop vibrant communities of users, adopters, and contributors. The initial project leadership is appointed and approved in the creation review. Subsequently, additional Project Leads must be elected by the project's Committers and approved by the Project's PMC and the EMO(ED).
In the unlikely event that a member of the Project leadership becomes disruptive to the process or ceases to contribute for an extended period, the member may be removed by the unanimous vote of the remaining Project Leads (if there are at least two other Project Leads), or unanimous vote of the Project's PMC.
In exceptional situations, such as projects with zero active committers or projects with disruptive Committers and no effective Project Leads, the Project Leadership Chain has the authority to make changes (add, remove) to the set of committers and/or Project Leads of that project.
The previous version made specific references to the types of resources that a committer has write access to (code, web, and Bugzilla). In this version, the discussion of the resources has been generalized.
Each Project has a Development Team, led by the Project Leaders. The Development Team is composed of Committers and Contributors. Contributors are individuals who contribute code, fixes, tests, documentation, or other work that is part of the Project. Committers have write access to the Project's resources (source code repository, bug tracking system, website, build server, downloads, etc.) and are expected to influence the Project's development.
Contributors who have the trust of the Project's Committers can, through election, be promoted Committer for that Project. The breadth of a Committer's influence corresponds to the breadth of their contribution. A Development Team's Contributors and Committers may (and should) come from a diverse set of organizations. A Committer gains voting rights allowing them to affect the future of the Project. Becoming a Committer is a privilege that is earned by contributing and showing discipline and good judgment. It is a responsibility that should be neither given nor taken lightly, nor is it a right based on employment by an Eclipse Member company or any company employing existing committers.
The election process begins with an existing Committer on the same Project nominating the Contributor. The Project's Committers will vote for a period of no less than one week of standard business days. If there are at least three (3) positive votes and no negative votes within the voting period, the Contributor is recommended to the project's PMC for commit privileges. If there are three (3) or fewer Committers on the Project, a unanimous positive vote of all Committers is substituted. If the PMC approves, and the Contributor signs the appropriate Committer legal agreements established by the EMO (wherein, at the very least, the Developer agrees to abide by the Eclipse Intellectual Property Policy), the Contributor becomes a Committer and is given write access to the source code for that Project.
At times, Committers may become inactive for a variety of reasons. The decision making process of the Project relies on active committers who respond to discussions and vote in a constructive and timely manner. The Project Leaders are responsible for ensuring the smooth operation of the Project. A Committer who is disruptive, does not participate actively, or has been inactive for an extended period may have his or her commit status revoked by the Project Leaders. (Unless otherwise specified, "an extended period" is defined as "no activity for more than six months".)
Active participation in the user forums/newsgroups and the appropriate developer mailing lists is a responsibility of all Committers, and is critical to the success of the Project. Committers are required to monitor and contribute to the user forums/newsgroups.
Committers are required to monitor the mailing lists associated with the Project. This is a condition of being granted commit rights to the Project. It is mandatory because committers must participate in votes (which in some cases require a certain minimum number of votes) and must respond to the mailing list in a timely fashion in order to facilitate the smooth operation of the Project. When a Committer is granted commit rights they will be added to the appropriate mailing lists. A Committer must not be unsubscribed from a developer mailing list unless their associated commit privileges are also revoked.
Committers are required to track, participate in, and vote on, relevant discussions in their associated Projects and components. There are three voting responses: +1 (yes), -1 (no, or veto), and 0 (abstain).
Committers are responsible for proactively reporting problems in the bug tracking system, and annotating problem reports with status information, explanations, clarifications, or requests for more information from the submitter. Committers are responsible for updating problem reports when they have done work related to the problem.
Committer, PMC Lead, Project Lead, and Council Representative(s) are roles; an individual may take on more than one of these roles simultaneously.
The three Councils defined in Bylaws section VII are comprised of Strategic members and PMC representatives. The three Councils help guide the Projects as follows:
This version of this document formalizes the notion of an "Incubator" project. The original draft of this document attempted to restrict the number and structure of incubators, but the language was removed to allow for future flexibility. A project may have more than one incubator; an incubator project may itself have an incubator sub-project. Creating multiple incubators is expected to be atypical; attempts to create multiple incubators will be challenged by the PMC and EMO.
An important requirement for an incubator is that there must be some set of committers from the parent project who are also committers on the incubator. Since incubators are never expected to graduate, they do not require mentors.
A Project may designate a Sub-Project as an "Incubator". An Incubator is a Project that is intended to perpetually remain in the Incubation phase. Incubators are an excellent place to innovate, test new ideas, grow functionality that may one day be moved into another Project, and develop new committers.
Incubator Projects never have releases; they do not require yearly continuation reviews and they are not part of the annual release train. Incubators may have builds, and downloads. They conform to the standard incubation branding requirements and are subject to the IP due diligence rules outlined for incubating Projects. Incubators do not graduate.
The scope of an Incubator Project must fall within the scope of its parent project. The committer group of the Incubator Project must overlap with that of the parent project (at least one committer from the parent project must be a committer for the Incubator). Incubator projects do not require Architecture Council mentors (the parent project's committers are responsible for ensuring that the Incubator project conform to the rules set forth by the Eclipse Development Process).
An Incubator project should designated as such by including the word "Incubator" in its name (e.g. "Eclipse Incubator"). To do otherwise is considered exceptional and requires approval from the PMC and EMO(ED).
Only Top-Level Projects and Projects in the Mature phase may create an Incubator. Incubators are created via a Creation Review. Alternatively, an Incubator can be created as part of a Graduation, Promotion, or Restructuring Review.
This section has been modified to explicitly state that project may opt to aggregate their plan with that of descendant projects.
The Roadmap describes the collective Eclipse Projects future directions and consists of two parts:
The Roadmap must be consistent with the Purposes as described in Bylaws section 1.1. It is developed using the prescribed roadmap process.
The Roadmap is prepared by the Councils and approved by the Board annually. A proposed Roadmap or Roadmap update is disseminated to the Membership at Large for comment and feedback in advance of its adoption. This dissemination and all discussion and debate around the Roadmap must be held in an open and transparent public forum, such as mailing lists or newsgroups.
Prior to any Board vote to approve a Roadmap or Roadmap update, every Member has the right to communicate concerns and objections to the Board.
The process of producing or updating the Roadmap is expected to be iterative. An initial set of Themes and Priorities may be infeasible to implement in the desired timeframe; subsequent consideration may reveal new implementation alternatives or critical requirements that alter the team's perspective on priorities. The EMO orchestrates interaction among and within the Councils to drive the Roadmap to convergence.
This Development Process, the EMO, the Councils, and the Projects all acknowledge that the success of the Eclipse ecosystem is dependent on a balanced set of requirements and implementations. A Roadmap that provides too large a burden on the Projects will be rejected and ignored; similarly, a Roadmap that provides no predictable Project plans will be unhelpful to the business and technical plans being created by the ecosystem. A careful balance of demands and commitments is essential to the ongoing success of the Eclipse Projects, frameworks, and ecosystem.
The Project Leadership is expected to ensure that their Project Plans are consistent with the Roadmap, and that all plans, technical documents and reports are publicly available. To meet this requirement, each Project is required to create a transparently available Project Plan in an EMO-defined file format that meets the following criteria:
A Project may incrementally revise their Project Plan to deliver additional tasks provided that:
A project may produce an aggregate plan for itself and its descendants. In this case descendents would share their ancestor's plan.
All Eclipse Projects, and hence all Project Proposals, must be consistent with the Purposes and the then-current Roadmap.
Projects must work within their Scope. Projects that desire to expand beyond their current Scope must seek an enlargement of their Scope using a public Review as described below.
All projects are required to report their status at least quarterly using the EMO defined status reporting procedures.
Projects must provide advanced notification of upcoming features and frameworks via their Project Plan.
New Proposals that intend to do a Release are required to have at least two Mentors. New Proposals that will only Release code as part of a parent Project's Release are not required to have Mentors. Mentors must be members of the Architecture Council. The Mentors (including name, affiliation, and current Eclipse projects/roles) must be listed in the Proposal. Mentors are required to monitor and advise the new Project during its Incubation Phase, but are released from that duty once the Project graduates to the Mature Phase.
Projects go through six distinct phases. The transitions from phase to phase are open and transparent public reviews.
An individual or group of individuals declares their interest in, and rationale for, establishing a project. The EMO will assist such groups in the preparation of a project Proposal.
The proposers, in conjunction with the destination PMC and the community, collaborate in public to enhance, refine, and clarify the proposal. Mentors (if necessary) for the project must be identified during this phase.
After the project has been created, the purpose of the incubation phase is to establish a fully-functioning open-source project. In this context, incubation is about developing the process, the community, and the technology. Incubation is a phase rather than a place: new projects may be incubated under any existing Project.
Many Eclipse Projects are proposed and initiated by individuals with extensive and successful software development experience. This document attempts to define a process that is sufficiently flexible to learn from all its participants. At the same time, however, the Incubation phase is useful for new Projects to learn the community-defined Eclipse-centric open source processes.
Only projects that are properly identified as being in the incubation phase (including designated Incubator Projects) may use the Parallel IP process to reduce IP clearance process for new contributions.
The project team has demonstrated that they are an open-source project with an open and transparent process; an actively involved and growing community; and Eclipse Quality technology. The project is now a mature member of the Eclipse Community. Major releases continue to go through Release Reviews.
Projects that have demonstrated the characteristics of a Top-Level Project (e.g., consistent leadership in a technical area and the recruitment of a wider developer community) can be promoted to Top-Level Project status. This promotion occurs through a Promotion Review. Upon the successful completion of a Promotion Review, the EMO(ED) may recommend that the project be promoted to the Board of Directors and ask that its Charter be reviewed and approved.
Projects that become inactive, either through dwindling resources or by reaching their natural conclusion, are archived. Projects can reach their natural conclusion in a number of ways: for example, a project might become so popular that it is absorbed into one of the other major frameworks. Projects are moved to Archived status through a Termination Review.
If there is sufficient community interest in reactivating an Archived Project, the Project will start again with Creation Review. As there must be good reasons to have moved a Project to the Archives, the Creation Review provides a sufficiently high bar to prove that those reasons are no longer valid. It also ensures that the original or updated project goals are still consistent with the Purposes and Roadmap.
This iteration of the document removes the notion of a "review call" in favour of a "review period" during which the community is given an opportunity to comment. This acknowledges the reality that the optional review calls required by the previous version of this document never actually occurred. Given that there will be no review calls, references to "slides" have been removed.
See Bug 304878.
The Eclipse Development Process is predicated on open and transparent behavior. All major changes to Eclipse projects must be announced and reviewed by the membership-at-large. Major changes include the Project Phase transitions as well as the introduction or exclusion of significant new technology or capability. It is a clear requirement of this document that members who are monitoring the appropriate media channels (e.g., mailing lists or RSS feeds) not be surprised by the post-facto actions of the Projects.
All Projects are required to participate in at least one Review per year.
For each Review, the project leadership makes a presentation to, and receives feedback from, the Eclipse membership.
A Review is a fairly comprehensive process. Gathering the material for a Review and preparing the presentation is a non-trivial effort, but the introspection offered by this exercise is useful for the Project and results are very useful for the entire Eclipse community. In addition, Reviews have a specific relationship to the requirements of the Eclipse IP Policy.
All Reviews have the same general process:
The criteria for the successful completion of each type of Review will be documented in writing by the EMO in guidelines made available via the www.eclipse.org website. Such guidelines will include, but are not limited to the following:
The Review period is open for no less than one week and usually no more than two weeks of generally accepted business days.
If any Member believes that the EMO has acted incorrectly in approving or failing a Review may appeal to the Board to review the EMO's decision.
The purpose of the Creation Review is to assess the community and membership response to the proposal, to verify that appropriate resources are available for the project to achieve its plan, and to serve as a committer election for the project's initial Committers. The Eclipse Foundation strives not to be a repository of "code dumps" and thus projects must be sufficiently staffed for forward progress.
The Creation Review documents must include short nomination bios of the proposed initial committers. These bios should discuss their relationship to, and history with, the incoming code and/or their involvement with the area/technologies covered by the proposal. The goal is to help keep any legacy contributors connected to new project and explain that connection to the current and future Eclipse membership, as well as justify the initial Committers' participation in a meritocracy.
The purpose of the Graduation Review is to confirm that the Project is/has:
The Graduation Review is about the phase change from Incubation Phase to Mature Phase. If the Project and/or some of its code is simultaneously relocating to another Project, the Graduation Review will be combined with a Restructuring Review.
The purposes of a Release Review are: to summarize the accomplishments of the release, to verify that the IP Policy has been followed and all approvals have been received, to highlight any remaining quality and/or architectural issues, and to verify that the project is continuing to operate according to the Principles and Purposes of Eclipse.
The purpose of a Promotion Review is to determine if the Project has demonstrated the characteristics of a Top-Level Project, e.g., consistent leadership in a technical area and the recruitment of a wider developer community. The Project will already be a well-functioning Mature Eclipse Project, so evidence to the contrary will be a negative for promotion. Top-Level Projects, both through their existence and their Council memberships, have substantial influence over direction and operation of Eclipse, thus it behooves the membership to grant Top-Level status only for merit: for demonstrated service to the larger Eclipse ecosystem.
The purpose of a Continuation Review is to verify that a Proposal or Project continues to be a viable effort and a credit to Eclipse. The Project team will be expected to explain the recent technical progress and to demonstrate sufficient adopter, developer, and user support for the Project. The goal of the Continuation Review is to avoid having inactive projects looking promising but never actually delivering extensible frameworks and exemplary tools to the ecosystem.
The purpose of a Termination Review is to provide a final opportunity for the Committers and/or Eclipse membership to discuss the proposed withdrawal of a Proposal or archiving of a Project. The desired outcome is to find sufficient evidence of renewed interest and resources in keeping the Project or Proposal active.
A Move Review is considered to be a special type of Restructuring Review.
This iteration of the document provides more detail on Restructuring Reviews. It also considers a Move Review (as defined by the previous version of this document) to be a special type of a Restructuring Review.
This version of the document makes explicit a loophole that permits the creation of new projects without engaging in the full proposal/creation process. This applies only to new project with a scope that is a subset of the original project's scope. There is no explicit requirement that a project become a parent to the new projects. New projects can be created as siblings or elsewhere in the project hierarchy. In the event that a restructuring review results in unrelated projects, it is expected that the scope of the original project will be adjusted accordingly.
The purpose of a Restructuring Review is to notify the community of your intent to make significant changes to one or more projects. "Significant changes" includes:
A Restructuring Review may include the movement of significant chunks of code. A move is considered significant if it has an impact on the community (i.e. if segments of the community will notice that the code has moved). This may include entire projects, bundles, and features, but likely excludes small fragments, code snippets and individual files. The IP Log of all moved code must be reviewed prior to the start of the review period (this, typically, is a subset of the project's IP Log). If all of the code is moved out of a project, a Termination Review for that project can be combined with the Restructuring Review.
Note that, regardless of whether or not a review is required, moving code from one Project to another is subject to the Eclipse IP Policy.
A Restructuring Review may necessitate the construction of one or more new projects. This tends to occur when an existing project is decomposed into two or more projects. In this case, a Restructuring Review is similar to a Creation Review. Any new projects that are created as part of a Restructuring Review must have their scope explicitly specified as part of the review. The scope of any new project must be a subset of the scope of the original project. Likewise, the set of committers assigned to a new project must be a subset of the committers of the original project (additional committers can be elected to the new project after it is created). Any new projects that fall outside of the scope of the original project, or wish to establish a different set of committers, must undergo the full project creation process.
Committers can be moved along with code into a new project as part of the project provisioning process. Committers cannot be moved along with code into an existing project. In this case, the existing project must elect the new committers into the project.
A project is expected to socialize pending changes using established communication channels prior to initiating the review. A Restructuring Review must provide the community with at least one week to review and respond to the changes. Prior to the start of that review period, the community must be provided with (via the EMO) completed review documentation that describes in specific terms what will be changed as part of the restructuring.
This may include:
This section has been modified to explicitly allow multiple projects to participate in a single. It is possible, for example, for a project and its descendants to engage in a simultaneous Release Review.
Reviews can be combined at the discretion of the PMC and EMO. Multiple Projects may participate in a single Review. Similarly, multiple review types can be engaged in simultaneously. A parent Project may, for example, engage in an aggregated Release Review involving itself and some or all of its child projects; a consolidated Restructuring Review may move the code for several projects; or a Release Review may be combined with a Graduation Review. When multiple reviews are combined, the review documentation must explicitly state all of the Projects and types of reviews involved, and include the required information about each.
It should be noted that the purpose of combining reviews is to better serve the community, rather than to reduce effort on the part of the project (though it is fortunate when it does both). Combining a Release and Graduation review, or aggregating a Release Review of a Project and several of it's child Projects generally makes sense. Combining Release Reviews for multiple unrelated projects most likely does not.
(Most of this section is borrowed and paraphrased from the excellent Apache Software Foundation Releases FAQ. The Eclipse community has many of the same beliefs about Releases as does the Apache community and their words were already excellent. The Apache Software Foundation Releases FAQ is distributed under the Apache License, Version 2.0.)
Releases are, by definition, anything that is distributed outside of the Committers of a Project. If users are being directed to download a build, then that build has been released (modulo the exceptions below). All Projects and Committers must obey the Eclipse Foundation requirements on approving any release.
(Exception 1: nightly and integration builds) During the process of developing software and preparing a Release, various nightly and integration builds are made available to the developer community for testing purposes. Do not include any links on the project website, blogs, wikis, etc. that might encourage non-early-adopters to download and use nightly builds, release candidates, or any other similar package (links aimed at early-adopters and the project's developers are both permitted and encouraged). The only people who are supposed to know about such packages are the people following the developer mailing list and thus are aware of the limitations of such builds.
(Exception 2: milestone and release candidate builds) Projects are encouraged to use an agile development process including regular milestones (for example, six week milestones). Milestones and release candidates are "almost releases" intended for adoption and testing by early adopters. Projects are allowed to have links on the project website, blogs, wikis, etc. to encourage these outside-the-committer-circle early adopters to download and test the milestones and release candidates, but such communications must include caveats explaining that these are not official Releases.
x.yMz, e.g., 2.3M1 (milestone 1 towards version 2.3), 2.3M2 (milestone 2 towards version 2.3), etc.
x.yRCz, e.g., 2.3RC1 (release candidate 1 towards version 2.3).
x.y, e.g., 0.5, 1.0, 2.3, etc.
All official Releases must have a successful Release Review before being made available for download.
(Exception 3: bug fix releases with no new features) Bug fix releases (x.y.z, e.g., 2.3.1) with no new features over the base release (e.g., 2.3) are allowed to be released without an additional Release Review. If a bug fix release contains new features, then the Project must have a full Release Review.
Under no circumstances are builds and milestones to be used as a substitute for doing proper official Releases. Proper Release management and reviews is a key aspect of Eclipse Quality.
When a Member has a concern about a Project, the Member will raise that concern with the Project's Leadership. If the Member is not satisfied with the result, the Member can raise the concern with the parent Project's Leadership. The Member can continue appeals up the Project Leadership Chain and, if still not satisfied, thence to the EMO, then the Executive Director, and finally to the Board. All appeals and discussions will abide by the Guiding Principles of being open, transparent, and public.
Member concerns may include:
A variety of grievance resolutions are available to the EMO up to, and including, rebooting or restarting a project with new Committers and leadership.
In the event of a conflict between this document and a Board-approved project charter, the most recently approved document will take precedence.
As specified in the Bylaws, the EMO is responsible for maintaining this document and all changes must be approved by the Board.
Due to the continued evolution of the Eclipse technology, the Eclipse community, and the software marketplace, it is expected that the Development Process (this document) will be reviewed and revised on at least an annual basis. The timeline for that review should be chosen so as to incorporate the lessons of the previous annual coordinate release and to be applied to the next annual coordinated release.
The EMO is further responsible for ensuring that all plans, documents and reports produced in accordance with this Development Process be made available to the Membership at Large via an appropriate mechanism in a timely, effective manner.
This document was approved by the Eclipse Foundation Board of Directors in its meeting on May 19/2010. It takes effect (replacing all previous versions) on August 1/2010.
Back to the top


text:
Last week, Emory Orthopaedics & Spine Center physician, Oluseun Olufade, MD, attended "Ladies Night Out" at Emory Johns Creek Hospital. Ladies Night Out is an annual health event for women and provides them with a fun night of shopping, free health screenings and casual consultations with local physicians.
At the Emory Orthopaedics & Spine Center table, Dr. Olufade spoke with women about stress fractures and how to prevent them. Studies show that female athletes are more prone to stress fractures than male athletes. As a fun activity, attendees entered a free drawing for new running sneakers, a key item to preventing stress fractures and other orthopedic injuries. Four lucky women walked away from the event with new shoes, but we want to provide everyone with Dr. Olufade's helpful tips. Below are 12 things every woman should know about stress fractures:
What is a stress fracture?
1. A stress fracture is a tiny crack in the bone caused by repeated stress or force, often from overuse.
What are the symptoms of a stress fracture?
2. Pain that worsens over time; limping or tenderness. Possible swelling around painful area.
What are the risk factors for stress fractures?
3. Increased amount, distance, intensity or frequency of an activity too rapidly.
4. Female gender: lower bone density, less lean body mass in the lower limbs, low-fat diet and a history of menstrual disturbance are all significant risk factors for stress fractures.
5. Poor footwear: affects the distribution of weight.
6. Sports specific: change in training pattern (i.e., introduction of hill running), change of surface (i.e., soft clay tennis court to a hard court).
7. Weak bones: from osteoporosis, medications or eating disorders.
How do I prevent stress fractures?
8. Set incremental goals: apply stress to the bone in a controlled manner to strengthen the bone over time. Try increasing distance by <10% per week to allow bones to adapt.
9. Build muscle strength in the legs to increase shock absorption and muscle fatigue.
10. Alternate activities to help prevent injury.
11. Warm up before exercising, including stretching.
12. Use the proper equipment, including footwear. Make gradual changes to shoes and running surfaces. Well-cushioned running shoes that fit well can prevent stress fractures (depending on various factors including weight and shoe durability). Runners should replace their shoes every 300-700 miles to allow adequate mid-sole cushioning.
Think you may have a stress fracture? Make an appointment with an Emory sports medicine specialist. We'll get you up and running again!
About Dr. Olufade
Oluseun Olufade, MD, is board certified in Physical Medicine & Rehabilitation, Sports Medicine . He completed fellowship training in both Interventional Pain Medicine and Sports Medicine. During his fellowship training, he was a team physician for Philadelphia Union, a major league soccer (MLS) team, Widener University Football team and Interboro High School Football team.
Dr. Olufade employs a comprehensive approach in the treatment of sports related injuries and spinal disorders by integrating physical therapy, orthotic prescription and minimally invasive procedures. He specializes also in concussion, tendinopathies and platelet rich plasma (PRP) injections. He performs procedures such as fluoroscopic-guided spine injections and ultrasound guided peripheral joint injections. Dr. Olufade individualizes his plan with a focus on functional restoration.
Dr. Olufade has held many leadership roles including Chief Resident, Vice-President of Resident Physician Council of AAPM&R, President of his medical school class and Editor of the PM&R Newsletter. He has authored multiple book chapters and presented at national conferences.
Tags: acl injuries, cartilage injury, emory sports medicine center, how to preve

subset: commoncrawl


text:
1/10 Exceed RC Brushless PRO Electric Infinitive EP RTR Off Road Truck (Sava Green) RC Remote Control Radio Car
The Infinitive EP is equipped with robust and durable front and rear bumpers that protect the main body of the truck. It is also equipped with aluminum threaded shock bodies which allows the preload of the springs to be quickly and easily tuned. The camber and toe are also easily adjusted through the use of aluminum turnbuckles. These combined features allow the user to quickly and easily tune the suspension geometry, letting the user get the most out of the Infinitive EP platform.
The Infinitive EP is powered by a Sensorless Brushless Motor rated at 3300KV @ 12Turns and a programmable 60amp ESC, that?s capable of handling 4-9s Nickel batteries or 2-3s LiPo batteries. This new powertrain is easily capable of providing reliable and consistent power for extreme off-road driving. Best of all, the motor and transmission are both completely sealed to prevent dirt and grime from getting in and causing damage. This motor has been proven to be both durable and reliable, making the Infinitive EP a welcomed addition to the latest Exceed RC line. With 20 exciting color schemes to choose from the Infinitive EP is sure to be a favorite for RC enthusiasts everywhere.
More Featured Items


text:
Practical information
- Where: Roncesvalles
- Autonomous region: Autonomous Community of Navarre
- Province/Island: Navarre
- Category: Festivity of Tourist Interest
Numerous inhabitants of the various towns in the area of the Pyrenees make a pilgrimage every spring to venerate the Virgin of the Royal Collegiate Church of Santa María, in Orreaga-Roncesvalles, Navarre.
The most interesting pilgrimages include the one in the Arce valley, which has been in existence since the 16th century; and the one in the Aezkoa valley, which is the most visually striking and colourful. All over the area in May and June you'll come across pilgrims dressed in dark tunics, or barefoot penitents covered with black veils. All process silently towards the altar of the Virgin, offering an extremely moving spectacle.
For more information, check the official website .
Practical information
Contact details
Tel. +34 948760301


text:
Find local BMW Dealers and BMW Certified Inventory by entering your ZIP code
325 Three Springs Rd
Bowling Green, KY 42104-7552
Sales: (270) 745-0001
PRICED BELOW KBB, ONE OWNER CLEAN CARFAX, BLUE TOOTH COMMUNICATION, HEATED SEATS, FACTORY NAVIGATION GPS NAV, REAR BACKUP CAMERA, LOCAL TRADE IN, FACTORY MAINTENANCE UP TO DATE, SERVICE RECORDS AVAILABLE, CLEAN CARFAX, HEADS UP DISPLAY, PARK DISTANCE CONTROL, Advanced Real-Time Traffic Information, BMW Online & BMW Apps, Head-Up Display, Heated Front Seats, Instrument Cluster w/Extended Contents, Navigation System, Rear-View Camera, Remote Services, Satellite Radio, Technology Package. Clean CARFAX. 21/28 City/Highway MPG
* If you want your upscale SUV to accent "sport," then the 2015 BMW X3 may just be the ticket. Of course, with plenty of cargo space and a choice of two fuel-efficient engines, it's not short on utility, either. Source: KBB.com
* Large selection of potent and reasonably efficient engines; high-quality cabin; generous passenger and cargo room; crisp handling; comfortable rear seat. Source: Edmunds
* In 2015, BMW has made some subtle refinements to the stylish, five passenger X3. Still designed to convey elegance, agility, and power, its sleek silhouette and the new redesigned 3-dimensional kidney grille give it a bold and powerful face. The specially designed taillights show off its unique style and once inside, one immediately notices the space offered by high seating positions for extended shoulder room, legroom, and headroom. All without forgetting the luxury details BMW is known for. 2015 introduces the first xDrive28d diesel option, which makes use of the same 2.0-liter four-cylinder turbo-diesel that powers the 328d, making 180hp and 280 lb-ft of torque. AWD is standard in all models now, and the fuel-efficient turbocharged four-cylinder is standard in the xDrive28i model. This base 2L engine gives 240hp and goes 0-60mph in the mid-six second range, while bumping up to the 3L six-cylinder with two sport modes can get there in five seconds flat at 300hp. Standard is the buttery smooth eight-speed automatic transmission. The X3 is known for remarkable passing power and ability to be first on the on-ramp. This sports activity vehicle is also a quiet, comfortable ride; complimented by equally impressive appointments such as eight-way power front seats clad in leatherette upholstery with contrast stitching. Standard highlights include a power tailgate and rain-sensing windshield wipers with automatic headlight control. BMW offers a Technology Package that includes USB connectivity and Bluetooth with smartphone integration, in addition to navigation and iDrive refinements. Finally, the X3 offers a 12 speaker, 205-watt sound system and a slew of safety features including significant airbags, anti-theft alarm, and lower anchors and tethers for car seats. Source: The Manufacturer Summary
325 Three Springs Rd
Bowling Green, KY 42104-7552
(0 Miles)
Sales: (270) 745-0001
Year: 2015
Make: BMW
Model: X3 xDrive28i
Price: $14,599
Mileage: 158,207
Engine: I-4 cyl
Exterior Color: Jet Black
Interior Color: Black SensaTec
Fuel Type: Other
Stock #: T0D51253
City MPG: 21
Hwy MPG: 28
Featured Options
Driving Assistance Package
Technology Package
Roof rails in Satin Aluminum
Heated front seats
Burl Walnut Wood Trim
Included Packages
Driving Assistance Package
Technology Package
Additional Options
Roof rails in Satin Aluminum
Heated front seats
Burl Walnut Wood Trim
CO2 relevant vehicles
Automatic Start/Stop function
Brake Energy Regeneration
Multifunction steering wheel
Sport leather steering wheel
Tire pressure monitor
Alarm System
Power tailgate
Universal garage-door opener
Privacy glass
Floor mats
Auto-dimming mirrors
Auto-dimming rearview mirror
Power Front Seats
40/20/40 Split Rear Seat
Storage package
Black high gloss instr panel
Automatic climate control
Dynamic Cruise Control
Ambient Lighting
LED Fog Lights
Hi-fi sound system
Satellite radio preparation
DVD Area coding, North America
BMW Assist eCall
BMW TeleServices
Hands-free Bluetooth and USB
Oil Chg 10,000 mls/12 months
Daytime driving lights
Transport protection
Run-flat tires


text:
The final months of 2011 produced little in the way of weather news, but the tone for this year was set early in the year, and it was not good.
One of the highest tornado death tolls in recent memory and a devastating drought in parts of the South and Southwest were the big stories of the year. But there also were memorable snowstorms in the East, Southeast and Midwest, plus major spring flooding in the Midwest and South.
Summer didn't bring an end to the misery, with a 40-state heat wave in July and a hurricane that produced major flooding in late August.
Five people were killed in November tornadoes in the Carolinas, pushing the twister death toll this year in the country to near 500.
And the news wasn't limited to the continental United States. A storm of epic proportions hit the west coast of Alaska in November.
The year started with a Greenland block -- strong high pressure over Greenland that caused a Negative Arctic Oscillation and brought repeated bouts of cold weather to the East and Midwest. Storm systems formed along the edge of the circulation flow and brought heavy snow to the East.
In mid-February, the Greenland block weakened. With La Nina conditions, the persistent storm track brought several rounds of tornadoes to the South and Midwest.
Summer of 2011 was extremely hot. The storm track moved a bit north, and the result was a very wet season for the eastern Great Lakes and Northeast -- and a very dry summer elsewhere.
The hurricane season was, for the United States, a washout. Only one storm of note affected the country.
I'll recap Charlotte-area 2011 weather later this weekend, but here's a look at the big meteorological stories in the country for the year:
JANUARY SNOW ... A series of snowstorms hit the eastern United States in January. The first brought snow to the Carolinas around Jan. 9, and it moved up the coast. On Jan. 11, every state except Florida had snow on the ground somewhere.
Huntsville, Ala., had snow on the ground for eight straight days, setting a record. New York City and Hartford broke January snowfall records, and South Bend, Ind., set a 24-hour snowfall record with 26 inches on Jan. 8.
At the tail end of the month (actually stretching to Feb. 3) came a Midwest storm. Blizzard conditions, with two feet of snow, were reported in Chicago.
TORNADOES ... The jet stream set up a pattern for storms in April and May, with the track stretching from Texas across Tennessee and Kentucky. That put states from Missouri to the Carolinas in the danger zone for severe weather.
A tornado outbreak in the Carolinas and elsewhere in the Southeast killed 38 people April 14-16, but that was a prelude for the worst of it -- the April 25-28 tornadoes that killed 321 people. Tuscaloosa, Ala., was among the hardest-hit cities. Another outbreak, around May 22-24, included an F5 tornado in Joplin, Mo. The death toll was 177.
Then came the Nov. 16 tornadoes in the Carolinas, with three deaths in Rock Hill and two in Davidson County.
Probably the biggest impact from 2011's tornadoes is a fresh look at the warning system in the United States. A National Weather Service study on the Joplin twister showed that many people did not pay attention to tornado warnings issued by the Weather Service. Emergency management officials will spend 2012 trying to determine why -- and how to change this.
FLOODING ... Extremely heavy rainfall in late April and early May brought record flooding along parts of the Ohio and Mississippi rivers. The area below St. Louis, stretching down to Vicksburg, Miss., was especially hard-hit. But there also was severe flooding during the spring on the Souris River, near Minot, N.D.
JULY HEAT ... Temperatures regularly soared above 100 degrees in much of the South and Southwest, with places like Dallas and Austin shattering records for consecutive 100-degree days. Readings of 100 degrees or more were recorded in Austin and San Antonio as late as the end of September.
At least 40 states reported heat wave conditions. In the Carolinas and other parts of the Southeast, the humidity was a big story. While record heat was not a problem, the high humidity kept temperatures from falling below the mid 70s many nights from late June to mid August.
DROUGHT AND WILDFIRES ... The driest conditions in history were reported across all or parts of Texas, Oklahoma, Arkansas, Louisiana, Kansas, New Mexico, Arizona and Colorado. A lesser area of drought affected a corridor from Mississippi, across Alabama, Georgia and western South Carolina.
As might be expected, wildfires were a huge problem. Fires caused more than $1 billion damage in Texas, New Mexico and Arizona. The Bastrop fire, about 30 miles southeast of Austin, destroyed 1,500 homes and was the worst wildfire in Texas history.
ON THE OTHER HAND ... While part of the country was baking, another part was having a record wet year. Storm systems repeatedly crossed an area from Indiana, over Ohio, Pennsylvania, New York and New England. Then rain from Hurricane Irene added to the mess. The result was several episodes of flooding and some record amounts of precipitation for the year.
Philadelphia had more rain this year (64 1/2 inches) than did Bangkok, Thailand (59 inches).
HURRICANE IRENE ... It was the only hurricane to make landfall in the United States this year, but Irene left its mark. The storm first touched U.S. soil in North Carolina, carving a path slightly inland from the Outer Banks and causing major damage from Morehead City north to the Virginia line.
Irene's approach caused hurricane warnings to be issued for New York City, for the first time in many years. But the system weakened to tropical storm status before making a second U.S. landfall on Long Island. However, heavy rain from Irene's remnants caused massive flooding in Pennsylvania, New Jersey, New York, Connecticut and Vermont. Millions of people were without power for weeks.
ALASKA STORM ... The Bering Sea Superstorm of Nov. 8-9 had low pressure equal to that of a Category 3 hurricane, and it heavily damaged 40 villages and cities along Alaska's west coast. Carrying 100 mph winds, the storm created a 10-foot surge near Nome, and it produced incredible blizzard conditions with heavy snow, gigantic waves, and hurricane-force winds. Advance warning paid off, though, as only one life was claimed by the storm.
Friday, December 30, 2011
2011 ... a frightening weather year
The final months of 2011 produced little in the way of weather news, but the tone for this year was set early in the year, and it was not good.
Wednesday, December 28, 2011
Cold, snow? Where is it?
Those of you clamoring for cold weather and wintry precipitation -- a group that does not include me -- are suffering through what is, for you, a nightmarish December.
And it's starting to look as if the trend will carry into January.
Temperatures are nearly 6 degrees above average for the month and more than 13 degrees warmer than last December.
The word "snow" hasn't even been mentioned in a Piedmont forecast, and even the North Carolina mountains aren't seeing much frozen precipitation. It's been largely the same way from the eastern Great Lakes to New England.
Our pattern has been consistent -- one or two days of chilly weather, followed by several days of well-above-average temperatures. Fortunately, we've had plenty of rain, so there are no worried about a drought.
This has been classic La Nina conditions.
We had a La Nina last winter, but from early December until mid February, we also had a powerful high pressure system over Greenland that created a "negative" Arctic oscillation and sent very cold air into the eastern United States on a repeated basis.
This year, the Greenland high is not blocking mild air from the Pacific (which is what La Nina produces).
As of now, there are no signs of a different pattern through the first 10 or 11 days of January.
It looks as if we could get our coldest temperatures so far this winter next week. A northwest flow is expected to develop, due to a large trough over the eastern United States.
"It seems cold weather is on the way next week," says Doug Outlaw, of the National Weather Service office in Greer, S.C.
But the really cold air remains bottled up in the arctic, so the "cold" air that funnels down the trough into the Southeast next week won't be brutal. We're talking about a couple of days -- Tuesday and Wednesday, most likely, with highs in the mid to upper 40s and lows in the mid 20s.
Then guess what? The forecast is for a warming trend, from about Jan. 7 to 11. Temperatures could reach 60 degrees again in the second week of January.
As I've written several times already this season ... this pattern could change. A Greenland block could establish itself in late January or anytime in February. But we're apparently going to get through the first half of winter without much of the weather that the cold weather fans really want.
Monday, December 19, 2011
3 storms in next week; snow in the North?
Get ready for a week of unsettled weather across the Charlotte region, with a chance of three separate storm systems affecting the area between now and Christmas.
The last of those low pressure systems could be a snow-maker to parts of the Great Lakes, Mid-Atlantic and New England on Christmas Eve or Christmas Day.
If you're planning holiday travel, you're likely to encounter rain, no matter when you hit the road (or fly) before Christmas.
The situation is difficult to pin down, because the computer models are having a tough time getting the timing right.
But the main thing to remember for the Carolinas is the word "mild." Unlike last year, it will be far too warm for any snowfall. The chilly weather of the past few days will transform into another round of above-average temperatures for much of this week.
High temperatures will be in the 60s from Tuesday through Thursday, and it will remain in the upper 50s Friday and probably Saturday. Sunday is a bit of a question mark, because Christmas could turn out to be a chilly, rainy day.
If you're planning travel, here's the rundown, as of mid-afternoon Monday:
STORM #1: This is the system responsible for the blizzard warnings across parts of the Southwest and southern Plains. This storm will dump heavy snow in that area later Monday and early Tuesday, then make a run northeast. Rain will fall in most areas, for the heavy snow in parts of New Mexico, the Texas panhandle, western Oklahoma, southeast Colorado and western Kansas.
This system will bring moderate rain to the Mississippi and Ohio valley areas and then into the Great Lakes later Tuesday. It will bring showers to the Charlotte region from Tuesday evening into early Wednesday afternoon.
STORM #2: This will be a weaker system, coming out of Texas on Wednesday and crossing the South on Thursday and early Friday. It will produce scattered showers, including a chance of showers Thursday evening and early Friday in the Charlotte region.
STORM #3: This might be the news-maker, because of the snow potential. Some computer models indicate low pressure will swing south from the Rockies, move into Texas and intensify, and then cross the Southeast and swing up the East Coast. If you're traveling Saturday, this system could bring a considerable amount of rain from Georgia up the East Coast.
The highest chance of snow would be in cities like Chicago, Detroit, Cleveland, Pittsburgh and Buffalo, along with much of New York state, much of Massachusetts, western Connecticut, most of Pennsylvania except the Philadelphia area, and extreme western Maryland. The East Coast's big cities would get a cold rain.
If everything develops as indicated, it could mean a rainy Christmas Day in Charlotte -- especially early in the day -- with temperatures only in the 40s.
But some of the computer models are slower with this system, and some show it being weaker.
Tune in again tomorrow.
Wednesday, December 14, 2011
An early look at Christmas travel
Yesterday's blog entry dealt with the chances of snowfall for Christmas in various parts of the eastern United States, but there's another big question for many people ... what will travel conditions be like?
Christmas isn't quite the travel holiday that Thanksgiving is, but millions of people will be flying or driving a significant distance over a period of nearly two weeks.
The computer models have been hinting at the development of a big storm system next week. According to the scenario, the low pressure system would develop over Texas on Monday and then follow a path northeast, into the Great Lakes and then across northern New England. That path would mean accumulating snow in parts of Iowa, western and northern Illinois, Wisconsin, Minnesota, Michigan, New York, Vermont, New Hampshire and Maine. Tuesday and especially Wednesday would be the rough travel days, and the storm would bring heavy rain to parts of the South and the Ohio River valley.
But the computers have been waffling a bit on the forecasts, so this qualifies as an "iffy" situation.
So, for entertainment purposes only (we'll have a much better idea by the weekend), here is the forecast for the week leading up to Christmas, and then a few days afterward.
CHARLOTTE, CAROLINAS and SOUTHEAST
Monday through Friday, Dec. 23: A mild week, with daytime highs from 60 to the mid 60s. Showers or a steadier rain are possible Tuesday (western Tennessee and Mississippi) and Wednesday (Carolinas, Georgia, eastern Tennessee), and another round of showers is possible on the 23rd.
Christmas Eve: Sunny, with highs in the low 50s.
Christmas Day: Same as Christmas Eve.
Dec. 26-28: Turning colder, with highs in the 40s. Some forecasts hint at rainy conditions on the 27th (the day of the Belk Bowl) or the 28th.
Monday through Friday, Dec. 23: It's a chilly week, but high temperatures are seasonal, in the 40s to near 50 (in places like St. Louis and Cincinnati). Rain spreads across the area Wednesday, and more rain is possible Friday. Snow could fall Friday in places like Milwaukee and Chicago.
Christmas Eve: A rain-snow mix in the eastern Lakes and near the Ohio River, but snow could fall in places like Detroit and Chicago. High temperatures in the 30s.
Christmas Day: Turning sunny but cold, with highs in the 20s (north) to mid 30s (south). Snow showers could still be possible in Cleveland, Buffalo and Pittsburgh.
Dec. 26-28: Becoming clear and turning milder, with highs in the 40s by the 28th.
MID-ATLANTIC (New York, Philadelphia, Washington-Baltimore, Boston)
Monday through Friday, Dec. 23: A mild week, with daytime highs in the 40s (Boston) and 50s elsewhere. But rain arrives by the 23rd.
Christmas Eve: Sunny, with highs in the low 40s (mid to upper 40s in DC and Baltimore).
Christmas Day: Same as Christmas Eve.
Dec. 26-28: Cold on Dec. 26, with rain or a rain-snow mix on the 27th. Then warmer and clearing for the 28th.
Monday through Friday, Dec. 23: A beautiful week, with partly sunny skies and daily highs in the mid and upper 70s.
Christmas Eve: A cold front brings rain and cooler weather, with highs in the upper 60s.
Christmas Day: Sunny but chilly, with highs in the 60s.
Dec. 26-28: Becoming warmer, and it could reach the 80s by the 28th.
Tuesday, December 13, 2011
White Christmas chances melting away
Wondering about our chances of having snow for a second consecutive Christmas?
Well, the Fat Lady might not be singing yet, but it doesn't look like "White Christmas" will be in her repertoire for 2011.
A winter storm provided the Charlotte region with a holiday thrill last year, as several inches of snow fell over much of the area -- although much of it fell early on Dec. 26 in Charlotte.
But the pattern that provided us with a brutally cold December and the white Christmas in 2010 is nowhere to be found this time around. That's the reason for our regular stretches of 60-degree-plus temperatures this December.
In fact, many of Carolinas residents who travel up North for the holidays and expect to see snow might view bare ground instead this year.
"Most of the Mid-Atlantic, southern New England, and the Southeast are likely out of the running for a white Christmas," says Alex Sosnowski, a meteorologist with Pennsylvania-based Accu-Weather. "There is too much mild air for snow in those areas."
And if the pattern doesn't change, we might be looking at a very mild winter.
La Nina conditions are present for the second straight year. La Nina (colder-than-average water temperatures in the eastern Pacific) brings mild and dry weather to the South. Cold air and storm systems typically hit the Northwest, upper Midwest, and upper Great Lakes.
Last year, La Nina was overwhelmed by another condition -- the Greenland Block. That is a strong high pressure system over Greenland, and it tends to steer arctic air into the eastern United States and also into Europe. It meant the Arctic Oscillation (AO) was negative, as the upper atmospheric pattern looked like the Thunder Road roller-coaster at Carowinds. The eastern United States was at the bottom of the tracks, and the arctic air tumbled down the tracks from Eskimo country.
"This year, that block is not present," says Scott Krentz, a meteorologist at the National Weather Service office in Greer, S.C. "So La Nina is a major governing factor in our weather."
In addition, a strong subtropical high pressure system is establishing itself over the South. That is keeping cold air far to our north.
How long will this condition last? Sosnowski, Krentz and other meteorologists don't know. Computer models only give us a two-week window into the future, but weather patterns don't tend to change in a hurry.
So it might turn cold in January, but odds of an icy and snowy start to 2012 are lower than they seemed a few weeks ago.
Here are predictions on white Christmas chances for some major cities, courtesy of Accu-Weather:
Probable: Denver, Milwaukee, Minneapolis-St. Paul, near Pittsburgh (especially east), eastern West Virginia, Buffalo, Syracuse, and inland New England.
Doubtful: Chicago, Cleveland, St. Louis, Cincinnati, New York City, Washington, Baltimore, Philadelphia and Boston. (Note: Detroit is between the "Probable" and "Doubtful" categories)
No: Charlotte and everywhere else south of the Mason-Dixon line.
Wednesday, December 7, 2011
Mountains to get a shot of winter
Much chillier air is headed for the Charlotte area, but it's the North Carolina mountains that stand to get a taste of wintry weather over the next 24 hours.
A cold front is crossing the state today, pushing away the mild, moist air that has caused cloudiness and well-above-average temperatures for the last two or three days.
In fact, the unofficial morning low at Charlotte/Douglas International Airport was 61 degrees, which is about 25 degrees below average. The warmest-ever low temperature for this date in Charlotte was 60 degrees, set in 1951. That reading probably won't set a record, though, because temperatures will tumble later today.
However, the mild temperatures are coming to an end. Two areas of rain are crossing the Carolinas today, and the cold front will push eastward of the area by early this afternoon. Temperatures will fall from the low and mid 60s Wednesday morning to the mid 50s by late afternoon. And those readings will tumble all the way to near 30 degrees by daybreak Thursday.
The cooler weather will stay through the weekend, with daily highs in the low to mid 50s, just a couple degrees below seasonal averages.
In the mountains, it'll be a different story.
The rain is forecast to change over to snow by this afternoon, accompanied by winds that might gust to 50 mph. No accumulations are expected in lower areas, like Asheville, but the ridge tops of the southern mountains could get an inch. And up to 4 inches could accumulate in the northern mountains.
Neil Dixon, of the National Weather Service office in Greer, S.C., said the biggest problem might be black ice. Quickly falling temperatures are expected to freeze the rain that falls this morning, and snow on top of the ice could make roads quite dangerous.
"Widespread black ice will create slick conditions on untreated roads, bridges and overpasses," Dixon said.
The low pressure system responsible for our rain and the mountain snow is expected to dump heavy wet snow on parts of West Virginia, western Maryland and Pennsylvania.
Tuesday, December 6, 2011
Gradually, the rain will get here
But it hasn't happened. The area of moderate to heavy rain over the Mid-South has moved very slowly eastward since Monday, but it's about to get a little nudge, and the rain intensity will increase across the Charlotte region soon.
Low pressure is expected to form along the slow-moving cold front and bring the whole system eastward later today and Wednesday.
We'll still remain dry much of the time today, but shower chances will increase considerably tonight. And Wednesday will be rainy much of the time. By the time the rain ends late Wednesday night, much of the area will get about an inch.
Since the growing season is over, many of us haven't been paying attention to rainfall totals, but the precipitation has been arriving at a healthy rate. Since Sept. 1, about a foot of rain has fallen in the Charlotte region. The months of September, October and November can be extremely dry some years, but we've been blessed with ample amounts of rain in autumn 2011. That will help us a lot when the 2012 growing season begins.
As you might expect, our balmy temperatures will go away when the rain ends and the cold front pushes through. In fact, it'll get downright chilly in the Charlotte area from Friday into Sunday, with highs struggling to hit 50 degrees over the weekend. And a couple inches of snow are likely in the mountains.
But there is nothing frigid on the horizon. Looking out two weeks, to around Dec. 19 and 20, the computer models don't show any really cold outbreaks in the Southeast.
The long-range forecasts point to a continuation of what we've been seeing -- brief chilly spells, followed by a warm-up and rain.
Thursday, December 1, 2011
Winter forecast ... an update
Today's the first day of meteorological winter (more about that later), and there are increasing signs that the winter of 2011-12 will be mild across the Southeast -- milder than initially thought.
First, about that "start of winter." I know the official date of winter's start is Dec. 21, but meteorologists believe true seasonal weather is closer to the first days of months. So winter is Dec. 1 to Feb. 28 (or 29); spring is March 1-May 31; summer is June 1-Aug. 31; and autumn is Sept. 1-Nov. 30.
Now, about the new forecast.
Let's go back and review the initial prediction. Forecasters said La Nina conditions in the Pacific would mean mild and dry weather in the South, and cold and snowy conditions in the northwest and parts of the Midwest. However, meteorologists also said that if a strong high pressure system develops over Greenland -- known as the Greenland Block -- it would cause a repeat of last winter.
Last year was a La Nina winter, but the Greenland Block overwhelmed La Nina and sent cold weather -- and a few winter storms -- into the Southeast and up the East Coast.
Forecasters said that they weren't sure if a Greenland Block would develop again this year.
So far, it hasn't. That means December will be milder than originally forecast, meteorologists say. They still aren't sure about January and early February, but they're sticking to their guns about a milder trend for latter February and March.
Accu-Weather, the big private company based in State College, Pa., updated its winter weather forecast today, noting that December will be relatively mild for much of the country.
Accu-Weather thinks the Carolinas will see little frozen precipitation this winter, and I've seen the same forecast from other meteorologists. Brad Panovich, the chief meteorologist at WCNC-TV, the Observer's news partner, has predicted that freezing rain -- not snow -- would be the more likely form of wintry precipitation in the Carolinas.
It would seem that most of our storms will bring cold rain -- or a "close call" between rain and freezing rain.
So here's a summary of the latest prediction for this winter:
CAROLINAS ... Generally, a mild December, with a few brief cold snaps. January is a question mark, and that's when we'd stand our best chance of seeing frozen precipitation. The best guess is that if February starts cold, it will turn mild.
One bad thing ... the current forecast indicates severe thunderstorms and tornadoes again will be a problem in late February and March (and probably into April) across the South.
REST OF THE SOUTH ... Virginia's weather will be a slightly cooler version of ours. Southern parts of Louisiana, Mississippi, Alabama, Georgia, and South Carolina, along with all of Florida, will be mild and dry.
The greatest chance of ice storms (mostly in January) will be in a band from north Texas, across Arkansas, Tennessee, northern Louisiana, northern Mississippi, northern Alabama, north Georgia, and Kentucky.
The severe weather threat will grow in late winter and early spring.
MID-ATLANTIC and NEW ENGLAND ... Not as harsh as last year. There will be a few major winter storms, but it will be nothing like the severe winter of 2010-11.
MIDWEST, GREAT LAKES ... This will be the worst of winter. Cold weather and snowstorms are likely from the Dakotas, across Minnesota, Wisconsin, Iowa, Michigan and northern parts of Illinois, Indiana and Ohio. It could be a nasty winter for Milwaukee, Minneapolis-St. Paul, Chicago, Detroit and Cleveland.
Less-frequent winter storms will impact places like St. Louis, Indianapolis and Cincinnati, where freezing rain or storms with both snow and rain are likely.
The Midwest will be at the heart of the winter storm track.
THE WEST ... The northwest will be colder than average, while the belt from California, across Arizona, Nevada, New Mexico and most of Texas will be mild and dry. That "dry" word is bad for drought-stricken Texas.


text:
Centennial Distinguished Lecture Series welcomes climate researcher Richard Alley
Free lecture planned for Tuesday, March 13 at UH Manoa Campus CenterUniversity of Hawaiʻi at Mānoa
UH Manoa Department of English
The UH Manoa Distinguished Lecture Series continues its Centennial year program this month with a presentation by Richard Alley, the Evan Pugh Professor of Geosciences at Penn St. University. Alley is one of the world's leading climate researchers, and has spent numerous field seasons in both Antarctica and Greenland studying the waxing and waning of ice sheets. The lecture presentation, "Get Rich and Save the World: Global Warming, Peak Oil, and Our Future," is scheduled for Tuesday, March 13, at 7:00 p.m. in the UH Manoa Campus Center Ballroom. It is free and open to the public.
Alley has chaired a National Research Council study on Abrupt Climate Change, and serves, or has served, on other advisory panels and steering committees related to climate change. In addition to publishing numerous scholarly articles on climate change and Earth's recent climate history, Alley's popular book The Two-Mile Time Machine: Ice Cores, Abrupt Climate Change, and Our Future (Princeton University Press) provides a first hand account of his own work drilling the Greenland ice sheet, and places the results of his own work in the context of global climate change research. The book received the 2001 Phi Beta Kappa Book Award in Science.
In addition to being recognized as an exceptional scholar, he is well known as a source of accessible public information about climate change, including appearance on TV (Nova, BBC), radio (NPR, Earth and Sky), and print outlets (New York Times, Time Magazine).
Alley will also lead a seminar — also open to the public at no charge — on the topic, "Fraying at the Edges — Sea Level and the Bizarre Behavior of Ice Sheets," Thursday, March 15, 3:00 - 5:00 pm in the Architecture Auditorium on the Manoa campus.


text:
The search found 391 results in 0.01 seconds.
The hashtag syllabus is a crowd-sourced body of work that can, in some cases, challenge the knowledge construction of the academy. Hashtag syllabi have the opportunity to reshape how knowledge is produced, whose knowledge is affirmed, and what knowledge people are exposed to.
Most historically and predominantly white institutions (HPWIs) now desire some number of black students on their campuses. However, recent theoretical scholarship suggests that HPWIs' desire for and willingness to embrace black students is predicated on their racial palatability. The theory of intraracial discrimination stipulates that white gatekeepers are increasingly inclined to screen blacks to "weed out" those they perceive as too concerned with race and racism.


text: Larry Brogan: Tattoo Convention Booth Set Up (Part I) By Larry Brogan Courtesy of Tattoo Road Trip: Most tattoo conventions provide a space for two working artists approximately 10'x10' but they can vary by a couple feet in either direction. You will usually have two long narrow tables, one to tattoo from and a front table to showcase and display your tattoo portfolio, original artwork, paintings, prints, tattoo machines, t-shirts or any other items and promotional material you choose provided they are permitted by the promoters and local law... Always be sure to have an ample supply of business cards or stickers with your name web address and contact information printed on them for people to grab. People always love free giveaways such as pens, stickers, CDs and even candy so having any of these can help draw more potential clients to your booth. Bringing your own table cloth can be a nice touch to help give an impressive presentation that will be more eye catching and make you stand out among the many other booths in the isle. A trip to a local fabric store will give you countless options for colorful and crazy table cloths and be sure to check into the Halloween fabrics where you will find some fun and festive designs. Your booth normally contains two artist chairs and two client chairs as well as at least 1 garbage can. The quality of the provided chairs varies from padded stackable banquet chairs to flimsy plastic folding chairs which are mostly useless and very uncomfortable. The padded banquet chairs can be used in many configurations such as stacking two or three high in order to reach a clients leg or lower back more comfortably or side by side to lay someone horizontally for areas such as ribs, underarms and hips. If you happen to by driving to the show, bringing your own office chair and or client chair or even a massage table can be very helpful. Many convention halls are very dark or you may be stuck in some dark corner of the room. I often bring 2 small clamp on halogen lights that I attach to the top of the pipe and drape behind the booth. You will need an extension cord at least 6 feet long with at least two outlets to be able to plug them into your power strip. Your booth will be much better lit than most others making it stand out more amongst the rest. You can buy these simple lights at hardware stores and home improvement stores such as Home Depot for around $10 each. Warning, they get extremely hot so unplug them at night and especially a bit in advance of taking them down at the end of a show or you will burn yourself. Your convention banner is the equivalent of flying your counties flag overhead and having something awesome and eye-catching will bring you more exposure. When sharing a booth with one or more artists you must keep in mind that there needs to be enough room for each artist to display their banner and enough space for items like flash, prints and t-shirts if necessary. I have found that a banner '2 to 3' wide by 4' to 5' high is the best overall fit for a booth containing two artists. Any longer, you will loose the lower portion behind the work table and any wider runs the risk of crowding your booth mate. While it is quite easy these days to get inexpensive banners printed with any images and info you need, as artists hand painting yours will help show your own artistic talent and just might earn you a little more respect from your peers. (Larry can be found at Tattoo City Skin Art Studio in Lockport, IL.)


text:
Health Fair is Saturday, March 2
- Details
- Category: Community
- Published on 27 February 2013
- Written by Mount Vernon Optic-Herald
The 2013 Franklin County Health Fair is Saturday, March 2 from 8:30 a.m. to noon in the First United Methodist Church Family Life Center.
The event will provide health care information to people of all ages about a range of health topics. Free blood pressure and glucose screenings will be available. For more information, see the Feb. 28 edition of the Mount Vernon Optic-Herald.


text: PEPPERELL–The Pepperell Senior Center is holding a table-decorating event and raffle. On Dec. 8, local businesses and individuals will be decorating tables with unique holiday centerpieces at the Senior Center. On Dec. 9 from 1 to 3 p.m. the center will be raffling off the majority of the center pieces. Each table will be individually styled with holiday decorations and lighting. Christmas music will be playing and refreshments will be served. Participants will vote on their favorite tables and the top three winners will receive awards. This event is open for the entire family. There is still room for anyone interested in entering a table. The cost is $5 to enter; with the entry fee comes with a raffle ticket. Those interested in participating or looking for more information can call the Pepperell Senior Center at 978-433-0326.


text:
EVERETT — Sheila Davis hadn't seen Special K, a striped gray tabby cat with a sweet disposition, since Memorial Day weekend 2012.
So when the Everett Animal Shelter gave the busy school bus driver a call last week, she couldn't believe what she was hearing. They'd found Special K.
"At first I was incredibly tentative because after two years, I've never heard of a cat coming back," Davis said. "My poor daughter, when I called and told her, she thought I was pulling her chain."
Taylor Davis, Sheila's 21-year-old daughter, loved the mild-mannered cat her family adopted in 2008. She was crushed when Special K disappeared in 2012. Since then, the family had moved from Marysville to Everett and given up on seeing their pet again.
"She's the most laid-back, easygoing cat," Sheila Davis said. "To have her come back is actually a blessing, and if she could talk, I'd love to know where she's been the past two years."
A Marysville resident found Special K wandering and brought her to the Everett Animal Shelter, shelter director Shannon Johnson said. Staff checked the cat for a microchip and discovered that the friendly tabby had been adopted from the Everett Animal Shelter nearly six years ago. The shelter microchips every animal that gets adopted, Johnson said, and Special K's chip led them to Davis.
"She was pretty hysterically happy when she found out we had her cat," Johnson said.
Already this month, the shelter has either adopted or reunited 111 animals with families, she said. That number will feed into a summer-long goal of more than 1,600 adoptions and reunions as the Everett Animal Shelter competes to win $100,000.
The shelter is one of 50 organizations around the country participating in the American Society for the Prevention of Cruelty to Animals Rachael Ray $100K Challenge. In its fifth year, the competition challenges shelters to top previous summer records for adopting out cats and dogs. This is the Everett Animal Shelter's first time competing, and the staff and volunteers will need to find homes for more than 1,600 cats and dogs by Aug. 31 in order to qualify for the $100,000 grand prize.
That's double last year's summer adoption numbers, Johnson said.
The city plans to use the prize money to create a program for low-income families to spay and neuter their pets, said Meghan Pembroke, a city of Everett spokeswoman. Johnson said the shelter also could pay for free vaccination clinics or microchipping.
Throughout the summer, the shelter will host fairy-tale-themed weekend events, such as a Rapunzel adoption day with a discount on long-haired animals and a wizard-themed adoption day with a free magic show, Pembroke said.
The shelter, which serves all of Snohomish County and has contracts with a number of nearby cities, relies on 15 paid staff and 300 regular volunteers for day-to-day operations, Johnson said. As of noon Monday, the shelter housed 125 animals.
Kari Bray: 425-339-3439, firstname.lastname@example.com.
Talk to us
- You can tell us about news and ask us about our journalism by emailing firstname.lastname@example.com or by calling 425-339-3428.
- If you have an opinion you wish to share for publication, send a letter to the editor to email@example.com or by regular mail to The Daily Herald, Letters, P.O. Box 930, Everett, WA 98206.
- More contact information is here.


text:
Gerig, Sebastian (1839-1924)
Sebastian Gerig, bishop of the Sugar Creek Mennonite Church (MC), Wayland, Iowa, from 1879 to 1924, was born in Pfastatt, Alsace, the son of Jakob and Elisabeth (Zimmermann) Gerig. He united with the Amish Mennonite Church in France at the age of 17, and in 1856 immigrated to America to escape compulsory military service. After spending a few weeks in Ontario he traveled to Iowa, living in Davis and Lee counties for six years and in Ohio approximately two years. After his marriage to Magdalena, youngest daughter of Bishop Joseph Goldsmith he established his home in Henry County, Iowa, where he lived the rest of his life. To this union were born twelve children, all of whom became members of his church. Three of his grandsons were in the ministry of the Mennonite Church (MC): Vernon Gerig, Wayland, Iowa; Willard Leichty, Wayland, Iowa; and Maynard Wyse, Archbold, Ohio.
Gerig was ordained to the ministry in the Sugar Creek Amish Mennonite Church in 1869 and ten years later to the office of bishop, In 1916 he ordained his successor Simon Gingerich. Gerig was a leader in the Western District Amish Mennonite Conference, serving either as moderator or assistant moderator in 1897, 1900, 1904, 1905, 1906, 1908, and 1909. A man of sound judgment and keen insight, he led his congregation through the changes brought about by the introduction of Sunday schools, young people's meetings, evangelistic services, and the English language.
Gospel Herald (17 April 1924): 63.
|Olive G Wyse
|Date Published
Cite This Article
MLA style
Wyse, Olive G. "Gerig, Sebastian (1839-1924)." Global Anabaptist Mennonite Encyclopedia Online. 1956. Web. 13 Jul 2020. https://gameo.org/index.php?title=Gerig,_Sebastian_(1839-1924)&oldid=141129.
APA style
Wyse, Olive G. (1956). Gerig, Sebastian (1839-1924). Global Anabaptist Mennonite Encyclopedia Online. Retrieved 13 July 2020, from https://gameo.org/index.php?title=Gerig,_Sebastian_(1839-1924)&oldid=141129.
Adapted by permission of Herald Press, Harrisonburg, Virginia, from Mennonite Encyclopedia, Vol. 2, pp. 480-481. All rights reserved.
©1996-2020 by the Global Anabaptist Mennonite Encyclopedia Online. All rights reserved.


text:
I had my baby shower this past weekend! It was truly a wonderful (yet exhausting) day. I'll share all the food with you today then in the next couple posts, I'll share a couple recipes that I made. On the table were also painted wooden frames with copies of sonogram pictures of my little boy from the gestational age of 10-28 weeks. This was my favorite addition to the table.
Here is all the food:
Everything at the shower was homemade by either my mother, my mother-in-law or myself. It was all delicious but this cake was bakery made. It's my all-time favorite cake- Chocolate Italian Cream with chocolate cream cheese frosting and it's just amazing. Oh what I wouldn't do to get my hands on that recipe!
Not everyone that came to the shower liked coconut or pecans (or had allergies) so I also made a vanilla bean bundt cake with strawberries as well. I put it on my Jadeite cake pedestal that I bought on the day I found out I was pregnant with this little guy :-)
These are the adorable napkins that I bought from a local hardware store. I love that they look like onesies and that they stand up. I think people were afraid to use them, so I had a lot left over.
We had limeade punch with a frozen ring of limes and cherries. My mother-in-law said she couldn't find frozen limeade, so she used frozen margarita concentrate (non-alcoholic) instead and I thought it was pretty good!
We had ham and asparagus roll-ups- blanched asparagus wrapped up in deli ham with a schmear of Boursin cheese in between. These make great appetizers in you cut them into bite sized pieces.
These are sausage balls and chunks of fresh pineapple turned into kabobs. This is a spin on bacon wrapped pineapple- also very delicious!
A veggie and cheese tray with homemade Ranch dressing. All that was missing were the cucumber slices that were accidentally left at home.
Deviled eggs- never get tired of these!
Strawberries with Romanoff sauce. Seriously love this stuff!
I made mini cheesecakes but wasn't entirely thrilled with the way they looked. They turned out quite tasty but they sunk in the middle and the recipe made way more than stated. So I had to improvise and made the rest of the batter into Oreo cheesecakes (on the bottom). The plain ones on top were topped with lemon curd and fresh berries. Those got rave reviews but I didn't get to taste them since they disappeared so fast!
For some color for the table I took Hershey miniatures and wrapped them in strips of coordinating scrapbook paper. I think they turned out pretty cute.
Of course our hairy daughter, Autumn, was there. And she took the liberty to sit on the couch since it was vacant and no one else would sit there!
Mr. h and I next to some beautiful orange roses a friend dropped by. I am 29 weeks, 3 days pregnant in this picture.
And these were the favors I made for the shower- powdered sugar coated buttery pecan cookies. These were so good and just melt in your mouth. The recipe came from my neighbor and I will share those with you next week as well.
All in all, it was a wonderful day and we were more than blessed by our friends and our family. Thank you to all who played a part in making our day so special!


text:
The Innkeeper's Daughter is a rare artifact from the Dwarf branch of Archaeology. You must have at least 150 skill points in Archaeology before you even have the chance of seeing the project.
You will need to gather 150 x (or less if you use up to three Dwarf Archaeology Fragment) in order to solve the project. Dwarf Rune Stone
Excluding the spirit that can sometimes spawn after using it, the item functions exactly like a hearthstone. (Although you will have to use Blizzard's Item Restoration service if you destroy it, whereas a replacement Hearthstone may be acquired from any innkeeper NPC.)
- Both items have a 10-second cast time and can be used in combat.
- Both items share a cooldown.
- Both items bind you to the same location. You cannot set different inns.
- Both items have their cooldown reduced by the
level 8guild perk, . Hasty Hearth
The spirit itself is a vanity pet, meaning that summoning another vanity pet will cause her to despawn. She will also despawn if you perform any action that requires the client to use a zone loading screen (like teleporting to a battleground). She was hotfixed during Cataclysm so that she could not be targeted by healing or harmful effects. The item itself was changed in Mists of Pandaria so it cannot be sold to vendors.
Interestingly, the spirit of Keelin Stonekeeper - a.k.a. The Innkeeper's Daughter - shares the exact same appearance with Thaegra Tillstone.


text:
Sleeping is one of the many essentials in our daily life. Anxiousness, exhaustion, worries or just simply thinking about tedious task on work can be few a factors that can affect our sleep. In the video below, I would like to share this simple method of falling asleep fast and easy.
This method works most of the time, and if that does not work for you, don't worry. You need to modify it and experiment with it until it works for you. I don't always fall asleep myself using this method, but I know it works for me and many other people, who left their comments to prove it.
If you are looking for guided meditation and hypnosis, which is really good, watch these videos that will take you from fully awaken to fully asleep in 10-15 minutes or less:
Sweet dreams 🙂
Related Articles:


text:
A nebulizer is a device used to deliver liquid medicine in the
form of a fine mist (aerosol) or powder. Medicine may be given through a
nebulizer to treat respiratory problems, such as asthma, chronic obstructive
pulmonary disease (COPD), or pneumonia.
The nebulizer allows the medicine to go directly to a person's
airways and lungs, and the medicine can be given over a long period of time.
The person inhales the medicine while breathing normally through a mouthpiece
or face mask. A nebulizer makes inhaling medicine easier for people who are
having serious difficulty breathing or who have trouble using an inhaler, which
requires careful timing and control of one's breathing.
Last Revised:
March 17, 2011
Healthwise Staff
Medical Review:
E. Gregory Thompson, MD - Internal Medicine & Lora J. Stewart
This information does not replace the advice of a doctor. Healthwise, Incorporated disclaims any warranty or liability for your use of this information. Your use of this information means that you agree to the Terms of Use. How this information was developed to help you make better health decisions.
To learn more visit Healthwise.org
© 1995-2012 Healthwise, Incorporated. Healthwise, Healthwise for every health decision, and the Healthwise logo are trademarks of Healthwise, Incorporated.


text:
The men's basketball ushers (Event Staff) had their preseason meeting on Tuesday night, and we got to wander around Crisler Arena afterwards. Only part of it is open to walk through; the rest is still a construction zone, with only 15 days until the first game. The part of the outer concourse we saw was gorgeous. It looks like a whole new arena. I can't wait to see the rest of it, including the escalators and the waterfall.
Here are the photos I took.
Go Blue!