lgtm!

As the GitHub repository is now officially unmaintained and the source has moved to Phabricator, it would be a good idea to open up a new product on bugs.kde.org so that users can report bugs. You'll probably need to contact Sysadmin for this.

designed from @delsarto

Yeah, you need QT 5.10 to cook vvave, qt 5.9.4 won't cut it

I've now added that key. Please note that it isn't possible to authorise access based on the key fingerprint, we need the actual public key.
I've grabbed that in this case from your Identity account.

Hi @bcooksley .
Could I get please permission on the vvaveadmin@mimi service for this another key:
31:41:2a:39:ca:aa:91:60:09:55:6a:d3:f3:10:b7:88 camilo@camilohr

I'm afraid that uploading keys to Identity only affects things that can be accessed through your Developer account (Git and SVN essentially)
All other services (like the vvaveadmin@mimi account) are managed independently (to minimize the security risk)

...and name stylisation/pronunciation :D

ok

Maybe we could keep the heart as part of the brand on the vvave app and keep it simple on the vvave stream side?

In T8261#135018, @camiloh wrote:

with the heart:

nice I would add the heart somewhere as brand.

with the heart:

Here's a demo of the live page for the platform
https://vvave-stream.kde.org/

I miss the hearth

In T8261#135014, @camiloh wrote:

Some alts

Thank you so much Ben.
You're awesome! :)

The DNS and other server changes are now complete.
Your login for maintenance of vvave-stream.kde.org has now changed to vvaveadmin@mimi.kde.org from the previous babeitadmin@mimi.kde.org account previously used for SSH access.

The repositories have now been renamed on git.kde.org and Phabricator.
I will update the websites shortly to pull from their new sources, and make the relevant DNS changes.

It wasn't sent to a specific mailing list, it was sent to a group of people that Lydia thought could help me find a better name:
Paul Brown <paul.brown@kde.org>,
Ivana Isadora Devcic <isadora@kde.org>,
Jens Reuterberg <jens@ohyran.se>,
Sebastian Kügler <sebas@kde.org>,
Neofytos Kolokotronis <neofytosk@posteo.net>,
and Uri Herrera

Having the discussion on a mailing list is perfectly fine, and is the generally accepted means of having discussions within the KDE Community.

Hi Nicolas,
the first discussion was held on a meeting with the KDE e.V on the last week of February i think. The discussion was about the BabeIt platform and some legal issues around it. Then the issue about the name came up and it was suggested to look for a better name as Babe seemed to came up as sexist and childish. Then thanks to Lydia the discussion moved on to a mailing list between some members of the community where some ideas for a new named where tossed.

Out of curiosity, where did the discussion about the new name happen? It seems problematic for saying out loud…

In T8260#134271, @bcooksley wrote:

What will be happening to the original Babe repository (https://phabricator.kde.org/source/babe/) given that it doesn't seem to be getting renamed?

What will be happening to the original Babe repository (https://phabricator.kde.org/source/babe/) given that it doesn't seem to be getting renamed?

There's already a basic integration with youtube on the client side (vvave app). It is missing on the platform, but i think i'd like to keep it this way:

Collaboration with YouTube and nextcloud would be awesome

Look good to me. I prefer icons pink

This is what i have so far:

Branding task at:
https://phabricator.kde.org/T8261

Opening ticket to change babe-qml repo name to vvave at:
https://phabricator.kde.org/T8260

Right now the issues are being handle on the GitHub repo