Difference between revisions of "DSDP/TM/Committer Phone Meeting 14-Nov-2006"

From Eclipsepedia

< DSDP‎ | TM
Jump to: navigation, search
Line 23: Line 23:
  
 
== Agenda ==
 
== Agenda ==
* Our top goals
+
* '''C'mon and celebrate!'''
** '''Grow the Communities''' - active users and adopters --> tutorial, docs, mailinglist help
+
** RSE 1.0 is released - what did we accomplish in the past year?
** '''Get the APIs Right''' --> enable public API discussion --> ISV docs, Wiki API discussion, [api] bugzilla's
+
*** Created infrastructure - project, website, wiki, mailing list, newsgroup, bugzilla, processes for everything
** Get our '''Processes''' in place --> JUnit, nightly builds, infocenter, update site
+
*** Got all the code through legal review, implemented nightly build system
* Latest News
+
*** Grew the community - contributors and users, 220 downloads on 1.0RC2; EclipseCon talk, upcoming tutorial
** Martin --
+
*** Refactored RSE (service/subsystem approach), implemented deferred queries
** DaveD --
+
*** Added ssh and ftp subsystems, discovery component
** DaveM --
+
** In the past year: What did you like? What did you dislike? What's the favorite thing you want to do next?
** Kushal --
+
*** DaveD:
** Javier --
+
*** DaveM:
** Ted --
+
*** Kushal:
** Uwe --  
+
*** Javier:
 +
*** Michael:
 +
*** Ted:
 +
*** Uwe:
 +
*** Martin:
 +
** Bug statistics - [http://www.eclipse.org/dsdp/tm/developmnet/bug_process.php Bug Process Page]
 +
** How do you like our processes? Improvements, Suggestions?
 +
*** Bugzilla: All have their personal queries?
 +
*** [[RSE 1.0 Testing]] - was the effort right? Especially verification
 +
* Any Latest News?
 
** Michael --
 
** Michael --
 
** Other News --
 
** Other News --
Line 41: Line 50:
 
** '''#2 - Continue fixing bugs and improving documentation''' - Let's make sure that users who have problems with 1.0 can get a subsequent I-build as patch soon after. Let's make sure users get missing documentation wherever needed. Instead of answering a question by E-Mail, let's fix the corresponding documentation or FAQ and point the users to it.
 
** '''#2 - Continue fixing bugs and improving documentation''' - Let's make sure that users who have problems with 1.0 can get a subsequent I-build as patch soon after. Let's make sure users get missing documentation wherever needed. Instead of answering a question by E-Mail, let's fix the corresponding documentation or FAQ and point the users to it.
 
** '''#3 - Plan RSE 2.0'''
 
** '''#3 - Plan RSE 2.0'''
* Looking back on RSE 1.0
 
** Download statistics
 
** Bug statistics - [http://www.eclipse.org/dsdp/tm/developmnet/bug_process.php Bug Process Page]
 
** User Statistics
 
** How do you like our processes? Improvements, Suggestions?
 
*** Bugzilla: All have their personal queries?
 
*** Bugzilla: When fixing a bug, please add a short note where it was fixed, e.g. "Fixed in DStoreRemoteFile". This helps tremendously to find and understand the fix, in case it should be needed again later
 
*** [[RSE 1.0 Testing]] - was the effort right? Especially verification
 
 
* Upcoming Work
 
* Upcoming Work
 
** Start IBM and EMO review process for User Actions and Import/Export (DaveD)
 
** Start IBM and EMO review process for User Actions and Import/Export (DaveD)
 
** Start creating Unit Tests, Testing feature (DaveD, Uwe)
 
** Start creating Unit Tests, Testing feature (DaveD, Uwe)
 
** Continue bug fixing on HEAD (All)
 
** Continue bug fixing on HEAD (All)
 +
*** Look at your personal bugs and assign target milestones: What can you fix for 1.0.1? What can you fix for 2.0? For anything yet unknown, keep the open milestone "---"
 +
*** Bugzilla: When fixing a bug, please add a short note where it was fixed, e.g. "Fixed in DStoreRemoteFile". This helps tremendously to find and understand the fix, in case it should be needed again later
 
** Fix compiler warnings (Kushal) - prepare for running FindBugs
 
** Fix compiler warnings (Kushal) - prepare for running FindBugs
 
** Add ISV Javadoc where it is still missing or incorrect; review, and improve all docs
 
** Add ISV Javadoc where it is still missing or incorrect; review, and improve all docs
 
** [[RSE 2.0 Planning]] - Finalize the 2.0 Project Plan
 
** [[RSE 2.0 Planning]] - Finalize the 2.0 Project Plan
** Think about limiting the API:
 
*** Make APIs internal
 
*** Along the way of updating documentation, and making Unit tests, we'll see some API we want "internal"
 
*** We should DOCUMENT these for now and DO it soon after 1.0.1
 
 
** '''New bugs''': REVIEW [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&component=RSE&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=exact&email1=dsdp.tm.rse-inbox%40eclipse.org&cmdtype=doit Assigned to Inbox], [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&component=RSE&bug_status=NEW&cmdtype=doit Status NEW]
 
** '''New bugs''': REVIEW [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&component=RSE&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=exact&email1=dsdp.tm.rse-inbox%40eclipse.org&cmdtype=doit Assigned to Inbox], [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&component=RSE&bug_status=NEW&cmdtype=doit Status NEW]
 
*** Open bugs: [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&component=RSE&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&priority=P2&cmdtype=doit P1, P2 bugs], [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=%5Bapi&classification=DSDP&product=Target+Management&component=RSE&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit API bugs], [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&component=RSE&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit&field0-0-0=attachments.ispatch&type0-0-0=equals&value0-0-0=1 Open with Patch],
 
*** Open bugs: [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&component=RSE&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&priority=P2&cmdtype=doit P1, P2 bugs], [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=%5Bapi&classification=DSDP&product=Target+Management&component=RSE&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit API bugs], [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&component=RSE&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit&field0-0-0=attachments.ispatch&type0-0-0=equals&value0-0-0=1 Open with Patch],

Revision as of 10:29, 13 November 2006

Meeting Title: TM Committer Phone Meeting
Date & Time: Tuesday Nov 14, 2006 at 8am SFO / 10.00am Rochester / 11.00pm Toronto / 4pm London / 5pm Salzburg
Dial-in: International +44 (0)1452 567588
North America +1 (866) 6161738 (toll free)
UK National 08712460713
Passcode: 0587322148 #

MartinO to start conference call - please dial in using the numbers above.
Please be available for Skype Chat in parallel to the call. MartinO will start Skype chat just prior to call.
Skype fallback dial-in - only if less than 5 participants: martin.oberhuber, ddykstal (or david_dykstal), david-k-mcknight, kushal.munir, javier.montalvoorus, tedatteddotnet, michael_scharf, and uwe.stieber.

Contents

Attendees

  • IBM - Dave Dykstal, Dave McKnight, Kushal Munir
  • Symbian - Javier Montalvo Orús
  • Wind River - Martin Oberhuber, Uwe Stieber, Michael Scharf, Ted Williams
  • Tradescape - Lothar Werzinger

This is an Open call, so anyone else can join (though we expect the talk to be interesting for committers only).

Agenda

  • C'mon and celebrate!
    • RSE 1.0 is released - what did we accomplish in the past year?
      • Created infrastructure - project, website, wiki, mailing list, newsgroup, bugzilla, processes for everything
      • Got all the code through legal review, implemented nightly build system
      • Grew the community - contributors and users, 220 downloads on 1.0RC2; EclipseCon talk, upcoming tutorial
      • Refactored RSE (service/subsystem approach), implemented deferred queries
      • Added ssh and ftp subsystems, discovery component
    • In the past year: What did you like? What did you dislike? What's the favorite thing you want to do next?
      • DaveD:
      • DaveM:
      • Kushal:
      • Javier:
      • Michael:
      • Ted:
      • Uwe:
      • Martin:
    • Bug statistics - Bug Process Page
    • How do you like our processes? Improvements, Suggestions?
      • Bugzilla: All have their personal queries?
      • RSE 1.0 Testing - was the effort right? Especially verification
  • Any Latest News?
    • Michael --
    • Other News --
  • Top Priorities this week:
    • #1 - Being responsive - on Newsgroup, Mailinglist and bug reports. We'll probably get lots of new users as we have RSE 1.0. Let's nurture our user community and encourage them to become contributors in case they have requests. Make sure that E-Mail notifications are turned on for bugzilla (and probably also the Wiki FAQ etc.)
    • #2 - Continue fixing bugs and improving documentation - Let's make sure that users who have problems with 1.0 can get a subsequent I-build as patch soon after. Let's make sure users get missing documentation wherever needed. Instead of answering a question by E-Mail, let's fix the corresponding documentation or FAQ and point the users to it.
    • #3 - Plan RSE 2.0
  • Upcoming Work
    • Start IBM and EMO review process for User Actions and Import/Export (DaveD)
    • Start creating Unit Tests, Testing feature (DaveD, Uwe)
    • Continue bug fixing on HEAD (All)
      • Look at your personal bugs and assign target milestones: What can you fix for 1.0.1? What can you fix for 2.0? For anything yet unknown, keep the open milestone "---"
      • Bugzilla: When fixing a bug, please add a short note where it was fixed, e.g. "Fixed in DStoreRemoteFile". This helps tremendously to find and understand the fix, in case it should be needed again later
    • Fix compiler warnings (Kushal) - prepare for running FindBugs
    • Add ISV Javadoc where it is still missing or incorrect; review, and improve all docs
    • RSE 2.0 Planning - Finalize the 2.0 Project Plan
    • New bugs: REVIEW Assigned to Inbox, Status NEW
  • Communications
    • We should have a longer architecture / planning meeting for upcoming "larger" 2.0 changes soon. Possible Dates?
    • DSDP/TM/Code_Ownership
    • API changes: we'll not introduce any api changes between 1.0 and 1.0.1
      • But prepare for API changes soon after 1.0.1
    • Shall we get rid of unused icons, e.g. rse.ui/icons/full/obj16/system390_obj.gif ?
    • Shall we get rid of commented out source code ?
  • Change Requests
  • Vacations, Holidays etc.
    • US Thanksgiving - End of November
  • Free discussion -- feelings, comments, critics

Action Items

  • Last Meeting Action Items
  • DaveD - Edit Code Ownership. Submit UDA and Import/Export for review; JUnit tests; Hi-Pri bugs. New bug for moving DTD.
  • DaveM - Enter Resume into www.eclipsecon.org; Bugs
  • Kushal - Bugs
  • Martin - Work on 2.0 project plan; TM FAQ on the Wiki; Hi-pri bugs;
  • Javier - Hook up with Scott Lewis once SD is committed and works
  • Ted - Terminalview; Document the build process

Next Meeting