discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNUstep @ FOSDEM 2010 6th and 7th February 2010


From: address@hidden
Subject: Re: GNUstep @ FOSDEM 2010 6th and 7th February 2010
Date: Tue, 20 Oct 2009 00:43:28 -0700 (PDT)
User-agent: G2/1.0

On 20 Okt., 00:36, Lars Sonchocky-Helldorf <lars.sonchocky-
address@hidden> wrote:
> Am 17.10.2009 um 10:21 schrieb address@hidden:
>
> >> I think we may just not ask for the stand this year... just ask for a
> >> dev-room. And only do a few talks (i.e., "State of GNUstep 2010") and
> >> keep hacking the rest of the time.
> >> Put posters pointing to the dev room in the hallway, and that's it!
>
> > When looking at the recent growth of new members of this list, I think
> > there is a lot of more interest in GNUstep than before. Probably by
> > new iPhone developers who want to extend their newly gained experience
> > to GNUstep and want to learn what it is and how it can be used
> > uefully.
>
> currently only 4 people (including myself) have declared intend to  
> come to FOSDEM 2010. This is not to overwhelming if you ask me. Btw,  
> how about you, Nikolaus? Are you planning a FOSDEM presence? I am  
> also looking for some co-organisers for our FOSDEM presence. You did  
> already this two (or more?) times in the past so I'd appreciate your  
> experience here.

Let's say I am thinking about the basic question when I should start
planning :)
My focus of activities has shifted a little over the last two years
but it could be good to go to FOSDEM anyway.
So, I have to regret that I won't take the role of co-organiser. But
if there are questions, I am happy to help answering them. And if
there is interest in a presentation about QuantumSTEP running on the
latest embedded devices (e.g. Openmoko, Beagleboard), I can prepare
one.

I think there are many others reading the list and really an
impressive number has commented Greg's recent request for improved
marketing. Here is now the chance to really participate in activities
and shape the future of GNUstep.

>
> > Therefore, we should have some "Introduction to GNUstep & tutorial"
> > talk that is done only once every day (e.g. Sat 14:00, Sun 14:00).
> > This needs a DevRoom and is IMHO more important than a stand. And it
> > should be the only formal "presentation" we do. All other activities
> > can be code sprints, hacking, discussing, meeting, etc. We can also
> > set up a "demo & brochures" corner.
>
> I think a good mixture out of some presentations (I guess we need at  
> least some to get the dev-room and those make people from outside our  

That is an important point. The FOSDEM organizers probably won't give
us a "private" room just for us.

> group interested in GNUstep) and the more GNUstep internal activities  
> (code sprints, hacking, discussing, meeting and such) would be the  
> best. All our talks and presentations last year were well visited,  
> our room was never empty. Of course the value of this is more on the  
> marketing side, making GNUstep known between developers (and those  

IMHO, FOSDEM participation of GNUstep (and any project that wants to
attend FOSDEM) has three targets:
* make latest GNUstep achievements known to the public
* attracting new developers
* meet companion developers in person and perhaps find some time to
discuss and solve issues (for really solving issues, most successfull
projects have separate code-sprint developer meetings)

> are the people that write our future killer apps ;-)). But I am still  
> waiting for input here (also on the "GNUstep-internal" activities).
>
>
>
> > And, lingering around all the day in a devroom may be more healthy
> > than manning a stand in the cold hallway with a air-conditioner in the
> > back :)
>
> That's true. Most people at the stand had only cursory interest while  
> people sitting in a dev-room talk/presentation/lecture could be  
> impressed much more sustainable.
>
>
>
> > Nikolaus
>
> regards,
>
>         Lars

Nikolaus


reply via email to

[Prev in Thread] Current Thread [Next in Thread]