Our best recruitment base is our user base. The more we use them the tighter the link between user and developer gets, the more probable it is we get people. Community feeling is a strong motivator for doing the right thing.
And people we have, we lack imho skill. And this we need to build. We need to open ways into open office development. Set starting points with view little knowledge and need to slowly guide the volunteers to the deeper end of our projects. Currently we don't have roads like I described above, we only have a fast and frightening jungle. Getting users to evaluate what is a bug and what is not would be in my eyes a huge step forward. Of course the next step would be solving them. But for that we can vote, measure or find other ways to promote them Maybe slicing them up in micro jobs would work for some. Setting up a bazaar another. I would like to take one step after another. And only do things we think that they work with people we have. Because I do believe in that we need to do things in order that people join. All the best Peter Am 20. Mai 2017 10:14:11 MESZ schrieb Marcus <marcus.m...@wtnet.de>: >Am 20.05.2017 um 06:23 schrieb Jörg Schmidt: >>> From: Marcus [mailto:marcus.m...@wtnet.de] >> >>> absolutely, we need volunteers that would then work on these bug >>> reports. Assumed they *are* valid bugs and not "how can I do this >and >>> that" questions. ;-) >> >> yes, right, but that's not what I mean. > >maybe, but I was talking about more than just developers. Sure, we need > >more but we need also man-power to work on the additional reports. >Currently we have a large number of them open and it won't get less in >the future when the proposal comes true. ;-) > >> I mean we need developers who fix the bugs. And there are two >problems: >> >> (a) >> We do not have enough developers (ok, we have to see what the future >brings) >> >> (b) >> The existing developers work voluntarily and do what they want - how >do we get them to fix _specific_ bugs? >> Please understand what I mean: there are issues (respectively bug >reports) that are important for the users, but not interesting for the >developers. How do we motivate developers to work on _these_ issues? > >In project of volunteers we haven't hard arguments to say what one >"has" >to do (like salary, promotion, more things that work well in the >private >economy business). > >But in general, I would also expect that there is a base of >self-motivation and an eye for the important things. > >> btw: >> A spontaneous suggestion for (b) >> >> We could put 50 issues to vote for each release of OO separately and >fix the 10 which get the most votes from users. >> By this I do not mean to fix only 10 bugs per release, but the >developer's willingness to fix 10 specific bugs, which interest the >users, in addition to fixed, no matter whether the developers keep >these bugs important. > >The votes can be a good start. To generate a list of intersting and >valuable (for the users) things to fix or implement. > >Marcus > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >For additional commands, e-mail: dev-h...@openoffice.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
