Starting Introduction to Contributing to Apache OpenOffice Module
Hello, My name is Josh and I live in Seattle, WA. I am interested in getting as much QA experience as possible as quickly as possible. The reason for this is that I am moving into a QA position at work and want to get up to speed and be an effective member of my team. I have completed the first course of the UW Java Dev classes and also done some simplistic programming in Python and practiced in a program called Raptor. Not sure how this process goes exactly, but I am eager to help and a quick learner. Hope to be of help to someone and get some experience under my belt soon! Thanks
stupid program
I hate Open Office—I have tried to fix it, I have a Mac OSX 10.9.1 and I know OO has a bug and I have tried to fix it, got to the library and deleted the folder, but still can’t shut down OO and, therefore, can’t update any other application. I have looked all over the internet, have spent hours trying to get rid of this travesty, and I think this is totally irresponsible of this company, free or not, to NOT fix this easily. This makes Windows look like child’s play—at least you can uninstall programs…..am very disappointed with Apache and OO. It is probably going to cost me money to get my computer back….Jenifer Watkins - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Extensions "wish list" placementt?
Every once in a while a topic arises on this list and gets a response like "that might be a good idea for an extension". And, we have a fair number of folks who are interested in helping with development as well. So, I'm wondering a few things -- * Is is a good idea to steer new developers into extension development maybe as an introductory step? * and, assuming we can track down some of proposed extensions, where is a good place to record these for future reference? -- - MzK "Cats do not have to be shown how to have a good time, for they are unfailing ingenious in that respect." -- James Mason
framesets on the web server
Does anyone know off-hand if framesets are allowed for web page display on the web server? I have just uploaded an area using frames, and well, it doesn't work as I expected. If not, I'll retool. Thanks. -- - MzK "Cats do not have to be shown how to have a good time, for they are unfailing ingenious in that respect." -- James Mason
Re: Better visibility for dev builds (Re: [RELEASE]: Beta downloads and feedback and a proposed way to the final)
Hi Andrea, I am only commenting on a Foundation policy regarding advertising builds. Infrastructure is shared and while the impact of 1000s of users downloading a nightly build may seem small it has a possible negative influence on the 150 other projects and 50 podlings that share this infrastructure. If you want guidance or clearance on an exception to the policy then I think you know where to go. Infrastructure will need to agree and the board must not object. Best Regards, Dave On Mar 19, 2014, at 5:22 PM, Andrea Pescetti wrote: > Marcus (OOo) wrote: >> This means, normal users go to: >> www.openoffice.org/download/ >> Power users, dev's, qa's, etc. should be pointed to: >> openoffice.apache.org/developer-faqs.html >> So, putting text from Andrea's webpage proposal into the webpage Kay has >> found (again ;-) ) could be the golden way. > > They are two improvements in two different directions. Both good (as it would > be good to add text to the ci.apache.org page; some of us, but not me, do > have access to it). > > I see no reasons against doing both (pending resolution of the -1 by Dave; > but I hope this can be withdrawn after the new explanations). > > 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: Better visibility for dev builds (Re: [RELEASE]: Beta downloads and feedback and a proposed way to the final)
On Thu, Mar 20, 2014 at 7:27 AM, Jürgen Schmidt wrote: > On 3/20/14 3:13 PM, Andrea Pescetti wrote: > > Jürgen Schmidt wrote: > >>> http://www.openoffice.org/download/devbuilds.html > >> Development continues on trunk and completely new unrelated problems can > >> come up here. > > > > I don't want to divert the discussion, but wouldn't it make sense to > > have daily builds both for AOO410 and for trunk? Sure, this means more > > effort and more resources, but even if a daily build only fixes those > > couple bugs that may have been approved as stoppers the day before, it's > > already quite useful to volunteers who don't build OpenOffice themselves. > > sure that would make sense > > > > >> For the release only the aoo410 branch is relevant. Well I have moved > >> yesterday the SNAPSHOT tag on a proper version of the aoo410 branch and > >> the next snapshot build comes closer to what we want release. But the > >> SNAPSHOT build from the bots is Windows only. > > > > OK, so we are starting to have Windows (and Linux, right?) builds that > > are intermediate steps between 4.1.0-Beta and 4.1.0. These do not > > require extra effort, and these are the ones that should be very visible > > to our volunteers and prospective volunteers if we want to get the > > maximum QA coverage. > > no Linux from the bots, we have only a windows bot building the SNAPSHOT > as far as I know > > Juergen > We have a 32 bit Linux SNAPSHOT, and a windows 7 SNAPSHOT which builds once a week on Sunday at 7:00A (not sure about timezone). The 4.10 tag is also building once a week on Sunday. > > > > >> I hope you see my point and we should first work on the basics. > > > > I can edit the page to keep only builds that are from the AOO410 branch. > > Remember, I see this as a targeted effort to deliver great quality in > > 4.1.0. So I would make the page visible again when a new release is > > approaching, to show what we will have available at that time. > > > > 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 > > -- - MzK "Cats do not have to be shown how to have a good time, for they are unfailing ingenious in that respect." -- James Mason
4.1.0_release_blocker requested: [Issue 124375] Active optional hyphens invisible for the NuevaStd font in exported PDF
j...@apache.org has asked for 4.1.0_release_blocker: Issue 124375: Active optional hyphens invisible for the NuevaStd font in exported PDF https://issues.apache.org/ooo/show_bug.cgi?id=124375 - 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)
On 3/20/14 3:13 PM, Andrea Pescetti wrote: > Jürgen Schmidt wrote: >>> http://www.openoffice.org/download/devbuilds.html >> Development continues on trunk and completely new unrelated problems can >> come up here. > > I don't want to divert the discussion, but wouldn't it make sense to > have daily builds both for AOO410 and for trunk? Sure, this means more > effort and more resources, but even if a daily build only fixes those > couple bugs that may have been approved as stoppers the day before, it's > already quite useful to volunteers who don't build OpenOffice themselves. sure that would make sense > >> For the release only the aoo410 branch is relevant. Well I have moved >> yesterday the SNAPSHOT tag on a proper version of the aoo410 branch and >> the next snapshot build comes closer to what we want release. But the >> SNAPSHOT build from the bots is Windows only. > > OK, so we are starting to have Windows (and Linux, right?) builds that > are intermediate steps between 4.1.0-Beta and 4.1.0. These do not > require extra effort, and these are the ones that should be very visible > to our volunteers and prospective volunteers if we want to get the > maximum QA coverage. no Linux from the bots, we have only a windows bot building the SNAPSHOT as far as I know Juergen > >> I hope you see my point and we should first work on the basics. > > I can edit the page to keep only builds that are from the AOO410 branch. > Remember, I see this as a targeted effort to deliver great quality in > 4.1.0. So I would make the page visible again when a new release is > approaching, to show what we will have available at that time. > > 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: Better visibility for dev builds (Re: [RELEASE]: Beta downloads and feedback and a proposed way to the final)
Jürgen Schmidt wrote: http://www.openoffice.org/download/devbuilds.html Development continues on trunk and completely new unrelated problems can come up here. I don't want to divert the discussion, but wouldn't it make sense to have daily builds both for AOO410 and for trunk? Sure, this means more effort and more resources, but even if a daily build only fixes those couple bugs that may have been approved as stoppers the day before, it's already quite useful to volunteers who don't build OpenOffice themselves. For the release only the aoo410 branch is relevant. Well I have moved yesterday the SNAPSHOT tag on a proper version of the aoo410 branch and the next snapshot build comes closer to what we want release. But the SNAPSHOT build from the bots is Windows only. OK, so we are starting to have Windows (and Linux, right?) builds that are intermediate steps between 4.1.0-Beta and 4.1.0. These do not require extra effort, and these are the ones that should be very visible to our volunteers and prospective volunteers if we want to get the maximum QA coverage. I hope you see my point and we should first work on the basics. I can edit the page to keep only builds that are from the AOO410 branch. Remember, I see this as a targeted effort to deliver great quality in 4.1.0. So I would make the page visible again when a new release is approaching, to show what we will have available at that time. Regards, Andrea. - 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)
On 3/20/14 8:59 AM, Andrea Pescetti wrote: > Jürgen Schmidt wrote: >> which builds exactly do you want to promote here and with what >> explanation? >> - build bots are fine, need no or only little explanation >> - manually built snapshot/milestones >> -- please no further page where entries have to be edited manually as >> well > > Whatever is useful to our community. Anyway, the draft is online at > http://www.openoffice.org/download/devbuilds.html > and I think it's rather clear if one reads all of it. I have read it and I see not how it can help for the release. Feedback on nightly builds from trunk does not help us really at the moment. Development continues on trunk and completely new unrelated problems can come up here. For the release only the aoo410 branch is relevant. Well I have moved yesterday the SNAPSHOT tag on a proper version of the aoo410 branch and the next snapshot build comes closer to what we want release. But the SNAPSHOT build from the bots is Windows only. I hope you see my point and we should first work on the basics. Juergen > >> Again somebody should continue to work on build bots that are identical >> with the build release machines that we can use this builds directly. > > This is a unrelated problem, and does not apply to this release, even > though I hope we can make some steps forward here too and indeed align > the buildbots with the release baseline for a future release. > > 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: Better visibility for dev builds (Re: [RELEASE]: Beta downloads and feedback and a proposed way to the final)
Jürgen Schmidt wrote: which builds exactly do you want to promote here and with what explanation? - build bots are fine, need no or only little explanation - manually built snapshot/milestones -- please no further page where entries have to be edited manually as well Whatever is useful to our community. Anyway, the draft is online at http://www.openoffice.org/download/devbuilds.html and I think it's rather clear if one reads all of it. Again somebody should continue to work on build bots that are identical with the build release machines that we can use this builds directly. This is a unrelated problem, and does not apply to this release, even though I hope we can make some steps forward here too and indeed align the buildbots with the release baseline for a future release. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [CWiki] Account Whitelisting
Sandhya Sivakumar wrote: I have been volunteering in AOO in and out for a year.I wanted to add my name to the list of volunteers. Sure, please add it yourself, you now have the necessary rights and can edit pages. If you lost your CWiki password, you can get a new one at your hotmail.com address (at least, it seems that the CWiki account is linked to that one). Regards, Andrea. - 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)
On 3/20/14 1:22 AM, Andrea Pescetti wrote: > Marcus (OOo) wrote: >> This means, normal users go to: >> www.openoffice.org/download/ >> Power users, dev's, qa's, etc. should be pointed to: >> openoffice.apache.org/developer-faqs.html >> So, putting text from Andrea's webpage proposal into the webpage Kay has >> found (again ;-) ) could be the golden way. > > They are two improvements in two different directions. Both good (as it > would be good to add text to the ci.apache.org page; some of us, but not > me, do have access to it). > > I see no reasons against doing both (pending resolution of the -1 by > Dave; but I hope this can be withdrawn after the new explanations). which builds exactly do you want to promote here and with what explanation? - build bots are fine, need no or only little explanation - manually built snapshot/milestones -- please no further page where entries have to be edited manually as well Again somebody should continue to work on build bots that are identical with the build release machines that we can use this builds directly. Different configuration switches can trigger release, beta or dev builds Juergen > > 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
