libmetalink new release & moving to github, should other projects move to github?

[Anthony Bryan]

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 <notifi...@github.com>
Date: Sat, Jun 27, 2015 at 2:35 AM
Subject: [libmetalink] libmetalink v0.1.3
To: metalink-dev/libmetalink <libme...@noreply.github.com>

• 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.

--

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

[Bram Neijt]

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

Bram

--
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 metalink-discus...@googlegroups.com.
To post to this group, send email to metalink-...@googlegroups.com.
Visit this group at http://groups.google.com/group/metalink-discussion.
For more options, visit https://groups.google.com/d/optout.

[Anthony Bryan]

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.

[Neil M.]

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

> <mailto:libme...@noreply.github.com>>
>
>
> * 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
> metalink-discus...@googlegroups.com

> <mailto:metalink-discus...@googlegroups.com>.

> To post to this group, send email to
> metalink-...@googlegroups.com

> <mailto:metalink-...@googlegroups.com>.

> 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 metalink-discus...@googlegroups.com

> <mailto:metalink-discus...@googlegroups.com>.

> To post to this group, send email to
> metalink-...@googlegroups.com

> <mailto:metalink-...@googlegroups.com>.

> 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 metalink-discus...@googlegroups.com

> <mailto:metalink-discus...@googlegroups.com>.

> To post to this group, send email to
> metalink-...@googlegroups.com

> <mailto:metalink-...@googlegroups.com>.

[Anthony Bryan]

On Wed, Jul 1, 2015 at 6:53 PM, Neil M. <nabb...@gmail.com> wrote:
> 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

I'm not sure? I assumed the others were just imported. but maybe?
perhaps the Windows support is better now too

> 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. :-)

yeh, nasty tricks!

> 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.

yes, gh can do binaries. I'm not sure if TT pays for it, but
libmetalink has them

https://github.com/metalink-dev/libmetalink/releases

> 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.

it might be good to explicitly sort out the licensing anyways?

> 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.

I don't remember...

hmm, trac links seem to redirect for me too
http://sourceforge.net/apps/trac/metalinks/wiki/GettingSupport

> 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.

that's prolly a good idea. does it export the issues too, or just code?

> email to metalink-discus...@googlegroups.com.
> To post to this group, send email to metalink-...@googlegroups.com.

[Tatsuhiro Tsujikawa]

On Thu, Jul 2, 2015 at 12:46 PM Anthony Bryan <anthon...@gmail.com> wrote:

On Wed, Jul 1, 2015 at 6:53 PM, Neil M. <nabb...@gmail.com> wrote:
> 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

I'm not sure? I assumed the others were just imported. but maybe?
perhaps the Windows support is better now too

> 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. :-)

yeh, nasty tricks!

> 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.

yes, gh can do binaries. I'm not sure if TT pays for it, but
libmetalink has them

https://github.com/metalink-dev/libmetalink/releases

github supports binary file distributions for free. When creating release, you will see the upload section, where you can upload files.

Best regards,

Tatsuhiro Tsujikawa

[Neil M]

I think we are pretty good on having markings in the code files
themselves and full licenses in the directories. What we should
probably have is a page describing how new contributions should be
handled. For example you should use a OSI approved license, include
that in code headers, etc. We could make specific license
recommendations like LGPL for libraries, GPL for software, just as an
example, but I don't think we have to.

>
>> 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.
>
> I don't remember...
>
> hmm, trac links seem to redirect for me too
> http://sourceforge.net/apps/trac/metalinks/wiki/GettingSupport

Looks like trac is dead:

https://sourceforge.net/p/forge/community-docs/Hosted%20Apps%20Retirement/

I know they had an incomplete howto on how to move it to project space
that I guess never actually worked, the data might still be there
somewhere.

>
>> 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.
>
> that's prolly a good idea. does it export the issues too, or just code?

Yeah it will do the wiki too. I think the one thing it doesn't do is
the "Downloads" aka binary releases but there don't appear to be any in
this particular case:

https://code.google.com/p/support-tools/wiki/GitHubExporterFAQ

[Neil M]

Yeah I have the trac backup files so we might be able to do something
with those.

[Anthony Bryan]

we could have a README.rst which seems to be displayed beyond the code
like how libmetalink does it
https://github.com/metalink-dev/libmetalink

does it make sense to have all the separate directories be different
repositories under https://github.com/metalink-dev or keep them the
way they are?

>>> 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.
>>
>>
>> I don't remember...
>>
>> hmm, trac links seem to redirect for me too
>> http://sourceforge.net/apps/trac/metalinks/wiki/GettingSupport
>
>
> Looks like trac is dead:
>
> https://sourceforge.net/p/forge/community-docs/Hosted%20Apps%20Retirement/
>
> I know they had an incomplete howto on how to move it to project space that
> I guess never actually worked, the data might still be there somewhere.
>
>>
>>> 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.
>>
>>
>> that's prolly a good idea. does it export the issues too, or just code?
>
>
> Yeah it will do the wiki too. I think the one thing it doesn't do is the
> "Downloads" aka binary releases but there don't appear to be any in this
> particular case:
>
> https://code.google.com/p/support-tools/wiki/GitHubExporterFAQ

cool, there are a few releases:
https://code.google.com/p/metalink-chrome-extension/downloads/list?can=1&q=

the rest were only on the Chrome Web Store for autoupdating
https://chrome.google.com/webstore/detail/metalink-downloader/jnpljlobbiggcdikagmiepniibjdinap

looking at this page, it still has 8,000 users. nothing to sneeze at.
it might be worth working on the issues if anyone is interested

> Yeah I have the trac backup files so we might be able to do something with
> those.

great!

[Bram Neijt]

How are we going to structure the whole transition. I jumped in by
running a subversion import and configuring SF to have a message
telling everybody we are moving, but I never got around to making a
TODO list with things like "ressurecting the release binaries on
github".

Should we create a collection of issues on the github tracker?

[Neil M]

Yeah I guess while we are moving things around that makes a lot of sense
to split them up. We can keep issues separate that way too.

[Anthony Bryan]

separate issues & downloads/binaries too, altho checking at SF, it
looks like only Metalink checker, command line, & Editor really had
releases.

I dunno what makes the other directories/smaller projects more
visible/discoverable, all being in one repo or having separate ones?

or maybe have the major ones & another misc/extra-tools for the other
things that aren't touched much?

[Bram Neijt]

Ooh, I'm against splitting up. I think that with the little amount of
change the project has, we should keep everything in one place to keep
it more lively.

What I was trying to talk about was making a TODO list. Like:
- Create release tags
- Add the SF releases to the release tag
- Move trac information into a new wiki structure on github
etc.

Maybe it's best to start a single github issue "the move from SF" and
add comments about what needs to be done there?

[Anthony Bryan]

On Thu, Jul 2, 2015 at 1:49 PM, Bram Neijt <bne...@gmail.com> wrote:
> Ooh, I'm against splitting up. I think that with the little amount of
> change the project has, we should keep everything in one place to keep
> it more lively.

true, good point!

> What I was trying to talk about was making a TODO list. Like:
> - Create release tags
> - Add the SF releases to the release tag
> - Move trac information into a new wiki structure on github
> etc.
>
> Maybe it's best to start a single github issue "the move from SF" and
> add comments about what needs to be done there?

https://github.com/metalink-dev/libmetalink/issues/1

:) I like it.