Introducing The ASF’s New Logo Read Now

Board history: Graffito

ASF Oak Leaf Icon

Graffito

What the board has decided about this committee or office, and the reports it filed, most recent first. Generated from the published minutes.

These categorised views are best effort. They are read from the published minutes by a program, and what it can attribute to a committee depends on how each resolution happens to be worded — so a page may be incomplete, and nothing here overrides the minutes themselves. The raw minutes are the source of truth.

Please note. The board approves the minutes of a meeting at the meeting after it, and they are published then - so the most recent meeting is not usually here. ASF Members can read the draft in the board's own repository until it is.

[raw] the published minutes, which are the record. [main index]

Reports

2006-10-25 — in the Incubator's report

Graffito is a framework for content-based applications, especially in
portlet environments. Graffito entered incubation on September 20,
2004.

Top three items to resolve before graduation:

Upgrade to the latest license header and copyright notice policy

Create an incubating Graffito release

Move the JCR mapping component to the Jackrabbit project

Graffito activity has increased noticeably since the last report,
especially due to interest from within the Jackrabbit community. New
bug reports and patches are also being contributed.

Jukka Zitting was voted in as a new mentor for the project. He will
accompany Raphael Luta in that role.

Given positive feedback from both communities, we are evaluating
options for moving the JCR mapping component from Graffito into the
Jackrabbit project.  This would expose the component to a wider JCR
developer community and a larger audience of potential users.

There has been renewed discussion on producing incubating releases of
the Graffito components

Edgar Poce has been working on a related JCR-based wysiwyg portlet
prototype, using the Graffito mailing list for design discussions, but
the implementation approach differs from the Graffito portlet model,
so at least for now the tool is not being integrated into Graffito

2006-01-18 — in the Incubator's report

Graffito has nicely grown recently with activity encouraged by the final
release of Jetspeed 2.0 and good progress made on the JCR support though
Jackrabbit.

We've just added a new committer :

Alexandru Popescu

and some existing Portals committers also actively contributing to the
integration of Graffito with Portals.

2005-07-28 — in the Incubator's report

* The main news in this quarter is that we have expanded the committer
  base beyond the original contributors with the addition of Oliver
  Kiessler and Sandro Boehme.

* Both are busily working on building support for JCR (through
  Jackrabbit).

* Work is also underway to use Graffito as a native CMS engine
  in Jetspeed 2.

2005-04-27 — in the Incubator's report

1) Any legal, cross-project or personal issues that still need to be
   addressed?

no

2) What has been done for incubation since the last report?

* The most important work was made on the Jetspeed 2 integration &
  building some JSR-168 portlets. There is a content tree view, a
  document viewer and an admin browser portlet. Futhermore, we have
  integrate an HTML editor (Kupu).
* Some work has been done for the security management (fine grain
  access control, permission management, JAAS support, ...).
* We have started raising awareness and promoting the project on
  some other Apache and non-Apache lists in order build further
  the community.
* New developers have started collaborating with the core team
  on Graffito work, especially JCR mapping tools.

3) Plans and expectations for the next period?

* Implementing our JCR mapping framework with Jackrabbit.
* XML editor integration.
* A Graffito implementation for the Jetspeed 2 page manager.
* Continue our work on the JSR-168 portlets (search & version management).
* Start a site demo with a Jetspeed integration
* We expect the committer base to expand during next period given the
  current developer participation on the dev mailing-lists.

4) Any recommendations for how incubation could run more smoothly for
   you?

None so far.

2005-01-19 — in the Incubator's report

1) Is the STATUS file up to date?

   Yes

2) Any legal, cross-project or personal issues that still need to be
   addressed?

   * Software grant has been recieved by the ASF.
   * All trademark issues with project name have been resolved.
   * We have renamed the JCMS project as Graffito to avoid naming
     confusion with Jalios JCMS, another Java based CMS system.

3) What has been done for incubation since the last report?

   * We cleaned up repository, site, build process, site deployment
     and publishing to help new users and developers jump into the
     project.
   * Christophe Lombart account has been created and karma granted
   * ASF Infrastructure has been set up for Graffito
   * We are working on the Jetspeed 2 integration & building JSR 168
     portlets.

4) Plans and expectations for the next period?

   * Add more info in the Graffito site
   * WEBDAV integration
   * More work on Jetspeed 2 integration, building portlets.
   * Introduce Graffito to some important related projects:
       Slide, JackRabbit, Jetspeed ... in order to grow the
       development community

5) Any recommendations for how incubation could run more smoothly for
   you?

   None so far.

Subscribe to ASF Plus One, Our Monthly Newsletter

Subscribe Now