Re: [Mingw-w64-public] About the recent sourceforge events
Hi, One more service provider to mention and I think that one is very notable: launchpad. Historically, launchpad had only supported code hosting through bazaar but this is no longer the case: http://blog.launchpad.net/general/git-code-hosting-beta It's still beta but it seems it is already usable and launchpad has all the features currently used by mingw-w64 on sourceforge: mailing-lists, code hosting, forum, bug tracker, file hosting, ... and the UI isn't too clumsy. I haven't yet tried to setup a project there but I have fairly high hopes for it. -- Adrien Nader -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] About the recent sourceforge events
On 6/12/2015 05:21, Martin Mitáš wrote: > > Umm, it is much more complicated then that. There are many mingw-w64 repos > on github: > > (1) mirror/mingw-w64, which is likely a mirror repo on sf.net [1], > (2) as of now, 7 forks of the above [2] (AndreRH's repo is one of these), > (3) mingw-w64/mingw-w64 [3], where 1st "mingw-w64" stands for an organization > account [4] (i.e. not a personal account). However there are no public > members, i.e. only those within the organization can see user accounts which > are members of the organization so I have no idea who is behind that. If it > is no one from mingw-w64 of project's core developer, perhaps you could > try to contact github's support to get some contact to them. > > [1] https://github.com/mirror/mingw-w64 > [2] https://github.com/mirror/mingw-w64/network/members > [3] https://github.com/mingw-w64/mingw-w64 > [4] https://github.com/blog/674-introducing-organizations > The mingw-w64 organization on github is owned by me, yes it is a mirror that is manually synced. 0xD4EBC740.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] About the recent sourceforge events
Umm, it is much more complicated then that. There are many mingw-w64 repos on github: (1) mirror/mingw-w64, which is likely a mirror repo on sf.net [1], (2) as of now, 7 forks of the above [2] (AndreRH's repo is one of these), (3) mingw-w64/mingw-w64 [3], where 1st "mingw-w64" stands for an organization account [4] (i.e. not a personal account). However there are no public members, i.e. only those within the organization can see user accounts which are members of the organization so I have no idea who is behind that. If it is no one from mingw-w64 of project's core developer, perhaps you could try to contact github's support to get some contact to them. [1] https://github.com/mirror/mingw-w64 [2] https://github.com/mirror/mingw-w64/network/members [3] https://github.com/mingw-w64/mingw-w64 [4] https://github.com/blog/674-introducing-organizations Regards, Martin Dne 11. 6. 2015 v 22:50 Vincent Torri napsal(a): > On Thu, Jun 11, 2015 at 9:54 PM, Adrien Nader wrote: >> >> On github there's already https://github.com/mingw-w64 but I have no >> idea who is behind that. > > https://github.com/AndreRH > > it seems that he's a Wine guy, according to his website > > Vincent > > -- > ___ > Mingw-w64-public mailing list > Mingw-w64-public@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] About the recent sourceforge events
On Thu, Jun 11, 2015 at 9:54 PM, Adrien Nader wrote: > > On github there's already https://github.com/mingw-w64 but I have no > idea who is behind that. https://github.com/AndreRH it seems that he's a Wine guy, according to his website Vincent -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] About the recent sourceforge events
On Thu, Jun 11, 2015, Ruben Van Boxem wrote: > 2015-06-10 23:24 GMT+02:00 Adrien Nader : > > > My initial notes for possible other service providers: > > > > http://librelist.com/ for mailing-lists > > - activity status unknown (not asked) > > - dispute resolution process unknown (not asked) > > - only mailing-lists > > > > http://www.tuxfamily.org/en/about for everything but bug tracker; but > > bug tracker software can be installed without trouble > > - not terribly active but definitely maintained > > - admins are known and are free software activists, makes it possible to > > take over in case some more admin is needed > > > > http://github.com for code hosting, web pages hosting (not binaries), > > light bug tracker, not mailing-lists nor forums > > - possible network effect (although I have some doubts considering the > > difficulty of most tasks) > > - hosting of large binaries is not guaranteed at all > > - hosting of binaries is couple to actual releases > > > > https://notabug.org/ only code hosting? > > - the gogs software is fairly new and doesn't have all features > > needed as far as I know > > > > http://codingteam.net everything but forum and mailing-lists > > - has a fairly nice look > > - the website warns that their current resources are not enough for > > livecd-style downloads and it's probably the same with large binaries > > that are currently in the file release system > > > > http://savannah.nongnu.org or http://gna.org everything but forums > > - mailing-lists! > > - well-known > > - need to check the current mingw-w64 usage of file downloads matches > > well > > - need to check how much graphical communication can be done on the > > project page (remember there is already a website to serve as > > frontend) > > > > Here's another two to add to the list: > http://www.codeplex.com/ (see http://www.codeplex.com/) > - mailing lists > - source code > - downloads > - issue tracker > - wiki > - continuous integration > bitbucket.org > - might be limited to 5 "users" collaborating on a project > - source code, > - downloads, > - issue tracker > - wiki > - no mailing lists > and of course the always available option: Thanks. For mailing-lists, POQDavid on IRC has reminded me of http://www.freelists.org/ . Again, only mailing-lists but that's the most annoying thing to handle across all the features provided by sourceforge. > Private server/hosting > - costs money Not the main issue. > - needs someone maintaining the guts Main issue, by far. Hosting is cheap enough and can be sponsored but admin time not so much. Plus it's a job that is high-risk and low reward and consideration. > - can do everything at once > - can it handle the load? Load shouldn't be an issue. 10k downloads per day of 100MB is 1TB, which is around 100Mbps. If we were to reach such a bandwidth in practice, we'd be sooner kicked off from the free hosting than from a dedicated server. > I think it is a good idea to at least have project names taken on the large > hosting sites (codeplex, github, savannah) so that the name is not taken by > anyone else. The project can then link to the main site and mirror the git > repository. On github there's already https://github.com/mingw-w64 but I have no idea who is behind that. I've registered projects on codeplex and bitbucket. I was feeling a bit lazy for savannah: worst case we get in touch with the admins there. Bitbucket apparently didn't want to keep hyphens so it's at https://bitbucket.org/mingww64/mingw-w64 . For codeplex, they require several more steps which I really don't feel like doing now (push code, add a description, chose a licence [ mingw-w64 doesn't fit in their license choices ] and another one which I've forgotten). The project will be deleted in 30 days if thie steps aren't done. We'll see by then. We couldn't keep the hyphen either. > If Sourceforge continues its actions like this, MinGW-w64 needs to keep its > options open. No action is required now, but at least opening some doors > never hurts, and reserving a project name with other hosting sites only > spreads MinGW-w64 availability and fame. That's really the spirit. Noone feels like doing the work currently but we should also make sure sourceforge cannot do bad stuff easily. I've been unable to track down how many people get on the sourceforge page directly rather than through what is now at http://mingw-w64.org and how they get there. It's quite opaque and sometimes dubious. Unfortunately that means that putting direct links to files and screenshots and anything else will not make most people safe in case something happens. Unfortunately^2 this also means we'll have to think about redistributions of binaries by sourceforge or another group in the future. Installers that come with adware is something that has been seen for VLC, Firefox and OpenOffice at least. They mostly solved that through trademarks as far as I know but that's probably a topic
Re: [Mingw-w64-public] About the recent sourceforge events
If you've not already investigated it for options for the binary downloads, this is worth considering and currently free for OSS https://bintray.com/ It could be compelling when combined with some of the other mentions. Jon On Thu, Jun 11, 2015 at 12:04 PM, Ivan Garramona wrote: > Hi Ruben, i think public repos doesn't have any user limits on bitbucket. > > -- > > ___ > Mingw-w64-public mailing list > Mingw-w64-public@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] About the recent sourceforge events
Hi Ruben, i think public repos doesn't have any user limits on bitbucket. -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] About the recent sourceforge events
2015-06-10 23:24 GMT+02:00 Adrien Nader : > My initial notes for possible other service providers: > > http://librelist.com/ for mailing-lists > - activity status unknown (not asked) > - dispute resolution process unknown (not asked) > - only mailing-lists > > http://www.tuxfamily.org/en/about for everything but bug tracker; but > bug tracker software can be installed without trouble > - not terribly active but definitely maintained > - admins are known and are free software activists, makes it possible to > take over in case some more admin is needed > > http://github.com for code hosting, web pages hosting (not binaries), > light bug tracker, not mailing-lists nor forums > - possible network effect (although I have some doubts considering the > difficulty of most tasks) > - hosting of large binaries is not guaranteed at all > - hosting of binaries is couple to actual releases > > https://notabug.org/ only code hosting? > - the gogs software is fairly new and doesn't have all features > needed as far as I know > > http://codingteam.net everything but forum and mailing-lists > - has a fairly nice look > - the website warns that their current resources are not enough for > livecd-style downloads and it's probably the same with large binaries > that are currently in the file release system > > http://savannah.nongnu.org or http://gna.org everything but forums > - mailing-lists! > - well-known > - need to check the current mingw-w64 usage of file downloads matches > well > - need to check how much graphical communication can be done on the > project page (remember there is already a website to serve as > frontend) > Here's another two to add to the list: http://www.codeplex.com/ (see http://www.codeplex.com/) - mailing lists - source code - downloads - issue tracker - wiki - continuous integration bitbucket.org - might be limited to 5 "users" collaborating on a project - source code, - downloads, - issue tracker - wiki - no mailing lists and of course the always available option: Private server/hosting - costs money - needs someone maintaining the guts - can do everything at once - can it handle the load? I think it is a good idea to at least have project names taken on the large hosting sites (codeplex, github, savannah) so that the name is not taken by anyone else. The project can then link to the main site and mirror the git repository. If Sourceforge continues its actions like this, MinGW-w64 needs to keep its options open. No action is required now, but at least opening some doors never hurts, and reserving a project name with other hosting sites only spreads MinGW-w64 availability and fame. Cheers, Ruben > -- > Adrien Nader > > > -- > ___ > Mingw-w64-public mailing list > Mingw-w64-public@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] About the recent sourceforge events
My initial notes for possible other service providers: http://librelist.com/ for mailing-lists - activity status unknown (not asked) - dispute resolution process unknown (not asked) - only mailing-lists http://www.tuxfamily.org/en/about for everything but bug tracker; but bug tracker software can be installed without trouble - not terribly active but definitely maintained - admins are known and are free software activists, makes it possible to take over in case some more admin is needed http://github.com for code hosting, web pages hosting (not binaries), light bug tracker, not mailing-lists nor forums - possible network effect (although I have some doubts considering the difficulty of most tasks) - hosting of large binaries is not guaranteed at all - hosting of binaries is couple to actual releases https://notabug.org/ only code hosting? - the gogs software is fairly new and doesn't have all features needed as far as I know http://codingteam.net everything but forum and mailing-lists - has a fairly nice look - the website warns that their current resources are not enough for livecd-style downloads and it's probably the same with large binaries that are currently in the file release system http://savannah.nongnu.org or http://gna.org everything but forums - mailing-lists! - well-known - need to check the current mingw-w64 usage of file downloads matches well - need to check how much graphical communication can be done on the project page (remember there is already a website to serve as frontend) -- Adrien Nader -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
[Mingw-w64-public] About the recent sourceforge events
Hi, You might have seen news about sourceforge.net hijacking projects or project names to distribute adware (or worse). Following this, several projects have started to move away from sourceforge. Since we use it, moving away from it is a question that we must bring up (this is not a vote thread). As of today, we are not moving away from sourceforge.net nor planning a move. We are merely assessing the current and possible future situations. We haven't have troubles ourselves so far. First, a recap of what has happened. For several years, sourceforge.net has proposed projects to wrap their installers in installers for adware. Revenue is shared between SF and the project. This has been accepted by Filezilla at least and the blame lies on both filezilla and sourceforge (one for thinking about it, the other for accepting it). Two weeks ago, the GIMP people found out that a Windows installer, that wasn't updated anymore but was still available for download, had been wrapped in the same kind of adware installer without any consent from them. [1] A number of projects have since then been complaining about similar things too. One notable is nmap. To the best of my knowledge, the issue is different and is actually about large "DOWNLOAD THIS"-style ads in the download page, i.e. much bigger than the actual button. Recap done. This isn't a very fun topic but as I said above, it must be brought up. Should the mingw-w64 project seek to move entirely or partially away from Sourceforge? If at least one service should be moved away from it, how can its features continue to be provided in the future? Currently the website is a dokuwiki, hosted elsewhere, with a domain name upon which we have full control. Since it is a wiki, we don't have a use for a separate service. The mailing-lists, file downloads, bug tracker, forums and git hosting are all services provided by sourceforge. Apart from the forums, all of these are heavily used (and even the forums have seen an increase in usage recently). It probably makes no sense to move anything if the file downloads don't move. Sourceforge is one of the few services providing all of these for free. Please answer with your thoughts on the matter (but again, no vote, no "+1" or similar) and how the services could be replaced. [1] https://mail.gnome.org/archives/gimp-developer-list/2015-May/msg00144.html -- Adrien Nader -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public