Re: Proposed F19 Feature: Replace MySQL with MariaDB

[Norvald H. Ryeng]

----- Fedora(a)FamilleCollet.com wrote:

>  Le 24/01/2013 02:49, Andrew Rist a écrit :
>  > We've been following the discussions to replace MySQL with MariaDB
>  ...
>  
>  /me speaking from my experience.
>  
>  I don't maintain MySQL, but various other mysql packages
>  (mysql-utilities, mysql-connector-python, mysql-workbench, ...).
>  
>  Maintaining Oracle stuff in Fedora becomes a nightmare.
>  
>  Every new release introduce new issues, mostly because there is a lack
>  of communication (upstream and downstream) 
Hi,

I'm sorry to hear about the lack of communication. I'm a MySQL 
developer, and for the last year I've been working with different 
packagers. Linux distributions are an important part of our community,
and we'd like very much to hear your feedback and help make package
maintainers' lives easier. We've had a really constructive cooperation
on MySQL with Debian and Ubuntu the last year, and I am hoping we can
extend that to Fedora and other distributions. Please let me know how I
can help and be a direct connection to MySQL Engineering, bypassing all
the FUD currently out there.

This goes for both MySQL Server and related packages, such as those you
maintain.

Regards,

Norvald H. Ryeng

Proposed F19 Feature: Replace MySQL with MariaDB

[Michael Scherer]

Le jeudi 24 janvier 2013 à 12:11 -0800, Norvald Ryeng a écrit :

>  I'm sorry to hear about the lack of communication. I'm a
> MySQL 
>  developer, and for the last year I've been working with different 
>  packagers. Linux distributions are an important part of our community,
>  and we'd like very much to hear your feedback and help make package
>  maintainers' lives easier. We've had a really constructive cooperation
>  on MySQL with Debian and Ubuntu the last year, and I am hoping we can
>  extend that to Fedora and other distributions. Please let me know how I
>  can help and be a direct connection to MySQL Engineering, bypassing all
>  the FUD currently out there. 
So let's take a very narrow and specific example, and see what could you
do after the fact to make packagers life easier. 

While working with Remi on a package review[1], I was quite surprised to
see that one Oracle engineer created a internal bug for the inclusion of
a patch from a external community member, to be added to a free software
project. Neither do he care to create proper tarballs, which is 

While this is less important than the whole story of missing tests
cases, that's 2 details that should be easy to get right, so are IMHO a
perfect test. 

So, in order to show the commitment of your employer toward more
openness and to make the life of packagers easier, let's try to see if
you 
- can do what it take to have a private bug become fully public, in this
case, the bug 13956819, which is referred in the review ( ie, the bug
for the inclusion of the patch of Remi )

- can do what it take to actually follow the best practices in term of
software distribution, ie publish proper tarballs for mysql-utilities
( among others )

That should not be hard to do, and a easy way to start creating trust
between you and the community.

What do you think ?

[1] https://bugzilla.redhat.com/show_bug.cgi?id=812099