[WEBSITE] QA manual test cases...new revision

[Kay Schenk]

Sorry for the noise about this. I will replacing all the test cases I
uploaded a week ago with renamed ones that include the original AOOTest-xxx
name from TestLink. So, if you're working on any of these, my apologies.

The test case area:
http://www.openoffice.org/qa/testcase/ManualTesting/

is currently NOT viewable at all and I've infra for some assistance on
this. It was OK for a day or so after the original upload on March 30th.

In any case, you will see a few svn changes through the commits list
shortly.

-- 
--
MzK

"Less is MORE."

Re: Licensing for College

[Peter Kovacs]

Hello Miss Victoria Stevenson,


Please take my appologies, I saw the adress tori.steven...@lonestar.edu 
 and assumed a male person.


I am deeply sorry for the gender confusion.


All the best

Peter Kovacs


On 04.04.2018 22:47, Peter Kovacs wrote:


Hello Mr Stevenson,

I would like to add a small, but important detail.

The use of the software "As is", is free as stated already.
The development /maintenance of the product is not free. It costs 
involvement of volunteers.
If the team of Volunteers manage to bring out a new version, it is 
again downloadable for free.


We are open to everyone, who wants to help developing OpenOffice, 
under the License we distribute the Software with 
(https://www.openoffice.org/license.html).

We need volunteers for:
# producing user Documentation (we are open for all formats)
# user support (we currently have 2 channels: user mailing list, forum)
# evaluating Bug reports
# testing new releases
# anylsing code for bugs
# developing new features in the core of the software or as add on.
# maintaining existing code or add ons.

I am sorry if this goes beyond what you are interested in, but I think 
you need to understand our DNA. (And where free as in it does not cost 
something ends)


Thanks for your time
Peter

On 03.04.2018 19:34, Stevenson, Victoria wrote:


Hello,

We have 3 laptops that have been donated to our College.  We are 
writing to make sure Open Office can be used for education or 
business use without violating any licensing.


Please let us know.

Thank you,

Tori Stevenson, ITIL

Client Technologies Tech I

Office of Technology Services

Lone Star College

30555 Tomball Parkway, S-209

Tomball, Texas 77375

281-357-3788 (office)

tori.steven...@lonestar.edu 

LoneStar.edu/OTS 

cid:image002.gif@01D076D6.DE495090

LSC 20|20 “I act intentionallywith no fearto inspire excellence. I 
put my trustin others, knowing we are better together. And it’s all 
because students matter.”







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

Re: Licensing for College

[Peter Kovacs]

Hello Mr Stevenson,

I would like to add a small, but important detail.

The use of the software "As is", is free as stated already.
The development /maintenance of the product is not free. It costs 
involvement of volunteers.
If the team of Volunteers manage to bring out a new version, it is again 
downloadable for free.


We are open to everyone, who wants to help developing OpenOffice, under 
the License we distribute the Software with 
(https://www.openoffice.org/license.html).

We need volunteers for:
# producing user Documentation (we are open for all formats)
# user support (we currently have 2 channels: user mailing list, forum)
# evaluating Bug reports
# testing new releases
# anylsing code for bugs
# developing new features in the core of the software or as add on.
# maintaining existing code or add ons.

I am sorry if this goes beyond what you are interested in, but I think 
you need to understand our DNA. (And where free as in it does not cost 
something ends)


Thanks for your time
Peter

On 03.04.2018 19:34, Stevenson, Victoria wrote:


Hello,

We have 3 laptops that have been donated to our College.  We are 
writing to make sure Open Office can be used for education or business 
use without violating any licensing.


Please let us know.

Thank you,

Tori Stevenson, ITIL

Client Technologies Tech I

Office of Technology Services

Lone Star College

30555 Tomball Parkway, S-209

Tomball, Texas  77375

281-357-3788 (office)

tori.steven...@lonestar.edu 

LoneStar.edu/OTS 

cid:image002.gif@01D076D6.DE495090

LSC 20|20 “I act intentionallywith no fearto inspire excellence. I put 
my trustin others, knowing we are better together. And it’s all 
because students matter.”

Re: Licensing for College

[Marcus]

Am 04.04.2018 um 21:23 schrieb Chuck Davis:

Victoria, all Apache products are open source and freely available to use
on as many computers as you wish for the cost of a free download.
OpenOffice is available at www.openoffice.apache.org.  DO NOT pay anybody
to use OpenOffice unless you wish to support open source projects by a
donation to Apache Software Foundation.


I'm sure Chuck wanted to mention this website to download the offical 
installation files for OpenOffice:


https://www.openoffice.org/download/

Marcus




On Tue, Apr 3, 2018 at 10:34 AM, Stevenson, Victoria <
tori.steven...@lonestar.edu> wrote:


Hello,

We have 3 laptops that have been donated to our College.  We are writing
to make sure Open Office can be used for education or business use
without violating any licensing.

Please let us know.

Thank you,

Tori Stevenson, ITIL



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

Re: Licensing for College

[Marcus]

Hi Tori,

yes, OpenOffice is open source software. And therefore free of any 
license fees.


You can use it for private purposes, or educational, for commercial 
businesses or a charity background.


Fore more details please see the license of the Apache Software 
Foundation we are using:

https://www.openoffice.org/license.html

Have fun with OpenOffice.

Marcus



Am 03.04.2018 um 19:34 schrieb Stevenson, Victoria:
We have 3 laptops that have been donated to our College.  We are writing 
to make sure Open Office can be used for education or business use 
without violating any licensing.


Please let us know.

Thank you,

Tori Stevenson, ITIL



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

Re: Licensing for College

[Chuck Davis]

Victoria, all Apache products are open source and freely available to use
on as many computers as you wish for the cost of a free download.
OpenOffice is available at www.openoffice.apache.org.  DO NOT pay anybody
to use OpenOffice unless you wish to support open source projects by a
donation to Apache Software Foundation.



On Tue, Apr 3, 2018 at 10:34 AM, Stevenson, Victoria <
tori.steven...@lonestar.edu> wrote:

> Hello,
>
>
>
> We have 3 laptops that have been donated to our College.  We are writing
> to make sure Open Office can be used for education or business use
> without violating any licensing.
>
>
>
> Please let us know.
>
>
>
> Thank you,
>
>
>
> Tori Stevenson, ITIL
>
> Client Technologies Tech I
>
> Office of Technology Services
>
> Lone Star College
>
> 30555 Tomball Parkway
> ,
> S-209
>
> Tomball, Texas  77375
>
> 281-357-3788 (office)
>
> tori.steven...@lonestar.edu
>
> LoneStar.edu/OTS 
>
>
>
> [image: cid:image002.gif@01D076D6.DE495090]
>
>
>
> LSC 20|20 “I act intentionally with no fear to inspire excellence. I put
> my trust in others, knowing we are better together. And it’s all because 
> students
> matter.”
>
>
>

Licensing for College

[Stevenson, Victoria]

Hello,

We have 3 laptops that have been donated to our College.  We are writing to 
make sure Open Office can be used for education or business use without 
violating any licensing.

Please let us know.

Thank you,

Tori Stevenson, ITIL
Client Technologies Tech I
Office of Technology Services
Lone Star College
30555 Tomball Parkway, S-209
Tomball, Texas  77375
281-357-3788 (office)
tori.steven...@lonestar.edu
LoneStar.edu/OTS

[cid:image002.gif@01D076D6.DE495090]

LSC 20|20 "I act intentionally with no fear to inspire excellence. I put my 
trust in others, knowing we are better together. And it's all because students 
matter."

Re: [WEBSITE] QA area changes, and differences between staging and production

[Kay Schenk]

On Tue, Apr 3, 2018 at 1:59 PM, Keith N. McKenna 
wrote:

> On 4/2/2018 7:29 PM, Kay Schenk wrote:
> 
> > ​OK, I think the filenames are fixed now. Bad commit the first time I
> guess.
> > Great if you could help with the restructuring. Please keep in mind that
> > this is not ALL the TestLink files. I need to see what we're missing and
> > want to have at this point.
>
> Another Question. When you downloaded the files from the testlink site
> did you filter for only manual execution? I notice that your initial
> directory was for ManualExecution.
>
> Regards
> Keith
>

​Hi Keith --
I followed the instructions I posted on the QA list In February --

​

https://lists.apache.org/thread.html/fdca925316308fda4f4faed31276f79c4e48baf4badea8842f452f4d@%3Cqa.openoffice.apache.org%3E

​The "browse cases" give you viewing of manual test cases. The new
directory I created under --
​http://www.openoffice.org/qa/testcase/ManualTesting

are written test cases previously used in QA "manual" testing.

If you're finding ManualExecution on TestLink(?), this is an area that I
did not use.

There is a LOT more cleanup and documentation of process to do at this
point, and I now see the new area is NOT available for public viewing as it
was on March 30, so I need to investigate the cause.

Hope this helps.


-- 
--
MzK

"Less is MORE."

Re: gbuild migration (Was: Re: Building module store error on macOS)

[Damjan Jovanovic]

Thank you, I appreciate it.

The list of gbuild modules is in main/Module_ooo.mk. The rest are using
dmake. The next one I expect to port is main/jurt, and that will be a
substantial patch.

Will our release process keep testing trunk until it's ready, then make a
branch of it to use for the release?

If necessary I can work on modules offline or in another branch, then
commit or merge them back when the release is over.


On Wed, Apr 4, 2018 at 3:06 PM, Jim Jagielski  wrote:

>
>
> > On Apr 4, 2018, at 9:01 AM, Jim Jagielski  wrote:
> >
> >
> > I will start another thread on the gbuild topic...
> >
>
> First and foremost, I am incredibly impressed with the work
> being done on the gbuild migration. I really am.
>
> However, and there's always a "however", there must come
> a time where we "hold the line" on migration in hopes of getting
> a 4.2.0 out. As such, I think some sort of plan might be due
> (and apologies if we have such a documented plan already
> in place)...
>
> Does it make sense to spend time to list modules that still
> need that migration and then prioritize them? As well as
> create a policy such that all "new and updated" modules
> must use gbuild but for existing modules, "if it ain't broke,
> don't fix it"?
>
> I'm not trying to stifle the migration, it's just that it appears
> to me that we need better management about it.
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

gbuild migration (Was: Re: Building module store error on macOS)

[Jim Jagielski]

> On Apr 4, 2018, at 9:01 AM, Jim Jagielski  wrote:
> 
> 
> I will start another thread on the gbuild topic...
> 

First and foremost, I am incredibly impressed with the work
being done on the gbuild migration. I really am.

However, and there's always a "however", there must come
a time where we "hold the line" on migration in hopes of getting
a 4.2.0 out. As such, I think some sort of plan might be due
(and apologies if we have such a documented plan already
in place)...

Does it make sense to spend time to list modules that still
need that migration and then prioritize them? As well as
create a policy such that all "new and updated" modules
must use gbuild but for existing modules, "if it ain't broke,
don't fix it"?

I'm not trying to stifle the migration, it's just that it appears
to me that we need better management about it.


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

Re: Building module store error on macOS

[Jim Jagielski]

Sometimes just a "heads-up" before the (sizable) commits might be
nice, esp on commits that will likely break builds.

At some point, however, we need to draw a line in the sand and
say "we will hold things steady for awhile" or else we'll never get
to a point where we can reasonably build and test 4.2.0. For example,
if a dev release is made, and some bugs are found, and potentially *fixed*,
but in the meantime more work is done on the gbuild migration, it makes
it harder to see if those fixes actually work. It's hard to QA a constantly
changing project.

I will start another thread on the gbuild topic...

> On Mar 27, 2018, at 11:51 AM, Matthias Seidel  
> wrote:
> 
> Am 27.03.2018 um 17:43 schrieb Dave Fisher:
>> Damian,
>> 
>> Jim is reasonably asking for some heads up so that he can know what to 
>> expect before he does Mac and Linux builds.
>> 
>> Matthias would certainly like the same as well for Windows although 
>> buildbots do help.
> 
> I always monitor new commits here:
> https://svn.apache.org/viewvc/openoffice/trunk/?view=log
> 
> Damjans comments are always descriptive (unlike mine).
> But sometimes he is committing faster than I can test! ;-)
> 
> Regards,
>Matthias
> 
>> 
>> Speaking of Mac Buildbots Jim did offer to make one available in his 
>> location and infrastructure knows how to hook that up. Is now the time?
>> 
>> I think we have several developers doing builds now which is great!
>> 
>> Regards,
>> Dave
>> 
>> Sent from my iPhone
>> 
>>> On Mar 27, 2018, at 8:13 AM, Damjan Jovanovic  wrote:
>>> 
>>> Hi
>>> 
>>> Between the gbuild migration, Win64 migration and MSVS 2015 migration, all
>>> of which are project-wide, modules will break, a lot.
>>> 
>>> If I had access to a Mac, I would definitely be testing these changes.
>>> Since I don't, Infra keep refusing to get us a Mac buildbot, Apple is my
>>> least favourite platform, Apple products are disproportionately expensive,
>>> and I do so much for AOO already (being its biggest contributor), I think
>>> asking me to test Mac builds is unreasonable. If you want to change that, I
>>> could be bought a Mac or given remote access to one, Mac developers could
>>> pull their own weight, or Mac could be dropped as a supported platform.
>>> 
>>> Now as for the store build regression, please post the output of "build
>>> --from store".
>>> 
>>> Regards
>>> Damjan
>>> 
>>> 
>>> 
>>> 
 On Tue, Mar 27, 2018 at 3:29 PM, Jim Jagielski  wrote:
 
 Looks like recent build changes have broken the macOS
 build again... This time we die when trying to build
 store.
 
 
 IMO, it would be nice if when updating, people were
 a little more circumspect on how/if this would affect
 other builds. I realize that it is hard to anticipate
 such things, but at least some sort of warning, or
 "head's up" or some summary of what was changed and
 why/how, instead of just a huge commit, might make
 things easier for people who then need to dig into
 the weeds and fix other platforms.
 
 
 -
 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: Building module store error on macOS

[Jim Jagielski]

I actually have a mac mini that I had been using until I decided to
move to macOS VMs (so I could take advantage of faster machines).
As with most things, the issue isn't getting the h/w but rather the
administration of the machine.

> On Mar 28, 2018, at 1:26 AM, Damjan Jovanovic  wrote:
> 
> Oh I wasn't aware. In that case, thank you Larry, great work :).
> 
> Why don't we hear from you Mac guys more? How can we work better together?
> What happened to Jim's Mac buildbot idea?
> 
> 
> On Wed, Mar 28, 2018 at 5:03 AM, Dave Fisher  wrote:
> 
>> Hi Damjan,
>> 
>> Larry has contributed Release and Build testing for MacOS. I thank him for
>> that.
>> 
>> We are all in this together. No one individual should feel overburdened.
>> Enough have stuck around and things are developing.
>> 
>> Larry - Are you ready to test Jim’s MacOS build instructions and try to
>> build on your Mac?
>> 
>> Regards,
>> Dave
>> 
>> Sent from my iPhone
>> 
>>> On Mar 27, 2018, at 7:44 PM, Damjan Jovanovic  wrote:
>>> 
>>> On Wed, Mar 28, 2018 at 12:57 AM, Larry Gusaas 
>>> wrote:
>>> 
 
 
 On 2018-03-27, 4:32 PM Dave Fisher wrote concerning "Re: Building module
 store error on macOS":
 
 For development purposes Apple does not allow virtualization and
> development has to proceed on physical Apple boxes.
> 
> If we could have macOS on a VM not on Apple hardware then we would
>> have a
> Apache hosted macOS buildbot now and for the prior four years.
> 
 
 True, but there are very good reasons for Apple to work that way.
 
 So, Apple does cost the project more.
> 
 
 Yes. But that is not what I responded to. The specific quote was "Apple
 products are disproportionately expensive", which is pure FUD. That
>> along
 with the statement "or Mac could be dropped as a supported platform"
>> gets
 my hackles up. It is typical of the anti-Mac rhetoric I encounter way
>> too
 often.
 
>>> 
>>> If Apple is that cheap for you and you believe in it that much, I've
>>> already outlined what you can do, such as buying us a Mac mini or
>> providing
>>> access to one, or contributing as a developer.
>> 
>> 
>> -
>> 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