Re: [dev] Re: [marketing] extending the OpenOffice BugBounty Programm
John McCreesh wrote (6-2-2009 23:00) I would suggest contacting the folks at FOSDEM and getting them to photocopy and handout leaflets tomorrow... Since we are not finished yet ... But it's a good idea to announce it ... be aware, coming soon ... I'll do something for that. Thanks for the idea, John, Cor -- Cor Nouws-nl.OpenOffice.org marketing contact = "2008: The Year of 3" = www.nieuwsteoffice.nl = - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] extending the OpenOffice BugBounty Programm
Martin Hollmichel wrote:
Hi,
last year we initiated the bug bounty program ...
Are there any other ideas to make the Program more attractive ?
or should we stop this effort because it's hopeless ?
May I suggest that some of the bounty money, and/or equivalent time and
effort, might be better spent on lowering the entry barriers for newcomers?
Consider our target audience, those we're trying to attract. Are we
limiting our search to the pool of the Linux/SVN-capable? Or, do we want
to fish in the (much larger!) sea of Windows developers? The logic here
is, why are they developing under Windows? If we're offering money, we
should offer it to the money-hungry.
Windows developers would be expectably running Ms's latest-and-greatest,
Windows Vista (or W7 pre-releases). If they decide to take a look at
the code ("Do I want to get involved with this?"), they hit an immediate
barrier: the SVN folks only boast a client for WXP. A little of our
money here, or just a few friendly words, might help. (The developer
reaction we want to avoid is, "Oh, these kids are locked in their Linux
playpen. Forget it!")
Removing the next barrier -- allowing (and documenting!) OO.o
development under Windows -- involves significant (but not massive)
effort on our part. It should be readily doable (assuming a solution for
the SVN problem), since both the compilers and the product run under WV.
Resources expended on fixing particular bugs will fix those bugs, once.
Investing in process improvement should help us forever.
--
T. J. Frazier
Melbourne, FL
(TJFrazier on OO.o)
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] extending the OpenOffice BugBounty Programm
T. J. Frazier wrote:
Windows developers would be expectably running Ms's latest-and-greatest,
Windows Vista (or W7 pre-releases). If they decide to take a look at
the code ("Do I want to get involved with this?"), they hit an immediate
barrier: the SVN folks only boast a client for WXP. A little of our
money here, or just a few friendly words, might help. (The developer
reaction we want to avoid is, "Oh, these kids are locked in their Linux
playpen. Forget it!")
TortoiseSVN works on Windows Vista. There are a few known issues (see
http://tortoisesvn.net/vistaproblems), but none of them are showstoppers. So
this isn't a barrier.
Martin
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] extending the OpenOffice BugBounty Programm
Hi, Removing the next barrier -- allowing (and documenting!) OO.o development under Windows -- involves significant (but not massive) effort on our part. It should be readily doable (assuming a solution for the SVN problem), possible since a long time: http://wiki.services.openoffice.org/wiki/Building_OOo_with_Cygwin_on_Windows Best regards Max - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] extending the OpenOffice BugBounty Programm
Martin Whitaker schrieb:
T. J. Frazier wrote:
Windows developers would be expectably running Ms's
latest-and-greatest, Windows Vista (or W7 pre-releases). If they
decide to take a look at the code ("Do I want to get involved with
this?"), they hit an immediate barrier: the SVN folks only boast a
client for WXP. A little of our money here, or just a few friendly
words, might help. (The developer reaction we want to avoid is, "Oh,
these kids are locked in their Linux playpen. Forget it!")
TortoiseSVN works on Windows Vista. There are a few known issues (see
http://tortoisesvn.net/vistaproblems), but none of them are
showstoppers. So this isn't a barrier.
Martin
Hi,
you can also use putty to access svn via ssh. See the section
Windows ssh setup with putty on
http://wiki.services.openoffice.org/wiki/Setting_up_Subversion_Access
Regards,
Oliver
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
[dev] Patch is waiting review for >6 motnh - Issue 35579 (Calc).
Dear developers, please review and comment on latest patch in voted http://www.openoffice.org/issues/show_bug.cgi?id=35579. Thanks a lot. WBR, KP. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] extending the OpenOffice BugBounty Programm
Oliver Specht wrote:
Martin Whitaker schrieb:
T. J. Frazier wrote:
Windows developers would be expectably running Ms's
latest-and-greatest, Windows Vista (or W7 pre-releases). If they
decide to take a look at the code ("Do I want to get involved with
this?"), they hit an immediate barrier: the SVN folks only boast a
client for WXP. A little of our money here, or just a few friendly
words, might help. (The developer reaction we want to avoid is, "Oh,
these kids are locked in their Linux playpen. Forget it!")
TortoiseSVN works on Windows Vista. There are a few known issues (see
http://tortoisesvn.net/vistaproblems), but none of them are
showstoppers. So this isn't a barrier.
Martin
Hi,
you can also use putty to access svn via ssh. See the section
Windows ssh setup with putty on
http://wiki.services.openoffice.org/wiki/Setting_up_Subversion_Access
You can indeed, but I doubt you'll attract many Windows developers if you tell
them they need to use a CLI! The advantage of TortoiseSVN is that it
integrates into Windows Explorer, so the Windows users can stay in their
familiar environment.
Regards,
Martin
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
