Archive for the ‘Uncategorized’ category

Contribute to OpenOffice QA Team

March 8, 2010

How to start…
Contributing is easy as 1,2,3!

Welcome to the Quality Assurance of OpenOffice.org!

Contributing and helping in a large project like OOo is simpler than you think…. The first thing is to register as an Openoffice.org user. You can do so on the Register page.
Supporting the Quality Assurance of OpenOffice.org is graduated in 3 Participation Steps:

  1. The first participation step (““Report bugs”) is meant for newbies to acquire general knowledge about issues in common. Participants on the first stage are able to find and write issues themselves. The link holds all the information you need to know for starting to contribute.
  2. The second step (“Manual testing”) is meant for participants with more skills. You are able to do manual testing on your own. You can execute and write Test-Case-Specifications (TCS) and submit issues found when dealing with Test-Case-Specifications.
    The page contains all information needed to contribute to the second participation step.
  3. In the third participation step (“Join QA”) you can apply to join the QA Team of OOo at one of the “OOoQA-Teamleads”. You have now collected enough knowledge about issue handling to confirm issues and close them by yourself. Having reached this stage of participation brings a lot of advantages: you have direct contact to the StarOffice/Openoffice.org developers and Quality Assurance engineers, you will get listed as a direct member of the OpenOffice.org Quality Assurance Team, you will be able to send own issue right to the responsible engineer, you get direct responsibility, more rights (like “canconfirm”) and more weight in decisions.

Advertisements

DFD 2010: Free your documents, save your information!

March 8, 2010

Will you be able to read your documents 20 years from now? Every day, millions of computer users like you edit text and spreadsheets, take pictures and record audio and video. What if you couldn’t read your private letters anymore, or even open that album with pictures from your honeymoon? What if you couldn’t exchange those files with friends, because the software used by each one of you can’t talk to each other? To help you make your documents future-proof, we celebrate Document Freedom Day on March 31.

Any person can save documents in open document formats, which are based on Open Standards, and be sure that people will be able to read those files, independently of the software they use. Anyone can build applications that read and write files in these formats. The Internet was built upon Open Standards, and that’s why you see so much innovation online.

On Document Freedom Day, we will raise awareness for Open Document Formats and Open Standards by organizing activities all over the world together with partner organizations and volunteers.

During the whole month of March, we will spread the word on open document formats and Open Standards. We will publish information, talk to the press, tell our friends about it, and spread the DFD logo all over the Internet.

There are many ways to take part on this campaign, so pick one and join us:

  • Put a banner in your website, linking to DFD website. You can find banners in our Artwork Website.
  • Publish a blog post on Document Freedom Day, or Open Standards, and spread the word about the campaign. Send us      a link, and we’ll include it in the DFD website.
  • Use your microblog to spread DFD news and articles! Tag them using !dfd or #dfd2010
  • Organize an activity in your city on March 31st. For ideas on activities, check the Document Freedom Day website.
  • Donate money to DFD. Your contribution makes Document Freedom Day possible!
  • Become a partner organization. Contact our Campaign Team on how to do that.

Want to find out more about Open Standards?

Document Freedom Day is about helping you to really own your data. You shouldn’t be tied to particular applications for living your life in the digital world, and you shouldn’t have to use any specific software to deal with your government, your school or anyone else.

For more information on Document Freedom Day, visit our website: www.documentfreedom.org

Contact:

Fernanda Weiden
DFD Campaign Coordinator
Email: weiden -at- fsfeurope.org
Tel:   +41 76 4021866

Bookmark and Share

Ubuntu Manual Project To Do List

March 3, 2010



Getting Started with Ubuntu 10.04 is a complete beginners manual for Ubuntu, featuring comprehensive guides, How Tos and information on anything you need to know after first installing Ubuntu.

Designed to be as user-friendly and easy to follow as possible, it should provide the first point of reference to any Ubuntu newcomer with lots of information in one easy to access PDF file. Plus, every six months there will be a new revision released to coincide with each new release of Ubuntu.

The manual is written and maintained by the Ubuntu Manual Team.

We need your contribution.

THE TOP FIVE THINGS WE NEED

1. More authors for Chapter 4, 6, 9 and 10
2. Python developers for Quickshot*
3. Editors for the entire manual
4. Translators**
5. Web developers (look in /website in the branch)

Think you can help with any of these or anything below? Join #ubuntu-manual on irc.freenode.net and away you go.

Read more at:

http://pad.ubuntu-uk.org/aA6ygCXL9F

Thanks.

https://wiki.ubuntu.com/ubuntu-manual/

https://wiki.ubuntu.com/ubuntu-manual/contributions

Get involved with Nagios!

March 1, 2010

Nagios® is a system and network monitoring application. It watches hosts and services that you specify, alerting you when things go bad and when they get better.

Getting Involved

The Nagios project is looking for new people to get involved and help out the project in various ways. We’re looking for you!

Here’s how you can help:

  1. Check out the list of “open positions” (below) the project is looking to fill
  2. If you’d like to help out or claim an open position…
    1. edit the section and add your name and email address so others can see you want to be involved
    2. Send an email to contribute@nagios.org
    3. We’ll get back to you with details on next steps for the role you’d like to fill

Currently Open Positions

Nagios GUI Team

The Nagios Gui team is looking for:

  • PHP developers with experience on object oriented php development using the mvc paradigm. You need to have experience with modern web technologies such as ajax as well. An extra plus is if you have experience with the Kohana framework.
  • Translaters. Do you want Nagios in French, Swedish or perhaps simplified Chinese, go a head. Ninja uses gettext for multilingual support.

It’s also good if you have experience or are willing to put effort into testing. We really need your help here!

Jeffrey Negro – jnegro1176@gmail.com

Nagios Binary Builds

We’d like to add community-contributed binary builds of Nagios, the Nagios plugins, and various Nagios addons to the Nagios downloads page. If you’ve got access to one of the following systems, and would like to participate, please do! The Nagios developers don’t have direct access to these systems, so we require your assistance to deliver these to the community. Here’s a list of systems we’d like to have binaries created for:

  1. AIX
  2. Solaris
  3. Irix
  4. HP-UX

We’ll give participants an easy method to upload daily binary builds to Nagios Exchange. NOTE: It probably makes the most sense to have people who contribute in the Tinderbox setup (see below) auto-upload their compiled binaries.

Want to contribute? Add your name and contact details here, along with the operating systems you’d be interested in building binaries for.

Edit Guntram Blohm: I can provide some Irix work (Irix 6.5.22, with gcc). I already compiled nrpe and most of the plugins, and i’m in the process of getting the core to run. After that i’ll try to make tardist files of everything, and then i’ll be ready to upload and submit patches. I might be able to get tinderbox running as well, but that depends on how new the perl needs to be.

2nd Edit Guntram Blohm: Unfortunately, i didn’t get a reply to my mail to contribute@nagios.org yet. Still, i have working versions of nagios, plugins, and nrpe for IRIX, that you can download at http://www.guntram.de/nagios/nagios.html. Still interested in making this “official” if any of the nagios developers reads this. — nagios1@guntram.de

Nagios RPMs/Packages

We’d like to provide up-to-date RPMs and packages of Nagios, the Nagios Plugins, and Nagios addons. Many Linux distros (e.g. Debian) provide packages, but the version shipped with the distros often lag when compared to the most current versions available. We’d like to work with community members who are interested in automatically generating RPMs and packages on a daily basis. This will make installing the latest version of Nagios easy for new users – a definite must!

We’ll give participants an easy method to upload daily package builds to Nagios Exchange.

Want to contribute? Add your name and contact details here, along with the operating systems/distributions you’d like to create/build packages for.

If you are a current port/package maintainer, please get in touch with Ethan at egalstad at nagios.org to join a special mailing list to coordinate things and share ideas.

Tinderbox Clients

We’re in the process of building a new Nagios Tinderbox server at tinderbox.nagios.org. The Nagios Tinderbox server will allow developers to see how Nagios, the Nagios plugins, and various Nagios addons compile under different operating systems and distributions. We need all types of systems for running these tests, so if you’ve got some spare CPU cycles, please consider getting involved.

We’re looking for people with the following systems to volunteer to participate:

  1. AIX
  2. HP-UX
  3. Solaris
  4. Irix
  5. RHEL
  6. SuSE
  7. Fedora
  8. CentOS
  9. Ubuntu Server
  10. Ubuntu Desktop
  11. Debian
  12. FreeBSD
  13. OpenBSD
  14. NetBSD

NOTE: It probably makes the most sense to have people who contribute in the Tinderbox setup to auto-upload their (successfully) compiled binaries, so we have OS/distro-specific binaries that are available for the community to download (read further up the page for information on this).

Want to contribute? Add your name and contact details here, along with the operating systems/distributions you can add to the Tinderbox tests.

Performance Testing

It would be nice to have a team of people that coordinated efforts for Nagios performance testing. Many users ask “How many services/hosts can I monitor with Nagios on this ACME server?” The answer depends on things like: check interval, types of checks (Perl, SSH, etc.), network bandwidth, whether graphing/trending is used, DB backends, etc.

Ideally, a set of performance test scripts could be developed that would allow anyone to run the tests on their local box. In the short term, they could report their findings on the Wiki somewhere. In the long run, it would be nice to have a facility available to auto-report the findings to DB on api.nagios.org, so they could automatically be published for everyone to see.

Interested in helping with performance testing? Add your name and contact details here, along with the operating systems you’d be interested in building binaries for.

For more details,  

http://wiki.nagios.org/index.php/Get_Involved

Server Bug Zapping – Call for Participation

March 1, 2010

In October 2009, just before the release of Ubuntu 9.10 (Karmic),
Mathias Gug, Dan Nurmi, and I holed up for a couple of very long days,
working on the Ubuntu Eucalyptus package. Over the course of 72 hours,
we uploaded Eucalyptus 7 times, fixing over 30 bugs! While Mathias, Dan,
and I were co-located, we were also greatly assisted by Thierry Carrez
(located +7 hours ahead) and community member Joseph Salisbury. Thierry
and Joe helped tremendously with regression testing of the rapid fire
uploads, triaging and squashing any new issues as they arose. This
“push” was essential to delivering UEC for Ubuntu 9.10!

Well, the Server Team is going to do it again, for Ubuntu 10.04, and
covering several other important server packages in addition to
Eucalyptus, and we’re hoping to get your help this time!

We’re calling this effort Server Bug Zapping. The schedule and plans are
detailed here: https://wiki.ubuntu.com/ServerLucidBugZapping

http://blog.dustinkirkland.com/2010/02/server-bug-zapping-call-for.html

Translating software descriptions with Nightmonkey

March 1, 2010

Nightmonkey:
http://go2.wordpress.com/?id=725X1342&site=davidplanella.wordpress.com&url=http%3A%2F%2Fnightmonkey.ubuntu.hu%2F

What’s this?

Nightmonkey is a project created and driven by the Ubuntu Hungarian team
to allow an easier translation of the descriptions of packages, with
István Nyitrai as the main developer and rockstar.

These are the short and long texts used to describe what a particular
software package does. They are shown in different places in the system,
most notably on Software Center when you are looking at an application’s
info page.
Why is this so cool?

For multiple reasons. Let me just mention a few:

* It’s a community project around translations, providing an alternative
view to translatable packages in Launchpad. This makes them more
discoverable and eases the translation process.
* It was designed with upstream collaboration in mind. István and
Michael Vogt made a great effort to ensure these translations can be
sent back to Debian.
* It’s very easy to use, and it allows filtering translations according
to popularity, so that translators can focus their work on the
descriptions of most important applications.
* It is a great tool for teams to set translation goals and use it for
Translation Jams, for example.

Can you contribute to it?

Well of course!, Nightmonkey is Open Source, and you can:

* Translate it: https://translations.launchpad.net/ddtp-lp-html
* Improve it: https://code.launchpad.net/ddtp-lp-html
* Report bugs: https://bugs.launchpad.net/ddtp-lp-html
* Ask and answer questions: https://answers.launchpad.net/ddtp-lp-html

http://davidplanella.wordpress.com/2010/02/26/translating-software-descriptions-with-nightmonkey/

Help localization testing with the ISO tracker

March 1, 2010

The Ubuntu Testing Team is currently testing Lucid Alpha 3 candidate images.

* Testing Team Wiki: https://wiki.ubuntu.com/Testing
* Testing Lucid Alpha 3 images

This cycle we have a brand new set of localization test cases for
everyone to check and make sure language support in Lucid is top notch,
and we need your help!

Here’s how you can contribute; the procedure for testing is very easy,
and it involves:

* Signing up – create an account at the ISO testing tracker and log in
* Running the test cases – run the localization test cases following the
given steps
* Reporting – report on them (pass/fail, comments, bugs, etc.)

If you are interested in helping out, please visit the link below for
in-depth instructions on how to set up your own testing tracker.

http://davidplanella.wordpress.com/2010/02/24/help-localization-testing-with-the-iso-tracker/