Re: git.lyx.org - developers! your ssh public key please

[Scott Kostyshak]

Good points, Yihui. I think you are right that on Github small
contributers would be more likely to stick around, improve their skills,
and possibly become more major contributors.

At some point, I think a transition would be wise in order to take
advantage of new tools that make things easier. I have no idea if that
point is now or in a few years. I think that depends on if someone
volunteers to take the lead.

Best,

Scott

On Sun, Feb 19, 2017 at 10:31:37PM -0600, Yihui Xie wrote:
> Hi Scott,
> 
> I agree with everything you said.. If it were five years ago, it would
> be very likely that I'd volunteer to help with the transition if the
> LyX development team want. Unfortunately I have got more open source
> projects to work on than I can really afford now.  That said, things
> can be a lot easier if we don't migrate old issues on Trac but just
> lock the system and direct future users to Github. I think moving the
> GIT repo to Github is very straightforward. The Wiki is a little
> tricky, and I don't know what to do with it. The lyx.org website can
> actually be switched to a Markdown-based website, too. For example,
> Hugo is an amazing static website generator. You can host the
> Markdown-based website on Github and build it to HTML automatically on
> push (e.g. you can hook the website repo with Netlify for free). There
> are just so many amazing modern free tools to use now, and the
> development team can spend much less time on maintaining all backend
> tools and servers. All I can promise now is that I can provide
> suggestions on tools/platforms to use, but I cannot take the lead to
> make the transition.
> 
> Bottom line: if we wish LyX longevity, I believe the right way is not
> to work as hard as the LyX team can, but to make it part of the life
> of as many users as possible. From my experience of merging probably a
> few hundreds pull requests on Github, if a user can contribute a typo
> fix easily (without having to email back and forth), it is likely that
> he/she can bring more significant fixes in the future, and the project
> is likely to be part of his/her life, because he/she feels encouraged
> to contribute.
> 
> Regards,
> Yihui
> --
> https://yihui.name
> 
> 
> On Sun, Feb 19, 2017 at 3:52 PM, Scott Kostyshak  wrote:
> > Thanks for the link, Yihui. It is an interesting read.
> >
> > First I want to say that I really don't know much about Git or our
> > current system, so I don't really trust myself on these matters. But
> > that said, I'll give my opinion.
> >
> > I think if everything were already on Github, it would be better. But I
> > think the transition to it would not be trivial. If someone were serious
> > about taking the lead and taking care of *everything* about the
> > transition, then I would personally be in favor of it.
> >
> > If no one steps up to take the lead, then I would not feel comfortable
> > if it were just a few people who all said "yeah I can help a little"
> > because I think things would get stuck in the mud and it would be a
> > mess. I really think we would need someone to lead.
> >
> > I don't think Yihui was volunteering to take the lead. If, however, he
> > were interested (and he should not be, because it would be a burden) in
> > accepting responsibility for everything, I would feel comfortable going
> > forward. This is because I know Yihui's work and trust him as a
> > developer and a person.
> >
> > As for the benefits (i.e., why I would be in favor if to my surprise
> > someone does want to accept responsibility for the transition), I see
> > several benefits:
> >
> > - Patches would not be left to rot. We could easily see in the "pull
> >   requests" tab which patches are still pending.
> > - There would be no down time. Our server is having problems. Just
> >   yesterday either trac was not working for me or it would take 1 minute
> >   to load a ticket.
> > - We don't have to worry about upgrading trac (our 0.12.5 version is
> >   based on the 0.12 major version, which was released in June 2010).
> > - An increase in minor contributions. I personally don't think the
> >   number of serious, long-time contributors will change as the result of
> >   the transition. But I do think that minor patches and "drive-by
> >   contributions", and e.g. fixes of typos would increase and I think
> >   that minor patches are important and can add up.
> > - We won't have problems with Trac losing all users (one time I think
> >   everyone had to re-register).
> > - In trac, it is hard to get a response from a reporter of a bug report
> >   from 5 years ago because they often have changed their email address.
> >   With Github, if they change the email address, they will still be
> >   notified.
> > - We will get more bug reports and enhancement requests. Although it is
> >   silly, I'm sure many people do not make bug reports because they do
> >   not want to register. Many are already registered on Github.
> > - Even if our server 

Re: git.lyx.org - developers! your ssh public key please

[Yihui Xie]

Hi Scott,

I agree with everything you said.. If it were five years ago, it would
be very likely that I'd volunteer to help with the transition if the
LyX development team want. Unfortunately I have got more open source
projects to work on than I can really afford now.  That said, things
can be a lot easier if we don't migrate old issues on Trac but just
lock the system and direct future users to Github. I think moving the
GIT repo to Github is very straightforward. The Wiki is a little
tricky, and I don't know what to do with it. The lyx.org website can
actually be switched to a Markdown-based website, too. For example,
Hugo is an amazing static website generator. You can host the
Markdown-based website on Github and build it to HTML automatically on
push (e.g. you can hook the website repo with Netlify for free). There
are just so many amazing modern free tools to use now, and the
development team can spend much less time on maintaining all backend
tools and servers. All I can promise now is that I can provide
suggestions on tools/platforms to use, but I cannot take the lead to
make the transition.

Bottom line: if we wish LyX longevity, I believe the right way is not
to work as hard as the LyX team can, but to make it part of the life
of as many users as possible. From my experience of merging probably a
few hundreds pull requests on Github, if a user can contribute a typo
fix easily (without having to email back and forth), it is likely that
he/she can bring more significant fixes in the future, and the project
is likely to be part of his/her life, because he/she feels encouraged
to contribute.

Regards,
Yihui
--
https://yihui.name


On Sun, Feb 19, 2017 at 3:52 PM, Scott Kostyshak  wrote:
> Thanks for the link, Yihui. It is an interesting read.
>
> First I want to say that I really don't know much about Git or our
> current system, so I don't really trust myself on these matters. But
> that said, I'll give my opinion.
>
> I think if everything were already on Github, it would be better. But I
> think the transition to it would not be trivial. If someone were serious
> about taking the lead and taking care of *everything* about the
> transition, then I would personally be in favor of it.
>
> If no one steps up to take the lead, then I would not feel comfortable
> if it were just a few people who all said "yeah I can help a little"
> because I think things would get stuck in the mud and it would be a
> mess. I really think we would need someone to lead.
>
> I don't think Yihui was volunteering to take the lead. If, however, he
> were interested (and he should not be, because it would be a burden) in
> accepting responsibility for everything, I would feel comfortable going
> forward. This is because I know Yihui's work and trust him as a
> developer and a person.
>
> As for the benefits (i.e., why I would be in favor if to my surprise
> someone does want to accept responsibility for the transition), I see
> several benefits:
>
> - Patches would not be left to rot. We could easily see in the "pull
>   requests" tab which patches are still pending.
> - There would be no down time. Our server is having problems. Just
>   yesterday either trac was not working for me or it would take 1 minute
>   to load a ticket.
> - We don't have to worry about upgrading trac (our 0.12.5 version is
>   based on the 0.12 major version, which was released in June 2010).
> - An increase in minor contributions. I personally don't think the
>   number of serious, long-time contributors will change as the result of
>   the transition. But I do think that minor patches and "drive-by
>   contributions", and e.g. fixes of typos would increase and I think
>   that minor patches are important and can add up.
> - We won't have problems with Trac losing all users (one time I think
>   everyone had to re-register).
> - In trac, it is hard to get a response from a reporter of a bug report
>   from 5 years ago because they often have changed their email address.
>   With Github, if they change the email address, they will still be
>   notified.
> - We will get more bug reports and enhancement requests. Although it is
>   silly, I'm sure many people do not make bug reports because they do
>   not want to register. Many are already registered on Github.
> - Even if our server did not have problems and were running like a
>   Porsche, why not take more stress from it by moving trac to Github
>   issues? It creates fewer problems in the future.
> - The features repository would be easier to handle and understand.
>   Everyone could just fork and make branches on their own personal
>   Github repository.
> - Several of our former Git gurus are not around often anymore. Vincent
>   and Lars would probably come to the rescue if we needed them, but it
>   would be nice not to have to depend on them. Nothing has really
>   broken, and whatever setup we're using feels robust to me, but it
>   still makes me a little worried.
>
> 

Re: git.lyx.org - developers! your ssh public key please

[Scott Kostyshak]

Thanks for the link, Yihui. It is an interesting read.

First I want to say that I really don't know much about Git or our
current system, so I don't really trust myself on these matters. But
that said, I'll give my opinion.

I think if everything were already on Github, it would be better. But I
think the transition to it would not be trivial. If someone were serious
about taking the lead and taking care of *everything* about the
transition, then I would personally be in favor of it.

If no one steps up to take the lead, then I would not feel comfortable
if it were just a few people who all said "yeah I can help a little"
because I think things would get stuck in the mud and it would be a
mess. I really think we would need someone to lead.

I don't think Yihui was volunteering to take the lead. If, however, he
were interested (and he should not be, because it would be a burden) in
accepting responsibility for everything, I would feel comfortable going
forward. This is because I know Yihui's work and trust him as a
developer and a person.

As for the benefits (i.e., why I would be in favor if to my surprise
someone does want to accept responsibility for the transition), I see
several benefits:

- Patches would not be left to rot. We could easily see in the "pull
  requests" tab which patches are still pending.
- There would be no down time. Our server is having problems. Just
  yesterday either trac was not working for me or it would take 1 minute
  to load a ticket.
- We don't have to worry about upgrading trac (our 0.12.5 version is
  based on the 0.12 major version, which was released in June 2010).
- An increase in minor contributions. I personally don't think the
  number of serious, long-time contributors will change as the result of
  the transition. But I do think that minor patches and "drive-by
  contributions", and e.g. fixes of typos would increase and I think
  that minor patches are important and can add up.
- We won't have problems with Trac losing all users (one time I think
  everyone had to re-register).
- In trac, it is hard to get a response from a reporter of a bug report
  from 5 years ago because they often have changed their email address.
  With Github, if they change the email address, they will still be
  notified.
- We will get more bug reports and enhancement requests. Although it is
  silly, I'm sure many people do not make bug reports because they do
  not want to register. Many are already registered on Github.
- Even if our server did not have problems and were running like a
  Porsche, why not take more stress from it by moving trac to Github
  issues? It creates fewer problems in the future.
- The features repository would be easier to handle and understand.
  Everyone could just fork and make branches on their own personal
  Github repository.
- Several of our former Git gurus are not around often anymore. Vincent
  and Lars would probably come to the rescue if we needed them, but it
  would be nice not to have to depend on them. Nothing has really
  broken, and whatever setup we're using feels robust to me, but it
  still makes me a little worried.

Despite the benefits I list above, I'm not interested in helping with
the transition. I don't have much time now, I don't know much about how
to do the transition, and I prefer to focus on other things.

Thank you for this discussion, Yihui. I always take your opinions very
seriously.

Scott


On Fri, Feb 17, 2017 at 11:26:14AM -0600, Yihui Xie wrote:
> Bumping a thread five years later... and just FYI, Python has moved to
> Github: https://github.com/python/cpython The story behind the move:
> https://snarky.ca/the-history-behind-the-decision-to-move-python-to-github/
> 
> I'm not sure if the LyX team knows more about Github or has more
> interest now, but I still believe Github is a better choice than
> maintaining everything (GIT, Wiki, Trac, and so on) by yourselves, and
> you are more likely to attract talents who are willing to contribute
> to this project in the future. That said, I'm not as eager as I was
> five years ago to convince you guys, since I rarely use LyX or LaTeX
> directly now (but LyX is still *the* best frontend for LaTeX in my
> mind). If there is an intention to move, great, and let me know if
> there is anything I can help, otherwise it is totally fine, too.
> Disclaimer: I'm not affiliated with Github in any sense. I'm just an
> ordinary user who happens to have benefited a lot from it when
> developing open source software.
> 
> Regards,
> Yihui
> --
> https://yihui.name
> 
> 
> On Fri, Mar 2, 2012 at 9:25 PM, Yihui Xie  wrote:
> > Well, I think I understand some of the advantages of GIT like easy
> > branching. I do not even bother to compare it to SVN because GIT is so
> > much better.
> >
> > I mean GitHub makes GIT even better; there are too many advantages and
> > I just list a few of them here:
> >
> > 1. developers manage their own SSH keys on GitHub and you do not need
> 

Re: git.lyx.org - developers! your ssh public key please

[Yihui Xie]

Bumping a thread five years later... and just FYI, Python has moved to
Github: https://github.com/python/cpython The story behind the move:
https://snarky.ca/the-history-behind-the-decision-to-move-python-to-github/

I'm not sure if the LyX team knows more about Github or has more
interest now, but I still believe Github is a better choice than
maintaining everything (GIT, Wiki, Trac, and so on) by yourselves, and
you are more likely to attract talents who are willing to contribute
to this project in the future. That said, I'm not as eager as I was
five years ago to convince you guys, since I rarely use LyX or LaTeX
directly now (but LyX is still *the* best frontend for LaTeX in my
mind). If there is an intention to move, great, and let me know if
there is anything I can help, otherwise it is totally fine, too.
Disclaimer: I'm not affiliated with Github in any sense. I'm just an
ordinary user who happens to have benefited a lot from it when
developing open source software.

Regards,
Yihui
--
https://yihui.name


On Fri, Mar 2, 2012 at 9:25 PM, Yihui Xie  wrote:
> Well, I think I understand some of the advantages of GIT like easy
> branching. I do not even bother to compare it to SVN because GIT is so
> much better.
>
> I mean GitHub makes GIT even better; there are too many advantages and
> I just list a few of them here:
>
> 1. developers manage their own SSH keys on GitHub and you do not need
> to ask them to submit their public keys to you;
>
> 2. people who are not in the developer team can fork the project with
> one-click to their own repositories, change the code and send pull
> request online (instead of emailing patches) so that you can review
> the patch online; a very critical feature here is you can _discuss_
> the code line by line with the one who submit this patch -- comments
> can be made in-between the code lines; if you are not satisfactory
> with the patch, you can require one to revise the code and resubmit;
> this process can go on and on until you are satisfied and accept the
> patch; see here for an example of my own:
> https://github.com/ramnathv/knitr/commit/33a75f4029
>
> Personally I believe it is very inefficient to email patches and it is
> so inconvenient to discuss code in emails. If people send me pull
> requests on GitHub, I may merge them in a few minutes, but patches in
> email often lay in my inbox for months.
>
> 3. you can either discuss on GitHub pages, or directly reply the email
> notifications from GitHub about the discussions; the email will go to
> GitHub. This is unlike trac, you have to go to the web page to discuss
> (maybe there are configurations that enable trac to manage emails, but
> I did not see this happen in LyX SVN ages).
>
> 4. bugs tracker; they call "issues", which are also closely tied to
> code; you can write a commit message like "fixed #43" to fix the issue
> 43 (the issue will be closed and there will be a reference to the
> commit in the issue page); it is also more convenient to manage bug
> reports: one thing I do not like trac is I'm unable to change the
> report after I submit it (e.g. I want to add more code examples, or
> fix typos).
>
> 5. wiki support: you can manage wiki pages by GIT, or edit them
> online; the default aesthetics looks good (e.g.
> https://github.com/yihui/formatR/wiki)
>
> 6. GitHub pages: you can even manage your website on GitHub by
> creating a branch named "gh-pages" and use the Jekyll engine to
> compile markdown files to HTML (this is automatic on GitHub so you
> only maintain lightweight markdown files); it is easy to setup and
> after that, you can manage the website by GIT (see, everything on
> GitHub can go to GIT); sorry to use my own projects as examples again,
> but you can see the source
> https://github.com/yihui/knitr/tree/gh-pages of the site
> http://yihui.name/knitr/ for example
>
> Here is a recent article "Lord of the Files: How GitHub Tamed Free
> Software (And More)":
> http://www.wired.com/wiredenterprise/2012/02/github/all/1
>
> In short, this is approximately true for me: GitHub = GIT + Trac +
> Wiki + Web and all are based on GIT. Anyway, this is just my 2 cents
> when I saw the transition from SVN to GIT, and of course you are free
> to invest time and efforts in setting up your own server.
>
> Regards,
> Yihui
> --
> Yihui Xie 
> Phone: 515-294-2465 Web: http://yihui.name
> Department of Statistics, Iowa State University
> 2215 Snedecor Hall, Ames, IA
>
>
>
> On Fri, Mar 2, 2012 at 4:01 AM, Vincent van Ravesteijn  wrote:
>> Op 2-3-2012 7:35, Yihui Xie schreef:
>>>
>>> I was actually wondering why not move to GitHub directly since
>>> everything is ready there and it saves a huge amount of server admin
>>> efforts... Maybe I missed some conversations earlier, but IMHO GitHub
>>> makes collaborations way way easier.
>>>
>>
>> In what sense does it make it easier ? Pull requests are nice, but this
>> requires all developers to read the 

Re: git.lyx.org - developers! your ssh public key please

[Lars Gullik Bjønnes]

On Sun, Mar 4, 2012 at 01:23, Uwe Stöhr uwesto...@web.de wrote:
 Am 03.03.2012 14:32, schrieb Vincent van Ravesteijn:

 Many thanks for the quick reply!


 You'll get a message: Your public key has been saved in .


 Yes, but the file is not stored in the given folder. However, 2 files were
 now created and I guess that I have to send Lars the one with the suffix
 .pub.

 One further question: I own several PCs and when I'm abroad. I also want to
 check out or commit to LyX. How is that possible? The generated public
 SSH-key seems to be connected to my PC because it contains the PC name.

The identificator in the ssh key file is mostly for you, it is not
connecting the key
machine where it was created.

I have several key pairs that I use, some of them are duplicated on several
machines. So you can copy the key-pair from you PC to your laptop, either using
same names (mean that the copied keys will be the primaries on the
laptop as well)
or give them different names (and thus setup for multiple key pairs on
the laptop)

-- 
        Lgb

Re: git.lyx.org - developers! your ssh public key please

[Lars Gullik Bjønnes]

On Sat, Mar 3, 2012 at 18:08, Yihui Xie x...@yihui.name wrote:
 This is expected to me: programmers tend to do everything by
 themselves. I cannot promise all the conversions, but GitHub supports
 importing from an svn repo with one click, so if you want to move
 there, I can certainly do it.

Albeit this seems very easy, it will also not be a very good conversion.
To make our repo convert nicely you have to use some grafting to connect
branches/tags correctly together, and also inject proper git tags where
subversion tags are used. Furtunately I have already done that work.

 For the rest of the jobs, they require
 more time, but I believe after the conversion it will be easier to
 maintain since almost everything is under GIT. I'm willing to
 contribute some time if you want, but from the replies I have got so
 far, I guess I can give up the attempt to convince you now.

Let's do the git on our own server dance first. As said if we later on
want to move to a hosted git service that will be very easy.

-- 
        Lgb

Re: git.lyx.org - developers! your ssh public key please

[Yihui Xie]

Oh, yes, absolutely. Thanks again for your hard work!

Regards,
Yihui
--
Yihui Xie xieyi...@gmail.com
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA



On Sun, Mar 4, 2012 at 6:54 AM, Lars Gullik Bjønnes lar...@gullik.org wrote:

 Let's do the git on our own server dance first. As said if we later on
 want to move to a hosted git service that will be very easy.

 --
         Lgb

Re: git.lyx.org - developers! your ssh public key please

[Lars Gullik Bjønnes]

On Sun, Mar 4, 2012 at 01:23, Uwe Stöhr  wrote:
> Am 03.03.2012 14:32, schrieb Vincent van Ravesteijn:
>
> Many thanks for the quick reply!
>
>
>> You'll get a message: "Your public key has been saved in ."
>
>
> Yes, but the file is not stored in the given folder. However, 2 files were
> now created and I guess that I have to send Lars the one with the suffix
> ".pub".
>
> One further question: I own several PCs and when I'm abroad. I also want to
> check out or commit to LyX. How is that possible? The generated public
> SSH-key seems to be connected to my PC because it contains the PC name.

The identificator in the ssh key file is mostly for you, it is not
connecting the key
machine where it was created.

I have several key pairs that I use, some of them are duplicated on several
machines. So you can copy the key-pair from you PC to your laptop, either using
same names (mean that the copied keys will be the primaries on the
laptop as well)
or give them different names (and thus setup for multiple key pairs on
the laptop)

-- 
        Lgb

Re: git.lyx.org - developers! your ssh public key please

[Lars Gullik Bjønnes]

On Sat, Mar 3, 2012 at 18:08, Yihui Xie  wrote:
> This is expected to me: programmers tend to do everything by
> themselves. I cannot promise all the conversions, but GitHub supports
> importing from an svn repo with one click, so if you want to move
> there, I can certainly do it.

Albeit this seems very easy, it will also not be a very good conversion.
To make our repo convert nicely you have to use some grafting to connect
branches/tags correctly together, and also inject proper git tags where
subversion tags are used. Furtunately I have already done that work.

> For the rest of the jobs, they require
> more time, but I believe after the conversion it will be easier to
> maintain since almost everything is under GIT. I'm willing to
> contribute some time if you want, but from the replies I have got so
> far, I guess I can give up the attempt to convince you now.

Let's do the "git on our own server" dance first. As said if we later on
want to move to a hosted git service that will be very easy.

-- 
        Lgb

Re: git.lyx.org - developers! your ssh public key please

[Yihui Xie]

Oh, yes, absolutely. Thanks again for your hard work!

Regards,
Yihui
--
Yihui Xie 
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA



On Sun, Mar 4, 2012 at 6:54 AM, Lars Gullik Bjønnes  wrote:
>
> Let's do the "git on our own server" dance first. As said if we later on
> want to move to a hosted git service that will be very easy.
>
> --
>         Lgb

Re: Re: Re: git.lyx.org - developers! your ssh public key please

[Kornel Benko]

Am Samstag, 3. März 2012 um 10:27:36, schrieb Kornel Benko kor...@lyx.org
 Attached as requested
 
   Kornel

Sorry, this time better ...ssh-dss 
B3NzaC1kc3MAAACBANtpQPjvzWLv45P5qzsrqzGUezRxDW59m2KQ7o9Vn0XVO4pB/f7iitRWV4ERrYK+8p4p5IoQzaV8QhsiOt4hZLnUkkjYcMqDo7MOgbsX1PsnFTI7j34iqW9H+JrlY8AXcjD9Gxr+nE8I+9wdr2A6mQskOYW90kjCkM60Bj6ngWoVFQDUHF6gQjywk6j1cH9ENxu6FJ0m0wAAAIBf6fnD+dWjsoy+i/uf64kzfEq+zyViGhBOxu+rSj1cQrGQxaTlEjwOtsDPfNyJd7h6tuTT9WMJa9A9kX5Oi3qK9Qy5tvgWLFW6peEs0fFZC92WkTExog9u80DNcIAKIhGNM5AxiomylAvM1E4xHjP/zI2ndjAZUtjPFS8fNjif3wAAAIEAn2ixSmKlo97zevXAD8II3G6MwhttmngvUvFy1X9ucyg8tub6Y5oa7uUBY6XZzsgZWZ3VTNSAMHOKDo7RwxzDGy4gTdre4bMD7E5BGZG5K9A/CBRpVSWrDA6gSB/0lJjJwrcPPq+mESSUitMaYOLZwuLiwere6jxrcthN+h07wdg=
 kornel@korben


signature.asc
Description: This is a digitally signed message part.

Re: git.lyx.org - developers! your ssh public key please

[Lars Gullik Bjønnes]

 In short, this is approximately true for me: GitHub = GIT + Trac +
 Wiki + Web and all are based on GIT. Anyway, this is just my 2 cents
 when I saw the transition from SVN to GIT, and of course you are free
 to invest time and efforts in setting up your own server.

Will _you_ step up to do all the conversions needed?
We already have an extensive wiki, we have nice web pages
and a running bug tracker.

Setting up a gitolite server for git is easy. And it is not like we are
closing the door on a later move to some git hosting service.

-- 
        Lgb

Re: git.lyx.org - developers! your ssh public key please

[Lars Gullik Bjønnes]

On Sat, Mar 3, 2012 at 04:25, Yihui Xie x...@yihui.name wrote:
[...]
 Personally I believe it is very inefficient to email patches

In what way inefficient?

git send-email HEAD~3

to send the small patchset for commenting somewhere is not exactly hard.

 and it is
 so inconvenient to discuss code in emails.

I couldn't disagree more I think.

-- 
        Lgb

Re: git.lyx.org - developers! your ssh public key please

[Pavel Sanda]

Yihui Xie wrote:
 the code line by line with the one who submit this patch -- comments
 can be made in-between the code lines; if you are not satisfactory
 with the patch, you can require one to revise the code and resubmit;
 this process can go on and on until you are satisfied and accept the
 patch; see here for an example of my own:
 https://github.com/ramnathv/knitr/commit/33a75f4029
 
 Personally I believe it is very inefficient to email patches and it is
 so inconvenient to discuss code in emails.

Perhaps matter of taste - on contrary I found the discussion through
email conference much more convenient that web-based forums. Actually
anything web based is an order of magnitude slower for my mutt/vim
based fingers... 

Pavel

Re: git.lyx.org - developers! your ssh public key please

[Uwe Stöhr]

Am 02.03.2012 02:07, schrieb Lars Gullik Bjønnes:


I am not going to setup anonymous cloning right now, but I want
developers to send me their public ssh keys.


I never used SSH until now, so could anybody please give me a short 
introduction what I need to do?

thanks and regards
Uwe

Re: git.lyx.org - developers! your ssh public key please

[Vincent van Ravesteijn]

Op 3-3-2012 14:17, Uwe Stöhr schreef:

Am 02.03.2012 02:07, schrieb Lars Gullik Bjønnes:


I am not going to setup anonymous cloning right now, but I want
developers to send me their public ssh keys.


I never used SSH until now, so could anybody please give me a short 
introduction what I need to do?


thanks and regards
Uwe


1. Install: 
http://msysgit.googlecode.com/files/Git-1.7.9-preview20120201.exe

2. Start Git Bash
3. type ssh-keygen
4. press enter to store the key in the default location
5. enter a passphrase or just press enter

You'll get a message: Your public key has been saved in .

6. send this public key to Lars.
7. after Lars has added your key to the server, the following should work:

ssh g...@git.lyx.org info
and
git clone g...@git.lyx.org:testing

8. Enjoy your checkout of the git test repo.

Vincent

Re: git.lyx.org - developers! your ssh public key please

[Yihui Xie]

I mean discussion in email is less efficient than directly in code,
where you can point out why this line is not good, and how that line
needs improvement, etc.

Regards,
Yihui
--
Yihui Xie xieyi...@gmail.com
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA



On Sat, Mar 3, 2012 at 4:31 AM, Lars Gullik Bjønnes lar...@gullik.org wrote:
 On Sat, Mar 3, 2012 at 04:25, Yihui Xie x...@yihui.name wrote:
 [...]
 Personally I believe it is very inefficient to email patches

 In what way inefficient?

 git send-email HEAD~3

 to send the small patchset for commenting somewhere is not exactly hard.

 and it is
 so inconvenient to discuss code in emails.

 I couldn't disagree more I think.

 --
         Lgb

Re: git.lyx.org - developers! your ssh public key please

[Yihui Xie]

This is expected to me: programmers tend to do everything by
themselves. I cannot promise all the conversions, but GitHub supports
importing from an svn repo with one click, so if you want to move
there, I can certainly do it. For the rest of the jobs, they require
more time, but I believe after the conversion it will be easier to
maintain since almost everything is under GIT. I'm willing to
contribute some time if you want, but from the replies I have got so
far, I guess I can give up the attempt to convince you now.

Regards,
Yihui
--
Yihui Xie xieyi...@gmail.com
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA



On Sat, Mar 3, 2012 at 4:06 AM, Lars Gullik Bjønnes lar...@gullik.org wrote:
 In short, this is approximately true for me: GitHub = GIT + Trac +
 Wiki + Web and all are based on GIT. Anyway, this is just my 2 cents
 when I saw the transition from SVN to GIT, and of course you are free
 to invest time and efforts in setting up your own server.

 Will _you_ step up to do all the conversions needed?
 We already have an extensive wiki, we have nice web pages
 and a running bug tracker.

 Setting up a gitolite server for git is easy. And it is not like we are
 closing the door on a later move to some git hosting service.

 --
         Lgb

Re: git.lyx.org - developers! your ssh public key please

[Yihui Xie]

Uwe,

Since you work under Windows, I also recommend TortoiseGIT with
msysgit, unless you like working with CLI heavily.

Regards,
Yihui
--
Yihui Xie xieyi...@gmail.com
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA



On Sat, Mar 3, 2012 at 7:32 AM, Vincent van Ravesteijn v...@lyx.org wrote:
 Op 3-3-2012 14:17, Uwe Stöhr schreef:

 Am 02.03.2012 02:07, schrieb Lars Gullik Bjønnes:

 I am not going to setup anonymous cloning right now, but I want
 developers to send me their public ssh keys.


 I never used SSH until now, so could anybody please give me a short
 introduction what I need to do?

 thanks and regards
 Uwe


 1. Install:
 http://msysgit.googlecode.com/files/Git-1.7.9-preview20120201.exe
 2. Start Git Bash
 3. type ssh-keygen
 4. press enter to store the key in the default location
 5. enter a passphrase or just press enter

 You'll get a message: Your public key has been saved in .

 6. send this public key to Lars.
 7. after Lars has added your key to the server, the following should work:

 ssh g...@git.lyx.org info
 and
 git clone g...@git.lyx.org:testing

 8. Enjoy your checkout of the git test repo.

 Vincent

Re: git.lyx.org - developers! your ssh public key please

[Vincent van Ravesteijn]

Op 3-3-2012 18:00, Yihui Xie schreef:

I mean discussion in email is less efficient than directly in code,
where you can point out why this line is not good, and how that line
needs improvement, etc.



If you're interested, I'll share some discussion of the git developers 
themselves. The git-community itself works only with e-mail. They don't 
have a bug tracker, and all the code, of all developers goes through the 
mailing list.


See the following discussion which took place in the last few days:
http://thread.gmane.org/gmane.comp.version-control.git/191835

Some quotes from this thread:

... the design of git was created with the idea of handling patches via 
e-mail in mind.
I run a project that is mainly hosted on github, but I absolutely 
positively refuse to use their web interface for anything.
I want everything in **one** interface, and I want it just the way 
**I** want it, and it shouldn't (necessarily) dictate how **you** should 
work. Email is just that.


Vincent

Re: git.lyx.org - developers! your ssh public key please

[Pavel Sanda]

Yihui Xie wrote:
 I mean discussion in email is less efficient than directly in code,
 where you can point out why this line is not good, and how that line
 needs improvement, etc.

You repeat this kind of argument which means either me or you do not follow.

There is nothing easier than comment on particular line of code when patch
is sent to the list and it happens here regularly, sometimes with pretty
complex structure of subthreads on the topic, haven't you seen yet?
Then we have mailling list with each commit automatically posted, so the
same applies for already committed code.

At the end it boils down to the choice of your favourite mail client
or web-based interface to the list. I don't follow what github offers
more (WRT code commenting) except it steals choice of tools particular
developer is pleased to use.

Pavel

Re: git.lyx.org - developers! your ssh public key please

[Yihui Xie]

Fair enough. Decision time: GitHub is heaven for me, and sort of hell
for you; it is a personal matter of taste, so I'm not going to
continue this discussion.

Sorry to bother all, and thank you all for the great work! I love LyX
and GIT, both of which have significantly increased my productivity.

Regards,
Yihui
--
Yihui Xie xieyi...@gmail.com
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA



On Sat, Mar 3, 2012 at 11:54 AM, Vincent van Ravesteijn v...@lyx.org wrote:
 Op 3-3-2012 18:00, Yihui Xie schreef:

 I mean discussion in email is less efficient than directly in code,
 where you can point out why this line is not good, and how that line
 needs improvement, etc.


 If you're interested, I'll share some discussion of the git developers
 themselves. The git-community itself works only with e-mail. They don't have
 a bug tracker, and all the code, of all developers goes through the mailing
 list.

 See the following discussion which took place in the last few days:
 http://thread.gmane.org/gmane.comp.version-control.git/191835

 Some quotes from this thread:

 ... the design of git was created with the idea of handling patches via
 e-mail in mind.
 I run a project that is mainly hosted on github, but I absolutely
 positively refuse to use their web interface for anything.
 I want everything in *one* interface, and I want it just the way *I* want
 it, and it shouldn't (necessarily) dictate how *you* should work. Email is
 just that.

 Vincent

Re: git.lyx.org - developers! your ssh public key please

[Uwe Stöhr]

Am 03.03.2012 14:32, schrieb Vincent van Ravesteijn:

Many thanks for the quick reply!


You'll get a message: Your public key has been saved in .


Yes, but the file is not stored in the given folder. However, 2 files were now created and I guess 
that I have to send Lars the one with the suffix .pub.


One further question: I own several PCs and when I'm abroad. I also want to check out or commit to 
LyX. How is that possible? The generated public SSH-key seems to be connected to my PC because it 
contains the PC name.


many thanks and best regards
Uwe

Re: Re: Re: git.lyx.org - developers! your ssh public key please

[Kornel Benko]

Am Samstag, 3. März 2012 um 10:27:36, schrieb Kornel Benko 
> Attached as requested
> 
>   Kornel

Sorry, this time better ...ssh-dss 
B3NzaC1kc3MAAACBANtpQPjvzWLv45P5qzsrqzGUezRxDW59m2KQ7o9Vn0XVO4pB/f7iitRWV4ERrYK+8p4p5IoQzaV8QhsiOt4hZLnUkkjYcMqDo7MOgbsX1PsnFTI7j34iqW9H+JrlY8AXcjD9Gxr+nE8I+9wdr2A6mQskOYW90kjCkM60Bj6ngWoVFQDUHF6gQjywk6j1cH9ENxu6FJ0m0wAAAIBf6fnD+dWjsoy+i/uf64kzfEq+zyViGhBOxu+rSj1cQrGQxaTlEjwOtsDPfNyJd7h6tuTT9WMJa9A9kX5Oi3qK9Qy5tvgWLFW6peEs0fFZC92WkTExog9u80DNcIAKIhGNM5AxiomylAvM1E4xHjP/zI2ndjAZUtjPFS8fNjif3wAAAIEAn2ixSmKlo97zevXAD8II3G6MwhttmngvUvFy1X9ucyg8tub6Y5oa7uUBY6XZzsgZWZ3VTNSAMHOKDo7RwxzDGy4gTdre4bMD7E5BGZG5K9A/CBRpVSWrDA6gSB/0lJjJwrcPPq+mESSUitMaYOLZwuLiwere6jxrcthN+h07wdg=
 kornel@korben


signature.asc
Description: This is a digitally signed message part.

Re: git.lyx.org - developers! your ssh public key please

[Lars Gullik Bjønnes]

> In short, this is approximately true for me: GitHub = GIT + Trac +
> Wiki + Web and all are based on GIT. Anyway, this is just my 2 cents
> when I saw the transition from SVN to GIT, and of course you are free
> to invest time and efforts in setting up your own server.

Will _you_ step up to do all the conversions needed?
We already have an extensive wiki, we have nice web pages
and a running bug tracker.

Setting up a gitolite server for git is easy. And it is not like we are
closing the door on a later move to some git hosting service.

-- 
        Lgb

Re: git.lyx.org - developers! your ssh public key please

[Lars Gullik Bjønnes]

On Sat, Mar 3, 2012 at 04:25, Yihui Xie  wrote:
[...]
> Personally I believe it is very inefficient to email patches

In what way inefficient?

git send-email HEAD~3

to send the small patchset for commenting somewhere is not exactly hard.

> and it is
> so inconvenient to discuss code in emails.

I couldn't disagree more I think.

-- 
        Lgb

Re: git.lyx.org - developers! your ssh public key please

[Pavel Sanda]

Yihui Xie wrote:
> the code line by line with the one who submit this patch -- comments
> can be made in-between the code lines; if you are not satisfactory
> with the patch, you can require one to revise the code and resubmit;
> this process can go on and on until you are satisfied and accept the
> patch; see here for an example of my own:
> https://github.com/ramnathv/knitr/commit/33a75f4029
> 
> Personally I believe it is very inefficient to email patches and it is
> so inconvenient to discuss code in emails.

Perhaps matter of taste - on contrary I found the discussion through
email conference much more convenient that web-based forums. Actually
anything web based is an order of magnitude slower for my mutt/vim
based fingers... 

Pavel

Re: git.lyx.org - developers! your ssh public key please

[Uwe Stöhr]

Am 02.03.2012 02:07, schrieb Lars Gullik Bjønnes:


I am not going to setup anonymous cloning right now, but I want
developers to send me their public ssh keys.


I never used SSH until now, so could anybody please give me a short 
introduction what I need to do?

thanks and regards
Uwe

Re: git.lyx.org - developers! your ssh public key please

[Vincent van Ravesteijn]

Op 3-3-2012 14:17, Uwe Stöhr schreef:

Am 02.03.2012 02:07, schrieb Lars Gullik Bjønnes:


I am not going to setup anonymous cloning right now, but I want
developers to send me their public ssh keys.


I never used SSH until now, so could anybody please give me a short 
introduction what I need to do?


thanks and regards
Uwe


1. Install: 
http://msysgit.googlecode.com/files/Git-1.7.9-preview20120201.exe

2. Start "Git Bash"
3. type "ssh-keygen"
4. press enter to store the key in the default location
5. enter a passphrase or just press enter

You'll get a message: "Your public key has been saved in ."

6. send this public key to Lars.
7. after Lars has added your key to the server, the following should work:

"ssh g...@git.lyx.org info"
and
"git clone g...@git.lyx.org:testing"

8. Enjoy your checkout of the git test repo.

Vincent

Re: git.lyx.org - developers! your ssh public key please

[Yihui Xie]

I mean discussion in email is less efficient than directly in code,
where you can point out why this line is not good, and how that line
needs improvement, etc.

Regards,
Yihui
--
Yihui Xie 
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA



On Sat, Mar 3, 2012 at 4:31 AM, Lars Gullik Bjønnes  wrote:
> On Sat, Mar 3, 2012 at 04:25, Yihui Xie  wrote:
> [...]
>> Personally I believe it is very inefficient to email patches
>
> In what way inefficient?
>
> git send-email HEAD~3
>
> to send the small patchset for commenting somewhere is not exactly hard.
>
>> and it is
>> so inconvenient to discuss code in emails.
>
> I couldn't disagree more I think.
>
> --
>         Lgb

Re: git.lyx.org - developers! your ssh public key please

[Yihui Xie]

This is expected to me: programmers tend to do everything by
themselves. I cannot promise all the conversions, but GitHub supports
importing from an svn repo with one click, so if you want to move
there, I can certainly do it. For the rest of the jobs, they require
more time, but I believe after the conversion it will be easier to
maintain since almost everything is under GIT. I'm willing to
contribute some time if you want, but from the replies I have got so
far, I guess I can give up the attempt to convince you now.

Regards,
Yihui
--
Yihui Xie 
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA



On Sat, Mar 3, 2012 at 4:06 AM, Lars Gullik Bjønnes  wrote:
>> In short, this is approximately true for me: GitHub = GIT + Trac +
>> Wiki + Web and all are based on GIT. Anyway, this is just my 2 cents
>> when I saw the transition from SVN to GIT, and of course you are free
>> to invest time and efforts in setting up your own server.
>
> Will _you_ step up to do all the conversions needed?
> We already have an extensive wiki, we have nice web pages
> and a running bug tracker.
>
> Setting up a gitolite server for git is easy. And it is not like we are
> closing the door on a later move to some git hosting service.
>
> --
>         Lgb

Re: git.lyx.org - developers! your ssh public key please

[Yihui Xie]

Uwe,

Since you work under Windows, I also recommend TortoiseGIT with
msysgit, unless you like working with CLI heavily.

Regards,
Yihui
--
Yihui Xie 
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA



On Sat, Mar 3, 2012 at 7:32 AM, Vincent van Ravesteijn  wrote:
> Op 3-3-2012 14:17, Uwe Stöhr schreef:
>
>> Am 02.03.2012 02:07, schrieb Lars Gullik Bjønnes:
>>
>>> I am not going to setup anonymous cloning right now, but I want
>>> developers to send me their public ssh keys.
>>
>>
>> I never used SSH until now, so could anybody please give me a short
>> introduction what I need to do?
>>
>> thanks and regards
>> Uwe
>
>
> 1. Install:
> http://msysgit.googlecode.com/files/Git-1.7.9-preview20120201.exe
> 2. Start "Git Bash"
> 3. type "ssh-keygen"
> 4. press enter to store the key in the default location
> 5. enter a passphrase or just press enter
>
> You'll get a message: "Your public key has been saved in ."
>
> 6. send this public key to Lars.
> 7. after Lars has added your key to the server, the following should work:
>
> "ssh g...@git.lyx.org info"
> and
> "git clone g...@git.lyx.org:testing"
>
> 8. Enjoy your checkout of the git test repo.
>
> Vincent
>
>
>

Re: git.lyx.org - developers! your ssh public key please

[Vincent van Ravesteijn]

Op 3-3-2012 18:00, Yihui Xie schreef:

I mean discussion in email is less efficient than directly in code,
where you can point out why this line is not good, and how that line
needs improvement, etc.



If you're interested, I'll share some discussion of the git developers 
themselves. The git-community itself works only with e-mail. They don't 
have a bug tracker, and all the code, of all developers goes through the 
mailing list.


See the following discussion which took place in the last few days:
http://thread.gmane.org/gmane.comp.version-control.git/191835

Some quotes from this thread:

"... the design of git was created with the idea of handling patches via 
e-mail in mind."
"I run a project that is mainly hosted on github, but I absolutely 
positively refuse to use their web interface for anything."
"I want everything in **one** interface, and I want it just the way 
**I** want it, and it shouldn't (necessarily) dictate how **you** should 
work. Email is just that."


Vincent

Re: git.lyx.org - developers! your ssh public key please

[Pavel Sanda]

Yihui Xie wrote:
> I mean discussion in email is less efficient than directly in code,
> where you can point out why this line is not good, and how that line
> needs improvement, etc.

You repeat this kind of argument which means either me or you do not follow.

There is nothing easier than comment on particular line of code when patch
is sent to the list and it happens here regularly, sometimes with pretty
complex structure of subthreads on the topic, haven't you seen yet?
Then we have mailling list with each commit automatically posted, so the
same applies for already committed code.

At the end it boils down to the choice of your favourite mail client
or web-based interface to the list. I don't follow what github offers
more (WRT code commenting) except it steals choice of tools particular
developer is pleased to use.

Pavel

Re: git.lyx.org - developers! your ssh public key please

[Yihui Xie]

Fair enough. Decision time: GitHub is heaven for me, and sort of hell
for you; it is a personal matter of taste, so I'm not going to
continue this discussion.

Sorry to bother all, and thank you all for the great work! I love LyX
and GIT, both of which have significantly increased my productivity.

Regards,
Yihui
--
Yihui Xie 
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA



On Sat, Mar 3, 2012 at 11:54 AM, Vincent van Ravesteijn  wrote:
> Op 3-3-2012 18:00, Yihui Xie schreef:
>
> I mean discussion in email is less efficient than directly in code,
> where you can point out why this line is not good, and how that line
> needs improvement, etc.
>
>
> If you're interested, I'll share some discussion of the git developers
> themselves. The git-community itself works only with e-mail. They don't have
> a bug tracker, and all the code, of all developers goes through the mailing
> list.
>
> See the following discussion which took place in the last few days:
> http://thread.gmane.org/gmane.comp.version-control.git/191835
>
> Some quotes from this thread:
>
> "... the design of git was created with the idea of handling patches via
> e-mail in mind."
> "I run a project that is mainly hosted on github, but I absolutely
> positively refuse to use their web interface for anything."
> "I want everything in *one* interface, and I want it just the way *I* want
> it, and it shouldn't (necessarily) dictate how *you* should work. Email is
> just that."
>
> Vincent

Re: git.lyx.org - developers! your ssh public key please

[Uwe Stöhr]

Am 03.03.2012 14:32, schrieb Vincent van Ravesteijn:

Many thanks for the quick reply!


You'll get a message: "Your public key has been saved in ."


Yes, but the file is not stored in the given folder. However, 2 files were now created and I guess 
that I have to send Lars the one with the suffix ".pub".


One further question: I own several PCs and when I'm abroad. I also want to check out or commit to 
LyX. How is that possible? The generated public SSH-key seems to be connected to my PC because it 
contains the PC name.


many thanks and best regards
Uwe

Re: git.lyx.org - developers! your ssh public key please

[Vincent van Ravesteijn]

Op 2-3-2012 7:35, Yihui Xie schreef:

I was actually wondering why not move to GitHub directly since
everything is ready there and it saves a huge amount of server admin
efforts... Maybe I missed some conversations earlier, but IMHO GitHub
makes collaborations way way easier.



In what sense does it make it easier ? Pull requests are nice, but this 
requires all developers to read the mailing lists and to keep track of 
any pull requests on github. It's easy to submit patches to the mailing 
list using git send-email. In this way, all developers can respond.


Using git, you could acquire commit rights faster than using svn, 
because at first you will be restricted to pushing branches like 
yihuixie/new-feature. This won't affect the source code until it gets 
merged in by someone.


Vincent

Re: git.lyx.org - developers! your ssh public key please

[Lars Gullik Bjønnes]

Xu Wang xuwang...@gmail.com writes:

| Excellent! How does this work for non-developers? For example, I would like
| to be able to do something and then do a pull-request. I think at this
| point I can only fix typos and maybe a small error, but my work would need
| to be verified.

As long as you have a public clone of the lyx repo anywere you can send
pull requests and have lyx developers act on them.

Basically just how git is supposed to work.

-- 
   Lgb

Re: git.lyx.org - developers! your ssh public key please

[Lars Gullik Bjønnes]

Vincent van Ravesteijn v...@lyx.org writes:

| Op 2-3-2012 7:35, Yihui Xie schreef:
 I was actually wondering why not move to GitHub directly since
 everything is ready there and it saves a huge amount of server admin
 efforts... Maybe I missed some conversations earlier, but IMHO GitHub
 makes collaborations way way easier.


| In what sense does it make it easier ? Pull requests are nice, but
| this requires all developers to read the mailing lists and to keep
| track of any pull requests on github. It's easy to submit patches to
| the mailing list using git send-email. In this way, all developers
| can respond.

I bet git request-pull can be used as well.


| Using git, you could acquire commit rights faster than using svn,
| because at first you will be restricted to pushing branches like
| yihuixie/new-feature. This won't affect the source code until it
| gets merged in by someone.

More likely get a separate repo for his work. Then others can trivially
pull from it.

(We don't want a multitude of branches in the man repo.)

-- 
   Lgb

Re: git.lyx.org - developers! your ssh public key please

[Lars Gullik Bjønnes]

Yihui Xie x...@yihui.name writes:

| I was actually wondering why not move to GitHub directly since
| everything is ready there and it saves a huge amount of server admin
| efforts... Maybe I missed some conversations earlier, but IMHO GitHub
| makes collaborations way way easier.

- bug tracker, a lot is invested in the one we have, by keeping the
  repo close we get tight integration.

You can use githup for your lyx work, but official upstream will be on
git.lyx.org.

Collaboration wise it makes little difference.

-- 
   Lgb

Re: git.lyx.org - developers! your ssh public key please

[Yihui Xie]

Well, I think I understand some of the advantages of GIT like easy
branching. I do not even bother to compare it to SVN because GIT is so
much better.

I mean GitHub makes GIT even better; there are too many advantages and
I just list a few of them here:

1. developers manage their own SSH keys on GitHub and you do not need
to ask them to submit their public keys to you;

2. people who are not in the developer team can fork the project with
one-click to their own repositories, change the code and send pull
request online (instead of emailing patches) so that you can review
the patch online; a very critical feature here is you can _discuss_
the code line by line with the one who submit this patch -- comments
can be made in-between the code lines; if you are not satisfactory
with the patch, you can require one to revise the code and resubmit;
this process can go on and on until you are satisfied and accept the
patch; see here for an example of my own:
https://github.com/ramnathv/knitr/commit/33a75f4029

Personally I believe it is very inefficient to email patches and it is
so inconvenient to discuss code in emails. If people send me pull
requests on GitHub, I may merge them in a few minutes, but patches in
email often lay in my inbox for months.

3. you can either discuss on GitHub pages, or directly reply the email
notifications from GitHub about the discussions; the email will go to
GitHub. This is unlike trac, you have to go to the web page to discuss
(maybe there are configurations that enable trac to manage emails, but
I did not see this happen in LyX SVN ages).

4. bugs tracker; they call issues, which are also closely tied to
code; you can write a commit message like fixed #43 to fix the issue
43 (the issue will be closed and there will be a reference to the
commit in the issue page); it is also more convenient to manage bug
reports: one thing I do not like trac is I'm unable to change the
report after I submit it (e.g. I want to add more code examples, or
fix typos).

5. wiki support: you can manage wiki pages by GIT, or edit them
online; the default aesthetics looks good (e.g.
https://github.com/yihui/formatR/wiki)

6. GitHub pages: you can even manage your website on GitHub by
creating a branch named gh-pages and use the Jekyll engine to
compile markdown files to HTML (this is automatic on GitHub so you
only maintain lightweight markdown files); it is easy to setup and
after that, you can manage the website by GIT (see, everything on
GitHub can go to GIT); sorry to use my own projects as examples again,
but you can see the source
https://github.com/yihui/knitr/tree/gh-pages of the site
http://yihui.name/knitr/ for example

Here is a recent article Lord of the Files: How GitHub Tamed Free
Software (And More):
http://www.wired.com/wiredenterprise/2012/02/github/all/1

In short, this is approximately true for me: GitHub = GIT + Trac +
Wiki + Web and all are based on GIT. Anyway, this is just my 2 cents
when I saw the transition from SVN to GIT, and of course you are free
to invest time and efforts in setting up your own server.

Regards,
Yihui
--
Yihui Xie xieyi...@gmail.com
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA



On Fri, Mar 2, 2012 at 4:01 AM, Vincent van Ravesteijn v...@lyx.org wrote:
 Op 2-3-2012 7:35, Yihui Xie schreef:

 I was actually wondering why not move to GitHub directly since
 everything is ready there and it saves a huge amount of server admin
 efforts... Maybe I missed some conversations earlier, but IMHO GitHub
 makes collaborations way way easier.


 In what sense does it make it easier ? Pull requests are nice, but this
 requires all developers to read the mailing lists and to keep track of any
 pull requests on github. It's easy to submit patches to the mailing list
 using git send-email. In this way, all developers can respond.

 Using git, you could acquire commit rights faster than using svn, because at
 first you will be restricted to pushing branches like
 yihuixie/new-feature. This won't affect the source code until it gets
 merged in by someone.

 Vincent

Re: git.lyx.org - developers! your ssh public key please

[Vincent van Ravesteijn]

Op 2-3-2012 7:35, Yihui Xie schreef:

I was actually wondering why not move to GitHub directly since
everything is ready there and it saves a huge amount of server admin
efforts... Maybe I missed some conversations earlier, but IMHO GitHub
makes collaborations way way easier.



In what sense does it make it easier ? Pull requests are nice, but this 
requires all developers to read the mailing lists and to keep track of 
any pull requests on github. It's easy to submit patches to the mailing 
list using "git send-email". In this way, all developers can respond.


Using git, you could acquire commit rights faster than using svn, 
because at first you will be restricted to pushing branches like 
"yihuixie/new-feature". This won't affect the source code until it gets 
merged in by someone.


Vincent

Re: git.lyx.org - developers! your ssh public key please

[Lars Gullik Bjønnes]

Xu Wang  writes:

| Excellent! How does this work for non-developers? For example, I would like
| to be able to do something and then do a pull-request. I think at this
| point I can only fix typos and maybe a small error, but my work would need
| to be verified.

As long as you have a public clone of the lyx repo anywere you can send
pull requests and have lyx developers act on them.

Basically just how git is supposed to work.

-- 
   Lgb

Re: git.lyx.org - developers! your ssh public key please

[Lars Gullik Bjønnes]

Vincent van Ravesteijn  writes:

| Op 2-3-2012 7:35, Yihui Xie schreef:
>> I was actually wondering why not move to GitHub directly since
>> everything is ready there and it saves a huge amount of server admin
>> efforts... Maybe I missed some conversations earlier, but IMHO GitHub
>> makes collaborations way way easier.
>>
>
| In what sense does it make it easier ? Pull requests are nice, but
| this requires all developers to read the mailing lists and to keep
| track of any pull requests on github. It's easy to submit patches to
| the mailing list using "git send-email". In this way, all developers
| can respond.

I bet "git request-pull" can be used as well.

>
| Using git, you could acquire commit rights faster than using svn,
| because at first you will be restricted to pushing branches like
| "yihuixie/new-feature". This won't affect the source code until it
| gets merged in by someone.

More likely get a separate repo for his work. Then others can trivially
pull from it.

(We don't want a multitude of branches in the man repo.)

-- 
   Lgb

Re: git.lyx.org - developers! your ssh public key please

[Lars Gullik Bjønnes]

Yihui Xie  writes:

| I was actually wondering why not move to GitHub directly since
| everything is ready there and it saves a huge amount of server admin
| efforts... Maybe I missed some conversations earlier, but IMHO GitHub
| makes collaborations way way easier.

- bug tracker, a lot is invested in the one we have, by keeping the
  repo close we get tight integration.

You can use githup for your lyx work, but official upstream will be on
git.lyx.org.

Collaboration wise it makes little difference.

-- 
   Lgb

Re: git.lyx.org - developers! your ssh public key please

[Yihui Xie]

Well, I think I understand some of the advantages of GIT like easy
branching. I do not even bother to compare it to SVN because GIT is so
much better.

I mean GitHub makes GIT even better; there are too many advantages and
I just list a few of them here:

1. developers manage their own SSH keys on GitHub and you do not need
to ask them to submit their public keys to you;

2. people who are not in the developer team can fork the project with
one-click to their own repositories, change the code and send pull
request online (instead of emailing patches) so that you can review
the patch online; a very critical feature here is you can _discuss_
the code line by line with the one who submit this patch -- comments
can be made in-between the code lines; if you are not satisfactory
with the patch, you can require one to revise the code and resubmit;
this process can go on and on until you are satisfied and accept the
patch; see here for an example of my own:
https://github.com/ramnathv/knitr/commit/33a75f4029

Personally I believe it is very inefficient to email patches and it is
so inconvenient to discuss code in emails. If people send me pull
requests on GitHub, I may merge them in a few minutes, but patches in
email often lay in my inbox for months.

3. you can either discuss on GitHub pages, or directly reply the email
notifications from GitHub about the discussions; the email will go to
GitHub. This is unlike trac, you have to go to the web page to discuss
(maybe there are configurations that enable trac to manage emails, but
I did not see this happen in LyX SVN ages).

4. bugs tracker; they call "issues", which are also closely tied to
code; you can write a commit message like "fixed #43" to fix the issue
43 (the issue will be closed and there will be a reference to the
commit in the issue page); it is also more convenient to manage bug
reports: one thing I do not like trac is I'm unable to change the
report after I submit it (e.g. I want to add more code examples, or
fix typos).

5. wiki support: you can manage wiki pages by GIT, or edit them
online; the default aesthetics looks good (e.g.
https://github.com/yihui/formatR/wiki)

6. GitHub pages: you can even manage your website on GitHub by
creating a branch named "gh-pages" and use the Jekyll engine to
compile markdown files to HTML (this is automatic on GitHub so you
only maintain lightweight markdown files); it is easy to setup and
after that, you can manage the website by GIT (see, everything on
GitHub can go to GIT); sorry to use my own projects as examples again,
but you can see the source
https://github.com/yihui/knitr/tree/gh-pages of the site
http://yihui.name/knitr/ for example

Here is a recent article "Lord of the Files: How GitHub Tamed Free
Software (And More)":
http://www.wired.com/wiredenterprise/2012/02/github/all/1

In short, this is approximately true for me: GitHub = GIT + Trac +
Wiki + Web and all are based on GIT. Anyway, this is just my 2 cents
when I saw the transition from SVN to GIT, and of course you are free
to invest time and efforts in setting up your own server.

Regards,
Yihui
--
Yihui Xie 
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA



On Fri, Mar 2, 2012 at 4:01 AM, Vincent van Ravesteijn  wrote:
> Op 2-3-2012 7:35, Yihui Xie schreef:
>>
>> I was actually wondering why not move to GitHub directly since
>> everything is ready there and it saves a huge amount of server admin
>> efforts... Maybe I missed some conversations earlier, but IMHO GitHub
>> makes collaborations way way easier.
>>
>
> In what sense does it make it easier ? Pull requests are nice, but this
> requires all developers to read the mailing lists and to keep track of any
> pull requests on github. It's easy to submit patches to the mailing list
> using "git send-email". In this way, all developers can respond.
>
> Using git, you could acquire commit rights faster than using svn, because at
> first you will be restricted to pushing branches like
> "yihuixie/new-feature". This won't affect the source code until it gets
> merged in by someone.
>
> Vincent

git.lyx.org - developers! your ssh public key please

[Lars Gullik Bjønnes]

I have begun to setup and do the lyx conversion proper.
Expect things to happen fairly quick now.

However I do not want to do this _too_ fast.

http://git.lyx.org/

I am not going to setup anonymous cloning right now, but I want
developers to send me their public ssh keys.
(If you do not already have write access to the svn repo, don't bother
sending me a public key either. Be sure to send as attachment.)

After I get your public key and add it you will get
access to clone, push and pull to the testing repo.
Play all you like with that.

In the meantime I will fixup the git repo I have of lyx, and
we should be able to make the switch over failr quick.
We need to make the proper track setup first though.

-- 
        Lgb

Re: git.lyx.org - developers! your ssh public key please

[Xu Wang]

Excellent! How does this work for non-developers? For example, I would like
to be able to do something and then do a pull-request. I think at this
point I can only fix typos and maybe a small error, but my work would need
to be verified.

Thank you for this, Xu

On Thu, Mar 1, 2012 at 8:07 PM, Lars Gullik Bjønnes lar...@gullik.orgwrote:

 I have begun to setup and do the lyx conversion proper.
 Expect things to happen fairly quick now.

 However I do not want to do this _too_ fast.

 http://git.lyx.org/

 I am not going to setup anonymous cloning right now, but I want
 developers to send me their public ssh keys.
 (If you do not already have write access to the svn repo, don't bother
 sending me a public key either. Be sure to send as attachment.)

 After I get your public key and add it you will get
 access to clone, push and pull to the testing repo.
 Play all you like with that.

 In the meantime I will fixup the git repo I have of lyx, and
 we should be able to make the switch over failr quick.
 We need to make the proper track setup first though.

 --
 Lgb

Re: git.lyx.org - developers! your ssh public key please

[Yihui Xie]

I was actually wondering why not move to GitHub directly since
everything is ready there and it saves a huge amount of server admin
efforts... Maybe I missed some conversations earlier, but IMHO GitHub
makes collaborations way way easier.

Regards,
Yihui
--
Yihui Xie xieyi...@gmail.com
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA



On Fri, Mar 2, 2012 at 12:09 AM, Xu Wang xuwang...@gmail.com wrote:
 Excellent! How does this work for non-developers? For example, I would like
 to be able to do something and then do a pull-request. I think at this point
 I can only fix typos and maybe a small error, but my work would need to be
 verified.

 Thank you for this, Xu

 On Thu, Mar 1, 2012 at 8:07 PM, Lars Gullik Bjønnes lar...@gullik.org
 wrote:

 I have begun to setup and do the lyx conversion proper.
 Expect things to happen fairly quick now.

 However I do not want to do this _too_ fast.

 http://git.lyx.org/

 I am not going to setup anonymous cloning right now, but I want
 developers to send me their public ssh keys.
 (If you do not already have write access to the svn repo, don't bother
 sending me a public key either. Be sure to send as attachment.)

 After I get your public key and add it you will get
 access to clone, push and pull to the testing repo.
 Play all you like with that.

 In the meantime I will fixup the git repo I have of lyx, and
 we should be able to make the switch over failr quick.
 We need to make the proper track setup first though.

 --
         Lgb

git.lyx.org - developers! your ssh public key please

[Lars Gullik Bjønnes]

I have begun to setup and do the lyx conversion proper.
Expect things to happen fairly quick now.

However I do not want to do this _too_ fast.

http://git.lyx.org/

I am not going to setup anonymous cloning right now, but I want
developers to send me their public ssh keys.
(If you do not already have write access to the svn repo, don't bother
sending me a public key either. Be sure to send as attachment.)

After I get your public key and add it you will get
access to clone, push and pull to the testing repo.
Play all you like with that.

In the meantime I will fixup the git repo I have of lyx, and
we should be able to make the switch over failr quick.
We need to make the proper track setup first though.

-- 
        Lgb

Re: git.lyx.org - developers! your ssh public key please

[Xu Wang]

Excellent! How does this work for non-developers? For example, I would like
to be able to do something and then do a pull-request. I think at this
point I can only fix typos and maybe a small error, but my work would need
to be verified.

Thank you for this, Xu

On Thu, Mar 1, 2012 at 8:07 PM, Lars Gullik Bjønnes wrote:

> I have begun to setup and do the lyx conversion proper.
> Expect things to happen fairly quick now.
>
> However I do not want to do this _too_ fast.
>
> http://git.lyx.org/
>
> I am not going to setup anonymous cloning right now, but I want
> developers to send me their public ssh keys.
> (If you do not already have write access to the svn repo, don't bother
> sending me a public key either. Be sure to send as attachment.)
>
> After I get your public key and add it you will get
> access to clone, push and pull to the testing repo.
> Play all you like with that.
>
> In the meantime I will fixup the git repo I have of lyx, and
> we should be able to make the switch over failr quick.
> We need to make the proper track setup first though.
>
> --
> Lgb
>

Re: git.lyx.org - developers! your ssh public key please

[Yihui Xie]

I was actually wondering why not move to GitHub directly since
everything is ready there and it saves a huge amount of server admin
efforts... Maybe I missed some conversations earlier, but IMHO GitHub
makes collaborations way way easier.

Regards,
Yihui
--
Yihui Xie 
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA



On Fri, Mar 2, 2012 at 12:09 AM, Xu Wang  wrote:
> Excellent! How does this work for non-developers? For example, I would like
> to be able to do something and then do a pull-request. I think at this point
> I can only fix typos and maybe a small error, but my work would need to be
> verified.
>
> Thank you for this, Xu
>
> On Thu, Mar 1, 2012 at 8:07 PM, Lars Gullik Bjønnes 
> wrote:
>>
>> I have begun to setup and do the lyx conversion proper.
>> Expect things to happen fairly quick now.
>>
>> However I do not want to do this _too_ fast.
>>
>> http://git.lyx.org/
>>
>> I am not going to setup anonymous cloning right now, but I want
>> developers to send me their public ssh keys.
>> (If you do not already have write access to the svn repo, don't bother
>> sending me a public key either. Be sure to send as attachment.)
>>
>> After I get your public key and add it you will get
>> access to clone, push and pull to the testing repo.
>> Play all you like with that.
>>
>> In the meantime I will fixup the git repo I have of lyx, and
>> we should be able to make the switch over failr quick.
>> We need to make the proper track setup first though.
>>
>> --
>>         Lgb
>
>