How long to become active? (unable to use git)

I am a new member. I used the name Andrew Pitonyak. I failed to use git
to obtain the latest copy of the documentation

$ 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).
fatal: The remote end hung up unexpectedly

I used ssh -v to check for possible reasons:


$ ssh -v AndrewPitonyak@git.gnome.org
OpenSSH_5.1p1, OpenSSL 0.9.8g 19 Oct 2007
debug1: Reading configuration data /andrew0/home/andy/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to git.gnome.org [209.132.176.202] port 22.
debug1: Connection established.
debug1: identity file /andrew0/home/andy/.ssh/identity type -1
debug1: identity file /andrew0/home/andy/.ssh/id_rsa type 1
debug1: identity file /andrew0/home/andy/.ssh/id_dsa type 2
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.3
debug1: match: OpenSSH_4.3 pat OpenSSH_4*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'git.gnome.org' is known and matches the RSA host key.
debug1: Found key in /andrew0/home/andy/.ssh/known_hosts:3
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /andrew0/home/andy/.ssh/id_dsa
debug1: Authentications that can continue: publickey
debug1: Offering public key: /andrew0/home/andy/.ssh/id_rsa
debug1: Authentications that can continue: publickey
debug1: Trying private key: /andrew0/home/andy/.ssh/identity
debug1: No more authentication methods to try.
Permission denied (publickey).

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.

I have not done anything with github, if that is required.

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?

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.

> 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.


Sven

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.

Hi Andrew,

On Sun, Jun 21, 2009 at 07:52:20PM -0400, Andrew Douglas Pitonyak wrote:
> 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.
You could follow the following pages and try to setup yourself a sandbox
to play with. As Sven already indicated, you create yourself a clone of
manual on which everyone is working on:

git clone git://git.gnome.org/gimp-help-2

The relevant and helpful sites you want to look at:

http://docs.gimp.org/help.html
http://live.gnome.org/Git

> 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.
This is more developer centric.

> >> 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.
As an 'anonymous' contributor you can work on your created copy with
git. You can make commits to your local repository and you can send in
your changes to one of the authors or me (git format-patch creates a set
of patches which can be easily applied and verified).

> 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.
That is provided by git, which as I've mentioned above is more developer
centric. You probably need a bit of time to understand and use it.

Good luck :)

I will try to setup a local copy.... It appears to be working, but
download speed is affected by a serious live Fedora-11 upgrade that is
in-progress. I figured that I would try it to see if it is as painless
as they proclaim.... Life will be interesting.

Roman Joost wrote:
> Hi Andrew,
>
> On Sun, Jun 21, 2009 at 07:52:20PM -0400, Andrew Douglas Pitonyak wrote:
>
>> 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.
>>
> You could follow the following pages and try to setup yourself a sandbox
> to play with. As Sven already indicated, you create yourself a clone of
> manual on which everyone is working on:
>
> git clone git://git.gnome.org/gimp-help-2
>
> The relevant and helpful sites you want to look at:
>
> http://docs.gimp.org/help.html
> http://live.gnome.org/Git
>
>
>> 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.
>>
> This is more developer centric.
>
>
>>>> 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.
>>
> As an 'anonymous' contributor you can work on your created copy with
> git. You can make commits to your local repository and you can send in
> your changes to one of the authors or me (git format-patch creates a set
> of patches which can be easily applied and verified).
>
>
>> 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.
>>
> That is provided by git, which as I've mentioned above is more developer
> centric. You probably need a bit of time to understand and use it.
>
> Good luck :)
>