[ANN] Wine @ SourceForge

[Dimitrie O. Paun]

Hi folks,

Some of you probably know that we had a wine project at SourceForge
for a long time, but not much was done with it. Recently, we decided
to transform it into our official download site:

http://sourceforge.net/project/showfiles.php?group_id=6241

It currently hosts source tarballs, support files, and binary packages
for FreeBSD, RedHat, and Slackware. Check it out.

We invite comments, criticism, and/or praise :).

[Eric Pouech]

Dimitrie O. Paun wrote:
> Hi folks,
>
> Some of you probably know that we had a wine project at SourceForge
> for a long time, but not much was done with it. Recently, we decided
> to transform it into our official download site:
>
> http://sourceforge.net/project/showfiles.php?group_id=6241
>
> It currently hosts source tarballs, support files, and binary packages
> for FreeBSD, RedHat, and Slackware. Check it out.
>
> We invite comments, criticism, and/or praise :).

I think we need to define clearly what is going to appear on winehq on 
one hand, and on SF on the other hand:
- which parts/info... are only be hosted on winehq
- which parts/info... are only be hosted on SF
- which parts/info... are only be hosted on both

since, the revamp of winehq is taking place, it may be worthwile to 
explain this split a little bit more

I'm also worried about the sort of trouble we had to maintain all 
RPM/DEB/... available on winehq, so what's going to change (for good) on SF

A+

[Dimitrie O. Paun]

On March 23, 2003 01:50 pm, Eric Pouech wrote:
> I think we need to define clearly what is going to appear on winehq on
> one hand, and on SF on the other hand:
> - which parts/info... are only be hosted on winehq
> - which parts/info... are only be hosted on SF
> - which parts/info... are only be hosted on both

For now things are pretty clear:
  -- the "Home" on SF points to www.winehq.org
  -- we are going to store only downloadable files on SF:
    - official tarballs
    - 3rd party support files that we can distribute
    - as many binary packages as possible (currently,
      we have binary packages for Debian and Suse, but
      the respective maintainers have not voiced their
      opinion on the matter).
  -- the other SF features (mailing lists, CVS, bug tracker,
     patch tracker, etc.) are not currently used. However,
     I will try to monitor the bug & patch tracker in case
     people start using them.

Did I leave anything out?

[Eric Pouech]

Dimitrie O. Paun wrote:
> On March 23, 2003 01:50 pm, Eric Pouech wrote:
> > I think we need to define clearly what is going to appear on winehq on
> > one hand, and on SF on the other hand:
> > - which parts/info... are only be hosted on winehq
> > - which parts/info... are only be hosted on SF
> > - which parts/info... are only be hosted on both
>
> For now things are pretty clear:
>   -- the "Home" on SF points to www.winehq.org
>   -- we are going to store only downloadable files on SF:
> - official tarballs
> - 3rd party support files that we can distribute
> - as many binary packages as possible (currently,
> we have binary packages for Debian and Suse, but
> the respective maintainers have not voiced their
> opinion on the matter).
>
> -- the other SF features (mailing lists, CVS, bug tracker,
>      patch tracker, etc.) are not currently used. However,
>      I will try to monitor the bug & patch tracker in case
>      people start using them.
>
> Did I leave anything out?

my point was really to ensure that winehq.org will remain the focal 
point for wine. this seems to be the case for now (but "for now" can 
always change)
A+

[Dimitrie O. Paun]

On Tue, 25 Mar 2003, Eric Pouech wrote:
> my point was really to ensure that winehq.org will remain the focal 
> point for wine.

Absolutely -- I have no intention in taking the SF stuff any further
than necessary. I'll monitor the bug/support/patch tracker in case
some people use those (few do) so they don't feel left out, but I don't 
want that do become 'primary' in any way, shape or form. I've stated 
before that I think wine-devel and wine-patches are the right forums 
for these issues, from all points of view.