New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OBF mail list issues #118
Comments
The Can we officially close the Is there another venue used for BioRuby discussion in Japanese we should mention? Would this be an acceptable English description for the list? Translating this into suitable Japanese is too hard for me:
Does it make sense to copy all the |
The |
I think so. Both bioruby-ja and bioruby-cvs can be closed. If possible, I'd like to post final message to close the bioruby-ja list. (bioruby-cvs can be closed silently).
I suppose most subscribers already subscribe to the bioruby@open-bio mailing list. |
+1 |
Current subscriber numbers, using
Given 165 of the 172 Japanese language subscribers did not subscribe to the English list, it seems wrong to automatically subscribe them. @ngoto @ktym Could you update the Or as it appears on I have updated the description for |
Cross reference: OBF/obf-docs#42 |
(To the Bioruby developers : this is per the OBF Board Meeting, feel free to edit/add to the ticket or text as needed)
As @peterjc has noted on the main OBF blog, the OBF hosted mail lists (including the various Bioruby lists) have had serious issues over the last several months due to heavy spam traffic on the OBF mailman server. We are soliciting community feedback from both Bioruby developers and users for the next steps forward on resolving this issue (see below). Please post suggestions or concerns here.
We (OBF) are migrating to a hosted solution that should provide more stability, with the downside that many lists will be shut down and archived due to hosting costs. The blog post details some suggestions.
Again, please note your concerns as soon as possible. We would like feedback by Dec. 28 so that we can decide on the next steps.
Thanks all!
@cjfields
The text was updated successfully, but these errors were encountered: