> -Original Message-
> From: Rob Weir [mailto:robw...@apache.org]
> This should be possible. Right now I'm mainly gathering ideas and
> feedback. Then I can propose some specific wording. If that is good,
> then we can think about translations.
Rob,
I would really like to to help,
On 16/11/2012 jan iversen wrote:
There is a nice example of cooperation on l10n, where the project lead of
libreOffice uses the list to have a volunteer translate non-AOO files to
greek (at least they do not carry the AOO license header).
Let's avoid dangerous misunderstandings. The software pr
There is a nice example of cooperation on l10n, where the project lead of
libreOffice uses the list to have a volunteer translate non-AOO files to
greek (at least they do not carry the AOO license header).
At least to avoid misunderstandings, I think Rob´s thought are highly
required so everybody
Rob Weir wrote:
The problem: Many (most?) open source contributors are not opposed to
AOO or LO. They are just interested in helping out. If they produce
a patch, or documentation, fix a bug or add a translation, they want
to maximize the public good that comes from that work.
You are writin
On Thu, Nov 15, 2012 at 4:16 AM, Jörg Schmidt wrote:
> Hello,
>
>> I've heard some discussion and interest in this topic off-list. There
>> has been some practical experience, but nothing that we've written
>> down or promoted. I'd be interested in seeing if we can come up with
>> some solid bes
Hello,
> I've heard some discussion and interest in this topic off-list. There
> has been some practical experience, but nothing that we've written
> down or promoted. I'd be interested in seeing if we can come up with
> some solid best practices.
>
> The problem: Many (most?) open source cont
I learned something again tonight. Since there is an audit trail then your
idea is perfect and first of all easy to handle.
Jan.
On 14 November 2012 20:21, Rob Weir wrote:
> On Wed, Nov 14, 2012 at 2:12 PM, jan iversen
> wrote:
> > On 14 November 2012 20:01, Rob Weir wrote:
> >
> >> On Wed, N
On Wed, Nov 14, 2012 at 2:12 PM, jan iversen wrote:
> On 14 November 2012 20:01, Rob Weir wrote:
>
>> On Wed, Nov 14, 2012 at 1:57 PM, jan iversen
>> wrote:
>> > +1 in general to your ideas, it would be VERY nice to have an easy way,
>> and
>> > the more we all do to make it easy the more develo
On 14 November 2012 20:01, Rob Weir wrote:
> On Wed, Nov 14, 2012 at 1:57 PM, jan iversen
> wrote:
> > +1 in general to your ideas, it would be VERY nice to have an easy way,
> and
> > the more we all do to make it easy the more developers will work for both
> > projects. I do however have one q
On Wed, Nov 14, 2012 at 1:57 PM, jan iversen wrote:
> +1 in general to your ideas, it would be VERY nice to have an easy way, and
> the more we all do to make it easy the more developers will work for both
> projects. I do however have one question.
>
> Regarding the mark #AOOCONTRIBUTION. It an A
+1 in general to your ideas, it would be VERY nice to have an easy way, and
the more we all do to make it easy the more developers will work for both
projects. I do however have one question.
Regarding the mark #AOOCONTRIBUTION. It an AOO committer take the code and
integrate it, would that not be
I've heard some discussion and interest in this topic off-list. There
has been some practical experience, but nothing that we've written
down or promoted. I'd be interested in seeing if we can come up with
some solid best practices.
The problem: Many (most?) open source contributors are not opp
12 matches
Mail list logo
