Confirmed users
2,595
edits
SeaMonkey/StatusMeetings/2009-10-06: Difference between revisions
SeaMonkey/StatusMeetings/2009-10-06 (view source)
Revision as of 14:06, 6 October 2009
, 6 October 2009→Any other business?
Philip Chee (talk | contribs) (→Ratty) |
Philip Chee (talk | contribs) |
||
| Line 229: | Line 229: | ||
* People need to write some blog posts for the SeaMonkey blog to show off what SM2 features. Mnyromyr needs to write a summary on tabmail anyway, so he can make a blog post from that as well. | * People need to write some blog posts for the SeaMonkey blog to show off what SM2 features. Mnyromyr needs to write a summary on tabmail anyway, so he can make a blog post from that as well. | ||
* Interesting talks with multiple people in Prague about future and esp. KompoZer collaboration/integration. | * Interesting talks with multiple people in Prague about future and esp. KompoZer collaboration/integration. | ||
* KompoZer: | |||
** [KaiRo] Bascially after SeaMonkey 2.0 and KompoZer 0.8 (both expected this/next month), we should do a clone of comm-central+mozilla-central in a user space on hg.m.o and try to get things running there, then merge back either the repository or the patches. | |||
** We also should look into getting some build machines to do at least nightly build cycles. | |||
** Ideally, KaiRo can get machines into the SeaMonkey pool and we might be able to get the builds into the SeaMonkey buildmaster. | |||
** The main issue there is hardware/VMs, but KaiRo needs to talk to Mozilla IT about that topic in any case. | |||
** If KompoZer becomes an official Community Project, that might be simpler. Kaze is working on this at the moment. | |||
* {{Bug|477845}} [Build a standalone (Gecko 1.9.1) Composer]. | |||
** We don't need <tt>MOZ_STANDALONE_COMPOSER</tt>. If we would, we could do it with app-config.mk. For example <tt>--enable-application=editor</tt>. | |||
* The next step is for kaze to get a hg account and doing that comm-central clone to play around with. | |||