On 02/29/2008 10:43, [EMAIL PROTECTED] wrote:
>       Ravenlock wrote:
> 
>> .... What has to happen is, we have to describe our ideas in terms
>> that non-E-devs can understand, and appreciate.
> 
>       (Nice work on this BTW)
> 
>       Ok, let's take a naive point of view - we're all now neophytes
> with no real knowledge of "e", and someone's asking you for help with
> their "e" stuff.. What would you say?

What you say below is true, but...

First, lets get in the correct mindset.  We are not "asking people to
help with our E stuff".  The goal of SoC is to help students learn and
to create more open source code.  Google is not putting up bounties for
things *we* want done.  Google is gonna pay a few students to further
their knowledge of Open Source in general, and to get more code out in
the wild.  The ideas we suggest are just that.  Just ideas.  Something
to tempt the students.  It may be that none of the ideas on our list get
picked up.  But maybe some student comes along falls in love with E and
has an entirely different idea that we approve of.  That student will
get paid to work on it, learn about OSS, and create some code.

> 
>       If you really want anyone unfamiliar with "e" to even begin
> to care about "e", then maybe you'd need to start by answering some
> fundamental questions: What is "e", and why should I care about it?
> 
>       Look at sourceforge, freshmeat, and others such.. There are
> tens of thousands of foss projects out there - many of them quite
> interesting. Why "e"?
> 
>       A window manager? So what, there are tons of those already.
> What else?
> 
>       An app development framework? There are mature, full-featured
> ones already... ones that have produced thousands of apps. How does
> "e" compare to those other frameworks, and what apps has it managed
> to produce? Why is its framework, or the apps it allows, 'better'
> somehow?
> 
>       What's the 'Big Picture' of "e", and why should others care?
> Is "e" something like a "rich app development framework"? Does it
> support or work well with the web?
>       Do you have a 'projects' page where I can see some of the
> things developed with this "e"?
> 
>       Why should 'we' care about "e"?

The above comments are all true, and applicable to this situation.  But
the entire wiki itself is designed to meet this need.  All of the
questions you have *should* be answered by the wiki itself (if they are
not the wiki needs some love), not necessarily by the one or two pages
created for SoC.  While a very brief summary of what you ask above will
be on our Google SoC application....  Its really (imho) a bit up to the
student to find a project (think E, think OpenOffice, think FreeBSD)
that they wish to get involved with.  Finding that project will require
some research on the students part.

Now, along these lines... I have been trying to make links on the SoC
ideas page to point to relevant areas of the wiki (or other sites) as
need be.  In the hopes that someone coming in cold off the street can
read the ideas page, and then follow links to learn more details about
things (edje, efl, etc)

Now, with all that said.... a lot of what I said is simply my opinion.
Maybe I'm wrong here.  Either way....  If you see an opportunity to
improve on what we are doing with regard to SoC... please jump in.  All
help is appreciated.

=============== End of reponse ====

As an aside:
Why is it *your* e-mail in particular is never *threaded* into the
appropriate conversations by my mailreader (Thunderbird).  Everyone
else's mail is fine.  :/


-- 
Regards,
Ravenlock


Attachment: signature.asc
Description: OpenPGP digital signature

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to