Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Corona Milestone 1.0.0M10"

m (→‎Collaboration Framework)
 
(16 intermediate revisions by 2 users not shown)
Line 9: Line 9:
 
== Theme ==
 
== Theme ==
  
−
The focus for this milestone release is improving the ''out-of-box'' experience.  This is the last milestone release for Coronas.  As of M10, Corona should be functional complete.
+
The focus for this milestone release is improving the ''out-of-box'' experience.  This is the last milestone release for Coronas.  As of M10, Corona should be functional complete.  Only those new features that are a '''must-have''' will be introduced into this milestone release.
  
 
== Schedule ==
 
== Schedule ==
Line 20: Line 20:
  
 
The list of items scheduled for this release are defined within [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=Corona&version=1.0.0&target_milestone=1.0.0+M10&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugzilla]
 
The list of items scheduled for this release are defined within [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=Corona&version=1.0.0&target_milestone=1.0.0+M10&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugzilla]
 +
 +
* Items [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=Corona&target_milestone=1.0.0+M10&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= planned for] this release.
 +
* Items that [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=Corona&target_milestone=1.0.0+M10&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&resolution=FIXED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= are in] this release.
  
 
== Objectives ==
 
== Objectives ==
Line 25: Line 28:
 
=== Collaboration Framework ===
 
=== Collaboration Framework ===
 
* ContextContainer model improvements
 
* ContextContainer model improvements
−
* Client-side handle of server-side shutdown
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=181831 CCX handling of container shutdown events]
  
 
=== Manageability ===
 
=== Manageability ===
Line 38: Line 41:
  
 
=== Test Framework ===
 
=== Test Framework ===
 +
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=175876 WSDM based test framework]
 
* Client side test cases
 
* Client side test cases
 +
** TBD
 
* Server side test cases
 
* Server side test cases
 +
** TBD
  
 
=== Data Stores ===
 
=== Data Stores ===
Line 47: Line 53:
 
** IP Pending
 
** IP Pending
  
−
=== Project user experience ===
+
=== Project User Experience ===
 +
* Handle Server Shutdown
 +
** Bugzilla item [https://bugs.eclipse.org/bugs/show_bug.cgi?id=181831 181831]
 
* Wizard for adding project container
 
* Wizard for adding project container
 +
** Bug item [https://bugs.eclipse.org/bugs/show_bug.cgi?id=182712 182712]
 
** Scope of the wizard:
 
** Scope of the wizard:
 
*** Container name (required)
 
*** Container name (required)
Line 55: Line 64:
 
*** Add repositories - projects, web pages (optional)
 
*** Add repositories - projects, web pages (optional)
 
** Current mechanism for adding empty container won't work; it doesn't contain the team member repository as well as a first user, so you won't be able to open such container
 
** Current mechanism for adding empty container won't work; it doesn't contain the team member repository as well as a first user, so you won't be able to open such container
 +
{{CommentBox|
 +
Can adding a new ProjectContextContainer be done manually?  It seems this could be supported with documentation.
  
−
* Logging to container
+
''--Dennis O'Flynn''
 +
}}
 +
 
 +
* User Authentication
 
** While opening project container there should be login dialog. Using system login name wouldn't work well in production.  
 
** While opening project container there should be login dialog. Using system login name wouldn't work well in production.  
 
** Some password protection should also available.
 
** Some password protection should also available.
 +
** Could it replace the login to chat.
 +
 +
{{CommentBox|
 +
Security has been a known open issue.  We will need to build our authentication / authorization model based upon Higgins identity management.  Corona plans to address security in follow-up release.  Recommend continuing using the JVM “user.name” and assume that user has already been validated by the local workstation (e.g. WinXP, Linux desktop).
 +
 +
''--Dennis O'Flynn''
 +
}}
  
−
* Automatic adding users for guests (?)
+
* [[Corona ProjectContainer Guest]]
 +
** Bugzilla item [https://bugs.eclipse.org/bugs/show_bug.cgi?id=181795 181795]
 
** Not sure of this one.
 
** Not sure of this one.
 
** If we would like to expose an example container at our vserver, having User_A, User_B, ... User_Z might not be a best solution. There might be conflicts - several people would login as User_A for instance.
 
** If we would like to expose an example container at our vserver, having User_A, User_B, ... User_Z might not be a best solution. There might be conflicts - several people would login as User_A for instance.
 
** So a unique temporary guest users could be added, so that they can participate fully in the container - chat, events, etc.
 
** So a unique temporary guest users could be added, so that they can participate fully in the container - chat, events, etc.
 +
** Should the guest account be automatically removed when user logs out?
  
 
* Adding projects to container by right-click -> add to container; dragging could also be an option
 
* Adding projects to container by right-click -> add to container; dragging could also be an option
Line 75: Line 98:
 
** Add an action "Start shared editor"; an event with shared editor settings is sent and others get an dialog if they want to join; if yes, session settings from event are taken
 
** Add an action "Start shared editor"; an event with shared editor settings is sent and others get an dialog if they want to join; if yes, session settings from event are taken
 
** Seems to be simple to do :)
 
** Seems to be simple to do :)
−
* Project checkout to working group with container name (probably very simple) - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170600 bug 170600]
+
* Indicator that a resource has a newer version in CVS; or at least information that there was some CVS check in
 
* Showing status of resources in the whole team
 
* Showing status of resources in the whole team
 
** show indicators that someone is working on a given file, some removed a file, etc.
 
** show indicators that someone is working on a given file, some removed a file, etc.
Line 82: Line 105:
 
*** when should the state be cleared?  
 
*** when should the state be cleared?  
 
*** would require some server-side state caching; otherwise when starting IDE you would always have a clear state, even though someone may be working on resources  
 
*** would require some server-side state caching; otherwise when starting IDE you would always have a clear state, even though someone may be working on resources  
−
* Indicator that a resource has a newer version in CVS; or at least information that there was some CVS check in
+
** would require consultation with usability experts
 
* RSS viewer [https://bugs.eclipse.org/bugs/show_bug.cgi?id=156275 bug 156275]
 
* RSS viewer [https://bugs.eclipse.org/bugs/show_bug.cgi?id=156275 bug 156275]
 
* Calendar (iCal) viewer [https://bugs.eclipse.org/bugs/show_bug.cgi?id=159606 bug 159606]
 
* Calendar (iCal) viewer [https://bugs.eclipse.org/bugs/show_bug.cgi?id=159606 bug 159606]
 +
* Project checkout to working group with container name (probably very simple) - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170600 bug 170600]
  
 
=== Documentation ===
 
=== Documentation ===

Latest revision as of 11:38, 17 April 2007

Eclipse Home Wiki Home Plan 1.0.0M9 1.0.0MRC1

Theme

The focus for this milestone release is improving the out-of-box experience. This is the last milestone release for Coronas. As of M10, Corona should be functional complete. Only those new features that are a must-have will be introduced into this milestone release.

Schedule

Planned Start Date Apr 9, 2007 Planned Finish Date May 4, 2007

The list of items scheduled for this release are defined within Bugzilla

Objectives

Collaboration Framework

Manageability

  • WSDM Enablement
  • Service start/stop
  • ContextContainer
    • Create / Update / Delete
  • ProjectContainer
    • Create / Update / Delete
    • TeamMemberRepository
      • Create / Update / Delete

Test Framework

Data Stores

  • Apache Derby 10.1.2.1 (Orbit)
    • IP Approved
  • Apache Jackrabbit
    • IP Pending

Project User Experience

  • Handle Server Shutdown
  • Wizard for adding project container
    • Bug item 182712
    • Scope of the wizard:
      • Container name (required)
      • Create team repository (required)
      • Add team members (required)
      • Add repositories - projects, web pages (optional)
    • Current mechanism for adding empty container won't work; it doesn't contain the team member repository as well as a first user, so you won't be able to open such container

Can adding a new ProjectContextContainer be done manually? It seems this could be supported with documentation.

--Dennis O'Flynn

  • User Authentication
    • While opening project container there should be login dialog. Using system login name wouldn't work well in production.
    • Some password protection should also available.
    • Could it replace the login to chat.

Security has been a known open issue. We will need to build our authentication / authorization model based upon Higgins identity management. Corona plans to address security in follow-up release. Recommend continuing using the JVM “user.name” and assume that user has already been validated by the local workstation (e.g. WinXP, Linux desktop).

--Dennis O'Flynn

  • Corona ProjectContainer Guest
    • Bugzilla item 181795
    • Not sure of this one.
    • If we would like to expose an example container at our vserver, having User_A, User_B, ... User_Z might not be a best solution. There might be conflicts - several people would login as User_A for instance.
    • So a unique temporary guest users could be added, so that they can participate fully in the container - chat, events, etc.
    • Should the guest account be automatically removed when user logs out?
  • Adding projects to container by right-click -> add to container; dragging could also be an option
    • For new we could require that the project is already shared
    • In future I think the code could identify SCM repository and use its settings to share project first, and then add to container

New features for project scope

  • Mylar
    • I liked the Mylar functionality with Corona (expert, etc). Would it be difficult to update it for Mylar provided with Europa?
  • ECF Shared Editor
    • Add an action "Start shared editor"; an event with shared editor settings is sent and others get an dialog if they want to join; if yes, session settings from event are taken
    • Seems to be simple to do :)
  • Indicator that a resource has a newer version in CVS; or at least information that there was some CVS check in
  • Showing status of resources in the whole team
    • show indicators that someone is working on a given file, some removed a file, etc.
    • probably difficult
    • problems:
      • when should the state be cleared?
      • would require some server-side state caching; otherwise when starting IDE you would always have a clear state, even though someone may be working on resources
    • would require consultation with usability experts
  • RSS viewer bug 156275
  • Calendar (iCal) viewer bug 159606
  • Project checkout to working group with container name (probably very simple) - bug 170600

Documentation

  • Wiki
    • Installation guide
  • plugin - org.eclipse.corona.doc
    • Outline
      • Server-Side
      • Collaboration Framework
      • Exemplary Implementation
Retrieved from "https://wiki.eclipse.org/index.php?title=Corona_Milestone_1.0.0M10&oldid=33853"

This page was last modified 11:38, 17 April 2007 by Dennis O'Flynn. Based on work by Marcin Okraszewski.

Back to the top