Mailing List Archive: Apache: Docs

To: Documentation Project Officer/Manager

Index | Next | Previous | View Threaded

nilgun at belgeler

May 6, 2008, 6:08 AM

Post #1 of 11 (201 views)
Permalink

To: Documentation Project Officer/Manager

Hi,

The person whose name appears next to "Turkish" in the list of
translation projects at your site (URL
http://httpd.apache.org/docs-project/translations.html )
has done no actual work in this project. If he is listed there
just because he translated some error messages or as such,
we (the actual translators) will not hesitate to leave
where we are ignored.

Or if you decide to list the actual translators, please apply
the patch I sent to the list on April 1st, 2008.

Please clearly state your decision in this regard. Depending on
that I will review my decision not send any further Turkish
translations.

Best regards,
Nilgün Belma Bugüner

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe[at]httpd.apache.org
For additional commands, e-mail: docs-help[at]httpd.apache.org

nd at perlig

May 6, 2008, 7:03 AM

Post #2 of 11 (190 views)
Permalink

Re: To: Documentation Project Officer/Manager [In reply to]

* Nilgün Belma Bugüner wrote:

> To: Documentation Project Officer/Manager

There is no such instance here. The whole docs work is (like the software
itself) a group effort of volunteers.

> The person whose name appears next to "Turkish" in the list of
> translation projects at your site (URL
> http://httpd.apache.org/docs-project/translations.html )
> has done no actual work in this project. If he is listed there
> just because he translated some error messages or as such,
> we (the actual translators) will not hesitate to leave
> where we are ignored.
>
> Or if you decide to list the actual translators, please apply
> the patch I sent to the list on April 1st, 2008.
>
> Please clearly state your decision in this regard. Depending on
> that I will review my decision not send any further Turkish
> translations.

Oh my, calm down.

You are not ignored. As far as I know every translation you submitted here
was committed so far. If something was ignored it was by accident and not
on purpose (people simply miss stuff, because they're not reading the list
each and every day). The solution is simple: Just resend it and nag about
it (but using a moderate tone is pretty helpful).
People will react as soon as they have some time to spare for it.

I'm not grepping the list archives now. Please resend your translations.html
patch and I'll apply it.

nd

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe[at]httpd.apache.org
For additional commands, e-mail: docs-help[at]httpd.apache.org

nilgun at belgeler

May 6, 2008, 7:20 AM

Post #3 of 11 (191 views)
Permalink

Re: To: Documentation Project Officer/Manager - patch [In reply to]

Salı 06 May 2008 17:03 sularında, André Malo şunları yazmıştı:
> I'm not grepping the list archives now. Please resend your translations.html
> patch and I'll apply it.
>

Attachments:

translations.xml.patch (0.60 KB)

nd at perlig

May 6, 2008, 7:52 AM

Post #4 of 11 (190 views)
Permalink

Re: To: Documentation Project Officer/Manager - patch [In reply to]

* Nilgün Belma Bugüner wrote:

> Salı 06 May 2008 17:03 sularında, André Malo şunları yazmıştı:
> > I'm not grepping the list archives now. Please resend your
> > translations.html patch and I'll apply it.

committed now. It'll take some time until the website is updated.

nd

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe[at]httpd.apache.org
For additional commands, e-mail: docs-help[at]httpd.apache.org

nilgun at belgeler

May 7, 2008, 2:22 AM

Post #5 of 11 (184 views)
Permalink

Re: To: Documentation Project Officer/Manager [In reply to]

Salı 06 May 2008 17:03 sularında, André Malo şunları yazmıştı:
> You are not ignored. As far as I know every translation you submitted here
> was committed so far. If something was ignored it was by accident and not
> on purpose (people simply miss stuff, because they're not reading the list
> each and every day). The solution is simple: Just resend it and nag about
> it (but using a moderate tone is pretty helpful).
> People will react as soon as they have some time to spare for it.
>
OK.
This is not a high traffic list. It will take no time even if you read
the entire communication within the last month (except for some recent
messages irrelevant to the list). I try to keep my messages short.

Being at it, please commit the attached files. These were missing in the
packages committed by Tony Stevenson the last time.

Best regards,
Nilgün

Attachments:

Turkish-files-080605.tar.bz2 (10.7 KB)

tony at pc-tony

May 7, 2008, 6:32 AM

Post #6 of 11 (182 views)
Permalink

Re: To: Documentation Project Officer/Manager [In reply to]

Nilgün Belma Bugüner wrote:
> Salı 06 May 2008 17:03 sularında, André Malo şunları yazmıştı:
>> You are not ignored. As far as I know every translation you submitted here
>> was committed so far. If something was ignored it was by accident and not
>> on purpose (people simply miss stuff, because they're not reading the list
>> each and every day). The solution is simple: Just resend it and nag about
>> it (but using a moderate tone is pretty helpful).
>> People will react as soon as they have some time to spare for it.
>>
> OK.
> This is not a high traffic list. It will take no time even if you read
> the entire communication within the last month (except for some recent
> messages irrelevant to the list). I try to keep my messages short.

You're right it is not a high volume traffic list. However we all still
have other things to do, I for one don't read all the lists I am
subscribed to every day. I may wait a day or so, especially for the
higher volume lists.

>
> Being at it, please commit the attached files. These were missing in the
> packages committed by Tony Stevenson the last time.
>

As I asked you last time, can you please submit patch files NOT complete
xml files. This way it allows all readers of the list to quickly and
easily see the differences in the files, even if these are new files.
People can then comment on the patch if the change warrants such a
discussion.

Now we have to manually diff the files, produce a patch, apply the
patch, and then commit it.

Not all patches are committed immediately. We will often leave larger
changes on list for a day or two to see if anyone raises any objections
before committing them.

Please resend as an SVN patch, that can be easily used by other readers
of the list. Once I see this I will be happy to apply and commit your
changes.

I apologise for missing this last time around, however I was trying to
get you to submit patches, and I guess this got missed in the mix.

--Tony

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe[at]httpd.apache.org
For additional commands, e-mail: docs-help[at]httpd.apache.org

nilgun at belgeler

May 7, 2008, 6:37 AM

Post #7 of 11 (180 views)
Permalink

Re: To: Documentation Project Officer/Manager [In reply to]

Çarşamba 07 May 2008 16:32 sularında, Tony Stevenson şunları yazmıştı:
> Nilgün Belma Bugüner wrote:
> > Salı 06 May 2008 17:03 sularında, André Malo şunları yazmıştı:
> >> You are not ignored. As far as I know every translation you submitted here
> >> was committed so far. If something was ignored it was by accident and not
> >> on purpose (people simply miss stuff, because they're not reading the list
> >> each and every day). The solution is simple: Just resend it and nag about
> >> it (but using a moderate tone is pretty helpful).
> >> People will react as soon as they have some time to spare for it.
> >>
> > OK.
> > This is not a high traffic list. It will take no time even if you read
> > the entire communication within the last month (except for some recent
> > messages irrelevant to the list). I try to keep my messages short.
>
> You're right it is not a high volume traffic list. However we all still
> have other things to do, I for one don't read all the lists I am
> subscribed to every day. I may wait a day or so, especially for the
> higher volume lists.
>
>
>
> >
> > Being at it, please commit the attached files. These were missing in the
> > packages committed by Tony Stevenson the last time.
> >
>
> As I asked you last time, can you please submit patch files NOT complete
> xml files. This way it allows all readers of the list to quickly and
> easily see the differences in the files, even if these are new files.
> People can then comment on the patch if the change warrants such a
> discussion.
>
> Now we have to manually diff the files, produce a patch, apply the
> patch, and then commit it.
>
> Not all patches are committed immediately. We will often leave larger
> changes on list for a day or two to see if anyone raises any objections
> before committing them.
>
> Please resend as an SVN patch, that can be easily used by other readers
> of the list. Once I see this I will be happy to apply and commit your
> changes.
>
> I apologise for missing this last time around, however I was trying to
> get you to submit patches, and I guess this got missed in the mix.
>
>
Please, you will not ask me create patches with svn diff for files
that do not exist in the repository.

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe[at]httpd.apache.org
For additional commands, e-mail: docs-help[at]httpd.apache.org

tony at pc-tony

May 7, 2008, 6:42 AM

Post #8 of 11 (182 views)
Permalink

Re: To: Documentation Project Officer/Manager [In reply to]

>>
> Please, you will not ask me create patches with svn diff for files
> that do not exist in the repository.

Actually, yes I will. How do I know they don't exist in repository until
I go and manually check?

As I said earlier this allows for a quick glance over the contents, and
the changes (even if it is a new file), within the email. I don't need
to fire up any clients an check. This will allow me to object to any
changes that I may not agree with.

We all submit patches to the list when it is a major change. Even when
we have commit access. That is the way we operate.

--Tony

>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docs-unsubscribe[at]httpd.apache.org
> For additional commands, e-mail: docs-help[at]httpd.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe[at]httpd.apache.org
For additional commands, e-mail: docs-help[at]httpd.apache.org

nd at perlig

May 7, 2008, 7:11 AM

Post #9 of 11 (181 views)
Permalink

Re: To: Documentation Project Officer/Manager [In reply to]

* Tony Stevenson wrote:

> > Please, you will not ask me create patches with svn diff for files
> > that do not exist in the repository.
>
> Actually, yes I will. How do I know they don't exist in repository until
> I go and manually check?
>
> As I said earlier this allows for a quick glance over the contents, and
> the changes (even if it is a new file), within the email. I don't need
> to fire up any clients an check. This will allow me to object to any
> changes that I may not agree with.
>
> We all submit patches to the list when it is a major change. Even when
> we have commit access. That is the way we operate.

As I don't see much sense in supplying diffs for completely new files
either, I'd like to suggest a compromise here. Let's just mark new files in
the submission mails clearly as such and everything else as patches. I
think, this should suffice everyone's needs.

nd

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe[at]httpd.apache.org
For additional commands, e-mail: docs-help[at]httpd.apache.org

tony at pc-tony

May 7, 2008, 7:16 AM

Post #10 of 11 (182 views)
Permalink

Re: To: Documentation Project Officer/Manager [In reply to]

André Malo wrote:
> * Tony Stevenson wrote:
>
>
>>> Please, you will not ask me create patches with svn diff for files
>>> that do not exist in the repository.
>> Actually, yes I will. How do I know they don't exist in repository until
>> I go and manually check?
>>
>> As I said earlier this allows for a quick glance over the contents, and
>> the changes (even if it is a new file), within the email. I don't need
>> to fire up any clients an check. This will allow me to object to any
>> changes that I may not agree with.
>>
>> We all submit patches to the list when it is a major change. Even when
>> we have commit access. That is the way we operate.
>
> As I don't see much sense in supplying diffs for completely new files
> either, I'd like to suggest a compromise here. Let's just mark new files in
> the submission mails clearly as such and everything else as patches. I
> think, this should suffice everyone's needs.
>

Fair enough, I am just repeating what I was told 'back in the day'

Tony

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe[at]httpd.apache.org
For additional commands, e-mail: docs-help[at]httpd.apache.org

nd at perlig

May 7, 2008, 9:38 AM

Post #11 of 11 (176 views)
Permalink

Re: To: Documentation Project Officer/Manager [In reply to]

* Tony Stevenson wrote:

> André Malo wrote:
> > * Tony Stevenson wrote:
> >>> Please, you will not ask me create patches with svn diff for files
> >>> that do not exist in the repository.
> >>
> >> Actually, yes I will. How do I know they don't exist in repository
> >> until I go and manually check?
> >>
> >> As I said earlier this allows for a quick glance over the contents,
> >> and the changes (even if it is a new file), within the email. I don't
> >> need to fire up any clients an check. This will allow me to object to
> >> any changes that I may not agree with.
> >>
> >> We all submit patches to the list when it is a major change. Even
> >> when we have commit access. That is the way we operate.
> >
> > As I don't see much sense in supplying diffs for completely new files
> > either, I'd like to suggest a compromise here. Let's just mark new
> > files in the submission mails clearly as such and everything else as
> > patches. I think, this should suffice everyone's needs.
>
> Fair enough, I am just repeating what I was told 'back in the day'

I see it that way: The one who commits it, decides how it's most effective
for him. A consensus is fine, but in this situation - if people doing the
work accept the input as files, nobody will stop them ;-)

On the other hand, I don't believe that a consensus can (nor should) be
reached for the personal way of working. This should be left for stuff
which affects more people.

nd

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe[at]httpd.apache.org
For additional commands, e-mail: docs-help[at]httpd.apache.org

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com