Re: Project Infrastructure

[John W. Eaton]

On 03/29/2017 02:10 PM, Olaf Till wrote:
> On Wed, Mar 29, 2017 at 12:14:11PM -0400, John W. Eaton wrote:
> > Could someone fill in more details about Octave Forge?
>
> Done.
>
> > As a related issue, maybe this would also be a good time to think about
> > merging the Octave Forge site with the Octave web site?  Would that help
> > users?  Would it be any easier to manage if we did this?
>
> Surely dreamhost doesn't provide multiple hg and git repositories,
> repository access regulations, and release trackers?

No, though they could probably be installed.  But anyway, I'm not 
proposing to move all infrastructure to dreamhost.

> So, since the repository and release infrastructure would have to
> remain on sourceforge anyway(?), I currently don't see an advantage in
> moving the website to dreamhost. It's just another commercial hosting
> provider, with probably a different specific set of flaws. It would
> only be a physical (on hard disk) vicinity to Octave, apart from maybe
> a name change of the website to something without 'sourceforge' in it.

It's not only about where it is hosted, or whether they are hosted and 
developed together, but about whether having what appears to be a single 
web site will provide a better experience for users.  People used to be 
constantly confused by having both Octave and Octave Forge projects. 
Were they the same?  Different?  Was Octave Forge a different version of 
Octave?  Why aren't the Octave sources on Octave Forge?  Why can't I 
find packages on the Octave site.  Etc.

For the users, I think it would be good if we had a single web site, 
where everything appears under the same domain name.

jwe