Thursday, November 22, 2018
Text Size

Site Search

  • SugarLoaf PLoP

    SugarLoaf PLoP

    SugarLoafPLoP'2018 Huaso Edition will be held on one of the campuses of Universidad Técnica Federico Santa María (UTFSM) in Valparaísr, Chile between November 20th and 23rd, 2018. SugarLoafPLoP is the premier Latin American Conference onPattern Languages of Programs. This is the twelfth SugarLoafPLoP conference and the first time that the SugarLoaf PLoP conference has been held in Chile. Read the full story Read More
  • 1

The Hillside Mission

The mission of the Hillside Group is to improve the quality of life and society as a whole. This includes architects, developers, managers, owners, workers, educators, students, and more. Understanding and helping the human element is critical for achieving success. The Hillside Group believes in making processes and design more humane by paying attention to real people and existing practices.

The Hillside Group promotes the use of patterns and pattern languages to record, analyze, and share knowledge to help achieve its mission. The Hillside Group sponsors a variety of activities to achieve this mission—organizing workshops, hosting PLoP (pattern) conferences, and producing publications for discussing, recording, and documenting successful practices.

The Hillside Group supports many different conferences such as: PLoP, EuroPLoP, AsianPLoP, VikingPLoP, SugarLoafPLoP, and ChiliPLoP. These conferences focus on writing groups to better improve patterns through group exposure. Each conference offers advanced topics for the more adept pattern writers. Participants have the opportunity to refine and extend their patterns with help from knowledgeable and sympathetic patterns enthusiasts.

Pattern Books

The Design Patterns Book Series showcases many patterns from PLoP conferences and leading experts in the patterns field.

See our Pattern Book Library filled with over 80 Pattern related books.

Patterns Resources

This letter was used as a suggested template for the one Shepherds use to introduce themselves to their authors and to introduce the shepherding process. Also see Shepherd Letter Bobby and Shepherd Letter David.

Dear PLoP Submitter:

Thank you for taking the risk of submitting your work to PLoP '98. We hope that your experience of having your paper reviewed for PLoP will be different from your experience with other conferences or publications. I have been assigned to your paper as a "shepherd". I have two primary responsibilities:

  1. Helping you improve your submission
2. Voting whether your submission meets PLoP's criteria for being
workshoped at the conference

Both activities go hand in hand. We're going to have several iterations over your paper where my job is to suggest you changes for improvement. Of course, it's your own decision, whether you'd like to incorporate the changes or not. However, experience shows that most remarks lead to some changes in the document--future readers will have more benefit from a clarification in the document than I will have if you explain the topic to me only. We have eigth weeks to work on the paper. We should use this time as well as we can.

During this shepherding, I collaborate with a member of the program committee. That person's job is to support me if I feel the need for a second vote. Please CC the program committee member on every mail you send to me.

Please make sure that our e-mail connection works. We're going to have a lot of traffic and a broken e-mail connection is about the worst things that can happen during this project.

After the shepherding period, I'm going to send the latest version of your paper (the "version for voting") to the program committee together with my vote on whether the paper is suitable for participation ion a writers' workshop.

However, my vote is not the only one. A second member of the program committee will vote on the version for vote independently from my vote. Depending on both votes the chairs will finally decide for acceptance. If your paper is accepted you have time to prepare the version that is going to be workshoped at the conference.

This may seem quite complicated, but I'll support you to track the dates and take care that you don't miss any deadline.

Please consult the shepherding guidelines page:

    http://st-www.cs.uiuc.ed ... shepherding.html

for more information on the shepherding process.

contents of this page originally posted on

This letter was used as a suggested template for the one Shepherds use to introduce themselves to their authors and to introduce the shepherding process. Also see Shepherd Letter Steve and Shepherd Letter David.

Dear <author_contact_name>,

My name is <shepherd_name>. Thank you for submitting your paper, "<paper_title>," for PLoP '99. We're now beginning the shepherding process, and I will be your shepherd for this paper. What this means is that I will help you improve it prior to the conference so that you can present the best possible paper for comment at the conference. It is also up to me to decide whether or not your paper is good enough for the conference. It's in your best interest to use this opportunity to improve your paper as much as possible. People who make the most of this process will have the best chances of being accepted to the conference.

Assisting me in the shepherding process is a member of the conference's program committee, <pc_member_name>. He'll keep an eye on the progress we're making and help us if we need any. I'll CC him on all my mail to you; please do the same when you write me.

Here's the schedule for what's due when:

    Shepherding Recommendations Due    Fri, June 18, 1999
Notification of Acceptance Thu, July 1, 1999
Final Conference Copy Due Fri, July 16, 1999
Conference Dates August 15-18, 1999

So we have between today and June 18th to work on your paper. If I accept your paper, you'll have another chance to make changes to your final draft for the conference. It is then due by July 16th.

I will be contacting you within a few days with my initial comments on your paper. In the meantime, if you have any questions about the review process or the conference, feel free to contact me at <shepherd_email_or_phone>.

I look forward to working with you.


contents of this page originally posted on

The position of Program Chair is one with rewards and recognitions But to get to that point, there are a number of things that must get done.

  • Conference -1 year
  1. Work with Hillside and the Conference Chair to determine the dates of PLoP
  2. Any special plans that you might have for the conference that can change the usual number of days needs to be communicated and planned for. The facility might not be available, or the dates might have to shift slightly.
  3. Consult with the conference chair to make arragements for
    • special speakers/attendees
    • game-master
  • Conference -9 months
  1. Start serious work on the call for papers.
    • Will it be only Writers' Workshops, or will there be some other kind of activity. Does that other activity need a leader to self-volunteer (like a hot topic at ChiliPLoP, or a "focus group")? What are the parameters around the focus group that need to be advertised?
  1. Prepare the website and call for papers
    • The Hillside website needs to be updated to point people to the current year's conference.
    • The conference website should have enough information for a focus group/hot topic leader to know what they need to do to submit one.
  2. Begin looking for shepherds
    • An initial call for shephers has sometimes been done.
    • Discussing the shepherding season schedule with your peers at the other conferences that meet in the summer & fall can help avoid *everyone* needing shepherds at the same time.
  3. Assemble program committee
    • These folks can give advice & counsel about general topics.
    • Traditionally they "oversee" the shepherding process by looking over author's shoulders
    • They might be able to draw in attendees also
  • Conference - 8 months
  1. Send the call for papers to all the websites and journals of interest
  • Submission Deadline - 1 month
  1. Turn on the submission website
  2. Personal invitaitions to regulars/strong participants to encourage papers/attendance
  3. What is the conference going to look like? What special touches do *you* want to add to PLoP? Start thinking about this.
  4. Revise website.
    • Make sure dates are correct for shepherding schedule
    • Add any new thoughts about focus groups/hot topics
  5. Reminder call for papers (Since CFP/website has been modified)
  • Submission Deadline
  1. Begin Triage of papers
    • Are they patterns?
    • Are there too many from the same author?
    • Are they ready for shepherding?
  2. Announce shepherding start
    • Support shepherds collecting papers
    • request additional shepherds
    • assign shephards and PC members to papers
  3. Watch shepherding and handle any issues
  4. Define 99% correct schedule for the actual conference. The Conference chair will want this to help start logistics of events and meals.
  • Paper Acceptance Deadline
  1. Collect recommendations from shepherds and PC members for each paper
  2. Decide which papers (if any) to reject
  3. Start grouping patterns into workshop groups. Use whatever method makes the most sense to you. (In 1997 the "non-OO" workshop group had a Smalltalk pattern
  • Pre-Conference Paper Deadline
  1. Accept the revised papers that are ready for workshopping. Ensure that you have all the latest ones, since the Conference Chair is going to burn CDs
  2. Prepare the pre-conference paper website with workshop information so people know which papers to read
  3. Identify workshop group leaders
    • These are the people that will get the group started,
    • train the newbies on how to act in a Writer's Workshop,
    • act as the final arbiter of conflict in the workshop group,
    • lead any of your special initiatives that relate to workshop groups,
    • mentor other members of the workshop group in pattern writing and writers' workshop moderation/leadership style.
  • Conference - 3 weeks
  1. Advertise the pre-conference paper website
  2. Encourage people to read papers in advance
  3. Encourage registration
  4. Prepare final schedule
  5. Encourage workshop groups to start an email dialog
    • Some issues can be settled in advance, like paper order, basic introductions, etc.
  • Conference - 1 week
  1. Final reminders
  2. Do you have your own plane tickets?
  3. Are the workshop groups all set? leaders ready?
  4. papers still all set (any papers that need to be removed because of non-registration)?
  5. Arrange demo Writers' Workshop
  • Select pattern to workshop
  • Who will participate? (usually "old-heads" and workshop group leaders)
  • Who will fill what roles? (Need a traditional moderator AND a meta-moderator)
  • Conference
  1. Introduce the conference
  2. Introduce Writers' Workshops
  3. Introduce workshop process (demo)
  4. Handle problems as they arise

Set dates for the conference.

  • Joe Yoder and the Conference Chair will help with this.

Establish the PC members.

  • Don’t talk anyone into it. Rather, make sure each person is interested and excited about doing it (or he/she won’t be much help).

  • Put the Conference Chair on the PC.

  • Ask the past year’s Program Chair to be on the PC.

Get the web page going.

  • Even if you don’t have all the information, post a placeholder stating that more information is coming soon.

Include Dates for:

  • Conference registration

  • Paper submissions due

  • Shepherding begins

  • Shepherd recommendations due

  • Notification of acceptance to the authors

  • Conference drafts due

  • Registration deadline

Write the Call for Participation.

  • Think about what events you want in addition to the usual Writers’ Workshops (focus groups, BoFs, etc.)

Decide on a submission system (and make sure it is working).

  • Ask PC members and other friends to help test it.


  • The Conference Chair should work on this with help from Joe Yoder and with your input.

Plan the Special Activities, such as:

  • games

  • special “big name” speakers

  • evening events

  • etc.

Keep in touch with shepherds and authors throughout the shepherding!

  • Send regular “how is it going?” emails, with reminders, during shepherding.

Handle the papers when they start coming in.

  • Get shepherds (and PC members) assigned to papers. Allow at least two weeks for this, but better yet, start lining them up before the papers come in.

  • Remember sound guidelines when accepting papers for the conference.

Assign to writers workshops.

  • Get help/input from PC members when doing this.

  • Hillside Fellowship Award
  • PLoP 2018 in Portland
  • Security Patterns in Practice
  • PLoP Conference Proceedings

The Hillside Fellowship Award

Congratulations to Ralph Johnson and Richard Gabriel for being presented the first Hillside Fellowship award at the 2016 PLoP event at Allerton, PLoP 2016 .

Hilside Fellowship Award Recipients 2016

The Hillside Fellowship Program was established in 2016 to recognize members of The Hillside Group who have made exceptional contributions to the Hillside community and to the patterns community at large. The title of Hillside

Read More

PLoP™ 2018 in Portland, Oregon

Check out the main PLoP Website for more information and details!!!

Read More

Security Patterns in Practice

Eduardo Fernandez's new book " Security Patterns in Practice: Designing Secure Architectures with Software Patterns " has been published.


It is the result of 14 years of producing security patterns with students and colleagues. Almost all of these patterns went through PLoP, EuroPLoP, AsianPLoP, or SugarLoafPLoP. Many of you have participated as shepherds or workshop commentators, the book owes something to

Read More

PLoP Conference Proceedings

After the PLoP Workshops, writers are encouraged to modify their papers and submit a final version. The final versions are collected and submitted to the ACM Digital Library. The versions are also available from the conference website. 

Conference Proceedings (ACM Digital Library)

Some of the PLoP accepted papers have been published on the  ACM Digital Library . The program committee will

Read More


Learn More about Patterns


Important: PLoP® is a registered
    trademark of The Hillside Group.

© Copyright 1994 - 2018, All Rights Reserved

Login Form