I don't have a github account. I've generally steered clear of git due to ugly Windows support compared to subversion. But it looks like github has branched out to support subversion now too and that is still how we access it? That sounds fine to me. I've been migrating some of my other things away from sourceforge, in particular the downloads due to the installer tricks they have been pulling. And I can add metalinks that way too. :-)

A few other things:

1) Do we have a way to distribute binaries? It looks like github can do this, I guess I just haven't seen it. I don't know if this is one of the pay-for upgrades or we have a quota limit or what.

2) One of the issues with github is that there is a lot of code just thrown up there without license information. With SF you could set a general license in the project page. I think we are OK with our stuff but need to keep that in mind if merging other projects in and adding new stuff.

3) Is there anything in the SF trac we need to grab? I think that had some bug tracking and documentation? I can't seem to get to it now.

4) Google Code is also shutting down and I'm an owner for metalink-chrome-extension. Looks like they make it easy to export to github so if you want to do that too it should be easy.

Neil

On 6/28/2015 6:20 PM, Anthony Bryan wrote:
I invited you & Hampus, but I don't see that Neil has an account on
github. if Neil's on board (he's actually been making commits lately),
that would cover everyone listed on
http://sourceforge.net/projects/metalinks/

Tatsuhiro imported libmetalink from bzr, I assume there's an importer
for svn. so hopefully we can get it all done at once if everyone agrees
that it's a good move.

On Sun, Jun 28, 2015 at 1:47 PM, Bram Neijt <[email protected]
<mailto:[email protected]>> wrote:

    I'm all for it. Is it something I can help with?

    Bram

    On Sat, Jun 27, 2015 at 11:09 PM, Anthony Bryan
    <[email protected] <mailto:[email protected]>> wrote:

        Tatsuhiro fixed a bug that the wget GSoC student ran across (&
        some other bugs).

        he also moved libmetalink from launchpad/bzr to github:
        https://github.com/metalink-dev/libmetalink

        we also have the project address (metalink was taken)
        https://github.com/metalink-dev/

        I've been thinking for a while it might be good to move to
        github & away from SourceForge (at least for our project there).
        SF seems to be getting less reputable lately & doing shady
        things, so now might be the time before it gets worse. does
        anyone have any objections or other suggestions?

        we have always been an umbrella type project with many parts
        working together, so no one needs to be under the project on
        github, but if you do just let us know.

        ---------- Forwarded message ----------
        From: *Tatsuhiro Tsujikawa* <[email protected]
        <mailto:[email protected]>>
        Date: Sat, Jun 27, 2015 at 2:35 AM
        Subject: [libmetalink] libmetalink v0.1.3
        To: metalink-dev/libmetalink <[email protected]
        <mailto:[email protected]>>


          * Use pkg-config to detect expat BUG#1241639
          * Define INT32_MIN if not defined BUG#1241635
          * Remove -Wall from compiler flags BUG#1241633
          * Fix bug that signature is not parsed properly BUG#1466506
          * Fix uninitialized pointer dereference and malloc return
            value check

        —
        View it on GitHub
        
<https://github.com/metalink-dev/libmetalink/releases/tag/release-0.1.3>.




        --
        (( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
           )) Easier, More Reliable, Self Healing Downloads

        --
        You received this message because you are subscribed to the
        Google Groups "Metalink Discussion" group.
        To unsubscribe from this group and stop receiving emails from
        it, send an email to
        [email protected]
        <mailto:[email protected]>.
        To post to this group, send email to
        [email protected]
        <mailto:[email protected]>.
        Visit this group at
        http://groups.google.com/group/metalink-discussion.
        For more options, visit https://groups.google.com/d/optout.


    --
    You received this message because you are subscribed to the Google
    Groups "Metalink Discussion" group.
    To unsubscribe from this group and stop receiving emails from it,
    send an email to [email protected]
    <mailto:[email protected]>.
    To post to this group, send email to
    [email protected]
    <mailto:[email protected]>.
    Visit this group at http://groups.google.com/group/metalink-discussion.
    For more options, visit https://groups.google.com/d/optout.




--
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
   )) Easier, More Reliable, Self Healing Downloads

--
You received this message because you are subscribed to the Google
Groups "Metalink Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To post to this group, send email to
[email protected]
<mailto:[email protected]>.
Visit this group at http://groups.google.com/group/metalink-discussion.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Metalink 
Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/metalink-discussion.
For more options, visit https://groups.google.com/d/optout.

Reply via email to