We're undergoing maintenance
We’re releasing a major feature that changes the way we handle billing and project.
We will have a planned downtime of 30-45 minutes, and be back with the new release.
We’re releasing a major feature that changes the way we handle billing and project.
We will have a planned downtime of 30-45 minutes, and be back with the new release.
One year ago Why, the Lucky Stiff left the Ruby community, deleting all his blogs and open-source repositories.
He left great pieces of code and the most amazing programming guide you ever read (which is incidentally now hosted by Mislav, who’s part of our team).
Teambox being a Ruby project, we couldn’t let this day pass by without remembering:
@_why: When you don’t create things, you become defined by your tastes. Your tastes only narrow & exclude people, so create.
Lots of chunky bacon for all the creative hackers out there, who make programming more fun every day.
Many of you, coming from bigger organizations, have asked for a better role management system.
Currently, we’ve been allowing users to create their own projects and invite whoever is involved with them. While this was very simple, it’s not flexible enough for larger groups.
That’s why we’re now very close to release organizations. This will allow you to create all your projects inside an organization, and making other users admins of the organization as well. Any admin or participant can create projects inside the organization, and you can have external workers as well.
The feature will be live during the next week. We’re all looking forward to it!
This is how you’ll be able to manage permissions inside an organization:
And this is how you can manage your organizations:
We keep improving and experimenting with Teambox features. While many times the changes are small and hard to notice, other times changes are more radical.
This is why we’re now adding an opt-in feature to preview new features. To activate this, go to your Settings and mark the checkbox “use beta features”.
We’re now experimenting with more compact navigation bar, as you can see here:
We’d love you to use it and send us your feedback!
Some days ago we decided to remove the conversations tab, in favor of a simpler interface. “Now that Teambox has threaded comments”, we said, “conversations are legacy”.
This was a big mistake.
It turns out that users interact with their projects in two modes:
When we removed the conversations tab, we were grossly underestimated how much people valued the structured mode of accessing Teambox. Creating a new conversation, or having a quick reference to past activity, is a strong point, and by removing the tab we had made it very hard to look up conversations.
This is why we brought them back. But we also wanted to take a chance to provide better value: Activity overview (what’s-new mode) and Conversations (reference mode) are radically different concepts. So we tried to re-purpose the conversations area.
This is a before and after comparison. The new design focuses on giving a bird’s eye view of conversations. You’ll find the title and the comment which started the conversation (the context-setter), and below links to view more. In the sidebar, we have an abbreviated list of titles for all conversations.
We tried to draw a visual hierarchy with font sizes and colors, while leaving appropriate margins to differentiate topics.
For the past months, the Teambox community took place on Google Groups. This was a good way to get started, but eventually the community has been growing and we were missing a better mailing list application.
This is why we’re now launching Teambox communities. They are a public mailing list + documentation source + community task management for your projects.
You can turn any of your projects into a community project, and manage it from the familiar Teambox interface.
Here’s how they look like. The screenshot is from our community site:
By making your project public, you get out of the box:
Your projects will be listed on the public communities directory. For an example, visit our official community.
Learn how to create and manage public projects.
It’s an excellent google groups replacement, and we’re very excited about the possibilities. Let us know about how you use this feature!
Now that Teambox has a real API, the possibilities for manipulating Teambox data are endless.
One such example I cooked up recently is a statistics generator.
For those who have used IRC in the past, you may recall the multitude of scripts available that analyze your logs and generate interesting statistics about them.
Borrowing from this general format, the generator analyzes recent activities in a Teambox project. It will tell you such things as:
Really, everything you could ever want to know about your project!
To use it run the script, supplying your username, password, and the project you want to examine. e.g.:
ruby teamboxstats.rb -u fred -p password teambox
This will login and dump the teambox project if you have access to it.
For those interested, the script is open-source and is available on github!
Stay in touch
read ourblog contact us follow us
on Twitter