Re: Change .page, see result

[Germán Poo-Caamaño]

Hi Hannie,

On Tue, 2017-12-05 at 17:37 +0100, Hannie Dumoleyn wrote:
> Op 05-12-17 om 12:24 schreef Ekaterina Gerasimova:
> > 
> > > What will happen if I commit/push the branch with the changed
> > > .page files I
> > > am happy with. Will they be added to gnome-user-docs (patches?).
> > > So far, I
> > > have only pushed the branch with changes to the nl.po file.
> > 
> > That is what will happen.
> > 
> > As this would be your first docs contribution, it would be better
> > if
> > you could push a branch for review or attach a patch to Bugzilla.
> > 
> > Generally, after seeing a few good patches and when I'm sure that
> > you're not breaking the build, I am likely to suggest that you
> > start
> > pushing minor fixes straight to master.
> > 
> 
> Hello Ekaterina,
> 
> I understand that it is better NOT to push the gnome-user-docs branch
> if I have changed .page files. Instead, I will attach the .page file
> (or part of it?) to a Bugzilla report (is that what you mean by
> "attaching a patch to Bugzilla?). I do not know how I can push a
> branch for review.

A patch is a representation of the minimal changes between your file(s)
and the one(s) in the repository. It allows people to focus only in the
changes, rather than looking through a whole file. With a little bit of
practice, you will get used to and you will find it handy (welcome to
the matrix! ;-)

That said, you may want to take a look at:
https://wiki.gnome.org/Newcomers/SubmitPatch

> I am currently trying to find out how things work. And I fully 
> understand that you will only allow me to push minor fixes straight
> to master after I have proven I can do it right. I will go through
> the buglist to see if I can fix some of them and send my changes, if
> any, to Bugzilla.

Another resource (perhaps not as detailed as you are asking) is:
https://wiki.gnome.org/DocumentationProject/Contributing

-- 
Germán Poo-Caamaño
http://calcifer.org/

signature.asc
Description: This is a digitally signed message part
___
gnome-doc-list mailing list
gnome-doc-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-doc-list

Re: Change .page, see result

[Hannie Dumoleyn]

Op 05-12-17 om 12:24 schreef Ekaterina Gerasimova:



What will happen if I commit/push the branch with the changed .page files I
am happy with. Will they be added to gnome-user-docs (patches?). So far, I
have only pushed the branch with changes to the nl.po file.

That is what will happen.

As this would be your first docs contribution, it would be better if
you could push a branch for review or attach a patch to Bugzilla.

Generally, after seeing a few good patches and when I'm sure that
you're not breaking the build, I am likely to suggest that you start
pushing minor fixes straight to master.


Hello Ekaterina,

I understand that it is better NOT to push the gnome-user-docs branch if 
I have changed .page files. Instead, I will attach the .page file (or 
part of it?) to a Bugzilla report (is that what you mean by "attaching a 
patch to Bugzilla?). I do not know how I can push a branch for review.


I am currently trying to find out how things work. And I fully 
understand that you will only allow me to push minor fixes straight to 
master after I have proven I can do it right. I will go through the 
buglist to see if I can fix some of them and send my changes, if any, to 
Bugzilla.


Hannie

___
gnome-doc-list mailing list
gnome-doc-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-doc-list

[quadrapassel] Created branch gnome-3-22

[Michael Catanzaro]

The branch 'gnome-3-22' was created pointing to:

 0e370fe... Remove myself from the doap file

___
gnome-doc-list mailing list
gnome-doc-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-doc-list

Re: Change .page, see result

[Ekaterina Gerasimova]

On 5 December 2017 at 10:09, Hannie Dumoleyn
 wrote:
> Op 04-12-17 om 19:34 schreef Gunnar Hjalmarsson:
>>
>> On 2017-12-04 17:59, Hannie Dumoleyn wrote:
>>>
>>> I do not know where the help files which I get when I press F1
>>> reside, and I do not want to mess them up. That is why I stored a
>>> copy of gs-use-system-search.page in a separate directory. I can
>>> experiment with it, without messing up the branch I downloaded.
>>
>>
>> Messing with the files you downloaded is exactly what you are supposed to
>> do. yelp can't read a file which isn't located together with the other files
>> (at least index.page must be present in the same directory).
>>
> Hello Gunnar,
>
> This is the right answer :) Thanks. I already thought it was not possible to
> copy a .page file to another directory and then see the result of the
> changes I made using yelp myname.page in the terminal. I wanted to use this
> method to be able to experiment with text, tags, code etc. without ruining
> the branch I downloaded.
>
> What I can do is this: experiment with .page files from the local branch,
> look at the results, and if something is wrong I can delete the branch on my
> local machine and download the branch again from git.
>
> What will happen if I commit/push the branch with the changed .page files I
> am happy with. Will they be added to gnome-user-docs (patches?). So far, I
> have only pushed the branch with changes to the nl.po file.

That is what will happen.

As this would be your first docs contribution, it would be better if
you could push a branch for review or attach a patch to Bugzilla.

Generally, after seeing a few good patches and when I'm sure that
you're not breaking the build, I am likely to suggest that you start
pushing minor fixes straight to master.

> @Andre: thanks for the tip (Ctrl L)
>
> @Jim: your information is helpful too. At this moment I am experimenting
> with .page files from gnome-user-docs and gnome-getting-started, but I may
> also want to work on documentation of applications like gedit.
>
> Hannie
>
>
> ___
> gnome-doc-list mailing list
> gnome-doc-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/gnome-doc-list
___
gnome-doc-list mailing list
gnome-doc-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-doc-list

Re: Change .page, see result

[Hannie Dumoleyn]

Op 04-12-17 om 19:34 schreef Gunnar Hjalmarsson:

On 2017-12-04 17:59, Hannie Dumoleyn wrote:

I do not know where the help files which I get when I press F1
reside, and I do not want to mess them up. That is why I stored a
copy of gs-use-system-search.page in a separate directory. I can
experiment with it, without messing up the branch I downloaded.


Messing with the files you downloaded is exactly what you are supposed 
to do. yelp can't read a file which isn't located together with the 
other files (at least index.page must be present in the same directory).



Hello Gunnar,

This is the right answer :) Thanks. I already thought it was not 
possible to copy a .page file to another directory and then see the 
result of the changes I made using yelp myname.page in the terminal. I 
wanted to use this method to be able to experiment with text, tags, code 
etc. without ruining the branch I downloaded.


What I can do is this: experiment with .page files from the local 
branch, look at the results, and if something is wrong I can delete the 
branch on my local machine and download the branch again from git.


What will happen if I commit/push the branch with the changed .page 
files I am happy with. Will they be added to gnome-user-docs (patches?). 
So far, I have only pushed the branch with changes to the nl.po file.


@Andre: thanks for the tip (Ctrl L)

@Jim: your information is helpful too. At this moment I am experimenting 
with .page files from gnome-user-docs and gnome-getting-started, but I 
may also want to work on documentation of applications like gedit.


Hannie

___
gnome-doc-list mailing list
gnome-doc-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-doc-list