Re: We need to talk about SourceForge

[Tatsuro MATSUOKA]

----- Original Message -----

> From: Tatsuro MATSUOKA 
> To: tmacchant"octave-maintainers
> Cc: 
> Date: 2015/6/16, Tue 15:53
> Subject: Re: We need to talk about SourceForge
<snip>
> Detailed information for Gimp project was shown on the above
> 
>  http://lwn.net/Articles/646118/
> 


I do not want to stand SourceForge (SF) side but I introduce the below

Third party offers will be presented with Opt-In projects only

http://sourceforge.net/blog/third-party-offers-will-be-presented-with-opt-in-projects-only/


SourceForge Past, Present and Future: Working to Maintain the Integrity of Our 
Open Source Backbone

http://sourceforge.net/blog/sourceforge-past-present-and-future-working-to-maintain-the-integrity-of-our-open-source-backbone/


Reading the above, they added adware to a very small number of unmaintained 
SourceForge projects.
The octave-forge project may not become a target of adware because the project 
is active and maintained.

However, their statement for what they did Gimp for windows is not consistent 
with statements of Gimp project.
I think that octave-forge (OF) started to leave SF seeing that Carne and jwe 
started move some contents from SF to Octave core.


The remaining issues: (I do not fully understand the issue so that please 
correct me)
 
 1. move version control system for OF packages somewhere else
  jwe stated that "I think savannah currently only allows one hg archive per 
project." 
  so that we have to move them to some other place
   Bitbucket(git and mecurial), Github (git) or somewhere else?

  https://en.wikipedia.org/wiki/Comparison_of_source_code_hosting_facilities

 

 2. maintain  facilities >> pkg install -forge (package name) 
  

Tatsuro