Luke Yelavich | 2 May 2010 04:59

http://www.opentts.org)

Greetings all,
I am writing to propose a new external dependency for GNOME. This external dependency will replace the
deprecated gnome-speech module as a desktop agnostic text to speech framework. OpenTTS is a fork of the
speech-dispatcher project, which is an open source text to speech framework. You can see the original
speech-dispatcher website at http://www.freebsoft.org/speechd. The reasons why a fork of
speech-dispatcher was made can be found on the OpenTTS website,  http://www.opentts.org/Frequently-Asked-Questions.

While the OpenTTS project does not currently have any commercial backing, the current community
contributors and project maintainers are an enthusiastic bunch of individuals who wish to see a standard
text-to-speech API and framework for the *nix ecosystem. Use by assistive technologies is our main drive
for a standard, but we also feel that text-to-speech has many other uses for many different people, not
only those with a disability.

We are in talks with Brailcom, the original non-proffit organisation behind the freebsoft and
speech-dispatcher projects, about returning our development focus back to speech-dispatcher.
However with questions still up in the air about a development model that will allow rapid development and
regular releases, the OpenTTS project maintainers do not feel that concensus will be reached any time
soon. Brailcom cannot promise that they will be able to commit much in the way of developer resources to
speech-dispatcher, and still wish for community contributors to make patches available, and Brailcom
developers occasionally reviewing these patches, committing them, and occasionally making releases
of the project. This will hoefully change in the future, however for now, the OpenTTS project maint
 ainers feel that a fork is still the best way forward. We will always be hopeful that OpenTTS development can
be merged back into speech-dispatcher proper.

OpenTTS is yet to see an official tarball release, however you can check out the code in its current form from
git://git.opentts.org/opentts.git. It is currently undergoing heavy development and cleanup, and
may not work properly, however you can test speech-dispatcher to get an idea of what OpenTTS is and how it
works. OpenTTS will likely follow a similar development model to GNOME, in that we will have a stable
release series, and develope new functionality in parallel until the new code is considered mature,
thereby becoming the new stable release. We intend to make our first release within the month, once the
(Continue reading)

Seif Lotfy | 3 May 2010 00:37
Gravatar

Re: Module Proposal: Zeitgeist

Dear GNOMErs,

GNOME Activity Journal is being moved to the GNOME Development Infrastructure...

 However after some heavy discussion within the Zeitgeist team, we decided to keep Zeitgeist in Launchpad, and not move it to the GNOME Development Infrastructure. While Zeitgeist has been developed for GNOME it doesn't heavily depend on any GNOME modules.

 Thus Zeitgeist could also gain adoption outside the GNOME ecosystem if it remains slightly independent, which would only serve to strengthen its reliability and usefulness on the GNOME desktop too.

 Our current workflow and teamwork has adopted perfectly to Launchpad. We don't intend to move to Git now or in the foreseen future, since it will disturb our organizational and development habits.

 So in case Zeitgeist can not be a GNOME module because of its development infrastructure, we hereby withdraw our proposal of Zeitgeist being a GNOME module and propose it as an external dependency for GNOME Activity Journal, so it will always have a close relation to GNOME.

Cheers
Seif

_______________________________________________
desktop-devel-list mailing list
desktop-devel-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Thorsten Prante | 3 May 2010 00:56
Picon

Module Proposal: GNOME Activity Journal

Purpose:

GNOME Activity Journal is not a File Browser but an Activity Browser.

It uses the Zeitgeist Framework to display what you did and introduces a better way of quickly finding the things that you were doing.

 

Target: desktop

 

Dependencies:

Zeitgeist (external)

PyGTK

Python 2.5

Cairo

DBus

Pango

 

Resource usage:

Bug tracker: http://bugs.launchpad.net/gnome-activity-journal

VCS: http://code.launchpad.net/gnome-activity-journal

Releases: http://launchpad.net/gnome-activity-journal/+download

 

We are waiting on GNOME git approval for a new repository at which point all resources will be moved to the GNOME Infrastructure.

 

Adoption:

Packages (at least) for Debian/Ubuntu, Fedora, openSuSE

 

GNOME-ness, community:

GNOME Activity Journal is a pure community effort with the only commercial backing being our last GSoC project and the Zeitgeist Hackfest in Bolzano 2009. Right now, we are 2 core maintainers, 4 developers, and 2 designers. We've striven to be open and visible in our development. This has also led to a steady inflow of new contributors.

 

Other notes:

...

 

Status and future:

The Journal is able to display all events of applications currently supported by Zeitgeist, such as:

- Totem

- gedit

- eog

- Banshee

- Rhythmbox

- Tomboy

- Firefox

- git

- bzr

- Telepathy

- vim

- ... Anything that pushes into Recently Used

We will provide a data-providers setup and management tool with our next release.

 

We are working to solve the performance issues on startup, caused by the amount of data that is being requested over DBus from Zeitgeist. Our next release should provide a proper solution.

 

There is a more detailed plan attached to our 0.3.4 release announcement [1].

 

--

On behalf of the GNOME Activity Journal team,

Thorsten

 

[1] https://lists.launchpad.net/gnome-zeitgeist-users/msg00048.html

_______________________________________________
desktop-devel-list mailing list
desktop-devel-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
daniel g. siegel | 3 May 2010 01:44
Picon

Re: Module Proposal: Zeitgeist

i really feel sorry for that decision, i would have loved to see
zeitgeist as a growing project inside the gnome infrastructure.

furthermore i hope that the gnome community does not loose interest in
this project, even if such a decision makes it harder to track whats
going on.

at last i hope, that you guys at least consider making zeitgeist a
freedesktop.org project.

daniel

On Mo, 2010-05-03 at 00:37 +0200, Seif Lotfy wrote:
> Dear GNOMErs,
> 
> 
> GNOME Activity Journal is being moved to the GNOME Development
> Infrastructure...
> 
> 
>  However after some heavy discussion within the Zeitgeist team, we
> decided to keep Zeitgeist in Launchpad, and not move it to the GNOME
> Development Infrastructure. While Zeitgeist has been developed for
> GNOME it doesn't heavily depend on any GNOME modules.
> 
>  Thus Zeitgeist could also gain adoption outside the GNOME ecosystem
> if it remains slightly independent, which would only serve to
> strengthen its reliability and usefulness on the GNOME desktop too.
> 
> 
>  Our current workflow and teamwork has adopted perfectly to Launchpad.
> We don't intend to move to Git now or in the foreseen future, since it
> will disturb our organizational and development habits.
> 
> 
>  So in case Zeitgeist can not be a GNOME module because of its
> development infrastructure, we hereby withdraw our proposal of
> Zeitgeist being a GNOME module and propose it as an external
> dependency for GNOME Activity Journal, so it will always have a close
> relation to GNOME.
> 
> 
> Cheers
> Seif
> 
> 
> _______________________________________________
> desktop-devel-list mailing list
> desktop-devel-list <at> gnome.org
> http://mail.gnome.org/mailman/listinfo/desktop-devel-list

--

-- 
this mail was sent using 100% recycled electrons
================================================
daniel g. siegel <dgsiegel <at> gnome.org>
http://home.cs.tum.edu/~siegel
gnupg key id: 0x6EEC9E62
fingerprint: DE5B 1F64 9034 1FB6 E120 DE10 268D AFD5 6EEC 9E62
encrypted email preferred
_______________________________________________
desktop-devel-list mailing list
desktop-devel-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
jhs | 3 May 2010 09:26
Picon

Re: Module Proposal: Zeitgeist

Hi!

> i really feel sorry for that decision, i would have loved to see
> zeitgeist as a growing project inside the gnome infrastructure.
>
> furthermore i hope that the gnome community does not loose interest in
> this project, even if such a decision makes it harder to track whats
> going on.
>
> at last i hope, that you guys at least consider making zeitgeist a
> freedesktop.org project.

Couldn't agree more with Daniel...

Johannes
Milan Bouchet-Valat | 3 May 2010 14:14
Picon

Re: Module Proposal: Zeitgeist

Le lundi 03 mai 2010 à 00:37 +0200, Seif Lotfy a écrit :

<snip>
> So in case Zeitgeist can not be a GNOME module because of its
> development infrastructure, we hereby withdraw our proposal of
> Zeitgeist being a GNOME module and propose it as an external
> dependency for GNOME Activity Journal, so it will always have a close
> relation to GNOME.
Sounds a sane solution to me, since you seem to head towards KDE support
too.

Though, having a git clone repository somewhere would be nice for people
willing to help on both sides. It's likely that GNOME contributors will
want to improve the engine, and not only the GUI. What about a clone on
git.gnome.org, just like the system-tools-backends-clone one? Would
there be a way in Launchpad to merge git branches by importing them to
bzr?

Regards

_______________________________________________
desktop-devel-list mailing list
desktop-devel-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Andre Klapper | 3 May 2010 22:15
Picon

GNOME 2.31.1 stable tarballs due

Looks like we missed to send out a reminder but better late than
never. :-/

Tarballs are due on 2010-05-03 before 23:59 UTC for the GNOME 2.31.1
unstable release, which will be delivered on Wednesday.

Having your tarballs uploaded before Monday 23:59 UTC is welcome though
this might be a bit unrealistic now.
Hence a bit later is most probably welcome too.

For more information about 2.31, the full schedule, the official
module lists and the proposed module lists, please see our colorful 2.31
page:
   http://www.gnome.org/start/unstable

For a quick overview of the GNOME schedule, please see:
   http://live.gnome.org/Schedule

andre
-- 
 mailto:ak-47 <at> gmx.net | failed
 http://www.iomc.de/  | http://blogs.gnome.org/aklapper

--

-- 
devel-announce-list mailing list
devel-announce-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/devel-announce-list

Eitan Isaacson | 4 May 2010 20:38

Fwd: Module Proposal: Caribou

crap, i'm even later than i thought. Didn't send this to desktop-devel.

---------- Forwarded message ----------
From: Eitan Isaacson <eitan <at> monotonous.org>
Date: Mon, May 3, 2010 at 9:17 PM
Subject: Module Proposal: Caribou
To: Joseph Scheuhammer <clown.scheuhammer <at> utoronto.ca>, GNOME A11y
<gnome-accessibility-list <at> gnome.org>
Cc: Ben Konrath <ben <at> bagu.org>, David Pellicer <dpellicer <at> warp.es>

I'm late, and sorry.

Purpose:
Caribou is a text entry and UI navigation application being developed
as an alternative to the Gnome On-screen Keyboard. The overarching
goal for Caribou is to create a usable solution for people whose
primary way of accessing a computer is a switch or pointer device.

Target: Desktop

Dependencies: None that are outside the usual. We might be using
clutter in the future for more interesting keyboards and features.

Resource Usage: Gnome Git, Bugzilla and FTP.

GNOMEyness, community:
From the start Caribou has been seen as The next generation GNOME
onscreen keyboard. The early design process included the community,
specifically the bigger a11y community. Caribou draws from GOK as it's
predecessor and seeks to fill the gap that is left now that GOK is not
following us into GNOME 3.0. On the technology front Caribou uses the
usual suspects PyGTK+, AT-SPI, etc.

Other Notes:
As mentioned above, GOK (GNOME Onscreen Keyboard) is being
discontinued along with it's deprecated dependencies in GNOME 2.x.
This leaves a need for an alternative input assistive technology. I
believe the a11y community supports Caribou and the goals it sets out
to achieve. In the last several months there has been a lot of
interest around Caribou from student groups like Project:Possibility
and HFOSS. There is also funding from Consorcio Fernando de los Rios
for warp.es adding switch access features.

Status and future:
Caribou is definitely still in early development stages. Hopefully
with the help of the different interested parties we could have a
limited, yet solid feature set for GNOME 3.0. We will continue
expanding on features in the following releases.

My personal investment is to see that this module is managed in a way
that is conducive to the larger GNOME project, conforms to the release
schedule, and eventually gets into users hands!
Frederic Peters | 4 May 2010 21:04
Picon

Re: Fwd: Module Proposal: Caribou

Thanks Eitan for the proposal!

> Dependencies: None that are outside the usual. We might be using
> clutter in the future for more interesting keyboards and features.

I just added caribou to jhbuild, I noted:

 - pyclutter: it is not explicitely listed in the external dependencies
   list, but probably we consider bindings to be okay.

 - virtkey: there is a 0.50 tarball on https://launchpad.net/virtkey
   but it extracts itself to the current directory, could you ask the
   authors to package this properly?  (alternatively it's certainly
   not that hard to replace it in pure Python, using the ctypes module
   for calls to X).

Cheers,

        Frederic
Johannes Schmid | 6 May 2010 11:46
Picon

FooCanvas for 3.0?

Hi!

As many of you probably know, GnomeCanvas is the only component that has
no replacement for 3.0 while being deprecated for some time. There was
kind of a discussion not to include any full-featured Canvas in the
future in the GNOME platform. 

However, in the current state nautilus and gnumeric already include the
FooCanvas sources. FooCanvas is a stripped down version of GnomeCanvas
with better integration into Gtk2 drawing cycle (according to Alex).
Currently we are discussing if we include FooCanvas in anjuta, too, to
get back the class-browser from anjuta-extras to anjuta. So, this will
make 3 modules inluding the source. In the evolution GnomeCanvas bug [1]
they also prefer FooCanvas, so I count 4.

Wouldn't it make sense to include this as a standalone module to be used
as a simple canvas inside GNOME instead of copying the source around?

Regards,
Johannes
_______________________________________________
desktop-devel-list mailing list
desktop-devel-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list

Gmane