-
Notifications
You must be signed in to change notification settings - Fork 20
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 Mailing Lists #42
Comments
I don't see a way to add line-by-line comments, so I'll just mention that I would change the word "closed" in "lists will be closed and archived" to "shut down" (because "closed" could be interpreted to mean "not open to the public). Other than that, it looks good. |
Merging EMBOSS & -dev mailing list; retiring -announce, -bug, -submit lists? |
Merging |
Merging |
Are there still tasks to do here, or can this be closed? |
There are still EMBOSS ones to do, there was no objection. |
Does anyone even use any of the EMBOSS lists anymore? Lists to migrate (please edit as appropriate):
|
Are the checkmarks supposed to indicate completion of migration? (None of these have been migrated) |
Oh. I optimistically interpreted Peter's comment, "There are still EMBOSS ones to do," as meaning that the rest were done. I will uncheck them. |
I thought this was for tracking consolidation within mailman, not migration which is the next step. |
(@hlapp : this is per the OBF Board Meeting; is there any other more general repo this can go to?)
As @peterjc has noted on the main OBF blog, the OBF hosted mail lists (including the various EMBOSS list and other general member 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 EMBOSS and general OBF 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
Update: Links to the relevant project-specific issues (including feedback):
BioPerl: bioperl/bioperl-live#258
Biopython: biopython/biopython#1481
Bioruby: bioruby/bioruby#118
BioJava: biojava/biojava#717
The text was updated successfully, but these errors were encountered: