New QA Volunteer
Hello my name is Phillip and I am a student at the University of Ballarat. I am currently undertaking a course that teaches about open source and one of the assessments for this course requires me to contribute to an open source project. I do not have any previous experience at working on something like this, but would like to contribute in the form of testing and QA. I am not sure how I can help or where to start so any advice or guidance would be apreciated :)
Re: Skills, Resources and Mentors
Tal Daniel schrieb: But I couldn't edit the wiki page (I'm logged in to as Talchu). Hi, I can confirm that problem. I am not familiar with with cwiki, but I added myself to "Directory of volunteers", where I currently also can't find a way how to edit that page. It seems currently cwiki only can be edited by very few persons? CU Rainer - To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org For additional commands, e-mail: qa-h...@openoffice.apache.org
Re: Note: Updated BZ for new AOO version
On Mon, Sep 30, 2013 at 5:47 PM, Andrea Pescetti wrote: > On 27/09/2013 Rob Weir wrote: >> >> I've deactivated 4.0.1-dev as a version for new defects. I've added >> 4.0.1 as new version. There already exists a 4.1.0-dev version string >> I also deactivated 4.0.1 as a milestone assignment. > > > Is it possible to add 4.0.1 to the "Latest confirmation on" field? > Done. -Rob > Thanks, > Andrea. > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org For additional commands, e-mail: qa-h...@openoffice.apache.org
Re: Note: Updated BZ for new AOO version
On 27/09/2013 Rob Weir wrote: I've deactivated 4.0.1-dev as a version for new defects. I've added 4.0.1 as new version. There already exists a 4.1.0-dev version string I also deactivated 4.0.1 as a milestone assignment. Is it possible to add 4.0.1 to the "Latest confirmation on" field? Thanks, Andrea. - To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org For additional commands, e-mail: qa-h...@openoffice.apache.org
Re: Skills, Resources and Mentors
On Mon, Sep 30, 2013 at 6:58 PM, Rob Weir wrote: > > [...] There should be a way that we can more clearly identify [...] who > knows how to do [...], who wants to learn how to [...], and who is willing > to mentor or teach others how to get > started. > > So I've started the following wiki page to track some of the most > common tasks in the project: > > https://cwiki.apache.org/confluence/display/OOOUSERS/Skills,+Resources+and+Mentors > > Feel free to insert additional tasks, or to add your name as an > expert, mentor or someone who wants to learn. > Rob, nice idea (somewhat overlaps the existing Directory of Volunteers page), But I couldn't edit the wiki page (I'm logged in to as Talchu). Tal
Skills, Resources and Mentors
This projects depends on volunteer efforts. We have many routine tasks that need to be performed during a release cycle and even during ordinarily operation of our website and other public-facing services. In many cases a given task is well-understood and many members of the project understand how to do it. For example, moderating the mailing lists. In other areas we might only have a single person who really understands how to do a task. We also have many volunteers, signing up on the mailing list and asking how to help, on nearly a daily basis. There should be a way that we can more clearly identify what the routine tasks are, who knows how to do them, who wants to learn how to do them, and who is willing to mentor or teach others how to get started. So I've started the following wiki page to track some of the most common tasks in the project: https://cwiki.apache.org/confluence/display/OOOUSERS/Skills,+Resources+and+Mentors Feel free to insert additional tasks, or to add your name as an expert, mentor or someone who wants to learn. (Of course there are many other routine tasks performed by Apache Infra and not listed here. I'm focused on the tasks that are owned by the AOO project) This might also help is identify areas where we are currently dependent on a single person and want to train a backup, to cover for holidays, etc. Regards, -Rob - To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org For additional commands, e-mail: qa-h...@openoffice.apache.org
Re: AOO 4 unusable under Linux64?
In subsequent checks I installed the deb (not arc!) package using dpkg -i *.deb On Mon, Sep 30, 2013, at 12:05, Herbert Duerr wrote: > On 29.09.2013 21:12, Edwin Sharp wrote: > > [...] > > Not sure what is meant by Crash bug, but here is relevant information: > > Current distribution I use: http://www.aptosid.com/ > > A great distribution, I use that too! > > > AOO was installed from arc file of the Buildbots. > > Ah, that's the reason. Linux has a different development philosophy than > most other platforms. On other platforms you tell the compiler to target > a specific baseline (e.g. OSX 10.4 or Windows XP). On Linux the > philosophy used to be "just recompile if any of the libraries changed > its APIs" or "update from your system's specific package repository > where one of the maintainers did that for you". Things have gotten much > better since but selecting a target API is still not easily possible. > > So to solve this for our releases we use the "greatest common > denominator" approach on Linux: Linux nowadays tries not to break older > binaries, so we're using a very old system for building the packages. A > system old enough that most current systems can work with it. > > These ancient systems are how we build our releases and release snapshots. > > Now the Linux64 buildbot uses Ubuntu 10.4 and the Linux32 buildbot runs > on Ubuntu 12.4. These systems are quite new and their new compilers are > much better than what is provided by the "greatest common denominator " > systems, which enables them to find and report important bugs. The > drawback is that unless your system is a descendant of these newer Linux > systems the builds they create are unusable for you. > > I suggest to check the official release candidate snapshots if we're in > the release phase. They have the maximum binary compatibility. > > If you want to check the latest experimental trunk releases created by > buildbots running new distributions I suggest to install that same > distribution or one of its descendants. > > Herbert > > - > To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org > For additional commands, e-mail: qa-h...@openoffice.apache.org > - To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org For additional commands, e-mail: qa-h...@openoffice.apache.org
Re: AOO 4 unusable under Linux64?
On 29.09.2013 21:12, Edwin Sharp wrote: [...] Not sure what is meant by Crash bug, but here is relevant information: Current distribution I use: http://www.aptosid.com/ A great distribution, I use that too! AOO was installed from arc file of the Buildbots. Ah, that's the reason. Linux has a different development philosophy than most other platforms. On other platforms you tell the compiler to target a specific baseline (e.g. OSX 10.4 or Windows XP). On Linux the philosophy used to be "just recompile if any of the libraries changed its APIs" or "update from your system's specific package repository where one of the maintainers did that for you". Things have gotten much better since but selecting a target API is still not easily possible. So to solve this for our releases we use the "greatest common denominator" approach on Linux: Linux nowadays tries not to break older binaries, so we're using a very old system for building the packages. A system old enough that most current systems can work with it. These ancient systems are how we build our releases and release snapshots. Now the Linux64 buildbot uses Ubuntu 10.4 and the Linux32 buildbot runs on Ubuntu 12.4. These systems are quite new and their new compilers are much better than what is provided by the "greatest common denominator " systems, which enables them to find and report important bugs. The drawback is that unless your system is a descendant of these newer Linux systems the builds they create are unusable for you. I suggest to check the official release candidate snapshots if we're in the release phase. They have the maximum binary compatibility. If you want to check the latest experimental trunk releases created by buildbots running new distributions I suggest to install that same distribution or one of its descendants. Herbert - To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org For additional commands, e-mail: qa-h...@openoffice.apache.org