On Tue, Aug 6, 2013 at 10:01 AM, RA Stehmann
<anw...@rechtsanwalt-stehmann.de> wrote:
> On 06.08.2013 15:43, Jürgen Schmidt wrote:
>
>>> I think it is more "tact" than "luck".  But we have had some success
>>> in making such requests in the past, generally quiet requests directly
>>> to the developer.  Most open source developers write code because they
>>> want it to be used and for people to benefit from it.  So if you give
>>> them an opportunity for their code to be even more widely used, this
>>> aligns with their goals as well.  But such requests must be made
>>> quietly, via private email, since there is a lot of peer pressure to
>>> be uncooperative with Apache.
>>
>> mmh, I don't like this under the hood tactic, I would prefer a public
>> blog post to invite developers to provide their patches under ALv2 to
>> make them available to all users of any OpoenOffice derivative.
>>
>> Why not asking directly? I personally don't care about people shooting
>> against me, especially not if their reasons are so stupid and against my
>> understanding of open source.
>>
>> Really open minded people will see the benefit of contributing to the
>> core and fix problems where the code intially comes from.
>
> An under the hood tactic wouldn't work, because the AOO sources are
> open, so everybody can see contributions coming from "LibreOffice
> developers". You can't keep the contributions secret.
>

Actually, it does work.   It has happened on several occasions, even
with AOO 4.0.

I think you are mixing up two things:  asking privately and
contributing publicly.  These are not contradictory.

In any case, I'd challenge anyone to point to an example where the
contrary approach worked:  asking publicly on the LO mailing list.

-Rob


> So IMO ask them in an open way - hoping to find open minded people.
>
> Regards
> Michael
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Reply via email to