Re: Questions

[Doc O'Leary]

For your reference, records indicate that 
Gregory Casamento <greg.casamento@gmail.com> wrote:

> On a side note: I have
> also often heard people express the idea that if you have a comment you
> should also be willing to help fix whatever you're commenting on.   While
> it would be nice if this were always the case it is not good practice to
> exclude the opinions of those who either don't have the skill or the time
> to contribute, but who want to USE the platform for their projects.  It
> would be a terrible mistake not to listen to them.

On this point I’d go a step further: if someone signs on to do work on a
part of the project, you should be accepting the *responsibility* of that
role, which should be seen as far greater than simply coding some bits to
suit your own purposes.  The reason I would like to see a clear goal
stated is so that people can understand the bigger picture and see where
their contributions fit into the whole.

> > GNUstep's mission is extended to one of bringing the ease of Cocoa
> > development to as many platforms as possible.
> >
> >
> > That is something I can agree with and find it attractive.
> >
> 
> I'm glad, then maybe we should change the website to reflect something
> similar.

But it still isn’t clear *how* GNUstep is organized to achieve that goal.
We can’t just ignore the big gorilla in the room (Apple), either.  I’m
not trying to make it sound like it needs to be complex, but it does need
to be *clear* where GNUstep positions itself in the sphere of Cocoa
development.  I maintain it isn’t clear if or how a Mac app can be run
with GNUstep, nor is it clear if or how a GNUstep-first app can be run on
a Mac.

-- 
"Also . . . I can kill you with my brain."
River Tam, Trash, Firefly