<<O>>  Difference Topic DevMeeting2006 (r1.7 - 17 Oct 2006 - PeterFox)

META TOPICPARENT WebHome

OPeNDAP Developer's Meeting 2007

CALL for participation, contributions and feedback

  • Presentations by the community: Tell others about what you've done.
  • Presentations by OPeNDAP core developers - hear what's new.
Added:
>
>
  • Feedback on structure of this meeting, what would YOU like?

  • Open Forum: What changes would you like to see OPeNDAP make?

General Topic areas (comment on these):


 <<O>>  Difference Topic DevMeeting2006 (r1.6 - 17 Oct 2006 - JamesGallagher)

META TOPICPARENT WebHome

OPeNDAP Developer's Meeting 2007

Line: 25 to 25

Logistics:

  1. Dates - mid-late February 2007
Changed:
<
<
  1. Length - 2 1/2 days? Perhaps preceeded by a hand-on SERVER4 tutorial
>
>
  1. Length - 2 1/2 days? Perhaps preceeded by a hands-on SERVER4 tutorial

  1. Venue - Boulder
Changed:
<
<
  1. Funding support? - who needs it?
>
>
  1. Funding support? - who will need it?

  1. Advertising - what are the venues to get the word out (worldwide)
  2. Program committee (want to join? have a say?)

 <<O>>  Difference Topic DevMeeting2006 (r1.5 - 16 Oct 2006 - PeterFox)

META TOPICPARENT WebHome
Changed:
<
<

OPeNDAP Developer's Meeting 2006

>
>

OPeNDAP Developer's Meeting 2007


Changed:
<
<
Feel free to edit this. Contact James Gallagher for an account.

Things we need to do to organize the meeting:

>
>
CALL for participation, contributions and feedback

  • Presentations by the community: Tell others about what you've done.
Added:
>
>
  • Presentations by OPeNDAP core developers - hear what's new.

  • Open Forum: What changes would you like to see OPeNDAP make?
Changed:
<
<
General Topic areas:
>
>
General Topic areas (comment on these):

  1. Server4 release and how to develop with it
  2. Security (authorization, authentication)
Line: 23 to 22

  1. Serving in situ data
  2. Using the Ocapi, with an emphasis on writing 'command extensions' for commercial applications
Deleted:
<
<
[ Of these, I think the first four are all really important. Can we cover four? I also think the user experiences stuff should be given a/the spotlight. I added two. James]

Logistics:
Changed:
<
<
  1. Dates -
  2. Length - 2 or 2 1/2 days? [I suggest 2 1/2 days. James]
  3. Venue - Boulder? May depend on if we piggy-back on another meeting [Boulder; better to not piggy-back if we're going for a 2 1/2 day meeting unless the you mean we'd get together for a day or so before as an OPeNDAP Board meeting. James]
  4. Funding support? - who needs it? [Do you mean support so people cn attend? James]
>
>
  1. Dates - mid-late February 2007
  2. Length - 2 1/2 days? Perhaps preceeded by a hand-on SERVER4 tutorial
  3. Venue - Boulder
  4. Funding support? - who needs it?

  1. Advertising - what are the venues to get the word out (worldwide)
  2. Program committee (want to join? have a say?)

Format:

Changed:
<
<
I suggest that we structure each day around a combination of presentations, all from people outside OPeNDAP about how the software is being used, providing them with a platform to say '...and here's what we wish it could do.' and tutorials where we can cover topics like 'How to develop a data handler for Server4.' I think each tutorial should have some sort of paper copy that people can take home.
>
>
We plan to structure each day around a combination of presentations, all from people outside OPeNDAP about how the software is being used, providing them with a platform to say '...and here's what we wish it could do.' and tutorials where we can cover topics like 'How to develop a data handler for Server4.' Each tutorial should have some sort of paper copy that people can take home.

Changed:
<
<
For the web, I think those tutorials should go up once the meeting is over. An agenda should be posted on the web just before the meeting, along with abstracts for the presentations. All three of these things would be the web record of the meeting.
>
>
Those tutorials will be uploaded once the meeting is over.

Changed:
<
<
-- JamesGallagher - 30 Aug 2006
>
>
A detailed agenda will be posted on the web just before the meeting, along with abstracts for the presentations.

Changed:
<
<
-- PeterFox - 31 Aug 2006
>
>
The website for the meeting will be maintained as a record of the meeting.

Changed:
<
<
-- JamesGallagher - 31 Aug 2006: Added some comments.
>
>
-- PeterFox - 16 Oct 2006


 <<O>>  Difference Topic DevMeeting2006 (r1.4 - 05 Sep 2006 - PeterFox)

META TOPICPARENT WebHome

OPeNDAP Developer's Meeting 2006


 <<O>>  Difference Topic DevMeeting2006 (r1.3 - 31 Aug 2006 - JamesGallagher)

META TOPICPARENT WebHome

OPeNDAP Developer's Meeting 2006

Line: 20 to 20

  1. DAP4 status and plans
  2. Strategies and directions
  3. ADD yours here and we'll iterate this list
Added:
>
>
  1. Serving in situ data
  2. Using the Ocapi, with an emphasis on writing 'command extensions' for commercial applications

[ Of these, I think the first four are all really important. Can we cover four? I also think the user experiences stuff should be given a/the spotlight. I added two. James]


Logistics:

  1. Dates -
Changed:
<
<
  1. Length - 2 or 2 1/2 days?
  2. Venue - Boulder? May depend on if we piggy-back on another meeting
  3. Funding support? - who needs it?
>
>
  1. Length - 2 or 2 1/2 days? [I suggest 2 1/2 days. James]
  2. Venue - Boulder? May depend on if we piggy-back on another meeting [Boulder; better to not piggy-back if we're going for a 2 1/2 day meeting unless the you mean we'd get together for a day or so before as an OPeNDAP Board meeting. James]
  3. Funding support? - who needs it? [Do you mean support so people cn attend? James]

  1. Advertising - what are the venues to get the word out (worldwide)
  2. Program committee (want to join? have a say?)
Added:
>
>
Format:

I suggest that we structure each day around a combination of presentations, all from people outside OPeNDAP about how the software is being used, providing them with a platform to say '...and here's what we wish it could do.' and tutorials where we can cover topics like 'How to develop a data handler for Server4.' I think each tutorial should have some sort of paper copy that people can take home.

For the web, I think those tutorials should go up once the meeting is over. An agenda should be posted on the web just before the meeting, along with abstracts for the presentations. All three of these things would be the web record of the meeting.


-- JamesGallagher - 30 Aug 2006

-- PeterFox - 31 Aug 2006

Added:
>
>
-- JamesGallagher - 31 Aug 2006: Added some comments.

 <<O>>  Difference Topic DevMeeting2006 (r1.2 - 31 Aug 2006 - PeterFox)

META TOPICPARENT WebHome

OPeNDAP Developer's Meeting 2006

Feel free to edit this. Contact James Gallagher for an account.

Things we need to do to organize the meeting:

Deleted:
<
<
  • Set a place and time. Suggestions: Boulder CO, date ?
  • Topics developers would like to see addressed at the meeting.

  • Presentations by the community: Tell others about what you've done.
  • Open Forum: What changes would you like to see OPeNDAP make?
Added:
>
>
General Topic areas:

  1. Server4 release and how to develop with it
  2. Security (authorization, authentication)
  3. Web services with OPeNDAP
  4. Enabling semantics with OPeNDAP
  5. OPeNDAP clients, GUIs
  6. Client use-cases, user/developer experiences
  7. TDS release and how to develop with it/use it
  8. DAP4 status and plans
  9. Strategies and directions
  10. ADD yours here and we'll iterate this list

Logistics:

  1. Dates -
  2. Length - 2 or 2 1/2 days?
  3. Venue - Boulder? May depend on if we piggy-back on another meeting
  4. Funding support? - who needs it?
  5. Advertising - what are the venues to get the word out (worldwide)
  6. Program committee (want to join? have a say?)

-- JamesGallagher - 30 Aug 2006

Added:
>
>
-- PeterFox - 31 Aug 2006

 <<O>>  Difference Topic DevMeeting2006 (r1.1 - 30 Aug 2006 - JamesGallagher)
Line: 1 to 1
Added:
>
>
META TOPICPARENT WebHome

OPeNDAP Developer's Meeting 2006

Feel free to edit this. Contact James Gallagher for an account.

Things we need to do to organize the meeting:

  • Set a place and time. Suggestions: Boulder CO, date ?
  • Topics developers would like to see addressed at the meeting.
  • Presentations by the community: Tell others about what you've done.
  • Open Forum: What changes would you like to see OPeNDAP make?

-- JamesGallagher - 30 Aug 2006