BeeSeek Blog

It isn't a movie title, but the people who will make the immediate future of BeeSeek: we are looking for debuggers.
After the bug 172810 will be fixed, as the developer Andrea Corbellini says, will begin the debugging period of Hive.

To become a protagonist:

- read the Community page
- subscribe the Developers' mailing list

You can find all the help pages about bug-hunting on the wiki:

- bug triaging
- debugging

Good luck!

andrea-bs, developers team leader, recently decided to modify the structure of the team to favor a division in two separate entities, Core Developers and Quality Assurance.

The two team will have the following goals:

BeeSeek Core Developers (beeseek-core-devs on Launchpad): will improve and develop every beeseek application, being able to autonomously upload code and check security bugs.

BeeSeek Quality Assurance (beeseek-core-bugs on Launchpad): must track down bugs, giving them priority and changing their status accordingly to fixes and contributions. Still, they don't have access to security bugs, like the Core Developers do.

N.B. Both teams are moderated by the Developers Team.

For more informations, you can look at Launchpad pages, and the wiki webpage dedicated to the Developers Team.

Translated by Ubuntista

Today, we have opened a number of Mailing Lists dedicated to announcement, general discussions about BeeSeek and 5 more lists, one for each Team involved in the project development.

A dedicated wiki page describes any details about the new mailing lists. We recommend that you subscribe at least the BeeSeek Announcement List, so you can keep in touch with breaking news regarding the developement of the project.

Also, you are probably interested in this general discussion mailing list, where your ideas can be discussed and shared among everyone interested in the BeeSeek project.