Dear Community members!

There was a fair deal of discussion yesterday during our meeting (see, 
http://merproject.org/meetings/mer-meeting/2014/mer-meeting.2014-06-24-08.44.html)<http://merproject.org/meetings/mer-meeting/2014/mer-meeting.2014-06-24-08.44.html%29>
 on two important topics raised by faenil.

I hope the following can clarify and give the expected amount of transparency 
and insight.

About the Community Beta Program:
I bet it won't be a surprise for any of you but we are currently having such 
activity with a limited amount of participants.
Just a few Community members whom with we interact closely, getting extremely 
valuable feedback before we launch our SailfishOS updates to the public.
It has remained confidential for multiple reasons but in a nutshell, we still 
need to improve on infrastructures and processes in order to scale-up 
gracefully.
We are confident that we could do so in a not so distant future, but first, we 
want to make sure the path is neat and clear for both our Community testers and 
us.
Loaning a test device, having feedback channels and needed monitoring is, as 
you can easily imagine, a costly exercise for any small structure.
The mention yesterday of cost of operations is at the core of our decisions, 
and it's not only about the financial aspect of maintaining infrastructure but 
getting the most out of any investment we make.
Be assured we're committed to bring more of these activities to you, and 
broaden the scope. The Opt-in way to test single features/patches as well as 
the Jolla Launcher Alpha testing are here to demonstrate our engagement to get 
as many of you onboard.
>From the new-comers to the most seasoned developers, we do it together.
Expect more to happen on this very front...

About SailfishOS bugzilla instance:
We are in a situation where we have multiple input sources to monitor, Nemo & 
Mer bugzillas, together.jolla.com, git repositories...
We do have enablers in our internal bugzilla instance to achieve a seamless 
tracking, and plans to get some automations that will provide more visibility 
on our activities.
On this very topic, I invite you to check https://github.com/bayoteers and also 
evangelize how awesome our bugzilla extensions are :)
In this context, we clearly need to evaluate what would be the benefit of a new 
instance and what would it be used for so the ROI remains as high as possible.
There was a concern that together.jolla.com isn't working for bug reports.
Let me assure you that it does, even beyond expectations, because of the tools 
and process mentioned above that we keep improving.
So from my personal perspective, before we do deploy another instance for 
feedback, I'd rather want to see consolidation (which directly relates to the 
Nemo middleware migration to Mer).
I would suggest we revisit this topic in the future and focus now on the 
existing above mentioned channels...

Cheers,
Eric Le Roux
Bugzilla & TJC admin @ Jolla
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Reply via email to