[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-user
Subject:    Re: Fwd: [Frescobaldi] GSoC Project "Add Support for Git Workflows to Frescobaldi" introduction (Urs
From:       Urs Liska <ul () openlilylib ! org>
Date:       2017-05-25 12:37:07
Message-ID: dd94a711-a32d-4a50-15d7-dd3e698ffd4f () openlilylib ! org
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Am 25.05.2017 um 14:04 schrieb Leszek Wroński:
>
> Guys,
>
> apologies if I've missed something obvious, but what is the intended
> place for discussing the very welcome 'Add Git support to Frescobaldi'
> project? Here? The Frescobaldi forum? The wiki (but where?)?

Well, the "natural" place for the discussion is the Frescobaldi mailing
list. But as I assume not all LilyPond/Frescobaldi users actually are
subscribed to that (and also LilyPond/not-Frescobaldi users may have
interesting views on the subject) I decided to forward it to
lilypond-user as well.

So while I hope it will not confuse people I suggest discussing the
project on either of the mailings lists.
The Wiki will probably be updated by Xin himself (or maybe also me).

>
> (I just have a minor requst: it would be convenient if we could create
> and change branches, I don't see that on the function list.)

Well, there are lots of things one could add to the list and wish, but
we have decided to limit the project plan to this "core Git workflow".
If that should be finished "too early" we will discuss what to implement
in addition. And if the GSoC project will "only" implement the current
plan there still will be a robust foundation to add more functionality
later.

>
> When it comes to the diff presentation, I'm partial to the 'Emacs +
> magit' combination (https://www.emacswiki.org/emacs/Magit )
>
We should keep that in mind. But for now we're only interested in
unstaged and staged changes.

Urs

> Good luck with the project!
>
> Cheers,
>
> Leszek.
>
> On 22 May 2017 at 18:00, <lilypond-user-request@gnu.org
> <mailto:lilypond-user-request@gnu.org>> wrote:
>
>
>
>        1. Fwd: [Frescobaldi] GSoC Project "Add Support for Git
>           Workflows to      Frescobaldi" introduction (Urs Liska)
>
>
>     ----------------------------------------------------------------------
>
>     Message: 1
>     Date: Mon, 22 May 2017 17:36:34 +0200
>     From: Urs Liska <ul@openlilylib.org <mailto:ul@openlilylib.org>>
>     To: lilypond-user <lilypond-user@gnu.org
>     <mailto:lilypond-user@gnu.org>>
>     Subject: Fwd: [Frescobaldi] GSoC Project "Add Support for Git
>             Workflows to    Frescobaldi" introduction
>     Message-ID: <fd0b8b06-3123-d7ac-9498-299be16568b8@openlilylib.org
>     <mailto:fd0b8b06-3123-d7ac-9498-299be16568b8@openlilylib.org>>
>     Content-Type: text/plain; charset="utf-8"
>
>     Hi LilyPond users,
>
>     below is a message by Wen Xin, a student who will work on adding Git
>     support to Frescobaldi over the summer as his GSoC project.
>
>     Please have a look at the introduction and also the Wiki page that is
>     linked, we would like to have more discussion before going into actual
>     implementation.
>
>     Best
>     Urs
>
>     #############
>
>     Hi developers,
>
>
>
>     my name is Wen Xin. I?m pursuing my master degree of computer
>     science in
>     Beijing University of Posts and Telecommunications. I?ve posted two
>     posts before. And I guess you all know that I will be mentored by
>     Urs in
>     this summer while working on the projec/t Add Support for Git
>     Workflows
>     to Frescobaldi. /
>
>
>
>     In my case, this project is to write a Git plugin for Frescobaldi. It
>     will have similar functionalities like other editors? Git plugins:
>
>     -      Git diff in gutter
>
>     <http://oq5gcgc8d.bkt.gdipper.com/GSOC/wiki/12.jpg
>     <http://oq5gcgc8d.bkt.gdipper.com/GSOC/wiki/12.jpg>>
>
>     display Git diff in gutter
>
>
>     -      Stage and discard changes in editor
>
>     -      Commit in editor
>
>     -      ?
>
>
>     A Git initialized file will have three states: modified, staged,
>     committed. Around the file?s three states, I design a Git
>     work-flow. All
>     the operations included will be implemented into Frescobaldi. For more
>     details, you can check this wiki
>     <https://github.com/wbsoft/frescobaldi/wiki/GSoC-2017:-Git-Support
>     <https://github.com/wbsoft/frescobaldi/wiki/GSoC-2017:-Git-Support>>.
>
>     <http://oq5gcgc8d.bkt.gdipper.com/fres%20%283%29.png
>     <http://oq5gcgc8d.bkt.gdipper.com/fres%20%283%29.png>>
>
>
>
>
>
>
>
>     This design is mainly discussed by me and Urs. We want to hear more
>     voices from the community to help make this design become better and
>     more practical. Please comment below if you have related ideas,
>     thank you!
>
>
>
>     Best,
>
>     Wen Xin
>
>     --
>     Frescobaldi homepage: http://www.frescobaldi.org/
>     Mailing list: http://groups.google.com/group/frescobaldi
>     <http://groups.google.com/group/frescobaldi>
>     Issue tracker: https://github.com/wbsoft/frescobaldi/issues
>     <https://github.com/wbsoft/frescobaldi/issues>
>     -------------- next part --------------
>     An HTML attachment was scrubbed...
>     URL:
>     <http://lists.gnu.org/archive/html/lilypond-user/attachments/20170522/029deb0d/attachment.html
>     <http://lists.gnu.org/archive/html/lilypond-user/attachments/20170522/029deb0d/attachment.html>>
>
>     ------------------------------
>
>     Subject: Digest Footer
>
>     _______________________________________________
>     lilypond-user mailing list
>     lilypond-user@gnu.org <mailto:lilypond-user@gnu.org>
>     https://lists.gnu.org/mailman/listinfo/lilypond-user
>     <https://lists.gnu.org/mailman/listinfo/lilypond-user>
>
>
>     ------------------------------
>
>     End of lilypond-user Digest, Vol 174, Issue 74
>     **********************************************
>
>
>
>
> _______________________________________________
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

-- 
ul@openlilylib.org
https://openlilylib.org
http://lilypondblog.org


[Attachment #5 (text/html)]

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">Am 25.05.2017 um 14:04 schrieb Leszek
      Wroński:<br>
    </div>
    <blockquote
cite="mid:CANmJ-E7afB4kq0ku5O=mLVv5r2kyXjbbVN3oMFxTqSq+hhqNFQ@mail.gmail.com"
      type="cite">
      <div dir="ltr"><br>
        <div class="gmail_extra">Guys,</div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">apologies if I've missed something
          obvious, but what is the intended place for discussing the
          very welcome 'Add Git support to Frescobaldi' project? Here?
          The Frescobaldi forum? The wiki (but where?)?</div>
      </div>
    </blockquote>
    <br>
    Well, the "natural" place for the discussion is the Frescobaldi
    mailing list. But as I assume not all LilyPond/Frescobaldi users
    actually are subscribed to that (and also LilyPond/not-Frescobaldi
    users may have interesting views on the subject) I decided to
    forward it to lilypond-user as well.<br>
    <br>
    So while I hope it will not confuse people I suggest discussing the
    project on either of the mailings lists.<br>
    The Wiki will probably be updated by Xin himself (or maybe also me).<br>
    <br>
    <blockquote
cite="mid:CANmJ-E7afB4kq0ku5O=mLVv5r2kyXjbbVN3oMFxTqSq+hhqNFQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">(I just have a minor requst: it would
          be convenient if we could create and change branches, I don't
          see that on the function list.)</div>
      </div>
    </blockquote>
    <br>
    Well, there are lots of things one could add to the list and wish,
    but we have decided to limit the project plan to this "core Git
    workflow". If that should be finished "too early" we will discuss
    what to implement in addition. And if the GSoC project will "only"
    implement the current plan there still will be a robust foundation
    to add more functionality later.<br>
    <br>
    <blockquote
cite="mid:CANmJ-E7afB4kq0ku5O=mLVv5r2kyXjbbVN3oMFxTqSq+hhqNFQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">When it comes to the diff presentation,
          I'm partial to the 'Emacs + magit' combination (<a
            moz-do-not-send="true"
            href="https://www.emacswiki.org/emacs/Magit">https://www.emacswiki.org/emacs/Magit</a>
  )</div>
        <div class="gmail_extra"><br>
        </div>
      </div>
    </blockquote>
    We should keep that in mind. But for now we're only interested in
    unstaged and staged changes.<br>
    <br>
    Urs<br>
    <br>
    <blockquote
cite="mid:CANmJ-E7afB4kq0ku5O=mLVv5r2kyXjbbVN3oMFxTqSq+hhqNFQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">Good luck with the project!</div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">Cheers,</div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">Leszek.</div>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On 22 May 2017 at 18:00, <span
              dir="ltr">&lt;<a moz-do-not-send="true"
                href="mailto:lilypond-user-request@gnu.org"
                target="_blank">lilypond-user-request@gnu.org</a>&gt;</span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex"><br>
              <br>
                   1. Fwd: [Frescobaldi] GSoC Project "Add Support for Git<br>
                       Workflows to         Frescobaldi" introduction (Urs
              Liska)<br>
              <br>
              <br>
              ------------------------------<wbr>------------------------------<wbr>----------<br>
  <br>
              Message: 1<br>
              Date: Mon, 22 May 2017 17:36:34 +0200<br>
              From: Urs Liska &lt;<a moz-do-not-send="true"
                href="mailto:ul@openlilylib.org">ul@openlilylib.org</a>&gt;<br>
              To: lilypond-user &lt;<a moz-do-not-send="true"
                href="mailto:lilypond-user@gnu.org">lilypond-user@gnu.org</a>&gt;<br>
              Subject: Fwd: [Frescobaldi] GSoC Project "Add Support for
              Git<br>
                          Workflows to      Frescobaldi" introduction<br>
              Message-ID: &lt;<a moz-do-not-send="true"
                href="mailto:fd0b8b06-3123-d7ac-9498-299be16568b8@openlilylib.org">fd0b8b06-3123-d7ac-9498-<wbr>299be16568b8@openlilylib.org</a>&gt;<br>
  Content-Type: text/plain; charset="utf-8"<br>
              <br>
              Hi LilyPond users,<br>
              <br>
              below is a message by Wen Xin, a student who will work on
              adding Git<br>
              support to Frescobaldi over the summer as his GSoC
              project.<br>
              <br>
              Please have a look at the introduction and also the Wiki
              page that is<br>
              linked, we would like to have more discussion before going
              into actual<br>
              implementation.<br>
              <br>
              Best<br>
              Urs<br>
              <br>
              #############<br>
              <br>
              Hi developers,<br>
              <br>
              <br>
              <br>
              my name is Wen Xin. I?m pursuing my master degree of
              computer science in<br>
              Beijing University of Posts and Telecommunications. I?ve
              posted two<br>
              posts before. And I guess you all know that I will be
              mentored by Urs in<br>
              this summer while working on the projec/t Add Support for
              Git Workflows<br>
              to Frescobaldi. /<br>
              <br>
              <br>
              <br>
              In my case, this project is to write a Git plugin for
              Frescobaldi. It<br>
              will have similar functionalities like other editors? Git
              plugins:<br>
              <br>
              -         Git diff in gutter<br>
              <br>
              &lt;<a moz-do-not-send="true"
                href="http://oq5gcgc8d.bkt.gdipper.com/GSOC/wiki/12.jpg"
                rel="noreferrer" \
target="_blank">http://oq5gcgc8d.bkt.gdipper.<wbr>com/GSOC/wiki/12.jpg</a>&gt;<br>  \
<br>  display Git diff in gutter<br>
              <br>
              <br>
              -         Stage and discard changes in editor<br>
              <br>
              -         Commit in editor<br>
              <br>
              -         ?<br>
              <br>
              <br>
              A Git initialized file will have three states: modified,
              staged,<br>
              committed. Around the file?s three states, I design a Git
              work-flow. All<br>
              the operations included will be implemented into
              Frescobaldi. For more<br>
              details, you can check this wiki<br>
              &lt;<a moz-do-not-send="true"
                href="https://github.com/wbsoft/frescobaldi/wiki/GSoC-2017:-Git-Support"
                
                rel="noreferrer" \
target="_blank">https://github.com/wbsoft/<wbr>frescobaldi/wiki/GSoC-2017:-<wbr>Git-Support</a>&gt;.<br>
  <br>
              &lt;<a moz-do-not-send="true"
                href="http://oq5gcgc8d.bkt.gdipper.com/fres%20%283%29.png"
                rel="noreferrer" \
target="_blank">http://oq5gcgc8d.bkt.gdipper.<wbr>com/fres%20%283%29.png</a>&gt;<br>  \
<br>  <br>
              <br>
              <br>
              <br>
              <br>
              <br>
              This design is mainly discussed by me and Urs. We want to
              hear more<br>
              voices from the community to help make this design become
              better and<br>
              more practical. Please comment below if you have related
              ideas, thank you!<br>
              <br>
              <br>
              <br>
              Best,<br>
              <br>
              Wen Xin<br>
              <br>
              --<br>
              Frescobaldi homepage: <a moz-do-not-send="true"
                href="http://www.frescobaldi.org/" rel="noreferrer"
                target="_blank">http://www.frescobaldi.org/</a><br>
              Mailing list: <a moz-do-not-send="true"
                href="http://groups.google.com/group/frescobaldi"
                rel="noreferrer" \
target="_blank">http://groups.google.com/<wbr>group/frescobaldi</a><br>  Issue \
tracker: <a moz-do-not-send="true"  \
                href="https://github.com/wbsoft/frescobaldi/issues"
                rel="noreferrer" \
                target="_blank">https://github.com/wbsoft/<wbr>frescobaldi/issues</a><br>
                
              -------------- next part --------------<br>
              An HTML attachment was scrubbed...<br>
              URL: &lt;<a moz-do-not-send="true"
href="http://lists.gnu.org/archive/html/lilypond-user/attachments/20170522/029deb0d/attachment.html"
  rel="noreferrer" target="_blank">http://lists.gnu.org/archive/<wbr>html/lilypond-user/<wbr>attachments/20170522/029deb0d/<wbr>attachment.html</a>&gt;<br>
  <br>
              ------------------------------<br>
              <br>
              Subject: Digest Footer<br>
              <br>
              ______________________________<wbr>_________________<br>
              lilypond-user mailing list<br>
              <a moz-do-not-send="true"
                href="mailto:lilypond-user@gnu.org">lilypond-user@gnu.org</a><br>
              <a moz-do-not-send="true"
                href="https://lists.gnu.org/mailman/listinfo/lilypond-user"
                rel="noreferrer" \
target="_blank">https://lists.gnu.org/mailman/<wbr>listinfo/lilypond-user</a><br>  \
<br>  <br>
              ------------------------------<br>
              <br>
              End of lilypond-user Digest, Vol 174, Issue 74<br>
              ******************************<wbr>****************<br>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
lilypond-user mailing list
<a class="moz-txt-link-abbreviated" \
href="mailto:lilypond-user@gnu.org">lilypond-user@gnu.org</a> <a \
class="moz-txt-link-freetext" \
href="https://lists.gnu.org/mailman/listinfo/lilypond-user">https://lists.gnu.org/mailman/listinfo/lilypond-user</a>
 </pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
<a class="moz-txt-link-abbreviated" \
href="mailto:ul@openlilylib.org">ul@openlilylib.org</a> <a \
class="moz-txt-link-freetext" \
href="https://openlilylib.org">https://openlilylib.org</a> <a \
class="moz-txt-link-freetext" \
href="http://lilypondblog.org">http://lilypondblog.org</a></pre>  </body>
</html>



_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic