[CWiki] Account Whitelisting

[Stephenie B]

Barrett, Stephenie Denver, ColoradoDocumentation, QA

Stephenie K Barrett
  

Re: AOO 4.1 Beta Survey Results

[Tal Daniel]

Just a small remark:

Jürgen Schmidt wrote:

> JSC: interesting is that only 10.7 and 10.9.2 systems were used. Ok ,
> 10.7 don't work anymore but I mean more the lack of 10.8, 10.9 10.9.1.
> Good to see that people upgrade fast
>

After installing 10.9.2, I can see why now: 10.9.2 upgrade is offered for
free(!) by Apple.
Maybe that helps to explain part of the mystery.

P.S. I'd recommend to mention the number of people, too; not just
percentages. E.g. Mac 10.7 - 11.11% (2)
In case number of people is small, 0% isn't that a rare incident.

Re: Update Available: Apache OpenOffice

[Roberto Galoppini]

2014-03-28 16:44 GMT+01:00 Roberto Galoppini :

>
>
> Il venerdì 28 marzo 2014, Oliver-Rainer Wittmann <
> orwittm...@googlemail.com> ha scritto:
>
> Hi,
>> On 27.03.2014 18:14, Rainer Bielefeld wrote:
>>
>>> Hi,
>>>
>>> few minutes ago I got following reminder 2 times. They are a little late
>>> for 4.0.1? Any Ideas?
>>>
>>
>> This is not from Apache OpenOffice. It is coming from SourceForge - our
>> friends hosting our installation packages for the download.
>>
>> We should ask Roberto about such postings.
>> It also contains wrong information:
>> AOO 4.0.1 had been released at 2013-10-01 - see
>> http://openoffice.apache.org/
>>
>>
>> The link 'DownloadLatest Version' works for me --> download of
>> corresponding AOO 4.0.1 for my system and language.
>>
>>
> Our support team fixed that yesterday, that's why works for you! ;-)
>
> I have been travelling all day and I didn't have a chance yet to close
> Rainer's ticket and add all instructions for managing that cpnfiguration.
> Will do once I will be back home.
>

Two clarifications:

1. Why you got an 'Update Available' email from SourceForge. The "keep me
updated" feature that allows anyone to subscribe to a service that notifies
end-users of the availability of new releases. No, why you got the message
now?


When AOO 4.0.1 was uploaded on SourceForge the 'default download' was not
updated accordingly. Couple of days ago when we have been notified about
this we updated the 'default download' info accordingly. Such update
triggered the email to users who subscribed the "keep me updated" service.
That's a feature, not a bug! :)

Hope this clarifies, sorry for the inconvenience it might have caused you.

2. What do for new releases. I have added a comment to Rainer's ticket
explaining how to update the 'default download' info here:
https://issues.apache.org/ooo/show_bug.cgi?id=124480

Roberto



>
> Roberto
>
>
>
>
>>
>> Best regards, Oliver.
>>
>>
>>>
>>> The Download Latest Version link leads to nirvana.
>>>
>>> CU
>>>
>>> Rainer
>>>
>>>
>>>
>>>  Original-Nachricht 
>>> Betreff: Update Available: Apache OpenOffice
>>> Datum: Thu, 27 Mar 2014 16:42:10 +
>>> Von: SourceForge.net 
>>> An: rainerbielefeld_ooo...@bielefeldundbuss.de
>>>
>>>
>>>
>>> Update Available: Apache OpenOffice
>>> SourceForge 
>>>
>>> *Find*, *Create*, & *Publish* Open Source Software for *free*.
>>>
>>>
>>>Hi! You have an update available.
>>>
>>> Apache OpenOffice >> >
>>>
>>>
>>>Apache OpenOffice
>>> 
>>>
>>> Apache OpenOffice, the Free and Open Source Productivity Suite
>>>
>>>
>>> Apache_OpenOffice_4.0.1_Win_x86_install_en-US.exe
>>> Released on 2013-09-25
>>>
>>> DownloadLatest Version
>>> >> files/latest/download?utm_campaign=updater&utm_medium=
>>> email&utm_source=subscribers>
>>>
>>>
>>>
>>>
>>> Unsubscribe
>>> >> rainerbielefeld_ooo...@bielefeldundbuss.de>
>>>
>>> me from receiving notifications for this project.
>>>
>>> This e-mail was intended for: rainerbielefeld_ooo...@bielefeldundbuss.de
>>> 
>>>
>>> Unsubscribe from project
>>> >> rainerbielefeld_ooo...@bielefeldundbuss.de>
>>>
>>> | Manage your subscriptions
>>> >> 7bdc50a5de9ab3c89321c555036db8c4>
>>>
>>> | Privacy policy 
>>>
>>>  SF 
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>
>>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>>

Re: Anything we can do about premature redistribution?

[Roberto Galoppini]

2014-03-28 21:24 GMT+01:00 Marcus (OOo) :

> Am 03/13/2014 10:01 PM, schrieb Marcus (OOo):
>
>> Am 03/09/2014 06:08 PM, schrieb Marcus (OOo):
>>
>>> Am 03/08/2014 12:09 AM, schrieb Andrea Pescetti:
>>>
 Rob Weir wrote:

> http://linux.softpedia.com/get/Office/Office-Suites/
 Apache-OpenOffice-253.shtml



  Or maybe a disclaimer in the voting thread email?
>

 Andrew's comments show clearly that these editors do not care to be
 careful or factual, or even read those disclaimers, unfortunately.

 We can be successful only if we manage to block their downloads. They
 link to our binaries hosted on SourceForge (which is fine). Just
 thinking loud, but if it was possible (on the Sourceforge side) to deny
 all download requests that do not come from the openoffice.org or the
 sourceforge.net domains, then the project would effectively be in
 control. The embargo could be lifted just after the release.

>>>
>>> For me this sounds like a great idea.
>>>
>>> Maybe we should start with denying all download requests that some from
>>> these bad websites.
>>>
>>> @Roberto:
>>> Can you tell us if this possible? If yes, is it much effort for you?
>>>
>>
>> Do you see a chance to get this implemented? I think it could help to
>> stop some bad websites to do bad things with our software.
>>
>
> @Roberto:
> Maybe you haven't seen this up to now.
>

Thanks for heads up Marcus, sorry for not having noticed this thread before.



>
> It would be great if you can tell us if it's possible to exclude some
> domains / IP addresses from downloading our software?
>

I need the domain list and I'll check out with our SiteOps if that's
doable. Feel free to send me a list with a direct message.

Roberto


>
> Then we can exclude requester that we don't want (e.g., malware
> "distributors").
>
> Also in time frames with Beta or RC releases it can help us to steer who
> is able and when it is possible to download OpenOffice like we want to see
> until the real release date is reached.


> Thanks
>
> Marcus
>
>
>
>  Sure, sites could still copy all binaries being voted upon and offer
 them locally, but this would require a more significant effort. on their
 side.

>>>
>>> And more HDD space and more own bandwith - which is also not what they
>>> want.
>>>
>>> Marcus
>>>
>>

[INFO] Bugzilla process

[Tal Daniel]

A small info request, and suggestion, regarding the bug tracking process:
The "How to file a good Issue [in Bugzilla] (
https://wiki.openoffice.org/wiki/QA/HowToFileIssue) end with this sentence:

> "[...], then press "Commit". Your bug report will now be in the Apache OOo
> Bugzilla database."


That's great, though...
(1) What happens NOW, after a bug is created? -- Does someone review it and
assign it, or should the reporter notify a mailing list, next to promote
it? Do BugZilla Admins review the bugs?
(2) What happens if the reporter feels no one read or did anything with his
bug report? (it happened to me a few times)

I'd recommend extend the above mentioned paragraph with this info, and
overview the process earlier within the Wiki page. I'll edit the wiki page,
according to info I'll receive.

Re: Better visibility for dev builds (Re: [RELEASE]: Beta downloads and feedback and a proposed way to the final)

[Tal Daniel]

Andrea Pescetti wrote:

> Tal Daniel wrote:
>
>> Excuse me for intervening the discussion, but I still don't get the
>> difference between these links:
>> [1] http://www.openoffice.org/download/all_beta.html
>> [2] http://www.openoffice.org/download/devbuilds.html
>> [3] https://cwiki.apache.org/confluence/display/OOOUSERS/
>> Development+Snapshot+Builds
>>
>> I'm lost, and others may feel the same.
>>
>
> ... Head to the download page http://www.openoffice.org/download/ (Right
> column, Additional Resources, Development builds) to get the builds between
> 4.1.0-beta and the coming 4.1.0 final. These are probably the ones you are
> interested in. Hebrew will be available after the next run (tomorrow). This
> corresponds to item #2 in your list above.
>
> Item #1 is the beta release, 4.1.0-beta. It is the one we want the general
> public to test. But volunteers who have already tested the beta and need to
> check specific bugs or features addressed after the beta will probably want
> to use #2.
>
> So we have: [Beta = #1] --> [Snapshots from AOO410 = download page or #2]
> --> 4.1.0
>
> Item #3 contains snapshots that are built from time to time. They can be
> built from the trunk or from a release branch (not every bugfix or feature
> we add now will go into 4.1.0: most of them will be used for the version
> after 4.1.0, so they go to "trunk" instead of going to the "AOO410
> branch"). They currently contain a snapshot that was taken for the Beta, so
> they are not useful at the moment. When we are not near a release, they are
> built from trunk and are a good way to test the latest changes.


*Thanks*, Andrea, for the explanation. It cleared things up.
I always feel so uncomfortable to mail the list with only a "thanks";
mailing lists should have a LIKE button too :)

Re: Pre-release IRC+video informal meeting?

[Dave Fisher]

Sent from my iPhone

> On Mar 29, 2014, at 6:44 AM, Rob Weir  wrote:
> 
>> On Sat, Mar 29, 2014 at 7:14 AM, Andrea Pescetti  wrote:
>>> On 27/03/2014 Jürgen Schmidt wrote:
>>> 
 On 3/27/14 1:59 AM, Andrea Pescetti wrote:
 
 Is there interest for a "live" (meaning: IRC + video, like Google
 Hangouts or similar) meeting to make sure that we (developers, QA,
 Localization, Documentation, website...) are all on the same page
 regarding the upcoming 4.1 release?
>>> 
>>> we can try such a meeting but I don't see the benefit compared to a
>>> clear communication on the mailing list (can be of course improved).
>> 
>> 
>> The benefit would be: make sure that active volunteers have a chance to be
>> heard and to influence the release. We are doing good now; still, we can do
>> better. See below for concrete examples.
>> 
>> 
>>> Either we do it in a more organized way and define exactly what we
>>> expect or I am not interested.
>> 
>> 
>> I am not interested in the other option. Well, maybe I misunderstood what
>> you mean by "organized", but for sure I would find it overkill that we have
>> to vote for someone to be in a call to represent a certain group (say, QA)
>> and vote on what the call topics should be. It's an informal meeting.
>> 
 It wouldn't be a meeting where things are decided (we have the lists for
 that!), but merely a meeting where people can inform each other to make
 sure that all priorities are being addressed ...
>>> 
>>> I am in favor of having such discussion mainly on the list to have it
>>> documented.
>> 
>> 
>> Note that it's more about being informed (about stuff that is already
>> somewhere on the lists), and discussion can follow on lists.
>> 
>> Maybe it helps if I make a concrete past example: the "Restore windows"
>> problem https://issues.apache.org/ooo/show_bug.cgi?id=119006 has been known
>> for two years. It only triggered on certain versions of Mac OS X and only
>> after a crash. Still it caused 500+ e-mails, and probably countless forum
>> posts and some enraged/lost users. In retrospect, we should have evaluated
>> it better.
>> 
>> How can we avoid the next "Restore windows", i.e., something that is known,
>> important to someone, already documented somewhere but that would deserve
>> better attention? It's important for OpenOffice as a project that active
>> volunteers feel that they can influence the release. And it is also very
>> good for OpenOffice as a product.
>> 
>> Now, the obvious answer is "Just place it in Bugzilla and nominate it as a
>> release blocker". This doesn't always work. For a release blocker, for
>> example, you would require in most cases that a patch is available, and a
>> description that is purely technical can miss to state why it is important
>> to get it fixed before release. And if you look at who is nominating
>> blockers, you'll see that only a few people do that.
>> 
>> The IRC+video meeting is the best solution I can find, but anything else
>> that guarantees proper escalation would work for me. Just, asking people to
>> simply follow the process is too demanding on volunteers and we need to
>> streamline it (another concrete example? we don't have 4.0 in Danish mainly
>> due to bad communication, since translation was completed before the 4.0
>> release but after the deadlines).
>> 
>> If you want yet another example... we already know that OpenOffice 4.1 is
>> going to have display problems for Gnome 3 users on Linux. Two bugs have
>> clearly been identified: no refresh on fields
>> https://issues.apache.org/ooo/show_bug.cgi?id=124482 and no scrollbars
>> https://issues.apache.org/ooo/show_bug.cgi?id=121627 ; the former has a
>> working patch by Andre and I'll nominate it as a blocker, but what about the
>> latter? Does it make sense to nominate it even if we don't have a fix
>> available? Will a meeting where active people can report on what they see on
>> the forums, lists etc help in making the assessment?
> 
> We can always have a Hangout on our Google+ page.  But I think that is
> limited to 10 people and ties us to a specific time, making it more or
> less convenient to people depending on their timezone.  So I'm not
> sure it is much more inclusive.
> 
> But you could make the argument that it is a best practice with Agile
> methodology for us to have "daily scrum" meeting to check in and
> review blockers.  But that could also be done via the mailing list,
> with a new thread each day, e.g., "2014-03-29 Daily Scrum".

As I read the other emails I was thinking that a bug scrub would be good. This 
would allow a group to discuss bugs and issues. The goal would be a priority 
list which could then be shared on list, debated. We can then commit ( agile 
term). Daily scrum then tracks the progress towards the goal. The scrum master 
records the info. Scrum master can change from day to day. It is clerical.

Regards,
Dave

> 
> In any case, if a PMC member wants to take the lead on a hangout, and

Re: Version for i-pad?

[Louis Suárez-Potts]

On 2014-03-29, at 08:58, Guy Waterval  wrote:

> Hi Louis,
> 
> Kickstarter ?
> Could you develop a little more ?
> I don't understand very well.
> Many thanks.
> 
> A+
> -- 
> gw

The issue is that to develop a working ODF editor (and call it what you want) 
that has close enough resemblance to the UI for AOO to be acceptable to the AOO 
(and even LO) user base is not by any means impossible but does require a 
significant investment of developer time and energy—and then a continuing 
commitment to keeping it up-to-date and bug free.

That the code should be open source would be nice.

Work along the lines of porting AOO to Android has been done; a port exists. 
But as the dev. has explained to me, it's more a proof of concept, though a 
working one, than a useful app. Part of the problem, as I see it, is that the 
UI and UX of any tablet differs rather a lot from the desktop's. For starters, 
there is less space; then there is no keyboard, though that can be added to a 
tablet, easily enough, via Bluetooth. But there are other issues, and they are 
not insignificant. 

I have not checked MS's iPad offering, as to actually use the apps for more 
than viewing (sigh), one has to pay 100US/annum. That's a lot, and why? If I 
want a proprietary tool that actually already reads and edits MSFT files, I can 
use Apple's free productivity apps. They're actually pretty good. But they do 
not support ODF. (I don't think, but have not checked, MSFT on the iPad 
supports ODF, either.)

UX Write also supports .docx on the iPad (and all iOS7 devices) but a) it 
doesn't have change tracking, b) doesn't yet support ODT, c) is so far 
proprietary; and d), is only on Apple's iOS. The developers would certainly 
include more things and conceivably alter licensing regime but….

Resources.

Resources can be simply the money to pay for developers. The inducement of 
building an app that would be used in this setting and that would also be, 
ideally, open source, is probably today a lot clearer than it was last week, 
prior to the advent of Office for iPad. The totally unsurprising popularity of 
Office/iPad will perhaps make it a lot easier to engage developers in building 
something equivalent for AOO—or, as I would prefer, in a way, a good-enough 
solution. (Good enough is another way of being realistic: I don't imagine that 
many spreadsheet mavens will want to do their thing on a tablet, even with a 
spare keyboard and the same could be said of some complex presentation work. 
But I can see people using the Draw component, and I do see many using and 
wanting to use even more the text components. So one builds for logical use. 
Second. I don't see the point of preserving the architecture of AOO, though 
that is what was done with the port to Android—and I see that as a mistake. Why 
bother with it? Peter Kelly of UX Write has built a brilliant text editor for 
iOS without it, using HMTL… and is working on ODT support.)

I further think that now is a rather good time to put out a call for table 
development. Again: Microsoft's belated splash into the pool. As always, the 
entry of Microsoft into a market that shadows its primary (tablet::desktop) 
profoundly alters that market's dynamics. 

Let's take advantage of that :-)

Hence, somewhat—but not entirely—facetious notion of a Kickstarter-like 
campaign to garner funds from the people. I would prefer to have any kind of 
funded engagement be within Apache's universe, but it need not be. 

-louis
> 
> 
> 2014-03-28 22:41 GMT+01:00 Louis Suárez-Potts :
> 
>> 
>> On 2014-03-28, at 17:24, FR web forum  wrote:
>> 
>>> Question asked many times
>>> See: https://forum.openoffice.org/en/forum/viewtopic.php?f=49&t=61238
>> 
>> Thanks. I'd guess we've already added this q. and its a. to the FAQ?
>> 
>> And, just for fun. Say I start a Kickstarter (or equivalent for open
>> source efforts) project. Idea to build an good enough ODF editor for iOS
>> and Android for, initially, text, then later presentation / calc
>> 
>> louis
>> 
>>> 
>>> - Mail original -
>>> De: "Ilona Gersh" 
>>> À: dev@openoffice.apache.org
>>> Envoyé: Vendredi 28 Mars 2014 17:11:22
>>> Objet: Version for i-pad?
>>> 
>>> Hi, Is there a version of Open Office for I-pads? If not, is one being
>> developed? If not, what do you suggest I use? Ilona
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>> 
>> 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Pre-release IRC+video informal meeting?

[Rob Weir]

On Sat, Mar 29, 2014 at 7:14 AM, Andrea Pescetti  wrote:
> On 27/03/2014 Jürgen Schmidt wrote:
>>
>> On 3/27/14 1:59 AM, Andrea Pescetti wrote:
>>>
>>> Is there interest for a "live" (meaning: IRC + video, like Google
>>> Hangouts or similar) meeting to make sure that we (developers, QA,
>>> Localization, Documentation, website...) are all on the same page
>>> regarding the upcoming 4.1 release?
>>
>> we can try such a meeting but I don't see the benefit compared to a
>> clear communication on the mailing list (can be of course improved).
>
>
> The benefit would be: make sure that active volunteers have a chance to be
> heard and to influence the release. We are doing good now; still, we can do
> better. See below for concrete examples.
>
>
>> Either we do it in a more organized way and define exactly what we
>> expect or I am not interested.
>
>
> I am not interested in the other option. Well, maybe I misunderstood what
> you mean by "organized", but for sure I would find it overkill that we have
> to vote for someone to be in a call to represent a certain group (say, QA)
> and vote on what the call topics should be. It's an informal meeting.
>
>>> It wouldn't be a meeting where things are decided (we have the lists for
>>> that!), but merely a meeting where people can inform each other to make
>>> sure that all priorities are being addressed ...
>>
>> I am in favor of having such discussion mainly on the list to have it
>> documented.
>
>
> Note that it's more about being informed (about stuff that is already
> somewhere on the lists), and discussion can follow on lists.
>
> Maybe it helps if I make a concrete past example: the "Restore windows"
> problem https://issues.apache.org/ooo/show_bug.cgi?id=119006 has been known
> for two years. It only triggered on certain versions of Mac OS X and only
> after a crash. Still it caused 500+ e-mails, and probably countless forum
> posts and some enraged/lost users. In retrospect, we should have evaluated
> it better.
>
> How can we avoid the next "Restore windows", i.e., something that is known,
> important to someone, already documented somewhere but that would deserve
> better attention? It's important for OpenOffice as a project that active
> volunteers feel that they can influence the release. And it is also very
> good for OpenOffice as a product.
>
> Now, the obvious answer is "Just place it in Bugzilla and nominate it as a
> release blocker". This doesn't always work. For a release blocker, for
> example, you would require in most cases that a patch is available, and a
> description that is purely technical can miss to state why it is important
> to get it fixed before release. And if you look at who is nominating
> blockers, you'll see that only a few people do that.
>
> The IRC+video meeting is the best solution I can find, but anything else
> that guarantees proper escalation would work for me. Just, asking people to
> simply follow the process is too demanding on volunteers and we need to
> streamline it (another concrete example? we don't have 4.0 in Danish mainly
> due to bad communication, since translation was completed before the 4.0
> release but after the deadlines).
>
> If you want yet another example... we already know that OpenOffice 4.1 is
> going to have display problems for Gnome 3 users on Linux. Two bugs have
> clearly been identified: no refresh on fields
> https://issues.apache.org/ooo/show_bug.cgi?id=124482 and no scrollbars
> https://issues.apache.org/ooo/show_bug.cgi?id=121627 ; the former has a
> working patch by Andre and I'll nominate it as a blocker, but what about the
> latter? Does it make sense to nominate it even if we don't have a fix
> available? Will a meeting where active people can report on what they see on
> the forums, lists etc help in making the assessment?
>

We can always have a Hangout on our Google+ page.  But I think that is
limited to 10 people and ties us to a specific time, making it more or
less convenient to people depending on their timezone.  So I'm not
sure it is much more inclusive.

But you could make the argument that it is a best practice with Agile
methodology for us to have "daily scrum" meeting to check in and
review blockers.  But that could also be done via the mailing list,
with a new thread each day, e.g., "2014-03-29 Daily Scrum".

In any case, if a PMC member wants to take the lead on a hangout, and
does not already have access to our Google+ page, let me know and I
can give you manager access.

-Rob


> Regards,
>   Andrea.
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Cost savings by using a thinner typeface

[Fernando Cassia]

On Fri, Mar 28, 2014 at 11:38 AM, Rob Weir  wrote:

> Interesting story:
>
>
> http://www.cnn.com/2014/03/27/living/student-money-saving-typeface-garamond-schools/index.html?c=us&page=0
>


http://fcw.com/articles/1998/09/27/dod-agency-sheds-the-paper-trail.aspx

"DOD's paperless contracting goals are part of DOD's overall Defense Reform
Initiative unveiled last year by Vice President Al Gore and Secretary of
Defense William Cohen. The department's re-engineering goals include the
creation of a "paperless society by the year 2001," Cohen said, and the
movement of all paper-based documentation and transactions to electronic
media."

I guess a paperless society will take some more time... ;)

FC
PS: I noticed Samsung has started offering its own toner-saving software
(aka Print optimization) in their web site for its laser printer. It
reduces ink usage by offering a preview of the printout (before it's sent
to the windows print spooler) and then lets you adjust grayscales and
basically sets "brightness" higher (blacks become grays, grays become
lighter grays, etc) saving a lot of toner in the process. Perhaps this
could be integrated as a "toner saver" feature in the print preview dialog,
so it benefits everyone not only those with Samsung printers or those who
have installed third party ink saving software?
-- 
During times of Universal Deceit, telling the truth becomes a revolutionary
act
Durante épocas de Engaño Universal, decir la verdad se convierte en un Acto
Revolucionario
- George Orwell

Re: Better visibility for dev builds (Re: [RELEASE]: Beta downloads and feedback and a proposed way to the final)

[Andrea Pescetti]

Tal Daniel wrote:

Excuse me for intervening the discussion, but I still don't get the
difference between these links:
[1] http://www.openoffice.org/download/all_beta.html
[2] http://www.openoffice.org/download/devbuilds.html
[3] 
https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds
I'm lost, and others may feel the same.


Making your life simpler is what this discussion is meant to do... so no 
problem!


Head to the download page http://www.openoffice.org/download/ (Right 
column, Additional Resources, Development builds) to get the builds 
between 4.1.0-beta and the coming 4.1.0 final. These are probably the 
ones you are interested in. Hebrew will be available after the next run 
(tomorrow). This corresponds to item #2 in your list above.


Item #1 is the beta release, 4.1.0-beta. It is the one we want the 
general public to test. But volunteers who have already tested the beta 
and need to check specific bugs or features addressed after the beta 
will probably want to use #2.


So we have:
[Beta = #1] --> [Snapshots from AOO410 = download page or #2] --> 4.1.0

Item #3 contains snapshots that are built from time to time. They can be 
built from the trunk or from a release branch (not every bugfix or 
feature we add now will go into 4.1.0: most of them will be used for the 
version after 4.1.0, so they go to "trunk" instead of going to the 
"AOO410 branch"). They currently contain a snapshot that was taken for 
the Beta, so they are not useful at the moment. When we are not near a 
release, they are built from trunk and are a good way to test the latest 
changes.


Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Version for i-pad?

[Guy Waterval]

Hi Louis,

Kickstarter ?
Could you develop a little more ?
I don't understand very well.
Many thanks.

A+
-- 
gw


2014-03-28 22:41 GMT+01:00 Louis Suárez-Potts :

>
> On 2014-03-28, at 17:24, FR web forum  wrote:
>
> > Question asked many times
> > See: https://forum.openoffice.org/en/forum/viewtopic.php?f=49&t=61238
>
> Thanks. I'd guess we've already added this q. and its a. to the FAQ?
>
> And, just for fun. Say I start a Kickstarter (or equivalent for open
> source efforts) project. Idea to build an good enough ODF editor for iOS
> and Android for, initially, text, then later presentation / calc
>
> louis
>
> >
> > - Mail original -
> > De: "Ilona Gersh" 
> > À: dev@openoffice.apache.org
> > Envoyé: Vendredi 28 Mars 2014 17:11:22
> > Objet: Version for i-pad?
> >
> > Hi, Is there a version of Open Office for I-pads? If not, is one being
> developed? If not, what do you suggest I use? Ilona
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Re: Better visibility for dev builds (Re: [RELEASE]: Beta downloads and feedback and a proposed way to the final)

[Tal Daniel]

Excuse me for intervening the discussion, but I still don't get the
difference between these links:
http://www.openoffice.org/download/all_beta.html
http://www.openoffice.org/download/devbuilds.html
https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds

I'm lost, and others may feel the same.

4.1.0_release_blocker requested: [Issue 124482] InputBox-es don't refresh itself in gnome shell/Adwaita theme

[bugzilla]

Andrea Pescetti  has asked  for 4.1.0_release_blocker:
Issue 124482: InputBox-es don't refresh itself in gnome shell/Adwaita theme
https://issues.apache.org/ooo/show_bug.cgi?id=124482


--- Additional Comments from Andrea Pescetti 
Suggesting as release blocker to improve the user experience of Gnome 3 users,
even though this is not the only bug related to Gnome 3.

A patch by Andre is available (as he writes, this is not the best since it
relies on hardcoded theme names; but it is very simple and it works).

Without the patch, if you go to the sidebar and click to increase the "Above
Paragraph Spacing" all numbers will overlap and become unreadable. The same
holds for the other dialogs (File - Save, font selection...). With the patch,
the problem is solved.

Screenshot: https://issues.apache.org/ooo/attachment.cgi?id=83027

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [CWiki] Account Whitelisting

[Andrea Pescetti]

Dave wrote:

Username: davepolit
Real name: David Paenson


Done, whitelisted.
Andrea

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

[CWiki] Account Whitelisting

[Dave]

Username: davepolit

Real name: David Paenson

Re: Pre-release IRC+video informal meeting?

[Andrea Pescetti]

On 27/03/2014 Jürgen Schmidt wrote:

On 3/27/14 1:59 AM, Andrea Pescetti wrote:

Is there interest for a "live" (meaning: IRC + video, like Google
Hangouts or similar) meeting to make sure that we (developers, QA,
Localization, Documentation, website...) are all on the same page
regarding the upcoming 4.1 release?

we can try such a meeting but I don't see the benefit compared to a
clear communication on the mailing list (can be of course improved).


The benefit would be: make sure that active volunteers have a chance to 
be heard and to influence the release. We are doing good now; still, we 
can do better. See below for concrete examples.



Either we do it in a more organized way and define exactly what we
expect or I am not interested.


I am not interested in the other option. Well, maybe I misunderstood 
what you mean by "organized", but for sure I would find it overkill that 
we have to vote for someone to be in a call to represent a certain group 
(say, QA) and vote on what the call topics should be. It's an informal 
meeting.



It wouldn't be a meeting where things are decided (we have the lists for
that!), but merely a meeting where people can inform each other to make
sure that all priorities are being addressed ...

I am in favor of having such discussion mainly on the list to have it
documented.


Note that it's more about being informed (about stuff that is already 
somewhere on the lists), and discussion can follow on lists.


Maybe it helps if I make a concrete past example: the "Restore windows" 
problem https://issues.apache.org/ooo/show_bug.cgi?id=119006 has been 
known for two years. It only triggered on certain versions of Mac OS X 
and only after a crash. Still it caused 500+ e-mails, and probably 
countless forum posts and some enraged/lost users. In retrospect, we 
should have evaluated it better.


How can we avoid the next "Restore windows", i.e., something that is 
known, important to someone, already documented somewhere but that would 
deserve better attention? It's important for OpenOffice as a project 
that active volunteers feel that they can influence the release. And it 
is also very good for OpenOffice as a product.


Now, the obvious answer is "Just place it in Bugzilla and nominate it as 
a release blocker". This doesn't always work. For a release blocker, for 
example, you would require in most cases that a patch is available, and 
a description that is purely technical can miss to state why it is 
important to get it fixed before release. And if you look at who is 
nominating blockers, you'll see that only a few people do that.


The IRC+video meeting is the best solution I can find, but anything else 
that guarantees proper escalation would work for me. Just, asking people 
to simply follow the process is too demanding on volunteers and we need 
to streamline it (another concrete example? we don't have 4.0 in Danish 
mainly due to bad communication, since translation was completed before 
the 4.0 release but after the deadlines).


If you want yet another example... we already know that OpenOffice 4.1 
is going to have display problems for Gnome 3 users on Linux. Two bugs 
have clearly been identified: no refresh on fields 
https://issues.apache.org/ooo/show_bug.cgi?id=124482 and no scrollbars 
https://issues.apache.org/ooo/show_bug.cgi?id=121627 ; the former has a 
working patch by Andre and I'll nominate it as a blocker, but what about 
the latter? Does it make sense to nominate it even if we don't have a 
fix available? Will a meeting where active people can report on what 
they see on the forums, lists etc help in making the assessment?


Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Cost savings by using a thinner typeface

[Arthur Buijs]

Rob Weir schreef op 28-3-2014 15:38:

Interesting story:

http://www.cnn.com/2014/03/27/living/student-money-saving-typeface-garamond-schools/index.html?c=us&page=0

I wonder what the impact would be if we encouraged our user base to do
something similar.  What would the cost savings be?


http://en.wikipedia.org/wiki/Ecofont

--
Regards,
Arthur



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org