openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Weir <>
Subject Re: Who wants to build OpenOffice?
Date Tue, 06 Sep 2011 16:57:27 GMT
On Tue, Sep 6, 2011 at 7:59 AM, Marc-Oliver Straub
<> wrote:
> As preparation for tomorrow, how will we deal with bugs found during the
> Linux builds? Tag them in the issue tracker? Post them on the mailing list
> only?

Since we will have (hopefully) new people participating in the event,
maybe we should keep it really easy.  People will join the
conversation and drop out at different times, etc.  So I'd recommend
just tracking the issues and findings in comments to a new mailing
list thread.  Then after the event we can go back over the thread and
turn issues into bugs or even just update the wiki directly.

Another lightweight alternative would be to start a new page on the
community wiki and track the issues there:

Again, the same idea.  Lightweight approach to record the issues, then
dispose of them later.

Would either of these approaches work?


> Thanks, Oli
> On 9/5/2011 11:51 PM, Rob Weir wrote:
>> On Mon, Sep 5, 2011 at 4:48 PM, Matt Richards<>  wrote:
>>> Now that I've built OpenOffice on Linux with moderate success, I'd like
>>> to
>>> lend a helping hand with the documentation side of things. As far as I am
>>> aware, the existing (maybe old now) wiki has been migrated to Apache
>>> Infra
>>> (via VM). Does this content need to be moved to the confluence wikis
>>> eventually? I do apologies if this is off topic, there's been so much
>>> discussion going on proving difficult to follow everything all the way
>>> through.
>> Excellent.  What distro where you using?  And what configure flags?
>> For the sake of this exercise we should probably track, on a wiki page
>> (confluence community wiki is fine) what combinations we're trying and
>> what corrections we'll want to make in the build instructions.
>> It is not clear yet where the build instructions will finally end up
>> living, but we don't need to solve that problem quite yet.
>> -Rob

View raw message