On 13/06/18 16:38, Carlos E. R. wrote:
On 2018-06-13 08:51, Stefan Seyfried wrote:
On 13.06.2018 08:48, Carlos E. R. wrote:
You should get an email with the information, in some time.
Please tell me how you obtained this wisdom.
Read the entire thread, it is there.
SL> In order to make this process slightly easier and more formal during las SL> weeks board discussion the board decided to the mailing list SL> opensuse-bugshare@opensuse.org where community members can send an email SL> then a volunteer SUSE employee can read the bug report then either open SL> it or provide a summary.
RB> By having this new "send-only" mailinglist, monitored by RB> SUSE-employeed volunteers, we now have one, easy to remember, place RB> for openSUSE contributors to go when they are impacted by the lack of RB> information about a bug. RB> It is not a mailinglist for discussion, just a simple way of reaching RB> out for help to a whole team at once. RB> This should be far more efficient than the previous approach of "just RB> find the nearest SUSE-employeed volunteer and ask them nicely".
And more posts from Richard Brown and Simon Lees in this thread but not all on the same mail list.
Yep this about sums it up, thanks Carlos :-), so far there has only been one example (that didn't actually make it to the list because the list settings were wrong), that particular bug was hard to open because it was reported by a customer but I was able to point the user to the upstream commit that fixed the issue which gave them all the info they needed. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B