Here's a quick summary of the audio conf we had this evening... Participants were Yen-Ju, Jesse, David, Quentin and me.
1/ We'll use a stable branch + trunk As a developer, you put the code you think is stable in it. Basically you put your code in trunk as currently, but when you have a version that you think is stable enough, you copy it in the stable branch. Users can then check that branch, not trunk, if they want a (hopefully) working release of étoilé :-) That way, users can safely report bugs against the stable branch, while not bothering developers with the trunk branch, which by definition is bleeding edge (as in, you'll cut yourself). For releases, it's also much easier for us -- we just need to copy the current stable code to a specific branch for the release (as the code in stable is supposed to work). 2/ Stable components that will go into that branch Bundles/Camaelon Bundles/EtoileBehavior Bundles/EtoileWildMenus Languages/Io Frameworks/AddressesKit Frameworks/PaneKit Frameworks/BookmarkKit Frameworks/CollectionKit Frameworks/RSSKit Frameworks/PopplerKit Frameworks/UnitKit Frameworks/OgreKit Frameworks/XWindowServerKit Frameworks/DistributedView Frameworks/OPMLKit Frameworks/EtoileFoundation Frameworks/EtoileUI Services/Private/MenuServer Services/Private/Azalea Services/Private/System Services/User/AddressManager Services/User/Grr Services/User/Calc Services/User/Typewriter Services/User/Vindaloo Services/User/DictionaryReader 3/ Other applications to be included on the livecd EasyDiff: yes, but we need to test it GNUMail: yes GWorkspace: yes, but only for the GNUstep desktop DBModeler: yes, need to test it too, and ideally provide a tutorial ProjectManager: yes. We won't include ProjectCenter. Cenon: yes Cynthiune: yes Affiche: yes As a rule of thumb... we want to focus on small cooperating applications. Cenon or GWorkspace should probably not be on the live cd in the future, or at least not for the étoilé account. We don't want to duplicate the GNUstep live cd and our goal is not to include all the available gnustep apps; on the other hand, for the moment it's nearly no extra-work, so we can just as well include some of the "big" gnustep apps on the livecd, and keep the gnustep account (also because it's a good way of showing differences between a gnustep desktop with gworkspace and étoilé). The live cd is basically (or should be) an example of an "ideal" étoilé installation/desktop/OS. 4/ the race condition bug when using the étoilé account on the livecd: What happens is that System is launching Azalea, then MenuServer, then GWorkspace. It's the intended order. On the livecd, they are launched in paralell; quentin fixed that on svn and now they are launched sequentially. But... Azalea is using NSWorkspace methods at some point -- which in turns will start GWorkspace if it is not started already. Eg, we can have Azalea -> GWorkspace -> MenuServer, which then will confuse GWorkspace on where to display its menu... Solution: we can use defaults write NSGlobalDomain GSWorkspaceApplication NotExist.app so GWorkspace is not started by NSWorkspace. 5/ Space vs GWorkspace Quentin has a prototype for a filemanager, Space, in his branch. Space uses the Io bridge and UKDistributedView. We decided to wait for Quentin to fix the io bridge and commit Space on trunk and use it for the live cd for the étoilé account, as for the live cd we do not need a fully working filemanager -- a simple application launcher / disk browser is enough. Also there's a lot of problems with using GW (see point 4, and the fact that we'd have two competing session management: System and GW...), and... it would be better to start working on our own filemanager after all :) The fact that Space is based on io isn't a problem as we can replace parts of it by Objective-C objects when/if needed, and using io is ideal for prototyping/fast development anyway. Quentin will hopefully write a small tutorial explaining how to replace part of an objc program by io parts and vice-versa. 6/ Desktop/Background/Dock We'll put AZDock and AZBackground on the livecd -- the current version on the svn should solve the bugs we saw at the fosdem. 7/ System will be splitted into a framework and an application, so that other apps can use System services without duplication 8/ Release date for the livecd and planning. We expect to release the 0.2 version for the 1st of May. Quentin hopes to have a working version of the io bridge / space filemanager in a couple of weeks. We'll have another audio conf in 3 weeks to see where we are. ... As a final note, I'll thanks all the participants to this audio conf (hopefully we'll have other devs on board next time), and while it was the first time we tried that, it didn't go too bad I think ;) Next audio conf same time (19hGMT), planned currently for the 8th of april. -- Nicolas Roard "La perfection, ce n'est pas quand il n'y a plus rien à ajouter, c'est quand il n'y a plus rien à retrancher." -- Antoine de St-Exupéry _______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev
