On May 16, 11:07 am, Christian Boos <[EMAIL PROTECTED]> wrote:
> Jeroen Ruigrok van der Werven wrote:

> > ... I am uncomfortable with especially when objections
> > seemingly are being overturned. And when that happens I'll just divert my
> > energy and attention elsewhere since my involvement will not matter anyway.
>
> It does matter. Sorry for all this mess (well, we didn't have a decent
> flame on Trac-dev since ages, so this is now fixed :-) ).

I, and no doubt everyone else in the project, agrees that your
contributions are very important. Please stay :-)

This turned out to be a long thread, sometimes deviating, and
sometimes bringing useful insights. To not leave everything hanging,
I'll attempt to summarize some conclusions from my perspective.

1) On the original issue of the thread: The improvements for tagging
text for translations are most welcome. Anything that can help make
sentences easier to understand and translate in the context of the po
file is a good thing. As I've started the nb_NO translation that is
what I found as well. Recent code changes to improve strings and
extractions seems useful, but if someone that knows could document
best practice for text tagging with various examples that would be
very helpful - "i18n for developers" would be much needed and
appreciated.

2) On the workflow and toolchain: The workflow stays according to the
needs of Jeroen to improve and coordinate contributions as before.
However, documentation of the workflow and toolchain is good, and
others should be able to recreate the exact same results if needed. Up-
to-date documentation is enough for now.

3) On committing: Separate changesets are made for feature and string
updates in the code base, re-generation of po files, and actual
contributions of translations. Try to group text updates and
regenerations when possible to avoid flooding the trunk as a courtecy
to all that need to review all the action in trunk.

4) On decisions: IRC has its benefits, but important discussions and
decisions happens on the mailing list. Full agreement.

5) On working with the project: We've re-confirmed that showing each
other respect is a good thing. Although the whole of the trunk is
indeed everyones shared responsibility, some are more equal than
others in certain areas (Animal Farm (tm)). Everyone on the team
should have quite an implicit understanding of what they are and how
they change over time. It is not a position of absolute power with
immunity against 'prosecution', it just means that we need to take
extra care to respect their needs and opinions.

Discussion and disagreement really is fine, and quite essential to
moving things forward in a project. However, participation and
involvement needs to be fun. We're all spending our time on this
project because we like the software, the people, the community and
for whatever other reasons we have. Please everyone, make sure it
stays fun for all involved!


:::simon

https://www.coderesort.com


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to