- Tuesdays - 9:00am Pacific, 12:00pm Eastern, 16:00 UTC
- Mozilla Building S
- +1 650 903 0800 x92 Conf# 347 (USA/International)
- +1 416 848 3114 x92 Conf# 347 (Canada)
- +1 800 707 2533 (pin 369) Conf# 347 (US Toll Free)
- #bespin for backchannel
If you can't dial in for some reason, let us know your info so we can try to bridge you in.
Since this is the first call, and this is the first time many people will have "heard" each other, lets go around the room and introduce ourselves, short backgrounds, why we are interested in Bespin, and what we are looking to get out of it!
Then we will get too:
- What is on the radar for the coming quarter, the coming month, and the coming week
- NOTE: April is "usable dogfood" month :)
- Bug update
- Blocker roundup
- Any pet bugs that people are working on / need help with?
- Tree gardening
- How is the tip doing, any pulls outstanding?
- How do we manage the trees, when does it make sense to grant people direct access to the Bespin tip (does it with DVCS?)
- Contributor Page: Please feel like you own your section so you can tweak it out in any way that you wish (link to your blog, add more info, etc).
If you have anything to add to the agenda, please feel free to add it below and put your name next to it!
- Popping out Bugzilla components so we don't need to use the whiteboard for it?
- Using 0.1 branch in repository
- Hasn't been used since 0.1.3
- Can we retro-tag the other 0.1.x versions on it?
The goal of this first meeting was just to touch base, discuss our vision, and get to talk to the various contributors. We started with introductions from around the world (after fun conference call issues)
Ben talked about the goals for 2009
- Captured on Labs/Bespin/Roadmap
- Third party installs
- Open source more productive (e.g. increase contributions to Firefox via Bespin)
- "Most productive and fun way to build Web applications"
- Play around with some rich tool features that integrate with the designer work flow
Dion talked through the detailed roadmap focusing on:
- April goals and the "Usable" theme
- Exciting / Fun Theme
We all talked over some of the issues that we have had with Mercurial. There are a couple of things for us to think about:
- Giving commit access to the public repo
- Is this the right thing to do if we are using DVCS?
- What should the process be for promoting people to use this?
- Putting together a "Mercurial Best Practices Document" on the Wiki on how best to integrate with the Bespin project
- E.g. how we use fetch, how we use our own repo on bitbucket, etc
- Testing Infrastructure
- Need to get feedback from the group on which tools to use
- Julian had a good idea on having a page that shows what you are working on as a contributor so people don't double book
- Gordon asked to see if we are able to get Bespin pulled up a level in Bugzilla so we can use components instead of the white board
- Still working through the process on our end on whether we can do this