Hi all,
I just created defect query for all defects reported after AOO 3.4
published in BugZilla, please take a view.
https://issues.apache.org/ooo/buglist.cgi?cmdtype=runnamednamedcmd=AOO34DefectsAfterMaylist_id=11524
You can go to Preference on your BugZilla home page and navigate to
Saved
Hi,
I propose that the correction of the Bug 119189
https://issues.apache.org/ooo/show_bug.cgi?id=119189 - Print Selection crash
in Writer (P3 Critical) may be added to the todo list for AOO3.4.1.
I do not know how to do that but if somebody find this is relevant, can you do
it for me ? (or,
Hi
Am 12.05.12 08:58, schrieb Guillaume:
Hi,
I propose that the correction of the Bug 119189
https://issues.apache.org/ooo/show_bug.cgi?id=119189 - Print Selection
crash
in Writer (P3 Critical) may be added to the todo list for AOO3.4.1.
I do not know how to do that but if somebody
2012/5/9 Kevin Grignon kevingrignon...@gmail.com:
Paulo,
I have already made a proposal to refresh the UX wiki and could use your help.
Let's quickly inventory the pages, note the last update date, and categorize
the content.
I suspect we will want to harvest relevant content, archive
2012/5/9 RGB ES rgb.m...@gmail.com
2012/5/9 Kevin Grignon kevingrignon...@gmail.com:
I was thinking on a central wiki page were our ideal users are
defined by tasks more than by apps
- Technical writers (scholars, scientific researchers, journalists,
free lance writers...)
- Non technical
On Mon, May 7, 2012 at 9:40 PM, Kevin Grignon kevingrignon...@gmail.comwrote:
Understanding who does what with our product is very important to defining
a product direction that resonates with our users.
The user experience team is about to refresh the UX work products on the
wiki. An
Hi.
I would like to help on this task also.
In fact, I've been fooling around the wiki and there are a bunch of
outdated information and some of them could be recycled, others simply
deleted, some of them could be updated. I was wondering if there is someone
taking care of this issue. Case not,
Don,
Exactly what we need - who doing what.
At this point there are no wrong answers and a broad inventory of users types
and goals is how we begin.
UX is working to clean up the wiki and we create a location to consolidate our
user roles and libraries in the upcoming days.
In the
Paulo,
I have already made a proposal to refresh the UX wiki and could use your help.
Let's quickly inventory the pages, note the last update date, and categorize
the content.
I suspect we will want to harvest relevant content, archive outdated reference
mayerial and remove irrelevant.
Hi,
RGB ES wrote:
2012/5/5 Albino Biasutti Neto biasut...@gmail.com:
Hi.
We have to focus on end users, and seek feedback to research, created
polls, and others.
We need to get statistics AOO.
Best,
Albino
Before that, we need to define who our end users are. We need a set of
ideal
2012/5/8 Louis Suárez-Potts lui...@gmail.com:
Hi,
RGB ES wrote:
2012/5/5 Albino Biasutti Neto biasut...@gmail.com:
Hi.
We have to focus on end users, and seek feedback to research, created
polls, and others.
We need to get statistics AOO.
Best,
Albino
Before that, we need to define
Am 05/01/2012 09:28 PM, schrieb Marcus (OOo):
Am 05/01/2012 06:24 PM, schrieb Juergen Schmidt:
On Tuesday, 1. May 2012 at 16:41, Rob Weir wrote:
Today, among the 100 version strings the users need to scroll through
in BZ, we have AOO340-dev.
What do we want after we release AOO 3.4?
Add
On Mon, May 7, 2012 at 6:28 PM, Marcus (OOo) marcus.m...@wtnet.de wrote:
Am 05/01/2012 09:28 PM, schrieb Marcus (OOo):
Am 05/01/2012 06:24 PM, schrieb Juergen Schmidt:
On Tuesday, 1. May 2012 at 16:41, Rob Weir wrote:
Today, among the 100 version strings the users need to scroll through
in
Am 05/08/2012 12:42 AM, schrieb Rob Weir:
On Mon, May 7, 2012 at 6:28 PM, Marcus (OOo)marcus.m...@wtnet.de wrote:
Am 05/01/2012 09:28 PM, schrieb Marcus (OOo):
Am 05/01/2012 06:24 PM, schrieb Juergen Schmidt:
On Tuesday, 1. May 2012 at 16:41, Rob Weir wrote:
Today, among the 100 version
On Mon, May 7, 2012 at 6:58 PM, Marcus (OOo) marcus.m...@wtnet.de wrote:
Am 05/08/2012 12:42 AM, schrieb Rob Weir:
On Mon, May 7, 2012 at 6:28 PM, Marcus (OOo)marcus.m...@wtnet.de wrote:
Am 05/01/2012 09:28 PM, schrieb Marcus (OOo):
Am 05/01/2012 06:24 PM, schrieb Juergen Schmidt:
On
Understanding who does what with our product is very important to defining a
product direction that resonates with our users.
The user experience team is about to refresh the UX work products on the wiki.
An updated set of user roles/personas is our first step. Existing data can get
us
On Sat, May 5, 2012 at 5:02 PM, RGB ES rgb.m...@gmail.com wrote:
ideal users with clear needs: students who do their homework,
independent writers that use on-line publishing systems
If, going forward, AOO team could design an extensible system to interface
AOO writer with different CMS
2012/5/5 Albino Biasutti Neto biasut...@gmail.com:
Hi.
We have to focus on end users, and seek feedback to research, created
polls, and others.
We need to get statistics AOO.
Best,
Albino
Before that, we need to define who our end users are. We need a set of
ideal users with clear needs:
Hi.
2012/5/5 RGB ES rgb.m...@gmail.com
2012/5/5 Albino Biasutti Neto biasut...@gmail.com:
Hi.
We have to focus on end users, and seek feedback to research, created
polls, and others.
We need to get statistics AOO.
Best,
Albino
Before that, we need to define who our end users
Hi.
We have to focus on end users, and seek feedback to research, created
polls, and others.
We need to get statistics AOO.
Best,
Albino
+1
On Fri, May 4, 2012 at 9:44 PM, Albino Biasutti Neto biasut...@gmail.comwrote:
Hi.
We have to focus on end users, and seek feedback to research, created
polls, and others.
We need to get statistics AOO.
Best,
Albino
--
Clóvis Tristão
Net Admin
Home Phone: 55 (19) 3296-4057 /
Suggest we add AOO 340 version as official release. And for those existing
opening defects, basically they should be moved to this version as well.
But considering we are not sure if many old defects still valid for AOO
3.4, it's better add one version as OOO and change all the defects before
AOO
Regards, Yan Ji
On Apr 29, 2012, at 12:32 AM, Rob Weir wrote:
I'm already starting to get questions on what we'll be doing after AOO
3.4 is released. Based on previous conversations on this list, I'm
able to speak confidently about a few things:
1) We'll probably graduate to a Top
Today, among the 100 version strings the users need to scroll through
in BZ, we have AOO340-dev.
What do we want after we release AOO 3.4?
Add AOO340? (Or just rename AOO340-dev to AOO340?)
Add AOO341-dev?
Add AOO450-dev?
The versions are for reporting issues against, so bugs reported from
On Sat, Apr 28, 2012 at 12:32 PM, Rob Weir robw...@apache.org wrote:
I'm already starting to get questions on what we'll be doing after AOO
3.4 is released. Based on previous conversations on this list, I'm
able to speak confidently about a few things:
1) We'll probably graduate to a Top
Today, among the 100 version strings the users need to scroll through
in BZ, we have AOO340-dev.
What do we want after we release AOO 3.4?
Add AOO340? (Or just rename AOO340-dev to AOO340?)
Add AOO341-dev?
Add AOO450-dev?
Also, are there any products that can be removed or demoted to
On Tuesday, 1. May 2012 at 16:41, Rob Weir wrote:
Today, among the 100 version strings the users need to scroll through
in BZ, we have AOO340-dev.
What do we want after we release AOO 3.4?
Add AOO340? (Or just rename AOO340-dev to AOO340?)
Renaming sounds good to me and all issues with
Am 05/01/2012 06:24 PM, schrieb Juergen Schmidt:
On Tuesday, 1. May 2012 at 16:41, Rob Weir wrote:
Today, among the 100 version strings the users need to scroll through
in BZ, we have AOO340-dev.
What do we want after we release AOO 3.4?
Add AOO340? (Or just rename AOO340-dev to AOO340?)
Hi Rob,
Rob Weir schrieb:
[..]
Also, are there any products that can be removed or demoted to
components under another product? What we have now is simpler than
what we had with OOo, but it is still very complicated with a lot of
dead wood at the top level.
Yes, the list is far too large.
on what we'll be doing after AOO
3.4 is released. Based on previous conversations on this list, I'm
able to speak confidently about a few things:
1) We'll probably graduate to a Top Level Project
2) IBM says they will contribute Symphony source code after 3.4 is released
3) We have some
On Apr 29, 2012, at 12:32 AM, Rob Weir wrote:
I'm already starting to get questions on what we'll be doing after AOO
3.4 is released. Based on previous conversations on this list, I'm
able to speak confidently about a few things:
1) We'll probably graduate to a Top Level Project
2) IBM
and
process asap. Automation framework and test tool should be available soon
for all tester in this project.
Thanks Best Regards, Yan Ji
On Apr 29, 2012, at 12:32 AM, Rob Weir wrote:
I'm already starting to get questions on what we'll be doing after AOO
3.4 is released. Based on previous
Agree with having a maintenance branch for traslation and critical bug fix.
It is time to unlock the code base to allow contributors to submit
improvments for later release.
On Sun, Apr 29, 2012 at 11:46 PM, Andrea Pescetti pesce...@apache.org wrote:
Rob Weir wrote:
1) We want to have a
On Tue, May 1, 2012 at 2:28 AM, Pedro Giffuni p...@apache.org wrote:
On 04/29/12 23:55, Juergen Schmidt wrote:
...
I think it all depends on how fast we plan to release 4.0.
It looks likely that merging Symophony may be easy for the
IBM guys, since symphony already updated theit base OOo,
On Mon, Apr 30, 2012 at 12:55 AM, Juergen Schmidt
jogischm...@googlemail.com wrote:
On Sunday, 29. April 2012 at 21:10, Pedro Giffuni wrote:
--- Sab 28/4/12, Rob Weir robw...@apache.org ha scritto:
...
All in all, I think we should focus on stability and
not on features.
On 30.04.2012 14:35, Rob Weir wrote:
On Mon, Apr 30, 2012 at 12:55 AM, Juergen Schmidt
jogischm...@googlemail.com wrote:
[..]
I don't think so, I would do it exactly in the other direction. Fixes for
critical issues or issues that are assigned for a 3.4.1 should be fixed on the
related
I don't think so, I would do it exactly in the other direction. Fixes for
critical issues or issues that are assigned for a 3.4.1 should be fixed on the
related stable branch and also merged into trunk.
+1
I thought Armin ran into some performance-related issues with merging.
Do we know
On 04/29/12 23:55, Juergen Schmidt wrote:
...
I think it all depends on how fast we plan to release 4.0.
It looks likely that merging Symophony may be easy for the
IBM guys, since symphony already updated theit base OOo,
so a release may be fast and the 3.x branch may be short
lived. (I don't
:
I'm already starting to get questions on what we'll be doing after AOO
3.4 is released. Based on previous conversations on this list, I'm
able to speak confidently about a few things:
1) We'll probably graduate to a Top Level Project
2) IBM says they will contribute Symphony source
Am 04/28/2012 06:32 PM, schrieb Rob Weir:
I'm already starting to get questions on what we'll be doing after AOO
3.4 is released. Based on previous conversations on this list, I'm
able to speak confidently about a few things:
1) We'll probably graduate to a Top Level Project
2) IBM says
Rob Weir wrote:
1) We want to have a maintenance branch that can be used to deliver
quick-turnaround releases. ...
2) We also want feature release, like 3.5, 3.6, etc. Almost anything
can go into them. ...
3) Then we have major updates, like 4.0. These are similar to #2,
only more
On 04/29/2012 07:16 AM, Marcus (OOo) wrote:
Am 04/28/2012 06:32 PM, schrieb Rob Weir:
I'm already starting to get questions on what we'll be doing after AOO
3.4 is released. Based on previous conversations on this list, I'm
able to speak confidently about a few things:
1) We'll probably
already starting to get questions on what we'll be doing after AOO
3.4 is released. Based on previous conversations on this list, I'm
able to speak confidently about a few things:
1) We'll probably graduate to a Top Level Project
2) IBM says they will contribute Symphony source code after 3.4
+1
-Original Message-
From: Kay Schenk [mailto:kay.sch...@gmail.com]
Sent: Sunday, April 29, 2012 09:00
To: ooo-dev@incubator.apache.org
Subject: Re: After AOO 3.4?
[ ... ]
I concur with Marcus's analysis and observation here, as well as
comments by Rob and Andrea. Bug fixes
--- Sab 28/4/12, Dave Fisher dave2w...@comcast.net ha scritto:
...
We also have to update some components. Anything with
an Apache tag on it, like Apache Commons or Apache Lucene
comes first because working with other Apache projects
is key for our graduation.
The amount of Apache
--- Sab 28/4/12, Rob Weir robw...@apache.org ha scritto:
...
All in all, I think we should focus on stability and
not on features.
What I am meaning here is that our users should not expect
false promises like adding an import Visio documents
feature that simply doesn't work. Of
On Sunday, 29. April 2012 at 21:10, Pedro Giffuni wrote:
--- Sab 28/4/12, Rob Weir robw...@apache.org ha scritto:
...
All in all, I think we should focus on stability and
not on features.
What I am meaning here is that our users should not expect
false promises
I'm already starting to get questions on what we'll be doing after AOO
3.4 is released. Based on previous conversations on this list, I'm
able to speak confidently about a few things:
1) We'll probably graduate to a Top Level Project
2) IBM says they will contribute Symphony source code after
Hello;
On 04/28/12 11:32, Rob Weir wrote:
I'm already starting to get questions on what we'll be doing after AOO
3.4 is released. Based on previous conversations on this list, I'm
able to speak confidently about a few things:
1) We'll probably graduate to a Top Level Project
2) IBM says
On Apr 28, 2012, at 1:07 PM, Pedro Giffuni wrote:
Hello;
On 04/28/12 11:32, Rob Weir wrote:
I'm already starting to get questions on what we'll be doing after AOO
3.4 is released. Based on previous conversations on this list, I'm
able to speak confidently about a few things:
1) We'll
On Sat, Apr 28, 2012 at 4:07 PM, Pedro Giffuni p...@apache.org wrote:
Hello;
On 04/28/12 11:32, Rob Weir wrote:
I'm already starting to get questions on what we'll be doing after AOO
3.4 is released. Based on previous conversations on this list, I'm
able to speak confidently about a few
On Mon, Apr 2, 2012 at 12:23 AM, Kevin Grignon kevingrignon...@gmail.comwrote:
Drew and Rob,
I'll defer to your experience with the OO recruiting. Your comments make
sense.
The key point I wanted to make was that I feel that diversity is a good
thing, and that product design need not
Drew and Rob,
I'll defer to your experience with the OO recruiting. Your comments make
sense.
The key point I wanted to make was that I feel that diversity is a good
thing, and that product design need not solely the domain of technical
people. Yes, the offering is software and that requires
Please cancel all emails to me.
Tkanks
On Sat, Mar 31, 2012 at 7:03 AM, drew jensen drewjensen.in...@gmail.comwrote:
On Fri, 2012-03-30 at 23:21 -0400, Rob Weir wrote:
On Thu, Mar 29, 2012 at 12:35 PM, drew jensen
drewjensen.in...@gmail.comwrote:
On Thu, 2012-03-29 at 09:04 -0400, Rob
On Thu, Mar 29, 2012 at 12:35 PM, drew jensen drewjensen.in...@gmail.comwrote:
On Thu, 2012-03-29 at 09:04 -0400, Rob Weir wrote:
On Thu, Mar 29, 2012 at 8:31 AM, Kevin Grignon
kevingrignon...@gmail.comwrote:
Rob,
Sounds like we can appeal to contributors intrinsic and extrinsic
On Fri, 2012-03-30 at 23:21 -0400, Rob Weir wrote:
On Thu, Mar 29, 2012 at 12:35 PM, drew jensen
drewjensen.in...@gmail.comwrote:
On Thu, 2012-03-29 at 09:04 -0400, Rob Weir wrote:
On Thu, Mar 29, 2012 at 8:31 AM, Kevin Grignon
kevingrignon...@gmail.comwrote:
Rob,
Rob,
Sounds like we can appeal to contributors intrinsic and extrinsic motivation.
Another newbie question: Does OO have any experience recruiting non-technical
volunteers. Many disciplines outside coding can have an impact on the offering.
Product management, UX, ID, training, visual design,
On 29 March 2012 05:51, Kevin Grignon kevingrignon...@gmail.com wrote:
Given the risk in a formal certification program,
Why would there be risk - well any more risk than doing anything else?
Not for profit is easy. Do it through ASDAN, (for example) a registered
charity in the UK and
Thanks Pedro for explaining the non-profit angle. The ASF does not
offer any such certificates currently - it's hard to see how they work
with our primary mission (of the ASF overall), which is providing
software for the public good.
There are plenty of other third parties who do this kind
On 29 March 2012 14:08, Shane Curcuru a...@shanecurcuru.org wrote:
Thanks Pedro for explaining the non-profit angle. The ASF does not offer
any such certificates currently - it's hard to see how they work with our
primary mission (of the ASF overall), which is providing software for the
On Thu, 2012-03-29 at 09:04 -0400, Rob Weir wrote:
On Thu, Mar 29, 2012 at 8:31 AM, Kevin Grignon
kevingrignon...@gmail.comwrote:
Rob,
Sounds like we can appeal to contributors intrinsic and extrinsic
motivation.
Another newbie question: Does OO have any experience recruiting
.
Regards,
Kevin
On Mar 27, 2012, at 10:47 PM, Rob Weir robw...@apache.org wrote:
On Mon, Mar 26, 2012 at 9:39 PM, Louis Suárez-Potts lui...@gmail.com
wrote:
Hi,
On 2012-03-19, at 08:41 , Rob Weir wrote:
Any ideas and the best ways how we can improve in this area after AOO
3.4 releases
improve in this area after
AOO
3.4 releases?
Lots, and these would complement the rather good ideas already
proposed.
What we did at OOo actually worked--to attract developers and
contributors
of all sorts. What worked against us I do not think I need spell out,
but
the cussedness
improve in this area after AOO
3.4 releases?
Lots, and these would complement the rather good ideas already proposed.
What we did at OOo actually worked--to attract developers and
contributors
of all sorts. What worked against us I do not think I need spell out,
but
the cussedness
in this area after
AOO
3.4 releases?
Lots, and these would complement the rather good ideas already
proposed.
What we did at OOo actually worked--to attract developers and
contributors
of all sorts. What worked against us I do not think I need spell out,
but
the cussedness
, Louis Suárez-Potts
lui...@gmail.com
wrote:
Hi,
On 2012-03-19, at 08:41 , Rob Weir wrote:
Any ideas and the best ways how we can improve in this area after
AOO
3.4 releases?
Lots, and these would complement the rather good ideas already
proposed.
What we did at OOo
Hi Ram;
We are strictly non-profit here so I am not sure how far
we could go with such certifications. I think it's a
delicate matter and sooner or later someone would likely
complain about students being exploited or your company
making money in exchange of ASF certificates.
We certainly can
Given the risk in a formal certification program, we could look to support
contributors intrinsic motivation by reducing barriers to entry and supporting
a positive on-boarding experience.
On Mar 29, 2012, at 12:37 PM, Pedro Giffuni p...@apache.org wrote:
Hi Ram;
We are strictly
, Mar 26, 2012 at 9:39 PM, Louis Suárez-Potts
lui...@gmail.com
wrote:
Hi,
On 2012-03-19, at 08:41 , Rob Weir wrote:
Any ideas and the best ways how we can improve in this area after
AOO
3.4 releases?
Lots, and these would complement the rather good ideas already
proposed.
What we did
Hi Pedro Giffuni,
You are absolutely right, i could not think the other side it(exploiting
making money inexchange of certificates). The certificates are issyed by
Apache and issued only when there is a contribution.
The second point is that most of the students generally do not have any
ideas
Hi;
--- Gio 29/3/12, q...@imsoftwaresystems.com ha scritto:
...
Hi Pedro Giffuni,
You are absolutely right, i could not think the other side
it(exploiting
making money inexchange of certificates). The certificates
are issyed by
Apache and issued only when there is a contribution.
The
how we can improve in this area after
AOO
3.4 releases?
Lots, and these would complement the rather good ideas already
proposed.
What we did at OOo actually worked--to attract developers and
contributors
of all sorts. What worked against us I do not think I need spell
out
...@apache.org wrote:
On Mon, Mar 26, 2012 at 9:39 PM, Louis Suárez-Potts lui...@gmail.comwrote:
Hi,
On 2012-03-19, at 08:41 , Rob Weir wrote:
Any ideas and the best ways how we can improve in this area after AOO
3.4 releases?
Lots, and these would complement the rather good ideas already proposed
Hi,
On 2012-03-19, at 08:41 , Rob Weir wrote:
Any ideas and the best ways how we can improve in this area after AOO
3.4 releases?
Lots, and these would complement the rather good ideas already proposed. What
we did at OOo actually worked--to attract developers and contributors of all
sorts
On 03/22/2012 08:06 PM, Ross Gardler wrote:
I'm not sure if Jim meant this or not, but being started doesn't mean
finding things to do. The first stage is figuring out how to set up a dev
environment. Could this be sensibly added to (our linked from) the get
involved page?
Ah, sorry for the
On 3/22/12 7:18 PM, Pedro Giffuni wrote:
On 03/22/12 11:09, Herbert Duerr wrote:
As a quick note, I'd *love* to dive in and start doing some
coding on AOOo; it's just that I've no idea where in the
heck to start... :)
Additionally to what Pedro said I'd like to point to our Bugzilla at
Hi,
On 23.03.2012 08:31, Jürgen Schmidt wrote:
On 3/22/12 7:18 PM, Pedro Giffuni wrote:
On 03/22/12 11:09, Herbert Duerr wrote:
As a quick note, I'd *love* to dive in and start doing some
coding on AOOo; it's just that I've no idea where in the
heck to start... :)
Additionally to what Pedro
On 20.03.2012 11:09, Armin Le Grand wrote:
Hi Rob,
[..]
Extendign after Reginas eMail:
- refactoring
- featues
- bugfixing
- tutoring
The tradeoffs are hard, but splitting time in
- refactoring
- featues
- bugfixing
is the key, the ratio is hard to determine, maybe everyone has to find a
As a quick note, I'd *love* to dive in and start doing some
coding on AOOo; it's just that I've no idea where in the
heck to start... :)
Hi Jim;
On 03/22/12 10:03, Jim Jagielski wrote:
As a quick note, I'd *love* to dive in and start doing some
coding on AOOo; it's just that I've no idea where in the
heck to start... :)
It depends on your particular interests. The codebase is
rather big and there's a lot to do.
There are big
As a quick note, I'd *love* to dive in and start doing some
coding on AOOo; it's just that I've no idea where in the
heck to start... :)
Additionally to what Pedro said I'd like to point to our Bugzilla at
https://issues.apache.org/ooo/ which is a fountain of inspiration. E.g.
On 03/22/12 11:09, Herbert Duerr wrote:
As a quick note, I'd *love* to dive in and start doing some
coding on AOOo; it's just that I've no idea where in the
heck to start... :)
Additionally to what Pedro said I'd like to point to our Bugzilla at
https://issues.apache.org/ooo/ which is a
I'm not sure if Jim meant this or not, but being started doesn't mean
finding things to do. The first stage is figuring out how to set up a dev
environment. Could this be sensibly added to (our linked from) the get
involved page?
Sent from my mobile device, please forgive errors and brevity.
On
Hi Regina,
Thanks for these excellent insights.
Best regards
Simon
Op 20-3-2012 13:29, Regina Henschel schreef:
(...)
It is impossible to understand the code without guides and without
mentoring.
Conclusion, wish or how you might call it:
(1) Document parts of the code very detailed in all
on the release. Post
AOO 3.4 we might want to adjust to a more balanced approach.
Any ideas and the best ways how we can improve in this area after AOO
3.4 releases?
The tradeoffs are hard, but splitting time in
- refactoring
- featues
- bugfixing
is the key, the ratio is hard to determine, maybe everyone
of the contributor base. With AOO 3.4
we have biases the effort toward forward progress on the release. Post
AOO 3.4 we might want to adjust to a more balanced approach.
Any ideas and the best ways how we can improve in this area after AOO
3.4 releases?
It is impossible to understand the code without guides
.
Any ideas and the best ways how we can improve in this area after AOO
3.4 releases?
-Rob
and the best ways how we can improve in this area after AOO
3.4 releases?
-Rob
88 matches
Mail list logo
