Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipse.org-committers] News from the Projects

***************************************************
*                                                 *
*  News From The Projects Side Of The Foundation  *
*                                                 *
***************************************************

Greetings Committers,

A few bits of news from the Directorate of Committers.

1. Project meta-data and reminder emails
2. Standard project information pages
  and the required left menu item
3. Keeping track of official development process changes
4. Seeking input on a standard project plan format

1. Project meta-data and reminder emails
========================================

The portal (http://portal.eclipse.org/) has a database of meta-data about
each project. Information like the download page, the mailing lists, the
planned and completed releases, etc.

This information helps drive the eclipse.org website (e.g., the mailing
lists page comes from the project meta-data, as does the time line). Thus
each project is required to keep this information up-to-date. To assist
you with this task, we've started enabling reminders (a.k.a. nag emails)
when your project meta-data is missing or out of date. You've probably
already seen some of these emails on your dev lists and there will be more.

Of course, you can avoid reminders by using the portal to update your
project meta-data. You could even do it now!

2. Standard project information pages
=====================================
https://bugs.eclipse.org/bugs/show_bug.cgi?id=207176

One of the things the project meta-data drives is the new standard project
information pages, e.g., http://www.eclipse.org/projects/project_summary.php?projectid=technology.dash
The goal of these pages is to have a standard format for basic project
information (downloads, mailing lists, source code location, etc) to
enable new people to find this information easily. We want to avoid the
"every project has a different home page layout" problem, while at the
same time avoiding the "we tell you what your home page must look like"
problem. Thus two pages: your project home page under your complete control
and the standard project information page generated from the meta-data.

2.1 The required left menu item
===============================

The standard project information pages replace the unloved previously
required standard left menu. Most projects just ignored the standard
left menu directive from the Board so, facing reality, we gave up and
switched to the standard project information page.  HOWEVER, projects
are required to have a single left menu item at the top of their project
home page left menu. This single required menu item will point to the
project's standard information page and thus will allow anyone to
navigate from any project home page to that project's standard information.

Please see the (now even easier than ever before) instructions for
implementing that *required* standard left menu item:
http://www.eclipse.org/projects/dev_process/project-status-infrastructure/left-menu.php

3. Keeping track of official development process changes
========================================================
https://bugs.eclipse.org/bugs/show_bug.cgi?id=206987

The Eclipse Development Process does not change very often (well, we
correct typos all the time, but the essence of the process changes
very slowly). If you'd like to keep up with the changes (both the
typos and the slow major changes), you can view them here:
http://www.eclipse.org/projects/whatsnew.php
or subscribe to the RSS feed:
http://www.eclipse.org/projects/dev-process-changes-atom.php

4. Seeking input on a standard project plan format
==================================================
https://bugs.eclipse.org/bugs/show_bug.cgi?id=215301

As part of our continuing effort to increase the available information
about the projects, the EMO and the Board would like to have a standard
machine readable project plan format. Rather than just dictating a format,
we've opened bug 215301 to gather your thoughts and ideas about the format.
Should it be XML? Should it use bugzilla? We'd like to roll out the
standard format in time for you all to be able to use it for your 2008-2009
annual plans.

That's all for now...


Back to the top