Might sound better as "contributing to".

exists -> exist

Thank you so much, Bjwebb!

It's now fixed in the repository.

I'm working on the fifth draft because I introduced two important sections that were missing in the fourth one. More on this soon.

Cheers!

Hello.

I thought I was not missing something, but I was wrong. Here's the fifth working draft: http://test.getgnulinux.org/temp/collaboration_guidelines/draft5/

Major changes:
+ Fixed many errata.
+ Added Locking and unlocking a file in a repository
+ Added why Translators should not use WYSIWYG editors.
+ Added Translating XML-based files.
+ Added what translators should never modify.

Complete changelog.

I think I was very demanding in several parts (again), but I'm not sure, what do you think? Please don't hesitate to tell me.

What do you think about the guidelines? Did I miss something? Should I removed something? Should I modify something? What about the HOWTOs?

By the way, doesn't "Collaborator Guide" sound better? Do you have a better title?

Once these guidelines are approved, we can start looking for more contributors, like more translators, ambassadors and people with access to the FSL repo.

Cheers!

I've been thinking that it makes no sense to include the section entitle "What anyone can do to help us out" in the Collaboration Guidelines. This guide is aimed at internal collaborators, not external ones.

That section's contents may easily be merged into http://planet.getgnulinux.org/help (actually, that section only extends this webpage).

What do you think about removing that section from the Collaborator Guidelines?

Don't fear me. I don't eat people.

If you think the guidelines are useless or dislike the overall work, please don't hesitate to say so.

Cheers!

I'll take your word for not eating us and step in ;-) Sorry for being late.

I have gone through everything I think and here are my remarks:

• Great work, and the part on SVN is especially great (screenshots and all). I really don't think it is a waste of time at all.
• The main problem is the tone generally - often it's quite severe and authoritative, when in fact collaborators are doing us a favor, not the opposite ;-) There are places where I'll occasionally correct, but most of the time it's not highly important. It can be done as the guidelines evolve.

Now as for the smaller things, I think the "guidelines" title sounds better (less authoritative) - and personally I like the way the "helping us" section is built. The content is very nicely structured so readers can read quickly through anything, anyway.

How do you edit these files? I use Conglomerate, which is pretty unstable and I'm quite lost (can't even export these files to PDF). In fact I have made almost no progress on the GGL transition to XML - I'm stuck.

Hi, Olivier.

Please modify the guidelines to make them sound friendly or anything else you want to add/remove/change. I thought that too when I was rereading that document, but I was not sure if some things need not be mandatory. This is mainly why I wanted to get some feedback.

On the other hand, do you think the svn how-to is absolutely beginner friendly? I mean, did I explained everything from scratch without supposing the reader had previous skills on something similar? If you were new to svn, that guide would be enough to get you started?

Cheers!

Here I go, once again.

Sixth working draft.

Major changes:
+ Now the guidelines are friendly (from my viewpoint).
+ Removed what anyone can do to help us out. That fits in the "Help us" section of our planet.

Exact changes (from Rev. 32 to 36).

Unless someone disagrees, I consider this can be the final document (at last!).

Cheers!

Great, Gustavo...
I hope I can make the move to DocBook soon, so that collaboration can be made easier.