<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Hi, Ignacio<br>
    <br>
    I am open to suggestions (accusations not accepted). I am a newbie
    in this and largely unqualified; however, I don't see a rush of more
    qualified volunteers to take this task on. <br>
    <br>
    Many, possibly a majority of these activities have not been touched
    since 2010. I would not like to wait until we get contact from
    contributors who have moved on to a day job.<br>
    <br>
    If all of the ASLO activities can be moved as repositories to
    github/sugarlabs - nothing has been lost. Corrections can be made to
    those repositories to include the famous 'repeal and replace'. The
    immediate benefit is that the developer hub on ASLO can be
    discontinued simplifying an effort to make ALSO itself more stable
    and maintainable. <br>
    <br>
    In addition, github makes it easier for the community at large to
    make corrections or improvements to the activities knowing that they
    are working on the one and only official version.<br>
    <br>
    In any case, a repository appears to give no credit to the creator -
    only to contributors. Contributions are, by definition, post the
    move of the repository to github.<br>
    <br>
    I am looking for advice on how to relate git.sugarlabs.org to the
    github repositories.<br>
    <br>
    Tony<br>
    <br>
    <div class="moz-cite-prefix">On 04/23/2017 10:23 AM, Ignacio
      Rodríguez wrote:<br>
    </div>
    <blockquote
cite="mid:CAA-Wi4e83B-Kbn5-VkAcofiis7=GbChmHMCucPW3Ruh=8=WdNg@mail.gmail.com"
      type="cite">
      <div dir="auto">I think we should focus on contact the creators of
        the activities before moving them -- sugar-activities org
        basically contains all aslo activities and nothing else (which
        can be used in case any activity has no maintainer/git
        repository)  --; probably most of the activities are in <a
          moz-do-not-send="true" href="http://git.sugarlabs.org"
          target="_blank">git.sugarlabs.org</a> (so we can move them
        safely).</div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Apr 22, 2017 22:24, "Walter Bender"
          <<a moz-do-not-send="true"
            href="mailto:walter.bender@gmail.com" target="_blank">walter.bender@gmail.com</a>>
          wrote:<br type="attribution">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div dir="ltr">Tony,
              <div><br>
              </div>
              <div>I can not speak for every contributor, but there is a
                lot more to contributing to a project than the end
                result. Many contributors take pride in their
                contributions and these days, one's GitHub contributions
                have value in the job market. A wholesale removal of the
                git history by Sugar Labs does not send a very welcoming
                message to past or future contributors. On a more
                mundane level, the lack of history means as a developer
                I have no way of knowing whom to ask for help.</div>
              <div><br>
              </div>
              <div>-walter</div>
            </div>
            <div class="gmail_extra"><br>
              <div class="gmail_quote">On Sat, Apr 22, 2017 at 9:17 PM,
                Tony Anderson <span dir="ltr"><<a
                    moz-do-not-send="true"
                    href="mailto:tony_anderson@usa.net" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:tony_anderson@usa.net">tony_anderson@usa.net</a></a>></span>
                wrote:<br>
                <blockquote class="gmail_quote" style="margin:0 0 0
                  .8ex;border-left:1px #ccc solid;padding-left:1ex">
                  <div text="#000000" bgcolor="#FFFFFF"> The process for
                    installing repositories requires that the target
                    repository be empty. <br>
                    <br>
                    I would appreciate someone who could itemize what
                    needs to be in a repository such as the license,
                    .gitignore, README.md, and so on. Much of that can
                    probably be done by a script using the information
                    available from ASLO.<br>
                    <br>
                    My sense is that PRs are appropriate for changes to
                    an activities functions (such as a port to gtk3) but
                    not for housekeeping.<span
                      class="m_4462542101142619432HOEnZb"><font
                        color="#888888"><br>
                        <br>
                        Tony</font></span><span><br>
                      <br>
                      <div
                        class="m_4462542101142619432m_8222172837798268816moz-cite-prefix">On
                        04/23/2017 07:27 AM, Love Mehta wrote:<br>
                      </div>
                      <blockquote type="cite">
                        <div dir="ltr">
                          <div>There are many activities lacking a
                            description at <a moz-do-not-send="true"
                              class="m_4462542101142619432m_8222172837798268816moz-txt-link-freetext"
                              href="https://github.com/sugar"
                              target="_blank">https://github.com/sugar</a>-activ<wbr>ities/ 

                            and it is hard to know the name and purpose
                            of the activity specially in the web
                            activities where one has to open the
                            index.html file. I think we should add the
                            descriptions from <a moz-do-not-send="true"
class="m_4462542101142619432m_8222172837798268816moz-txt-link-freetext"
                              href="https://activities.sugarlabs"
                              target="_blank">https://activities.sugarlabs</a>.o<wbr>rg

                            for each activity to the readme markdown
                            file. I thought of doing this but this will
                            lead to a large number of pull requests.
                            Should I go ahead with it?<br>
                          </div>
                        </div>
                      </blockquote>
                      <br>
                    </span></div>
                </blockquote>
              </div>
              <br>
              <br clear="all">
              <div><br>
              </div>
              -- <br>
              <div class="m_4462542101142619432gmail_signature"
                data-smartmail="gmail_signature">
                <div dir="ltr">
                  <div><font><font>Walter Bender</font></font><br>
                    <font><font>Sugar Labs</font></font></div>
                  <div><font><a moz-do-not-send="true"
                        href="http://www.sugarlabs.org" target="_blank"><font>http://www.sugarlabs.org</font></a></font><br>
                    <br>
                  </div>
                </div>
              </div>
            </div>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>