[Gimp-docs] How long to become active? (unable to use git)

[Andrew Douglas Pitonyak]

Sven Neumann wrote:
> Hi,
>
> On Sun, 2009-06-21 at 16:31 -0400, Andrew Douglas Pitonyak wrote:
>
>   
>> $ git clone ssh://AndrewPitonyak@git.gnome.org/git/gimp-help-2
>> Initialized empty Git repository in 
>> /andrew0/home/andy/Devsrc/Gimp/DocDev/gimp-help-2/.git/
>> Permission denied (publickey).
>>     
>
> Do you have an account for git.gnome.org account at all?
>   

I created an account with "live.gnome.org". I suppose that I was under 
the mistaken impression that they were related.

> Note that you can create a clone without having an account. Just clone
> from git://git.gnome.org/gimp-help-2  You only need to use the ssh URL
> if you intend to push your changes to the master repository.
>   

The only reason that I cared was because I spent a few hours reading 
through GIMP documentation. I submitted changes directly to Roman Joost. 
Roman indicated that he would integrate my changes but that he was busy 
so that it would likely take weeks. I told him that I would attempt to 
integrate the changes myself. I also indicated that unless someone was 
familiar with my work that I expected that my proposed changes would be 
vetted. With the process in place here, it is not clear to me how that 
is done, but with GIT I believe that it is possible (and that it would 
be very difficult with SVN). Note that apart from my initial exchange 
with Roman, I have not had further communications, so I am NOT saying 
that Roman indicated that this would be possible. I was merely 
attempting to take the work off of him to integrate the changes that I 
had submitted.

All of my past experience has either been directly with publishers and 
editors (for published materials) and with the OpenOffice.org project, 
which uses an entirely different process.

>> Must I do something specific so that my newly created username 
>> AndrewPitonyak (user name for live.gnome.org) will work with my newly 
>> created id_dsa or id_rsa. Note that I did set the permissions to 600 for 
>> the files and 700 for ~/.ssh itself.
>>     
>
> Your account for the GNOME Wiki has nothing to do with having commit
> access to the GNOME git repository. The latter is reserved for people
> who have already submitted a reasonable number of patches and needs
> approval from module maintainers
I see. OK, I think that I understand that what I was attempting to do is 
not possible. I will send a message to Roman and mention that he should 
take care of integrating the changes that I submitted.

My initial submission was as follows:

(1) A PDF document illustrating the initial documentation (complete with 
links to the original)

(2) A description of why I disliked the original

(3) What I thought that it should say.

(4) Comments on why I prefer the new text (including links into the 
documentation if I am commenting on consistency with other sections of 
the documentation.

Needless to say, this form of submission is very time consuming to 
produce and time consuming to integrate. In the time that I created this 
document for a few pages, I could have done many more. Unfortunately, 
the current documentation does not appear to lend itself to a "lets 
track changes and insert comments" mode of collaborative editing that I 
have used on the other projects in which I have participated. In this 
mode, the document "approver" is able to very quickly what changes have 
been made along with comments. It is then easy to accept and/or reject 
very low level changes in the documentation. On the other hand, I am 
also well aware of the inherent difficulties with the product to then 
generate multiple output types as is easily done with the form used by GIMP.

I assume, then, that I have no need for access if this is the expected 
form of submission from me for now.

-- 
Andrew Pitonyak
My Macro Document: http://www.pitonyak.org/AndrewMacro.odt
My Book: http://www.hentzenwerke.com/catalog/oome.htm
Info:  http://www.pitonyak.org/oo.php
See Also: http://documentation.openoffice.org/HOW_TO/index.html