On Tue, Dec 4, 2012 at 4:31 PM, Ariel Constenla-Haile <arie...@apache.org> wrote: > On Tue, Dec 04, 2012 at 03:00:13PM -0500, Rob Weir wrote: >> >> If we want something to be downloaded and used by the public then we >> >> should release it, period. We should not be looking for clever ways >> >> to avoid the important release steps of verifying IP, producing a >> >> source package and voting on it. >> > >> > It seems you are mixing things, as I only proposed to build all language >> > packages, while following the same release criteria as before (release >> > only languages with 100% UI and a localization team backing it). Where >> > do you see a clever way to avoid official procedures in this? >> > >> >> When you suggested that we point users to these un-released binaries. > > Well, this meant only: If a user sends a mail telling that AOO does not > work on his RHEL 5 system, I find it good to point her/him to the > packages I've made, this will solve her/his problem. So if I read the > mail, I will point her/him to my packages. The same would apply in this > case with the language packs (which I already plan to do for the > linux-glib-2.5 build). > > I didn't mean to "officially" point the users (whatever that could > mean). >
I think your little project is less of a practical concern. It probably doesn't use much bandwidth. The much larger danger is that we mention a new translation on the public website, and that gets mentioned on a popular website, or social media, or a magazine and all of a sudden we get massive download requests going to people.apache.org. Do you really want to see Infra get upset? Remember, the ASF has limited bandwidth. We cannot control this or prevent it from happening. It is out of our control once we mention something on the pubic website. So we need to act responsibly. And that means (IMHO) that if we're producing a test build for QA and NL people to test with, that we publicize only as much as needed for them to know that it exists. That means the mailing lists. We need to be aware of how big the AOO project is, in comparison to the rest of the ASF, and take such precautions if we want to stay welcome here. >> > In the end, it's just the same as I've done with the linux glib-2.5 >> > build, which is advertised in the portings page, and stored at >> > people.apache.org... I haven't heard any complaints about this, so far >> > only some people thankful >> > https://issues.apache.org/ooo/show_bug.cgi?id=119385#c13 >> > >> >> Perhaps we should start looking at such pseudo releases more carefully? > > I don't see the point, these are not (pseudo) releases, they are simply > community contributed packages, that might be useful for some users. The > same aipplies to adfinis solaris builds, and any other "unofficially" > community contributed stuff. > But these are not on people.apache.org, are they? -Rob > > Regards > -- > Ariel Constenla-Haile > La Plata, Argentina
