Hi, Am 02.07.2011 11:52, schrieb Nino Novak: > >> Some of these tasks even *should* not be done by developers, > I'd suggest to change the wording here to a positive form, like... > "Some of these tasks *should* be done by non-developers"
Well - I just some basic wisdom of software development - and it is really about who should rather *not* do certain things. E.g. a developer should not write a end-user documentation (or it will be missing lots of things that are trivial for the developer but hardly known to an end-user). > or even better avoid the negative form completely: > "... done by a mixed team of (advanced?) documenters/end- > users/designers/ux'ers/whatever ..." Yes - this is what it is meant do be finally. >> ... >> >> We need to come to a point, where non-developers help with all these >> things and collaborate with developers (code hackers). > (what I don't like here is the word "help", as it suggests "doing minor- > value work", so the problem or part of the problem might be the at least > somewhat "looking down" attitude of the developers?) This is not at all "minor value work". There is of course the problem that people tend to think that their own contribution is what really matters - for developers this might not only be a tendency ;) But this is really tricky, beause if no non-developers contribute to new feature implementation, you will very likely get a bad designed feature. If no developers contribute to new feature implementation you will get no feature at all. So just convince developers to implement "real good features or the users" instead of "implement cool features because we can". This can be done best if you make them aware that also non-developers *do* contribute a lot and ease developer's job. (Again - I don't want to say that "help" has less value than "developer's job" here.) > I like the idea to "make aware" as a first step. However... > > If you mean: "How to make implementing new features more attractive to > mixed teams instead of one-person-only?" Hmm .. I don't think, thats the problem. My experiment showed, that it is quite easy to have a "mixed team". For the spec I got input from Astron at the design-list, I got valuable feedback from Regina at the German list, I got hints for the code at IRC from moggi, bubli is reviewing my patch. So, this actually is a mixed team - but mostly of developers (people who already touched the source code). It is really about awarness (what needs to be done for a good feature implementation - and what can be done by non-developers and how can this be done). > then I think, this might be a > very sensible area as one of the major motivations of at least part of > the developers might be "to be the one who implements a feature". So > your question might be "who is willing to pioneer a mixed development > approach?" Oh - I'm actually doing this (at least I got the impression). André -- Unsubscribe instructions: E-mail to [email protected] Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/documentation/ All messages sent to this list will be publicly archived and cannot be deleted
