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 "Sequoyah/PhoneMeetings/Agenda10Jul12"

(Action Items)
(Summary)
Line 12: Line 12:
 
* Marcel proposed a code management strategy for Helios SR1 and a proposed 1.1 release.
 
* Marcel proposed a code management strategy for Helios SR1 and a proposed 1.1 release.
 
** [http://wiki.eclipse.org/images/6/65/Release_planning.pdf Release Planning Proposal]. The Scenario 1 was agreed to.
 
** [http://wiki.eclipse.org/images/6/65/Release_planning.pdf Release Planning Proposal]. The Scenario 1 was agreed to.
** The date for the 1.1 release is not going to be as the document suggests.  As the purpose of the 1.1 release is to expose the NDK functionality, when the feature is felt to be ready, we will start the release review process.
+
** The date for the 1.1 release is not going to be as the document suggests.  When the release is felt to be ready, we will start the review process.
* Doug suggested that a separate meeting around Android NDK debugging in Eclipse is needed. Because the majority of NDK discussions occur on the [http://groups.google.com/group/android-ndk Android NDK Google Group], it's best to have the planning there.
+
** Principal attendees are David Turner, Xavier Ducrohet, DougS, EricC, Daniel Franco
+
** '''Topics:''' What does Google want from NDK support in Eclipse?  How does the work in Sequoyah and the NDK list dovetail? (i.e. division of labor, where conversations exist, etc.)
+
 
* Marcel is working on list of bugs to send to dev list for voting up for SR1
 
* Marcel is working on list of bugs to send to dev list for voting up for SR1
* Discussed the process for submissions and how it applies to Android NDK contributions by Doug Schaefer and the MOTODEV Studio development team. After looking at the process flowchart that the Eclipse Foundation maintains, it was agreed that no CQ is necessary, but IP Logs are.
+
* Discussed the process for submissions and how it applies to contributions by Doug Schaefer and the MOTODEV team. After looking at the process flowchart that the Eclipse Foundation maintains, it was agreed that no CQ is necessary, but IP Logs are.
 
* Events
 
* Events
 
** [http://wiki.eclipse.org/Eclipse_Day_At_Googleplex_2010 Eclipse Day at Google] - Eric is presenting a 30 minute session on Sequoyah.  Marcel presented a suggested outline and he and Eric will refine it.
 
** [http://wiki.eclipse.org/Eclipse_Day_At_Googleplex_2010 Eclipse Day at Google] - Eric is presenting a 30 minute session on Sequoyah.  Marcel presented a suggested outline and he and Eric will refine it.
 
** Eclipse Summit Europe - It's not likely that anyone from a Sequoyah/Pulsar company will be in attendance, so we will not make a proposal.
 
** Eclipse Summit Europe - It's not likely that anyone from a Sequoyah/Pulsar company will be in attendance, so we will not make a proposal.
 
* Marcel reminded the meeting that he sent a proposal for the automated test framework to the mailing list two weeks ago and has not yet received any feedback.  
 
* Marcel reminded the meeting that he sent a proposal for the automated test framework to the mailing list two weeks ago and has not yet received any feedback.  
* There was a suggestion by Doug that a separate meeting for technical topics is needed. Eric proposed that Sequoyah follow Pulsar's example and alternate the bi-weekly meetings between technical and project topics.  The proposal was accepted and Eric will work to update the calendar entries and wiki with the proposal.
+
* Doug suggested that a separate meeting for technical topics is needed to keep the Sequoyah call focused on project issues.  
 +
** Eric proposed that Sequoyah follow Pulsar's example and alternate the bi-weekly meetings between technical and project topics.  The proposal was accepted and Eric will work to update the calendar entries and wiki accordingly.
 +
** For the next call, Eric will try to get attendance from several leaders of the Android NDK movement to attend.  Because the majority of NDK discussions occur on the [http://groups.google.com/group/android-ndk Android NDK Google Group], it's best to have the planning there.
 
* A discussion of the time of the meeting occurred.  It was agreed to move the meeting back 1 hour to 1700 UTC (4 PM BR, 1 PM ET, 12 CT, 10 AM PT)
 
* A discussion of the time of the meeting occurred.  It was agreed to move the meeting back 1 hour to 1700 UTC (4 PM BR, 1 PM ET, 12 CT, 10 AM PT)
  

Revision as of 14:17, 12 July 2010

Attendees

  • Eric Cloninger (Motorola)
  • Daniel Pastore (Eldorado)
  • Marcel Gorri (Eldorado)
  • Daniel Franco (Eldorado)
  • Jon Dearden (RIM)
  • Doug Schaefer (Wind River)

Summary

  • Marcel proposed a code management strategy for Helios SR1 and a proposed 1.1 release.
    • Release Planning Proposal. The Scenario 1 was agreed to.
    • The date for the 1.1 release is not going to be as the document suggests. When the release is felt to be ready, we will start the review process.
  • Marcel is working on list of bugs to send to dev list for voting up for SR1
  • Discussed the process for submissions and how it applies to contributions by Doug Schaefer and the MOTODEV team. After looking at the process flowchart that the Eclipse Foundation maintains, it was agreed that no CQ is necessary, but IP Logs are.
  • Events
    • Eclipse Day at Google - Eric is presenting a 30 minute session on Sequoyah. Marcel presented a suggested outline and he and Eric will refine it.
    • Eclipse Summit Europe - It's not likely that anyone from a Sequoyah/Pulsar company will be in attendance, so we will not make a proposal.
  • Marcel reminded the meeting that he sent a proposal for the automated test framework to the mailing list two weeks ago and has not yet received any feedback.
  • Doug suggested that a separate meeting for technical topics is needed to keep the Sequoyah call focused on project issues.
    • Eric proposed that Sequoyah follow Pulsar's example and alternate the bi-weekly meetings between technical and project topics. The proposal was accepted and Eric will work to update the calendar entries and wiki accordingly.
    • For the next call, Eric will try to get attendance from several leaders of the Android NDK movement to attend. Because the majority of NDK discussions occur on the Android NDK Google Group, it's best to have the planning there.
  • A discussion of the time of the meeting occurred. It was agreed to move the meeting back 1 hour to 1700 UTC (4 PM BR, 1 PM ET, 12 CT, 10 AM PT)

Action Items

  • [Eric] Start discussion on android-ndk list to find a time for the call. Perhaps the new technical call proposed below.
  • [Ronnie, Paul, Jon, etc.] Please read and comment on Marcel's automated testing proposal.
  • [Daniel Pastore] Send Doug Schaefer a link to latest Sequoyah nightly build with NDK build support.
  • [Paul B] Propose a time for a demo of the web tools. Introduce prospective contributor and start planning how to include the tools as part of an upcoming Sequoyah release.

Next Meeting

The next meeting will be on July 26, 2010.

Back to the top