RE: [eclipse.org-eclipsecon-program-committee] If you *add* any tags to

["Scott Rosenbaum" <scottr@xxxxxxxxxxxxxxxxxxxxx>]

I would have a strong preference to be able to do it all in the submission
system and not have to keep things in two places, e.g. spread-sheets and the
system. 

My opinion is that it is better to have a two tier system.  Tier 1 is a
coarse grain based on categories (like this years tags), which basically
represent how we split up the talks for evaluation, scheduling, and
allocation.  

I think the second layer should be tags which are fine grain and can be help
to add a layer of meta information about the talks that we can use to make
sure we have good coverage.  In the tags we would have specific Eclipse
project names, and technologies e.g. JPA or M2M.

That way we can manage across the entire committee at the category level,
but the individuals within a category can use the tags to balance their
content.

Scott


-----Original Message-----
From: eclipse.org-eclipsecon-program-committee-bounces@xxxxxxxxxxx
[mailto:eclipse.org-eclipsecon-program-committee-bounces@xxxxxxxxxxx] On
Behalf Of Oisin Hurley
Sent: Monday, January 04, 2010 9:30 AM
To: Eclipsecon Program Committee list
Subject: Re: [eclipse.org-eclipsecon-program-committee] If you *add* any
tags to a talk...

> Building a work flow for the conference site in the future would be a big
> help.

I'm already collecting 'lessons learned' and scribbling a decent workflow
for this tagging approach for future reference, should the 2011 gig decide
to go tagging again. No point in changing horses in mid-stream, so I'll
keep it until afer the program is announced and we can relax ;)

 --oh
_______________________________________________
eclipse.org-eclipsecon-program-committee mailing list
eclipse.org-eclipsecon-program-committee@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-eclipsecon-program-comm
ittee