maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Community (https://talk.maemo.org/forumdisplay.php?f=16)
-   -   How to define the Maemo Summit schedule (https://talk.maemo.org/showthread.php?t=29466)

VDVsx 2009-06-16 11:17

Re: How to define the Maemo Summit schedule
 
Quote:

Originally Posted by qgil (Post 297081)
It's nobody's interest to have sessions in the limbo, and if a session looks really weak/off-topic we can discard it asap.

The hard deadline on July 3rd also looks unrealistic, specially compared to the casual setting we had last year. I understand some of you want something with more structure but closing the call for papers 4,5 months before the event sounds almost like an academic convention or a business fair.

I agree with you, I personally tend to adopt the academic way, but in this scope I think we don't want to do that :) .



Quote:

Originally Posted by qgil (Post 297081)
Proposal to reword this:



July 5th and September 13th because they are Sundays and people tend to do a lot of weekend work when submitting proposals in these kind of events. You avoid any timezone misinterpretations looking at whatever has been received before Monday morning European time.

Seems fine to me, thanks for the your suggestions :)

sjgadsby 2009-06-16 13:32

Re: How to define the Maemo Summit schedule
 
Quote:

Originally Posted by Baloo (Post 296099)
PLATFORM DEVELOPERS: convince developers that they should be developing new software for Maemo (and try to pull people for iPhone, Blackberry, Android and other platforms although without the financial incentive that could be hard.).

Porting iPhone, Blackberry, Android, etc. applications wouldn't be platform development though, would it? Isn't the platform Upstart, Clutter, Meta Tracker, PulseAudio, Hildon, GTK, Qt, and so on? I'd think porting from other platforms would fall in with:
Quote:

Originally Posted by Baloo (Post 296099)
APP DEVELOPERS: convince upstream to port to Maemo and show how easy it is for technical people to package for Maemo.

How about:
  • Users: get the most out of Maemo and Mer, and get involved in our growing maemo.org community
  • Application developers: start your first Maemo application, bring your application to Maemo, and improve your development skills to take your applications further
  • Platform developers: dig in to enhance and extend the Maemo platform and the fantastic technologies upon which it builds
Good? No good? Suggestions? Should I put it into the wiki?

timsamoff 2009-06-16 14:05

Re: How to define the Maemo Summit schedule
 
Quote:

Originally Posted by sjgadsby (Post 297149)
Porting iPhone, Blackberry, Android, etc. applications wouldn't be platform development though, would it? Isn't the platform Upstart, Clutter, Meta Tracker, PulseAudio, Hildon, GTK, Qt, and so on? I'd think porting from other platforms would fall in with:


How about:
  • Users: get the most out of Maemo and Mer, and get involved in our growing maemo.org community
  • Application developers: start your first Maemo application, bring your application to Maemo, and improve your development skills to take your applications further
  • Platform developers: dig in to enhance and extend the Maemo platform and the fantastic technologies upon which it builds
Good? No good? Suggestions? Should I put it into the wiki?

Me likey.

Tim

Peter@Maemo Marketing 2009-06-17 06:57

Re: How to define the Maemo Summit schedule
 
Well, academic or not, I've got a confirmation for our VIP guest on Day 1: Jim Zemlin, Executive Director of Linux Foundation, will give us a key note presentation in the morning.

dneary 2009-06-17 09:32

Re: How to define the Maemo Summit schedule
 
Quote:

Originally Posted by sjgadsby (Post 297149)
How about:
  • Users: get the most out of Maemo and Mer, and get involved in our growing maemo.org community
  • Application developers: start your first Maemo application, bring your application to Maemo, and improve your development skills to take your applications further
  • Platform developers: dig in to enhance and extend the Maemo platform and the fantastic technologies upon which it builds
Good? No good? Suggestions? Should I put it into the wiki?

Gotta love conversations going on in 3 different places (wiki, Talk, email). In my mind, what is in the wiki as the call for content is the reference - so yes, any suggestions coming out of email or Talk should get put in the wiki or at least the Talk page there, so that we work towards a final call for content.

I suggested yesterday in email that there are two ways to define the tracks: either we talk about the target audience, or the type of presentations we think the target audience is interested in. In general, you can imagine that the descriptions starts with "People who..." or "Presentations about..."

I quickly thought that this might be a good way to describe the tracks, in both ways:

First way:
  • Users: Want to get the most out of their Maemo based hardware, or are interested in contributing to the Maemo community.
  • App developers: Write great applications on top of the Maemo platform.
  • Platform developers: Interested in getting down to bare metal, hacking on the platform or one of its components

Second way:
  • Users: Show off something cool that lets people get the most out of their hardware, or present an aspect of the Maemo community where you need help
  • App developers: Help people get the most out of the Maemo platform, and write great apps
  • Platform developers: You're hacking on the platform and want to show off great low-level hacks, this is the place for you

(or some variant of those)

The feedback I got was that the second way is better, so that's what I've just put in the wiki page.

Suggested improvements are welcome, we're going to send this out later to get presentation proposals started already.

Thanks!
Dave.

dneary 2009-06-17 09:45

Re: How to define the Maemo Summit schedule
 
Quote:

Originally Posted by dneary (Post 297428)
I suggested yesterday in email that there are two ways to define the tracks: either we talk about the target audience, or the type of presentations we think the target audience is interested in. In general, you can imagine that the descriptions starts with "People who..." or "Presentations about..."

Reading sjgadsby's suggestion, there is a third way - tell the target audience what kind of sessions they can expect. "Come here if you want to..."

Looking at the 3 side by side, I think that the call for content, being targeted more at the people who are submitting proposals, should give guidelines on the types of presentations we expect to see, which matches better the current version in the wiki.

Cheers,
Dave.

qgil 2009-06-17 11:53

Re: How to define the Maemo Summit schedule
 
Between http://wiki.maemo.org/Maemo_Summit_2009/Schedule and http://twitter.com/PeterMaemo/status/2204395247 Peter seems to be basically done with Friday morning already. That was much faster than what even myself expected.

Aiming to have the Friday afternoon somehow drafted during next week. Of course we might keep some slots for later. Feedback will be welcome about the content and format.

Then we could also start adding the clearly expected sessions in the schedule.

With Friday drafted and the obvious sessions in the schedule, the basic tone of the Summit will be set. This should be good enough to inspire submitters of new proposals and to help potential participants to make up their minds and start booking their travel.

timsamoff 2009-06-19 16:12

Re: How to define the Maemo Summit schedule
 
Official Council Post:

http://maemo.org/community/council/m...tent_now_open/

Please add your content to the list!

Tim

fpp 2009-06-19 20:42

Re: How to define the Maemo Summit schedule
 
Done. Is there a special prize for first post ? :-)

timsamoff 2009-06-19 20:44

Re: How to define the Maemo Summit schedule
 
Quote:

Originally Posted by fpp (Post 298016)
Done. Is there a special prize for first post ? :-)

You get quoted ^ with a "Thanks" under it. :p

No, really.... Thanks!

Tim


All times are GMT. The time now is 13:55.

vBulletin® Version 3.8.8