<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Hi, Walter and Alex<br>
    <br>
    Alex, if you are referring to maintaining ASLO, +1.<br>
    <br>
    My point was not about either gitorious or github but the fact that
    by design the source code for every activity (with some binary
    exceptions) is in the bundle. <br>
    It is always clear where the source is located, in the bundle.
    Frankly, I don't see either gitorious or github as relevant to Sugar
    activities. If we want to encourage learning about version control
    (a focus of a recent GSOC), we should find a way to deliver git with
    Sugar.<br>
    <br>
    As I mentioned many months ago, the appropriate place for the link
    to the the github repository is ASLO. If the link were there, I
    could click on it immediately.<br>
    <br>
    With the current scheme, to find out where the repository  is, I
    need to find the activity on ASLO, download, install (or unzip) it,
    use the Terminal activity and nano to display activity.info, and
    then get back on the internet to use the url. Alternatively, I could
    go to the github/Sugar labs site and scroll through up to seven
    screens to find it.<br>
    <br>
    Tony<br>
    <br>
    <div class="moz-cite-prefix">On 03/14/2017 11:02 AM, Alex Perez
      wrote:<br>
    </div>
    <blockquote
      cite="mid:F89E1D07-068E-4CB9-9BFE-7D67013D818D@alexperez.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      Tony/Walter,
      <div class=""><br class="">
        <div>
          <blockquote type="cite" class="">
            <div class="">On Mar 13, 2017, at 7:28 PM, Walter Bender
              <<a moz-do-not-send="true"
                href="mailto:walter.bender@gmail.com" class="">walter.bender@gmail.com</a>>
              wrote:</div>
            <br class="Apple-interchange-newline">
            <div class="">
              <div dir="ltr" class="">Tony,
                <div class=""><br class="">
                </div>
                <div class="">Not sure I agree about your asserts
                  regarding github vs gitroious.</div>
              </div>
            </div>
          </blockquote>
          <div><br class="">
          </div>
          Count me in here..<br class="">
          <blockquote type="cite" class="">
            <div class="">
              <div dir="ltr" class="">
                <div class=""><br class="">
                </div>
                <div class="">(1) the were/are many activities that were
                  not hosted in gitorious long before we switched to
                  github, so it wasn't obvious where to find the source
                  repo *before* the switch. This is one of the reasons I
                  started add the repo path to the <a
                    moz-do-not-send="true" href="http://activity.info/"
                    class="">activity.info</a> file.</div>
                <div class="">(2) ALSO needs work and maintenance
                  regardless of where the repos are hosted.</div>
              </div>
            </div>
          </blockquote>
          <div><br class="">
          </div>
          And it is incumbent upon Sugar Labs and the board to ensure
          that this happens, even if it requires you to spend actual
          money to make it happen.<br class="">
          <blockquote type="cite" class="">
            <div class="">
              <div dir="ltr" class="">
                <div class=""><br class="">
                </div>
                <div class="">-walter<br class="">
                  <div class="gmail_extra"><br class="">
                    <div class="gmail_quote">On Mon, Mar 13, 2017 at
                      10:02 PM, Tony Anderson <span dir="ltr" class=""><<a
                          moz-do-not-send="true"
                          href="mailto:tony_anderson@usa.net"
                          target="_blank" class=""><a class="moz-txt-link-abbreviated" href="mailto:tony_anderson@usa.net">tony_anderson@usa.net</a></a>></span>
                      wrote:<br class="">
                      <blockquote class="gmail_quote" style="margin:0 0
                        0 .8ex;border-left:1px #ccc
                        solid;padding-left:1ex">
                        <div text="#000000" bgcolor="#FFFFFF" class="">
                          Hi James,<br class="">
                          <br class="">
                          Your book is a wonder and should be much more
                          actively promoted. It is one of the major
                          contributions of Sugar to constructive
                          learning.<br class="">
                          <br class="">
                          I believe the use of <a
                            moz-do-not-send="true"
                            href="http://git.sugarlabs.org/"
                            target="_blank" class="">git.sugarlabs.org</a>
                          and github are major steps backwards from the
                          original conception of Sugar activities as
                          something which users could develop and make
                          available to the community.</div>
                      </blockquote>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </blockquote>
          <div><br class="">
          </div>
          Why do you believe this? It’s simply a convention for version
          control, one which millions of people understand, and does not
          preclude the use of the latter mechanism you describe. They
          are not mutually exclusive. Additionally, anyone can download
          a tarball/zip file of source code, or of a tagged release,
          from github, even if they have zero clue about how git works.
          Git is a convenience for *developers*</div>
        <div><br class="">
          <blockquote type="cite" class="">
            <div class="">
              <div dir="ltr" class="">
                <div class="">
                  <div class="gmail_extra">
                    <div class="gmail_quote">
                      <blockquote class="gmail_quote" style="margin:0 0
                        0 .8ex;border-left:1px #ccc
                        solid;padding-left:1ex">
                        <div text="#000000" bgcolor="#FFFFFF" class="">
                          In the first place, the activity bundle
                          contains the source code that is actually
                          being executed. Second, there is a simple
                          version system in <a moz-do-not-send="true"
                            href="http://activity.info/" target="_blank"
                            class="">activity.info</a>. The Developer
                          Hub at <a moz-do-not-send="true"
                            href="http://activities.sugarlabs.org/"
                            target="_blank" class="">activities.sugarlabs.org</a>
                          supplies an adequate means to control
                          maintenance activities (in the PR sense of
                          having someone monitor changes before
                          releasing them for general use). <br class="">
                        </div>
                      </blockquote>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </blockquote>
          <div><br class="">
          </div>
          We do definitely need to expand upon the filtering abilities,
          to prevent, say, an x86-only activity from being installed on
          ARM, and vice versa.</div>
        <div>
          <blockquote type="cite" class="">
            <div class="">
              <div dir="ltr" class="">
                <div class="">
                  <div class="gmail_extra">
                    <div class="gmail_quote">
                      <blockquote class="gmail_quote" style="margin:0 0
                        0 .8ex;border-left:1px #ccc
                        solid;padding-left:1ex">
                        <div text="#000000" bgcolor="#FFFFFF" class="">
                          <br class="">
                          If one wanted to update an activity, say
                          TuxMath, now the first step would be to clone
                          the repository not install the activity
                          itself. <br class="">
                        </div>
                      </blockquote>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </blockquote>
          <div><br class="">
          </div>
          <div>This is an incorrect assumption. </div>
          <blockquote type="cite" class="">
            <div class="">
              <div dir="ltr" class="">
                <div class="">
                  <div class="gmail_extra">
                    <div class="gmail_quote">
                      <blockquote class="gmail_quote" style="margin:0 0
                        0 .8ex;border-left:1px #ccc
                        solid;padding-left:1ex">
                        <div text="#000000" bgcolor="#FFFFFF" class="">
                          <br class="">
                          The ASLO site needs some work. Currently, the
                          latest version is not necessarily exposed (see
                          Browse or TuxMath, for example). In some
                          cases, activities do not support Arm or use
                          Hulahop and there is no way to specify which
                          versions of Sugar or its platforms are
                          supported. The availability of maintainers who
                          know the PhP implementation of ASLO is
                          apparently dwindling. Perhaps Sugar Labs could
                          undertake to re-implement ASLO using Python
                          (Django, flask, ...) or javascript to broaden
                          the base of potential maintainers. <br
                            class="">
                        </div>
                      </blockquote>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </blockquote>
          <div><br class="">
          </div>
          <blockquote type="cite" class="">
            <div class="">
              <div dir="ltr" class="">
                <div class="">
                  <div class="gmail_extra">
                    <div class="gmail_quote">
                      <blockquote class="gmail_quote" style="margin:0 0
                        0 .8ex;border-left:1px #ccc
                        solid;padding-left:1ex">
                        <div text="#000000" bgcolor="#FFFFFF" class="">
                          <br class="">
                          However, dependence on github creates a
                          duplicate repository for the source code. With
                          400+ activities, there is no mechanism in
                          github to make the activities visible.
                          Currently it may require searching 7 screens
                          to find if an activity is there (unlike ASLO
                          which has an effective search capability). <br
                            class="">
                        </div>
                      </blockquote>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </blockquote>
          <div><br class="">
          </div>
          ASLO is not a source code repository. It’s a convenience to
          end users. I know you think they should be one and the same,
          and in theory they could be, but I don’t necessarily see the
          benefit.<br class="">
          <blockquote type="cite" class="">
            <div class="">
              <div dir="ltr" class="">
                <div class="">
                  <div class="gmail_extra">
                    <div class="gmail_quote">
                      <blockquote class="gmail_quote" style="margin:0 0
                        0 .8ex;border-left:1px #ccc
                        solid;padding-left:1ex">
                        <div text="#000000" bgcolor="#FFFFFF" class="">
                          <br class="">
                          I am sympathetic to the desire to acquaint our
                          users with git and the concept of version
                          control. However, this approach limits the
                          opportunity to those who have internet access
                          (probably a minority of our users). <br
                            class="">
                        </div>
                      </blockquote>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </blockquote>
          <div><br class="">
          </div>
          I don’t see a reason why ASLO couldn’t simply be a front-end,
          pointing to .xo activity files which are mirrored elsewhere
          (even HTTP-accessible via Git/GitHub, or via a global CDN).
          That said, there is some value in hosting the activities
          directly on ASLO. There is also some risk, since, if ASLO goes
          offline, so does access to all activities.</div>
        <div><br class="">
          <blockquote type="cite" class="">
            <div class="">
              <div dir="ltr" class="">
                <div class="">
                  <div class="gmail_extra">
                    <div class="gmail_quote">
                      <blockquote class="gmail_quote" style="margin:0 0
                        0 .8ex;border-left:1px #ccc
                        solid;padding-left:1ex">
                        <div text="#000000" bgcolor="#FFFFFF" class="">
                          A more effective approach would be to
                          determine how git could be installed in Sugar
                          ( a git activity?) so that it can be used.
                          Your book could then be used as a basis for
                          helping our users learn to develop activities
                          using version-control. In this way version
                          control can be used locally by the developer
                          prior to submitting an updated or new activity
                          to ASLO (which may well involve a visit to an
                          internet cafe). <br class="">
                        </div>
                      </blockquote>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </blockquote>
          <div><br class="">
          </div>
          Git can absolutely be used locally (with branches, tags, etc)
          without external access to the Internet. It was designed to be
          use this way. That said, I don’t see why Git needs to be a
          sugar activity. It just needs to be a dependency of the
          development-specific Sugar packages (RPM/deb/etc)<br class="">
          <blockquote type="cite" class="">
            <div class="">
              <div dir="ltr" class="">
                <div class="">
                  <div class="gmail_extra">
                    <div class="gmail_quote">
                      <blockquote class="gmail_quote" style="margin:0 0
                        0 .8ex;border-left:1px #ccc
                        solid;padding-left:1ex">
                        <div text="#000000" bgcolor="#FFFFFF" class="">
                          <br class="">
                          Tony<br class="">
                          <br class="">
                          Tony
                          <div class="">
                            <div class="h5"><br class="">
                              <br class="">
                              <div
                                class="m_-8702763985395152740moz-cite-prefix">On
                                03/14/2017 03:39 AM, James Simmons
                                wrote:<br class="">
                              </div>
                            </div>
                          </div>
                          <blockquote type="cite" class="">
                            <div class="">
                              <div class="h5">
                                <div dir="ltr" class="">All,
                                  <div class=""><br class="">
                                  </div>
                                  <div class="">I have been neglecting
                                    the manual <i class="">Make Your
                                      Own Sugar Activities!</i> ever
                                    since I first wrote it. However, I
                                    did manage to make one needed update
                                    in the laziest way possible. Since
                                    Sugar Labs has moved away from <a
                                      moz-do-not-send="true"
                                      href="http://git.sugarlabs.org/"
                                      target="_blank" class="">git.sugarlabs.org</a>
                                    in favor of GitHub since I wrote the
                                    version control chapter I have added
                                    the following note to that chapter:</div>
                                  <div class=""><br class="">
                                  </div>
                                  <blockquote style="margin:0 0 0
                                    40px;border:none;padding:0px"
                                    class="">
                                    <div class=""><strong class="">Important
                                        Note</strong>: When this chapter
                                      was written Sugar Labs was still
                                      using <strong class=""><a
                                          moz-do-not-send="true"
                                          href="http://git.sugarlabs.org/"
                                          target="_blank" class="">git.sugarlabs.org</a></strong>
                                      as its code repository. While this
                                      still exists, the preferred
                                      repository is now <a
                                        moz-do-not-send="true"
                                        href="https://github.com/"
                                        target="_blank" class=""><a class="moz-txt-link-freetext" href="https://github.com/">https://github.com/</a></a>,
                                      using the <strong class="">sugarlabs</strong>
                                      organization. This chapter is
                                      still a reasonable introduction to
                                      using Git, but when you set up
                                      your project repository you should
                                      use the excellent instructions
                                      provided on GitHub instead of the
                                      Gitorious instructions provided
                                      here.</div>
                                  </blockquote>
                                  <div class=""><br class="">
                                  </div>
                                  <div class="">I hope this helps in
                                    some way.</div>
                                  <div class=""><br class="">
                                  </div>
                                  <div class="">James Simmons</div>
                                  <div class=""><br class="">
                                  </div>
                                </div>
                                <br class="">
                                <fieldset
                                  class="m_-8702763985395152740mimeAttachmentHeader"></fieldset>
                                <br class="">
                              </div>
                            </div>
                            <pre class="">______________________________<wbr class="">_________________
Sugar-devel mailing list
<a moz-do-not-send="true" class="m_-8702763985395152740moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.<wbr class="">org</a>
<a moz-do-not-send="true" class="m_-8702763985395152740moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/<wbr class="">listinfo/sugar-devel</a>
</pre>
    </blockquote>
    

  </div>


______________________________<wbr class="">_________________

Sugar-devel mailing list

<a moz-do-not-send="true" href="mailto:Sugar-devel@lists.sugarlabs.org" class="">Sugar-devel@lists.sugarlabs.<wbr class="">org</a>

<a moz-do-not-send="true" href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank" class="">http://lists.sugarlabs.org/<wbr class="">listinfo/sugar-devel</a>


</blockquote></div>

<div class="">
</div>-- 
<div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class=""><font class=""><font class="">Walter Bender</font></font>
<font class=""><font class="">Sugar Labs</font></font></div><div class=""><font class=""><a moz-do-not-send="true" href="http://www.sugarlabs.org/" target="_blank" class=""><font class="">http://www.sugarlabs.org</font></a></font>

</div></div></div>
</div></div></div>
_______________________________________________
Sugar-devel mailing list
<a moz-do-not-send="true" href="mailto:Sugar-devel@lists.sugarlabs.org" class="">Sugar-devel@lists.sugarlabs.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
</div></blockquote></div>
</div>


</blockquote>
</body></html>