On Tue, Oct 11, 2011 at 07:39, Ivan Zhakov <i...@apache.org> wrote: >... > I have reverted this change because I don't understand the goals. What > you are trying to achieve?
What we discussed back in July, regarding clarity of what that page links to. Some of the pages did not provide Apache Subversion binaries for the server component, so I marked them "client only". Some of the landing pages had no indication of how to get an Apache Subversion binary (like the VisualSVN, Apple, and Sunfreeware pages), so I removed those. People use packages.html to find binary packages of Apache Subversion. They scan the page, and find a link that should work for them (given the annotations we make for that link) and then they click it. The target page should have Apache Subversion on it. If it does not... then why should it be listed on the page for people *looking* for those binaries? > I have reverted without discussion because this change was immediately > propagated to the web-side. On the other hand, you haven't discussed > this change before the commit! We discussed this at the end of July. Further, the bulk of the changes were annotations to clarify what the person would find *before* they clicked on the link (only to be disappointed when they did NOT find an Apache Subversion binary). I removed links that did not provide binaries for *our* project. Yes, WANdisco and CollabNet also provide other offerings on their pages, but they *do* provide installs for Apache Subversion. Some of those installs were client-only, so I annotated that. > More particularly, you have removed the link to VisualSVN Server > saying it's not a Subversion binaries. Yup. As a user on visiting packages.html, looking for a binary... when I click that link, I do *not* find Apache Subversion binaries. I find VisualSVN. That doesn't help me. It wastes my time. I have to hit "back" and try another link to find the binaries that I'm seeking. I keeping saying "Apache Subversion" because that is what packages.html is all about. It is *not* about Jane's or Jack's variant of Subversion. It is about people wanting binaries for *our* project. OUR project. If the landing page does not provide that, then the link to that page has no purpose being listed on our site. That was the outcome of our discussion back in July. [ for readers on the dev@ list that are wondering wtf I'm talking about... this discussion was on our project's private list ] > VisualSVN Server is used by several hundreds of thousands of users. So fucking what? That does it give it any "Right" to be listed. If you want to start measuring dick sizes, I bet the WANdisco and CollabNet people would be happy to bring out statistics, and say they also serve hundreds of thousands of users. We still don't care. packages.html is for people looking for binaries. Totally independent of whether those binaries are popular. >... > So, what is the objective to remove the link to VisualSVN Server? Because that landing page is not providing Apache Subversion binaries. > The other side is that you have actually left links to CollabNET > Subversion Edge and Wandisco UberSVN (see details below). It > interesting that both are the direct competitors of VisualSVN Server. > Seems to be a biased change, isn't it? Not at all. I'm not biased. Fuck those guys, for all I care. Those landing pages provided binaries. Some were *only* client binaries, so I annotated the links to say as much. Did those pages also provide other software? Yup. But that doesn't matter. The pages *do* provide links for Apache binaries. That is all that matters to people on packages.html looking for software. > There is a simple way: let's totally remove the "Binary Packages" page Don't be stupid. The page is useful. >... > Have you even followed the links that are marked as "client only" by you? Absolutely. In fact, I even had to sign up with WANdisco to get links to the CentOS binaries. I wanted to see if the resulting links gave me client-only or both clients and servers. It provided both, so I did not have to annotate that link. I didn't have to register with CollabNet because it was already obvious (from their landing page) what the installation links provided. > > The http://www.collab.net/downloads/subversion/ leads to the page with > the following downloads: > * CollabNet Subversion Command-Line Client v1.6.17 (for Windows) > * CollabNet Subversion Edge 2.0.1 (for Windows 32 bit) > * CollabNet Subversion Edge 2.0.1 (for Windows 64 bit) > > Not a "client only". When talking about Apache Subversion... yes, client-only. And CollabNet is offering some other gunk on that page. Who cares. As long as I'm on packages.html, see a link that says I can get Windows binaries, and when I click... that I can get them. > The http://www.wandisco.com/subversion/download#windows leads to the > page dedicated to uberSVN. >... > Yes, there is a link to command line client in the bottom of the page. > But not a "client only" page, for sure. Same deal as CollabNet. If I can get what I'm looking for, then it is fine. You put VisualSVN back, but it should not be there unless/until that page tells me that I can get plain Apache Subversion binaries. If the page *only* offers me somebody other than Apache, then it has no reason to be listed on OUR project page. Cheers, -g
