- Inkscape Devel - Inkscape Mailman

Fwd: Elisa moves to bzr
by Bryce Harrington 01 Apr '08

01 Apr '08

Interesting post from one project recently moved to bzr. Bryce ----- Forwarded message from Loïc Minier <loic.minier@...1798...> ----- Date: Tue, 01 Apr 2008 17:27:05 +0200 From: Florian Boucault <florian@...693...> To: elisa <elisa@...1936...> Subject: [Elisa] Elisa organisation changes X-Spam-Status: No, score=-0.3 required=5.0 tests=AWL,BAYES_50 autolearn=disabled version=3.1.3 Hello Eliseros, After careful thinking, the Elisa team has decided to move over to Bazaar for version control and to Launchpad for bug tracking and release management. ** Why the move? ** The Elisa project is all about people making their own customised media center that fits their own particular needs. This is the rationale behind its fully pluggable architecture. In order to allow a similar flexibility for developers, it made complete sense to use a distributed version control system (DVCS). The choice between the myriad of existing DVCSes was driven by a simplicity of use enabling easy contribution and flexibility to adapt to any possible workflow we may need in the future. For all these reasons Elisa's source code, which was previously versioned using Subversion, is from now on stored in Bazaar branches. Bazaar is well documented and has nice tutorials help people get started such as this one: http://doc.bazaar-vcs.org/bzr.dev/en/mini-tutorial/index.html Obviously a full move to a decentralised working style meant that a good tool was needed to keep track of what is going on in the branches, bugs wise and also features wise. After some experiments with various tools that could have done the job, Launchpad proved to cover the use cases well and enable the kind of collaboration we all want to encourage. ** Teams and their purpose ** We are going to setup 2 launchpad teams. The first team, called elisa-developers, will be opened to all the developers that have read and signed the Fluendo copyright assignment document. Everyone will be able to branch bazaar branches registered by the elisa-developers team, but only the members will have write access to them. The second team, called elisa-contributors, will be open to everyone. Every member will have write access to the branches under the team. This team will make it easy for groups of developers to work together on their branches whenever and however they want to. ** Contribution processes ** Code ---- The first thing needed to start hacking on Elisa is a branch of an existing branch. The main development branch is at: http://bazaar.launchpad.net/~elisa-developers/elisa/main We never push directly to the main branch as we want all the changes to be reviewed first. When a developer wants some code to be committed, he sends a merge request to the elisa-commits@...1936... mailing list by using the bzr send command, which is documented here: http://doc.bazaar-vcs.org/latest/en/user-guide/index.html#sending-changes On the mailing list the changes are reviewed by one or more developers and, once they have been approved, they are merged into the main branch. The merging procedure varies depending on which bundle the changed code belongs. Changes to core, -base, -good, and -ugly have to be reviewed by at least two developers, changes to -bad by at least one developer. The last reviewer merges the changes back into the branch. We will setup a Bundle Buggy instance to track the merge requests and the reviews. The voting system used by Bundle Buggy is defined here: http://bundlebuggy.aaronbentley.com/help Bug reports ----------- Bug reports are stored in Launchpad which allows a per branch fine tracking of bugs. There is nothing really new here apart from the ability to have cross projects bug which will prove fairly useful in Elisa's case since it depends on many other libraries (eg. Pigment, GStreamer, etc.). Specifications -------------- Task specifications for new features will be centralised in one place in the upcoming Elisa's wiki and tracked in Launchpad blueprints allowing a quick and easy overview of all the current work being done and the various branches related to them. A quick task definition is written in Launchpad blueprints itself whereas more detailed information will be stored in Elisa's wiki and will contain: summary, rationale, use cases, implementation plan and whatever is necessary to communicate around the task. That's it for now. Thank you for reading so far. Hopefully all these changes and decisions will help make Elisa go forward by allowing everyone to collaborate as painlessly as possible. If there are any questions please do not hesitate to ask. The Elisa team ** Bundles policies ** Elisa's plugins are sorted into bundles depending on various criteria such as quality, dependencies, licensing, etc. Currently 4 bundles exist: base, good, bad and ugly. The policy is heavily based on GStreamer's (http://gstreamer.freedesktop.org/documentation/splitup.html) Base ---- - Must be of good code quality and fully functional - Must be well-tested (unittests, good code coverage, etc.) - Must comply with Elisa dual license model or be under MIT or a BSD license - Cannot depend on external libraries that Elisa core does not depend on Good ---- - Must be of good code quality and fully functional - Must be well-tested (unittests, good code coverage, etc.) - Must comply with Elisa dual license model or be under MIT or a BSD license Bad --- - Bad quality code (coding style not respected, etc.) - Not very well tested, not mature - Must comply with Elisa dual license model or be under MIT or a BSD license - Might have potential legal issues Ugly ---- - Must be of good code quality and fully functional - Must be well-tested (unittests, good code coverage, etc.) - Not complying with Elisa dual license model (eg. can be GPL only) - Might have potential legal issues -- warthogs mailing list warthogs@...1799... https://lists.ubuntu.com/mailman/listinfo/warthogs ----- End forwarded message -----

1 0

Adobe Mars
by Tobias Jakobs 01 Apr '08

01 Apr '08

Hi, I just read about Adobe Mars[1] and thought it is interesting for some of the developers here. [1] http://labs.adobe.com/wiki/index.php/Mars Here a copy from the homepage: "Mars is the code name for technology being developed by Adobe that provides an Extensible Markup Language (XML)-based representation of Portable Document Format (PDF) documents. Adobe(R) PDF is a universal file format for representing documents in a manner independent of the application software, hardware, and operating system used to create them and of the output device on which they are to be displayed or printed. XML is a cross-platform, extensible, and text-based standard for representing data that was created so that richly structured documents could be used over the web. The Mars Project is an XML friendly representation of PDF documents. Already an open specification, PDF is the global standard for trusted, high fidelity electronic documentation. The Mars file format incorporates additional standards such as SVG, PNG, JPG, JPG2000, OpenType, Xpath and XML into a ZIP-based document container. The Mars plug-ins for Acrobat 8 and Adobe Reader 8 enable creation and recognition of the Mars file format by Adobe Acrobat 8 and Adobe Reader 8 software. For additional Mars information see the documents below and check back for regular updates. The Mars Project is early release software and we welcome your feedback. Please use the feedback link below to request features, make comments and report problems. Please understand that this is an early release and is not yet feature complete. The file format contained within the Mars plug-ins is subject to change and using this technology for production may require you to make significant changes to your documents at a later date. Content created with this release may not be compatible with the shipping version." Regards, Tobias

3 3

Where is lxml?
by Brian Vanderburg II 01 Apr '08

01 Apr '08

Just a question about the windows release. I know on Linux, normally only the main files would be included and any dependencies would be managed by the package manager. But for windows, since the Inkscape installer includes everything else (GTK binaries, Python binaries, etc), why not go ahead and include lxml in the release. Otherwise the many of the scripts won't run and some users may have a time figuring out why or how to download it. Brian Vanderburg II

2 1

Inkscape 0.46 Announced on DeviantART
by Josh Andler 01 Apr '08

01 Apr '08

The announcement was posted here: http://news.deviantart.com/article/45610/ If you have a DeviantART account, please log in, visit that link, and show the article some love with the digg-like heart thingy. ;) Congrats to everyone! Win32 devs and testers, a huge kudos to you all for pulling things together in such short order (given the severity of some issues)! Cheers, Josh

2 1

Inkscape 0.46 save bug (I think)
by Donn 01 Apr '08

01 Apr '08

Hi, I fetched the (stable 0.46) source and compiled on Kubuntu Gutsy two days ago. In playing around I noticed that when you save your file it does not append the .svg to the filename, even if "inkscape svg" is chosen in the types combo. You can do it manually, however. I could be doing something dumb, but thought I'd mention it. \d

2 2

GSoC and Text
by Gail Carmichael 01 Apr '08

01 Apr '08

8 16

Re: [Inkscape-devel] [Inkscape-user] Snapping (WAS: GSOC 2008 / Technical Drawing in Inkscape)
by Diederik van Lierop 31 Mar '08

31 Mar '08

1 0

[GSoC2008] deadline extension
by Alexandre Prokoudine 31 Mar '08

31 Mar '08

Hi, Deadline for student applications submission is officially extended by one week. The new deadline for student applications is Monday, April 7, 2008. Timeline in FAQ is updated. Alexandre

2 1

problems in libgdl
by Jon A. Cruz 31 Mar '08

31 Mar '08

For the docking... I've seen these warnings, some of which might be significant. If anyone can give them a look, that would be helpful libgdl/gdl-dock-object.c:99: warning: unused parameter 'data' libgdl/gdl-dock-object.c: In function 'gdl_dock_object_get_type': libgdl/gdl-dock-object.c:99: warning: missing initializer libgdl/gdl-dock-object.c:99: warning: (near initialization for 'object_info.value_table') libgdl/gdl-dock-object.c: In function 'gdl_dock_param_get_type': libgdl/gdl-dock-object.c:833: warning: missing initializer libgdl/gdl-dock-object.c:833: warning: (near initialization for 'tinfo.base_init') libgdl/gdl-dock-master.c: In function 'gdl_dock_master_get_type': libgdl/gdl-dock-master.c:129: warning: missing initializer libgdl/gdl-dock-master.c:129: warning: (near initialization for 'object_info.value_table') (several more of those) libgdl/gdl-dock-item.c:276: warning: assignment from incompatible pointer type libgdl/gdl-dock.c: In function 'gdl_dock_dock_request': libgdl/gdl-dock.c:847: warning: comparison between signed and unsigned libgdl/gdl-dock.c:850: warning: comparison between signed and unsigned libgdl/gdl-dock.c:854: warning: comparison between signed and unsigned libgdl/gdl-dock.c:857: warning: comparison between signed and unsigned libgdl/gdl-dock-item-grip.c: In function 'gdl_dock_item_grip_expose': libgdl/gdl-dock-item-grip.c:147: warning: assignment from incompatible pointer type libgdl/gdl-dock-item-grip.c:150: warning: passing argument 2 of 'gdk_draw_rectangle' from incompatible pointer type libgdl/gdl-dock-item-grip.c:138: warning: unused variable 'item_or_child_has_focus' libgdl/gdl-dock-paned.c:568: warning: comparison between signed and unsigned libgdl/gdl-dock-paned.c:573: warning: comparison between signed and unsigned libgdl/gdl-dock-paned.c:577: warning: comparison between signed and unsigned

4 4

Joining the task force?
by Tali Gutman 31 Mar '08

31 Mar '08

Hi everybody, Thought I'd join in to the party this summer. I want to fix the pdf-exports-with-opacities bug, but I can do some other stuff too :) (In other words, this is just "Hello". Will get the code in the weekend maybe :) ) -- - Tali

1 0