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

Bug 204011

Summary:	Improved project-info meta-data component
Product:	Community	Reporter:	Bjorn Freeman-Benson <bjorn.freeman-benson>
Component:	Project Management & Portal	Assignee:	Portal Bugzilla Dummy Inbox <portal-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	nathan, nboldt
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:
Bug Blocks:	204725

Description Bjorn Freeman-Benson

2007-09-19 13:00:57 EDT

The initial project-info meta-data component is functional, but not very user friendly. This bug is a note to ourselves to improve the ui as follows:
* allow all committers to edit the meta-data (move to project-committers component)
* have a web-form style user interface (a la contact address) rather than a one-field-at-a-time style user interface. This will require some interesting design to get the long fields to fit into our current form design. And to get the multi-input fields to fit. But I'm sure we can come up with something.

Comment 1 Bjorn Freeman-Benson

2007-09-24 17:23:06 EDT

Comment from Nathan:
One thing that i've noticed is that a lot of the data that was imported from
the project-info.xml files isnt standardized.  Projects have been left to there
own idea of what goes into each field.  Two of the biggest problem fields I
encounter this with are the projectname and projectshortname fields.

Some projects have the project name and short name included in the projectname
field.  

BIRT->projectname = "Business and Intelligence Reporting Tools (BIRT)"
eRCP->projectname = "ERCP - Embedded Rich Client Platform"

For my category pages, and the projects page resolving this type of data issue
would help make our pages look more professional. 

Obviously the best place to affect this change is to put examples or details of
what we're looking for in a field in the Portal component.  Some work will need
to be done on defining what kinds of information were looking for in each
field.  But i'm sure standarizing this information will have benefit to the
projects and the pages we display their information on.

Comment 2 Nick Boldt

2007-09-26 16:25:32 EDT

Nathan:

How is that possible? The project-info.xml file is a standard format file, with VERY strict rules for content and schema. Shouldn't a db import be oh-so-very obvious, given the schema is so strict?

Comment 3 Nathan Gervais

2007-09-26 16:52:00 EDT

(In reply to comment #2)
> Nathan:
> 
> How is that possible? The project-info.xml file is a standard format file, with
> VERY strict rules for content and schema. Shouldn't a db import be oh-so-very
> obvious, given the schema is so strict?
> 

I'm not going to debate that the items should all be correctly described but the data that is in the database is what was imported from the project's projectinfo.xml.  It was the data in the project-info.xml files that is no standardized

Comment 4 Bjorn Freeman-Benson

2007-09-26 16:54:15 EDT

(In reply to comment #2)
> How is that possible? The project-info.xml file is a standard format file, with
> VERY strict rules for content and schema. 

Many people did not follow the strict scheme and content rules. That, in fact, was one reason to switch to a database for this data.

P.S. Ward and Gabe are actively working on this bug to provide a better user interface.

Comment 5 Gabé

2007-09-28 18:28:33 EDT

Now all project committers have the ability to edit meta data for a project.
The revert button could be made better in the case where you are editing a field.  Right now it takes you all the way back to the committer overview instead of back to the meta data questionnaire.

This is in the code, but will not be live till the next release.

gO'

Comment 6 Bjorn Freeman-Benson

2007-09-29 13:39:43 EDT

Fixed the "revert takes you all the way back" problem.
Fixed another problem with duplicate header lines.

Comment 7 Denis Roy

2007-10-01 09:37:54 EDT

Released