Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 347037

Summary:	What are project "status summaries"?
Product:	Community	Reporter:	David Williams <david_williams>
Component:	Project Management & Portal	Assignee:	Portal Bugzilla Dummy Inbox <portal-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description David Williams

2011-05-24 14:21:27 EDT

At this page, about project meta-data, 

http://wiki.eclipse.org/Development_Resources/HOWTO/Project_Meta-Data

I found this sentence: 

"Status summaries must be updated at least once a quarter. It's better to update them once a month. "

I first thought maybe there was some field or URL in the Portal meta-data that projects are supposed to update ... but, I could not find it. 

Am I missing it? Or does "status summaries" just refer to the whole general collection of all the metadata? Such as you'd see from the "about this project" pages, for example 

http://www.eclipse.org/projects/project_summary.php?projectid=webtools

It does after all say "summary" in the URL :) 

If there is not specific field, that's fine, but the wording in the "how to" might be improved with a parenthetical remark, perhaps 

"Status summaries (the collection of all meta-data) must be updated at least once a quarter. It's better to update them once a month. "

If there is a specific field, perhaps its name could be mentioned? Or ... maybe I'm just missing it in my reading of the metadata page?

Comment 1 David Williams

2011-05-25 11:56:53 EDT

BTW, I noticed this, or was "lead to it" while reviewing some up-coming changes to dev. process ... reading 

http://eclipse.org/projects/dev_process/development_process_2011.php?commentary

And there say "All projects are required to report their status at least quarterly using the EMO defined status reporting procedures." 

It didn't looked marked as "new", but I didn't recall seeing/hearing about it before, so followed the link in that sentence to the "how to" ... and, there, found it sort of vague. 

So, my main questions I guess could be said to be, is this a new requirement? Is there something specific type of status to report quarterly? Or does the dev. process statement just mean, basically, keep metadata up to date?

Comment 2 Wayne Beaton

2011-05-25 11:59:26 EDT

Pragamatically speaking, it's the latter: keep your project metadata up to date. That entry has been there for as long as I can remember.

Comment 3 Wayne Beaton

2011-12-14 21:40:14 EST

The discussion of status summaries looks like a holdover from when project metadata was stored in files. I've updated the entries.