+1 for me. I think there is some great potential for interesting features
in GNOME. I've always been a big fan of the mapping of documents on a
calendar so I know what I was working on a particular day.
As a marketing guy, I'd like us to beat our competition with unique
features that can't be
You know, when I first stumbled on zeitgeist running on my system a year or
so ago, I didn't know what in the world it was doing, although it appeared
to be logging... something. And I think I probably forced it to quit out of
pure habit, before going online to figure out what it was actually
Seif Lotfy wrote:
So I would still like to have my question answered. How is the policy
on using Zeitgeist for non-feature and non-UX related optimization and
maintenance distribution?
Do note this was not discussed by the release team, we'll have a
meeting soon and we can add that to the
On Wed, 2012-04-25 at 22:36 +0200, Frederic Peters wrote:
Seif Lotfy wrote:
So I would still like to have my question answered. How is the policy
on using Zeitgeist for non-feature and non-UX related optimization and
maintenance distribution?
Do note this was not discussed by the
On Wed, 2012-04-25 at 22:36 +0200, Frederic Peters wrote:
Seif Lotfy wrote:
So I would still like to have my question answered. How is the policy
on using Zeitgeist for non-feature and non-UX related optimization and
maintenance distribution?
Do note this was not discussed by the
On Sun, 2012-04-22 at 20:45 +0300, Rūdolfs Mazurs wrote:
Does design team use anything like meetbot?
http://meetbot.debian.net/Manual.html
As far as I know still no bots are used for managing and logging any
GNOME IRC meetings. Also see the short discussion here:
On Tue, Apr 24, 2012 at 2:54 PM, Andre Klapper ak...@gmx.net wrote:
On Sun, 2012-04-22 at 20:45 +0300, Rūdolfs Mazurs wrote:
Does design team use anything like meetbot?
http://meetbot.debian.net/Manual.html
The A11y team has a meetbot for logging meetings. They are the only team I
know of
Hi Emily,
On Sun, 2012-04-22 at 10:27 -0400, Emily Gonyer wrote:
Then the design team ought to be more open about what exactly 'their'
vision for gnome is, as well as open to other ideas/concepts.
Insisting on doing things their way, while being extremely vague as to
what exactly their way
Hi Emily,
On Tue, Apr 24, 2012 at 4:19 PM, Colin Walters walt...@verbum.org wrote:
Hi Emily,
On Sun, 2012-04-22 at 10:27 -0400, Emily Gonyer wrote:
Then the design team ought to be more open about what exactly 'their'
vision for gnome is, as well as open to other ideas/concepts.
On Sat, Apr 21, 2012 at 08:33:43PM -0700, Sriram Ramkrishna wrote:
What about you want to use a new technology but you don't want any new
features but rather using this new external dependency will simpifiy things
and making maintainance easier? I suppose that itself is the feature?
Easier
Hi Olav,
Thanks a lot for clearing it up. This makes a lot of sense.
As I see it there is two ways to approach this:
1) Implement first then propose as an external dependency:The risk is
that implementation is done and GNOME decides the dependency is
unacceptable, thus rendering a couple of
On Sat, Apr 21, 2012 at 9:28 PM, Luis Medinas lmedi...@gnome.org wrote:
do you really want to start talking about what the community think about
this ? Because if you want to start talking i recommend to see how many
threads we have, specially on gnome-shell ml, about design decisions that
Then the design team ought to be more open about what exactly 'their'
vision for gnome is, as well as open to other ideas/concepts. Insisting on
doing things their way, while being extremely vague as to what exactly
their way *is* is not helpful to the rest of the community who is trying to
get
On 22 April 2012 06:14, Olav Vitters o...@vitters.nl wrote:
Risk for the feature focus is that the external dependencies rules are
forgotten. E.g. I noticed that gnome-boxes increased its libosinfo
version requirement in 3.4.1. That's not so nice when distribution is in
a version freeze.
I agree with Florian here. It took me a bit of time to interact with
the design team but it is possible.
It is a very young team and extremely busy and overloaded. They are
welcoming for anyone to work with them on design and once you get
their attention they will help you integrate more. The best
While this thread reflects a bit about some community observations on
how things are handled in GNOME, and i support such a discussion, I
find it a bit off-topic. Can we start a new thread discussing these
issues or so.
Let us stay on topic.
Can an applications use Zeitgeist for
On Sun, Apr 22, 2012 at 4:27 PM, Emily Gonyer emilyyr...@gmail.com wrote:
Then the design team ought to be more open about what exactly 'their'
vision for gnome is, as well as open to other ideas/concepts. Insisting on
doing things their way, while being extremely vague as to what exactly
On Sun, 2012-04-22 at 18:21 +0200, Florian Max wrote:
Which brings us to the matter of openness: the results of everything
the design team does ends up on the GNOME wiki under
live.gnome.org/Design.
I think people are more concerned about being able to have input
on the process, not on seeing
In the end your history is scattered all over the place :P
The logs are there and there is not common way to manage them. Having
a central log like Zeitgeist will allow you to develop policies and
blacklist for logging. Having history at a central location and having
a central tool to
On Sun, Apr 22, 2012 at 7:09 PM, Florian Max florian.muell...@gmail.com wrote:
In the end your history is scattered all over the place :P
The logs are there and there is not common way to manage them. Having
a central log like Zeitgeist will allow you to develop policies and
blacklist for
Sv, 2012-04-22 12:36 -0400, Shaun McCance rakstīja:
On Sun, 2012-04-22 at 18:21 +0200, Florian Max wrote:
Which brings us to the matter of openness: the results of everything
the design team does ends up on the GNOME wiki under
live.gnome.org/Design.
I think people are more concerned
On Sun, Apr 22, 2012 at 9:21 AM, Florian Max florian.muell...@gmail.comwrote:
On Sun, Apr 22, 2012 at 4:27 PM, Emily Gonyer emilyyr...@gmail.comwrote:
Then the design team ought to be more open about what exactly 'their'
vision for gnome is, as well as open to other ideas/concepts. Insisting
On Sun, Apr 22, 2012 at 6:36 PM, Shaun McCance sha...@gnome.org wrote:
On Sun, 2012-04-22 at 18:21 +0200, Florian Max wrote:
Which brings us to the matter of openness: the results of everything
the design team does ends up on the GNOME wiki under
live.gnome.org/Design.
I think people are
On Sun, Apr 22, 2012 at 1:06 PM, Seif Lotfy s...@lotfy.com wrote:
On Sun, Apr 22, 2012 at 6:36 PM, Shaun McCance sha...@gnome.org wrote:
On Sun, 2012-04-22 at 18:21 +0200, Florian Max wrote:
Which brings us to the matter of openness: the results of everything
the design team does ends up
On Sun, Apr 22, 2012 at 10:18 PM, Sriram Ramkrishna s...@ramkrishna.me
wrote:
On Sun, Apr 22, 2012 at 1:06 PM, Seif Lotfy s...@lotfy.com wrote:
On Sun, Apr 22, 2012 at 6:36 PM, Shaun McCance sha...@gnome.org wrote:
On Sun, 2012-04-22 at 18:21 +0200, Florian Max wrote:
Which brings us to
I would like to quote Allan Day (from another public mail thread):
---
I realise that you're frustrated by the lack of Zeitgeist adoption in
GNOME, Seif. As I explained privately, the best way for you to pursue
this is to talk to maintainers who might need it for search results.
The decision to
I've talked to several of my coworkers, and they just think Zeitgeist
is the right technology for anything they're trying to do. A number of
people thought the time-based approach wasn't neat enough. They
brought up the recent flames over the Recently Used selection by
default in the
On Sat, 2012-04-21 at 12:59 -0400, Jasper St. Pierre wrote:
We have a design and a plan for finding
and reminding, and Zeitgeist doesn't seem like the right technology to
implement that plan.
Who's we? Where is this plan? And why isn't it going through
the feature proposal process?
--
Shaun
On Sat, Apr 21, 2012 at 1:20 PM, Shaun McCance sha...@gnome.org wrote:
On Sat, 2012-04-21 at 12:59 -0400, Jasper St. Pierre wrote:
We have a design and a plan for finding
and reminding, and Zeitgeist doesn't seem like the right technology to
implement that plan.
Who's we?
We, the GNOME
On Sat, 2012-04-21 at 13:46 -0400, Jasper St. Pierre wrote:
On Sat, Apr 21, 2012 at 1:20 PM, Shaun McCance sha...@gnome.org wrote:
On Sat, 2012-04-21 at 12:59 -0400, Jasper St. Pierre wrote:
We have a design and a plan for finding
and reminding, and Zeitgeist doesn't seem like the right
Shaun McCance wrote:
Your previous email seems to indicate that the features for 3.6 are
already a foregone conclusion, and that Zeitgeist doesn't fit into
that. But that just can't be, because WE the GNOME community decide
what's in the next version right here on d-d-l during the proposal
Hi,
thanks Shaun for your reply, unfortunatly looks like who decides everything
for GNOME Project are the Design team or the RedHat employees and not the
community. This makes me belive that the community no longer has the power
to decide anything that aren't the way that the designers planned,
On Sat, Apr 21, 2012 at 6:59 PM, Shaun McCance sha...@gnome.org wrote:
On Sat, 2012-04-21 at 13:46 -0400, Jasper St. Pierre wrote:
On Sat, Apr 21, 2012 at 1:20 PM, Shaun McCance sha...@gnome.org wrote:
On Sat, 2012-04-21 at 12:59 -0400, Jasper St. Pierre wrote:
We have a design and a plan
OK seems like i sent the mail to only Jasper (damn-reply to all)
Again I repeat. I am not talking about features.
Web is using an SQLite DB to store its HISTORY. This is code that they
need to maintain themselves.
Are the Web developers allowed and blessed to use Zeitgeist to store
that history.
Hey Luis.
Very good question. Zeitgeist and Tracker are compeletely different.
Tracker is a metadata storage. It is used to store tags and
information about files and other data on your computer.
Zeitgeist is a log. It is a very intelligent and responsive log. We
can not do what tracker providers.
On Sat, 2012-04-21 at 13:46 -0400, Jasper St. Pierre wrote:
On Sat, Apr 21, 2012 at 1:20 PM, Shaun McCance sha...@gnome.org wrote:
On Sat, 2012-04-21 at 12:59 -0400, Jasper St. Pierre wrote:
We have a design and a plan for finding
and reminding, and Zeitgeist doesn't seem like the right
On Sat, Apr 21, 2012 at 11:24 AM, Allan Day allanp...@gmail.com wrote:
I'm not saying that the feature proposal process is perfectly clear
though. ;)
It's a little rough, because we are only talking about features; we don't
really get to address new technologies or libraries that we might
On Sat, Apr 21, 2012 at 11:22 AM, Luis Medinas lmedi...@gnome.org wrote:
Hi,
thanks Shaun for your reply, unfortunatly looks like who decides
everything for GNOME Project are the Design team or the RedHat employees
and not the community.
Please, can we not finger specific companies when
2012/4/21 Sriram Ramkrishna s...@ramkrishna.me
On Sat, Apr 21, 2012 at 11:22 AM, Luis Medinas lmedi...@gnome.org wrote:
Hi,
thanks Shaun for your reply, unfortunatly looks like who decides
everything for GNOME Project are the Design team or the RedHat employees
and not the community.
On Sat, Apr 21, 2012 at 12:28 PM, Luis Medinas lmedi...@gnome.org wrote:
2012/4/21 Sriram Ramkrishna s...@ramkrishna.me
On Sat, Apr 21, 2012 at 11:22 AM, Luis Medinas lmedi...@gnome.orgwrote:
Hi,
thanks Shaun for your reply, unfortunatly looks like who decides
everything for GNOME
On Sat, Apr 21, 2012 at 11:48:59AM -0700, Sriram Ramkrishna wrote:
For instance, let's say Xan who has indicated some interest to use Zeitgist
in Web wanted to use it but not add any new features but instead uses Zg to
store bookmarks then really does this process help that? Does he even need
On Sat, Apr 21, 2012 at 8:10 PM, Olav Vitters o...@vitters.nl wrote:
On Sat, Apr 21, 2012 at 11:48:59AM -0700, Sriram Ramkrishna wrote:
For instance, let's say Xan who has indicated some interest to use
Zeitgist
in Web wanted to use it but not add any new features but instead uses Zg
to
Sounds like a reasonable approach. The reason we looked at zg in the first
place is because we were told that eds might not be a good solution for
this. I implement it how you suggested and demo it u guess :)
On 4/19/12, Rodrigo Moya rodr...@gnome-db.org wrote:
On Thu, 2012-04-19 at 10:31 +0100,
On Thu, 2012-04-19 at 02:20 +0200, Seif Lotfy wrote:
So let me try to take Web use cases that could use Zeitgeist:
* The user wants to type in the location bar and have
suggestions pop out while typing.
* The user wants to blacklist some websites or all websites
On Wed, 2012-04-18 at 23:43 +0200, Seif Lotfy wrote:
Clocks: The clocks app is designed by the GNOME designers.
It is still more
or less a prototype I am working on alongside Emily Gonyer.
We wanted to
make use of Zeitgeist in storing
On Thu, Apr 19, 2012 at 11:31 AM, Bastien Nocera had...@hadess.net wrote:
On Wed, 2012-04-18 at 23:43 +0200, Seif Lotfy wrote:
Clocks: The clocks app is designed by the GNOME designers.
It is still more
or less a prototype I am working on alongside Emily Gonyer.
On Thu, Apr 19, 2012 at 11:29 AM, Bastien Nocera had...@hadess.net wrote:
On Thu, 2012-04-19 at 02:20 +0200, Seif Lotfy wrote:
So let me try to take Web use cases that could use Zeitgeist:
* The user wants to type in the location bar and have
suggestions pop out while typing.
On Thu, 2012-04-19 at 10:31 +0100, Bastien Nocera wrote:
On Wed, 2012-04-18 at 23:43 +0200, Seif Lotfy wrote:
Clocks: The clocks app is designed by the GNOME designers.
It is still more
or less a prototype I am working on alongside Emily Gonyer.
Le mardi 17 avril 2012 à 22:47 +0200, Seif Lotfy a écrit :
Purpose:
Zeitgeist is an event logging framework. It stores user activity in a
structured manner and provides a powerful DBus API to query and
monitor the log. Zeitgeist as such does not have a graphical
component, but is intended to
Hi Seif,
FYI we dropped the module proposals period and replaced it by a proposal
period for systemwide features. See
https://mail.gnome.org/archives/devel-announce-list/2012-March/msg5.html
for the GNOME 3.5 call.
So the question would turn into Which (Zeitgeist-based) features could
On Wed, Apr 18, 2012 at 10:24 AM, Milan Bouchet-Valat nalimi...@club.frwrote:
Le mardi 17 avril 2012 à 22:47 +0200, Seif Lotfy a écrit :
Purpose:
Zeitgeist is an event logging framework. It stores user activity in a
structured manner and provides a powerful DBus API to query and
monitor
On Tue, 2012-04-17 at 22:47 +0200, Seif Lotfy wrote:
snip
We already have GNOME specific developments:
* We already log everything that pushes into Gtk.RecentlyUsed.
* For better logging we have Totem, Rhythmbox, and gedit
deploying loggers as a soft-dependency in the form
Hi Andre,
Thanks for the quick reply. I have some concern though that for framework
authors, it's very hard to understand the new module proposal process.
This might be slightly off the topic... so I understand if you would put
this in another thread.
New features get planned for GNOME 3.6.
Seif Lotfy s...@lotfy.com wrote:
...
There are 3 issues in discussion or in development where Zeitgeist
integration is reaching a halt due to the uncertainty of where Zeitgeist
stands:
Epiphany (Web): There has long been discussions on how to deploy Zeitgeist
as a backend for Web. Web needed
On Wed, Apr 18, 2012 at 11:35 PM, Allan Day allanp...@gmail.com wrote:
Seif Lotfy s...@lotfy.com wrote:
...
There are 3 issues in discussion or in development where Zeitgeist
integration is reaching a halt due to the uncertainty of where Zeitgeist
stands:
Epiphany (Web): There has
So let me try to take Web use cases that could use Zeitgeist:
- The user wants to type in the location bar and have suggestions pop
out while typing.
- The user wants to blacklist some websites or all websites starting
with porn from being stored in history
- The user wants to
*Purpose:
*Zeitgeist is an event logging framework. It stores user activity in a
structured manner and provides a powerful DBus API to query and monitor the
log. Zeitgeist as such does not have a graphical component, but is intended
to integrate wherever it makes sense. Just like Tracker, Folks
+1 for me. I think there is some great potential for interesting features
in GNOME. I've always been a big fan of the mapping of documents on a
calendar so I know what I was working on a particular day.
As a marketing guy, I'd like us to beat our competition with unique
features that can't be
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
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
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,
On Thu, 2010-04-22 at 19:01 +0200, Seif Lotfy wrote:
However we do want to keep our development branches in bzr+launchpad.
That sounds reasonable.
The Java bindings have been using bzr since before GNOME moved to svn.
Needless to say we kept using it, and likewise skipped the subsequent
move
On Mon, Apr 26, 2010 at 2:01 AM, Cody Russell brats...@gnome.org wrote:
Eh, github's pull requests are not really the same as a code review
system. At least last time I looked at it. You do a pull request and
the person you're requesting basically just gets a message that says,
Hey dude,
On Sun, 2010-04-25 at 19:01 -0500, Cody Russell wrote:
On Sun, 2010-04-25 at 22:44 +0200, Patryk Zawadzki wrote:
On Sun, Apr 25, 2010 at 7:59 PM, Curtis Hovey sinzui...@verizon.net
wrote:
My suggestion is to support the Zeitgeist's community's culture of
code
reviews. GNOME does not
On Fri, 2010-04-23 at 16:52 -0400, Curtis Hovey wrote:
I think you can:
* use bzr-git to push your Launchpad trunk to GNOME git
* setup an import of the git branch and make it trunk
launchpad just imports git master, right?
___
desktop-devel-list
On Mon, 2010-04-26 at 13:51 +0200, Rodrigo Moya wrote:
On Fri, 2010-04-23 at 16:52 -0400, Curtis Hovey wrote:
I think you can:
* use bzr-git to push your Launchpad trunk to GNOME git
* setup an import of the git branch and make it trunk
launchpad just imports git master, right?
No.
Le lundi 26 avril 2010 à 17:18:31% (+1000), Andrew Cowie a écrit:
but the whole point of decentralized VCS is disconnected operation
and having to have an active internet connection to get to some
centralized website in order to follow through workflow is a
non-starter for most of us.
I
2010/4/26 Dodji Seketeli do...@seketeli.org:
It would be interesting to find a way to make these tools -- bugzilla or
whatever patch review system -- be interoperable with email.
Launchpad supports answering to merge requests by mail (as well as
managing bugs, etc).
Le lundi 26 avril 2010 à 21:24:19% (+0200), Siegfried-Angel Gevatter Pujals a
écrit:
2010/4/26 Dodji Seketeli do...@seketeli.org:
It would be interesting to find a way to make these tools -- bugzilla or
whatever patch review system -- be interoperable with email.
Launchpad supports
On Fri, 2010-04-23 at 18:59 -0400, Owen Taylor wrote:
On Fri, 2010-04-23 at 16:52 -0400, Curtis Hovey wrote:
...
I think Launchpad + BZR and GNOME + git can interoperate fine.
I think you can:
* use bzr-git to push your Launchpad trunk to GNOME git
* setup an import of the git branch
On 24 April 2010 11:18, Johannes Schmid j...@jsschmid.de wrote:
Hi!
No one ever said that we wont accept git branches. Anything submitted
as a patch or git branch will merge just as easy as any bzr-based
contribution. The only thing that may be more inconvenient is the
hack directly in
On Sun, Apr 25, 2010 at 7:59 PM, Curtis Hovey sinzui...@verizon.net wrote:
My suggestion is to support the Zeitgeist's community's culture of code
reviews. GNOME does not have an official code review tool. Neither does
GitHub, which is why projects that host in GitHub also use Launchpad for
On Sun, 25.04.10 22:44, Patryk Zawadzki (pat...@pld-linux.org) wrote:
On Sun, Apr 25, 2010 at 7:59 PM, Curtis Hovey sinzui...@verizon.net wrote:
My suggestion is to support the Zeitgeist's community's culture of code
reviews. GNOME does not have an official code review tool. Neither does
On Sun, 2010-04-25 at 22:44 +0200, Patryk Zawadzki wrote:
On Sun, Apr 25, 2010 at 7:59 PM, Curtis Hovey sinzui...@verizon.net
wrote:
My suggestion is to support the Zeitgeist's community's culture of
code
reviews. GNOME does not have an official code review tool. Neither
does
GitHub,
On Sun, Apr 25, 2010 at 10:59 AM, Curtis Hovey sinzui...@verizon.net wrote:
My suggestion is to support the Zeitgeist's community's culture of code
reviews. GNOME does not have an official code review tool. Neither does
GitHub, which is why projects that host in GitHub also use Launchpad for
On 24 April 2010 00:59, Owen Taylor otay...@redhat.com wrote:
On Fri, 2010-04-23 at 16:52 -0400, Curtis Hovey wrote:
On Thu, 2010-04-22 at 19:01 +0200, Seif Lotfy wrote:
Our current development is heavily based on launchpad.
We are discussing the issue and we don't see a problem to have our
Hi!
No one ever said that we wont accept git branches. Anything submitted
as a patch or git branch will merge just as easy as any bzr-based
contribution. The only thing that may be more inconvenient is the
hack directly in trunk-workflow that is inherent to the monolithic
VCSs of old, but
There is the further issue of translation.
The Bulgarian team had prepared a translation to Zeitgeist available
here:
http://fsa-bg.org/project/gtp/browser/gnome/gnome3/zeitgeist.trunk.bg.po
We could not import it to Launchpad because a team member there had
locked the translation. (and we had
Hi Mikkel,
On Thu 22 Apr 2010 21:40, Mikkel Kamstrup Erlandsen mikkel.kamst...@gmail.com
writes:
Here's what we do. We set a series of milestones and target bugs and
blueprints to these milestones. We also attach branches (not patches)
to bugs and blueprints. When a linked branch is ready to
2010/4/23 Александър Шопов li...@kambanaria.org:
There is the further issue of translation.
We already agreed that translations can be moved to GNOME infrastructure.
I've just committed the translation, btw. Thanks!
--
Siegfried-Angel Gevatter Pujals (RainCT)
Free Software Developer
On Thu, 2010-04-22 at 19:01 +0200, Seif Lotfy wrote:
Our current development is heavily based on launchpad.
We are discussing the issue and we don't see a problem to have our
trunk from launchpad ported to git with every release. However we do
want to keep our development branches in
On Fri, 2010-04-23 at 16:52 -0400, Curtis Hovey wrote:
On Thu, 2010-04-22 at 19:01 +0200, Seif Lotfy wrote:
Our current development is heavily based on launchpad.
We are discussing the issue and we don't see a problem to have our
trunk from launchpad ported to git with every release.
On Sat, Apr 24, 2010 at 4:29 AM, Owen Taylor otay...@redhat.com wrote:
On Fri, 2010-04-23 at 16:52 -0400, Curtis Hovey wrote:
I think Launchpad + BZR and GNOME + git can interoperate fine.
[snip]
I think the question is, is this OK for a GNOME module?
The main point of requiring use of GNOME
On 22 April 2010 00:01, Johannes Schmid j...@jsschmid.de wrote:
Hi!
Resource usage:
Bug tracker: http://bugs.launchpad.net/zeitgeist
VCS: http://code.launchpad.net/zeitgeist
Releases: http://launchpad.net/zeitgeist/+download
According to
Hi!
(seems like the initial reply wasn't sent to the ML)
According to http://live.gnome.org/ReleasePlanning/ModuleProposing:
Use of GNOME resources: Modules must use GNOME FTP for releases.
Modules ought to use GNOME Bugzilla and GNOME Git (there had better be a
very good reason for not
Qua, 2010-04-21 às 22:41 +0200, Mikkel Kamstrup Erlandsen escreveu:
Purpose:
Zeitgeist is an event logging framework. It stores user activity in a
structured manner and provides a powerful DBus API to query and
monitor the log. Zeitgeist as such does not have a graphical
component, but is
On Thu, 2010-04-22 at 07:15 +, j...@jsschmid.de wrote:
We don't have any concrete plans. However moving our tarballs to
GNOME
FTP should pose no problem at all, likewise for i18n. Since we are
talking daemons here i18n is not a big part of the project.
As for VCS and bug tracking
On Thu, 2010-04-22 at 12:03 +0200, Murray Cumming wrote:
On Thu, 2010-04-22 at 07:15 +, j...@jsschmid.de wrote:
We don't have any concrete plans. However moving our tarballs to
GNOME
FTP should pose no problem at all, likewise for i18n. Since we are
talking daemons here i18n is not
On Thu, 2010-04-22 at 08:10 +0200, Mikkel Kamstrup Erlandsen wrote:
As for VCS and bug tracking it'll be quite a lot more work on our part
if we should move. I don't think anyone in the team is directly
opposed to the idea, but it's more the fact that it would be a major
inconvenience. We
On Thu, 2010-04-22 at 07:15 +, j...@jsschmid.de wrote:
Perhaps an unholy alliance of bzr-git and Launchpad's git-import
feature can make all parts happy (at least vcs-wise)? I will take a
look at this when I have the time.
I think you should rather see that the other way round - track
Our current development is heavily based on launchpad.
We are discussing the issue and we don't see a problem to have our trunk
from launchpad ported to git with every release. However we do want to keep
our development branches in bzr+launchpad. So with every branch merge with
our launchpad trunk
Hi!
Am Donnerstag, den 22.04.2010, 19:01 +0200 schrieb Seif Lotfy:
Our current development is heavily based on launchpad.
We are discussing the issue and we don't see a problem to have our
trunk from launchpad ported to git with every release. However we do
want to keep our development
2010/4/22 Johannes Schmid j...@jsschmid.de:
BTW; this workflow will be horrible for translators.
Could you please elaborate on that?
--
Siegfried-Angel Gevatter Pujals (RainCT)
Free Software Developer 363DEAE3
___
desktop-devel-list mailing
Siegfried-Angel Gevatter Pujals wrote:
2010/4/22 Johannes Schmid j...@jsschmid.de:
BTW; this workflow will be horrible for translators.
Could you please elaborate on that?
We are discussing the issue and we don't see a problem to have our
trunk from launchpad ported to git with every
On Thu, 2010-04-22 at 19:01 +0200, Seif Lotfy wrote:
Our current development is heavily based on launchpad.
We are discussing the issue and we don't see a problem to have our
trunk from launchpad ported to git with every release. However we do
want to keep our development branches in
On Thu, 2010-04-22 at 19:01 +0200, Seif Lotfy wrote:
Our current development is heavily based on launchpad.
We are discussing the issue and we don't see a problem to have our
trunk from launchpad ported to git with every release. However we do
want to keep our development branches in
On Thu, Apr 22, 2010 at 10:34 AM, Germán Póo-Caamaño g...@gnome.org wrote:
On Thu, 2010-04-22 at 19:01 +0200, Seif Lotfy wrote:
Our current development is heavily based on launchpad.
We are discussing the issue and we don't see a problem to have our
trunk from launchpad ported to git with
I wrote:
2010/4/22 Johannes Schmid j...@jsschmid.de:
BTW; this workflow will be horrible for translators.
Could you please elaborate on that?
We are discussing the issue and we don't see a problem to have our
trunk from launchpad ported to git with every release., but release
team
On Thu, 2010-04-22 at 10:37 -0700, Sandy Armstrong wrote:
In such case, should not it be a freedesktop project and be proposed as
an external dependency for the Activity Journal?
The Activity Journal is in Launchpad and would have the same issues as
we've been discussing (except moreso
2010/4/22 Frederic Peters fpet...@gnome.org:
We are discussing the issue and we don't see a problem to have our
trunk from launchpad ported to git with every release., but release
team is too late for translators.
Yeah, I agree that copying stuff over just before we release isn't
really
1 - 100 of 106 matches
Mail list logo
