PatternForge:Community Portal

From PatternForge

Jump to: navigation, search

This page is for planning the Pattern Forge site. Please add action items following the template, and/or add yourself as prime on any one of the items. The initial list is based on our discussion at EuroPLoP.

Contents

[edit] Availability

Who is available when? Please enter in the following table, when you will be around to help over the summer.

Name Dates
Michael not July 28 - Aug 12
Aliaksandr not Aug 1 - Aug 10
limited availability since 14 Aug till 22 Dec (Internship at CMU)
Name Dates

[edit] Content

Collecting, creating and presenting content. This includes a number of sub-items:

[edit] Profiles in Wiki

Enter your profile under People Behind this Repository.

Prime: All

[edit] Organization

About us? How different from Profiles in Wiki?

Prime: ?

[edit] Initial Pattern Format

Experiment with different formats for capturing patterns for our initial prototype. One proposal is the way the Patterns Almanac does it, the post-it cards we used at EuroPLoP suggest another. Note that this will be the format for the initial version of our pattern repository only, which we will use to document patterns from EuroPLoP. Future versions, not necessarily based on a Wiki but based on metadata, will be quite a bit more elaborate.

Prime: All

Michael notes:

  • During our discussion we agreed on using the short form for describing patterns or Patlets. However, there are still different ways to do this, and we should strive for a minimal but expressive format.
  • Does anyone know if there is a way to refer to sections on a MediaWiki page from a wiki link? Then, we could keep all patlets of one collection on the same page (more compact than separate pages).
  • However, by keeping all patlets from one collection on the same page, it may be difficult to tag them individually.

Aliaksandr's comments:

  • Can't we support different pattern formats? I am a fan of standardizing everything, and in the beginning I was really supporting the idea of the use of PLML-like format for all patterns, but having known more patterns, I would say that some of them look better in different formats. If I am not mistaken, Diethelm also mentioned something similar to this during the focus group.
  • On the other hand, Patlet format seems to capture all essential parts of any pattern and could be a good starting point.

Michael replies:

  • Agreed. I remember that we discussed supporting multiple format. However, here we are just talking about the initial format to use to get us started.

[edit] 50 Patterns from EuroPLoP

Enter a subset of the patterns from EuroPLoP 2007 as a proof of concept. Patterns should be documented in patlet form (also see Initial Pattern Format), and links between patterns should be stated.

Prime: All

Aliaksandr's questions:

  • Can we enter extended versions of EuroPLoP 2006 patterns (those after review)?
  • [cancelled] It seems that we also need a kind of "stub" concept - to use for those patterns currently absent in the repository (e.g. someone from EuroPLoP may refer to GoF patterns)[cancelled] - having experimented with adding patterns I admit that having links that propose add not-yet-existing patterns (i.e. ...action=edit links) is enough

[edit] License

Select a license for the repository content.

Prime: Christian, Michael

[edit] Patterns Almanac

Leon to provide FrameMaker version of the Patterns Almanac.

Prime: Leon

[edit] Wiki Gnome

Refactor wiki, clean up, make things run smoothly. The role is described in WikiGnome.

Prime: Andreas

[edit] Pattern Metadata

Define metadata for patterns and pattern languages. Describe existing efforts such as PLML-X, and tagging approach in Milos and Ondrej's system.

Prime: Diethelm, Milos

[edit] Focus Group Summary

Summarize the results of the focus group and subsequent BOF.

Prime: Michael, Aliaksandr

Michael notes:

  • There were two sets of results (socio-economic vs technical issues), and two overlapping groups interested in these issues. Our initial focus will be on community building and technical issues.

Aliaksandr notes:

Christian, could you upload also your images?

[edit] Schedule

Item Prime Due Date Complete
Profiles in Wiki All Jul 13 no
Organization  ?  ? no
Initial Pattern Format All Jul 27 YES
50 Patterns from EuroPLoP All Aug 17 no
License Christian, Michael Jul 27 no
Pattern Almanac Leon Aug 31 no
Metadata Diethelm, Milos Aug 17 no
Focus Group Summary Michael, Aliaksandr Jul 15 no

[edit] Brand

[edit] Advertising

Spreading the word about the repository.

Prime: Birgit

[edit] VikingPLoP Success Story

Get VikingPLoP participants to enter their patterns into the repository, and to tag them. A precondition for this action item is that we have documented 50 patterns from EuroPLoP as a proof of concept.

Prime: Michael (to contact organizers)

[edit] Schedule

Item Prime Due Date Complete
Advertising Birgit Aug 31 no
VikingPLoP Success Story Michael and others Aug 17 no

[edit] Tools

[edit] Restricted Access to MediaWiki

Required login to wiki to allow us to trace contributions.

Prime: Michael

Completed by Michael:

  • Account creation is not restricted, but users need to be logged in now before they can make edits.

[edit] Script Exchange

Platform for exchanging scripts and simple tools (eg scripts to extract patterns from existing repositories such as the Patterns Almanac). This is a precusor to creating an open source project for a joint pattern repository tool.

Prime: Michael

[edit] Integration with IDE

Demonstrate integration of repository with IDE. Christian has done work on an Eclipse plugin.

Prime: Christian

[edit] Social Tagging Plugin

Select Social Tagging Plugin for MediaWiki.

Prime: Christian (I just volunteered you), Michael

Michael notes:

Michael writes:

  • Simple tagging mechanisms implemented using Orange Dino plugin. To tag a pattern simply add a wiki category.

[edit] Regular Backup of Repository

Figure out how we can dump the wiki database at regular intervals, and keep a copy at another site.

Prime: Michael, Andreas

[edit] Describe Existing Tools

Describe our existing systems. The vision is that we can link our efforts either in terms of tools or tool components, or in terms of concepts. This goal needs to be elaborated on.

Michael notes:

  • As we had discussed, our initial focus will be on creating a first success story. This is more of an exercise of aligning the members of this group, rather than of building a sophisticated tool.

Prime: All

[edit] Captchas

Prevent spambots from creating accounts. Although it hadn't been on top of my list, this became quite urgent one month into the life of the site, spammers started to hit the wiki and create accounts.

Prime: Michael

Michael notes:

  • A simple to install captcha generator is reCAPTCHA. It is also quite neat as it creates captchas from words scanned in from old books that are being archived for the Internet Archive.

[edit] Support for BibTeX

Support bibliographies in BibTeX formst.

Prime: Michael, Yann-Gael

Michael notes:

  • Installed a BibTeX extension. It renders BibTeX references in HTML.
  • Still need to figure out how to best link to a reference (eg by creating anchors on wiki page).

[edit] Schedule

Item Prime Due Date Complete
Restricted Access to MediaWiki Michael Jul 13 YES
Script Exchange Michael Jul 27 no
Integration with IDE Christian Aug 31 no
Social Tagging Plugin Christian, Michael Jul 27 YES
Regular Backup of Repository Michael, Andreas Jul 27 no
Describe Existing Systems All Aug 31 no
Captchas Michael Aug 16 YES
Support for BibTeX Michael Aug 17 YES
Personal tools