Re: Matrix as a replacement for Telepathy

[Alejandro HC]

A comment as a user. Since Empathy ceased to be maintained, there has been
little concern for the communication system that is available in gnome
focused to end user (gnome-polari is targeted to IRC which is mostly used
by developer communities).

Matrix is great, but I feel it points to the same, so why not support GNU
Ring in GNOME ... Ring is a project that aims to be a free replacement for
Skype, in addition already has a good integration in gnome and it's easy to
use, offering its own communication protocol it offers support for SIP.

2017-08-24 17:40 GMT-03:00 Sriram Ramkrishna :

> I thought I would put it out there after some discussion to make sure it
> isn't a completely crazy idea.
>
> What do people think about integrating directly with Matrix as a
> replacement for Telepathy?  This would mean that we can focus on  chat,
> video-conferencing, and anything else through Matrix.  We'd have to abandon
> clients like empathy (or modify).  For IRC we would use our own library or
> use matrix's bridge.
>
> This way, we can push this support to an upstream that cares and is
> culturally compatible with us.  Matrix of course gets a boost from a major
> group relying on them and providing alternative clients and a superior
> (hopefully) user experience.
>
> sri
>
> ___
> desktop-devel-list mailing list
> desktop-devel-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/desktop-devel-list
>



-- 
*Hugo*
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Matrix as a replacement for Telepathy

[Alexandre Franke]

On Thu, Aug 24, 2017 at 10:40 PM, Sriram Ramkrishna  wrote:
> What do people think about integrating directly with Matrix as a replacement
> for Telepathy?

Yes please.

-- 
Alexandre Franke
GNOME Hacker & Foundation Director
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Matrix as a replacement for Telepathy

[Sriram Ramkrishna]

I thought I would put it out there after some discussion to make sure it
isn't a completely crazy idea.

What do people think about integrating directly with Matrix as a
replacement for Telepathy?  This would mean that we can focus on  chat,
video-conferencing, and anything else through Matrix.  We'd have to abandon
clients like empathy (or modify).  For IRC we would use our own library or
use matrix's bridge.

This way, we can push this support to an upstream that cares and is
culturally compatible with us.  Matrix of course gets a boost from a major
group relying on them and providing alternative clients and a superior
(hopefully) user experience.

sri
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Updating GNOME Goals?

[Daniel Mustieles García]

2017-08-24 10:55 GMT+02:00 Sébastien Wilmet :

> On Thu, Aug 24, 2017 at 09:45:18AM +0200, Daniel Mustieles García wrote:
> > Great, one less step.
> >
> > Then, it's ok to move this goal to the Deprecated Section? We could
> include
> > the link in the goal comments
>
> RemoveMarkupInMessages should not be moved to the Deprecated section, it
> should simply be "retired".
>

Agree. A goal should be a one-time task, to achieve an specific target that
cannot change easily in the time.

Adding new strings to modules is a daily task, so having it as a goal would
imply to review every day if those new strings have markup or not, updating
the goal if there are changes in an already fixed module...

Having it as a guideline is a "best practice" I think is a better idea than
having a goal.


> The Deprecated section is for the Autotools-specific goals that are not
> yet done.
>
> --
> Sébastien
> ___
> desktop-devel-list mailing list
> desktop-devel-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/desktop-devel-list
>
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Updating GNOME Goals?

[Sébastien Wilmet]

On Thu, Aug 24, 2017 at 09:45:18AM +0200, Daniel Mustieles García wrote:
> Great, one less step.
> 
> Then, it's ok to move this goal to the Deprecated Section? We could include
> the link in the goal comments

RemoveMarkupInMessages should not be moved to the Deprecated section, it
should simply be "retired".

The Deprecated section is for the Autotools-specific goals that are not
yet done.

--
Sébastien
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Updating GNOME Goals?

[Sébastien Wilmet]

On Thu, Aug 24, 2017 at 09:20:45AM +0200, Daniel Mustieles García wrote:
> have doubts about AddCodeCoverage, DistCheck.

- Meson instructions should be added for AddCodeCoverage.
- DistCheck is specific to Autotools.
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Updating GNOME Goals?

[Philip Withnall]

On Thu, 2017-08-24 at 09:20 +0200, Daniel Mustieles García wrote:
> Hi,
> 
> Some additional comments:
> 
> - /RemoveMarkupInMessages: it makes no sense to set a goal for this,
> because a fixed module today might change tomorrow, introducing new
> strings with markup. Maybe should be set as a guideline (and the goal
> moved to the Expired section)

Doesn’t mean it can’t be a goal. The benefit of doing it as a goal
means that it can be done on loads of modules at the same time in the
cycle (to fit in with translation work).

Philip

signature.asc
Description: This is a digitally signed message part
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Updating GNOME Goals?

[Alexandre Franke]

On Thu, Aug 24, 2017 at 9:20 AM, Daniel Mustieles García
 wrote:
> Hi,

Hi,

> - /RemoveMarkupInMessages: it makes no sense to set a goal for this, because
> a fixed module today might change tomorrow, introducing new strings with
> markup. Maybe should be set as a guideline (and the goal moved to the
> Expired section)

https://wiki.gnome.org/TranslationProject/DevGuidelines/Avoid%20markup%20wherever%20possible
already exists.

-- 
Alexandre Franke
GNOME Hacker & Foundation Director
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Updating GNOME Goals?

[Daniel Mustieles García]

Hi,

Some additional comments:

- /RemoveMarkupInMessages: it makes no sense to set a goal for this,
because a fixed module today might change tomorrow, introducing new strings
with markup. Maybe should be set as a guideline (and the goal moved to the
Expired section)

- MesonPorting: should we move it to Current GNOME Goals

- Goals about autotools: since we are moving to Meson, all
autotools-related goals should be moved to the Deprecated section. Not sure
about which goals are: have doubts about AddCodeCoverage, DistCheck. If
someone of those goals is still valid, but needs some comments about Meson
instead about autotools, we should update the info.

We should also update the template to list only the core modules. The list
can be obtained from the gnome-core-modules files from gnome-modulesets, is
this right?

I will help in whatever be in me hand :)

2017-08-23 18:32 GMT+02:00 Sriram Ramkrishna :

>
>
> On Wed, Aug 23, 2017 at 2:18 AM Sébastien Wilmet 
> wrote:
>
>> On Tue, Aug 22, 2017 at 06:42:07PM +, Sriram Ramkrishna wrote:
>> > I have gone ahead and contacted the
>> > owners of all the GNOME Goals that were more than a year old and asked
>> > whether they can either update the goal or retire it.
>>
>> You contacted me for 4 different GNOME goals, but I'm definitely not the
>> owner of those! I'm probably just the latest person who edited those
>> wiki pages…
>>
>
> Sorry, my man!  I looked at the last edit.. goals don't have an owner so I
> had to go with whoever touched it last.  I can see why people might feel
> reluctant to be the owner, but it would be nice to have a group of people
> responsibile for it if not an owner.  Or DDL is the owner and I'll just
> bring it on the list and see who takes charge. :-)
>
> So going forward we have:
>
> 1) reduce scope of the goals in regards to the modules
> 2) move goals to expired or uneeded.  Some of these goals have useful
> information so I don't want to delete them.
>
> Anything else?  I can volunteer to move all the autotools related work out
> of the goals.  But someone should take charge of reducing the scope.
> Probably all that is required is to take the list, run it against the core
> apps, and grep the status out of them and then put it back on the wiki.
>
> sri
>
>
>> --
>> Sébastien
>>
>
> ___
> desktop-devel-list mailing list
> desktop-devel-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/desktop-devel-list
>
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list