Closed bgruening closed 7 years ago
This is a great idea; I will happily participate to the extent I have time available.
I'd participate in some capacity.
Good idea. I may not be able to do things synchronously due to time constraints, but would be happy to participate otherwise.
@daler this could be a chance to see PR all 24h :)
What are your specific task ideas so far? In any case, I'd participate.
On Sun, Sep 4, 2016, 7:16 AM Björn Grüning notifications@github.com wrote:
@daler https://github.com/daler this could be a chance to see PR all 24h :)
— You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub https://github.com/bioconda/bioconda-recipes/issues/2277#issuecomment-244605911, or mute the thread https://github.com/notifications/unsubscribe-auth/AAv_vtEJkbZehD1yYIvD1u6dVJigjtIZks5qmtLEgaJpZM4J0iGT .
@brwnj I have added a few ideas to the top post.
Hey, I will also contribute. Especially #1860 sounds interesting for me :-)
Would be happy to contribute! I think weekends might be easier for me, but perhaps we should find a consensus time.
On Sun, Sep 4, 2016, 8:09 AM Florian Eggenhofer notifications@github.com wrote:
Hey, I will also contribute. Especially #1860 https://github.com/bioconda/bioconda-recipes/issues/1860 sounds interesting for me :-)
— You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub https://github.com/bioconda/bioconda-recipes/issues/2277#issuecomment-244608686, or mute the thread https://github.com/notifications/unsubscribe-auth/AKZXA4GbxIlVBQl5ByxCGKYn9zLjtIo4ks5qmt8MgaJpZM4J0iGT .
Hi all, I'm in! :smiley:
I will try participate too.
I am very pressed for time, but I will try to participate
Idea:
I would be very interested, but it depends on when.
On Sep 5, 2016 4:08 AM, "Tiago Antao" notifications@github.com wrote:
Idea:
2282 https://github.com/bioconda/bioconda-recipes/issues/2282 (age of
packages)
— You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub https://github.com/bioconda/bioconda-recipes/issues/2277#issuecomment-244636514, or mute the thread https://github.com/notifications/unsubscribe-auth/AFTFRlMLUwvW0qfChiisAUq3FELomNoQks5qm11pgaJpZM4J0iGT .
Same here; interested but depends on date/time.
I'm in of course. My time is very limited at the moment, but I'll try to join!!
I am also interested. My contribution depends as well on the time i have available and my knowledge of the bioconda system
I am also interested, time and familiarity with the bioconda system permitting! On Mon, 5 Sep 2016 at 11:46, Mattias de Hollander notifications@github.com wrote:
I am also interested. My contribution depends as well on the time i have available and my knowledge of the bioconda system
— You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub https://github.com/bioconda/bioconda-recipes/issues/2277#issuecomment-244705682, or mute the thread https://github.com/notifications/unsubscribe-auth/AASyG0400SO00G5G-oraOq7kFxAdpp6Zks5qm-T1gaJpZM4J0iGT .
bioconda has been a great resource to me. I'd be interested in helping.
Another potential issue to flag, related to #1860 is what to do with packages that were added to bioconda early on but are now upstream. (r-ggplot2, click, others? probably many now). maybe these should be pruned?
Is someone working on upgrading R and Rpy? If so I'll join you. We should make our own TODO-thread for this. I cannot do it alone: someone with a more complete understanding of R, Rpy2, anaconda and its quirks is needed.
I'll try to join if I have time!
This is a great idea!
This is great! I've been wanting to contribute more to bioconda so a sprint like this would be great!
On Wed, Sep 7, 2016, 10:32 Luca Pinello notifications@github.com wrote:
This is a great idea!
— You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub https://github.com/bioconda/bioconda-recipes/issues/2277#issuecomment-245357157, or mute the thread https://github.com/notifications/unsubscribe-auth/AAxNcJSMgpOitwQanGiM9z6ESZ1U3Theks5qnvUZgaJpZM4J0iGT .
I'd like to - might be able to join depending on timing.
I'm a bit behind on Bioconda recent changes however, would need to find out what's been happening.
Down for helping with this!
I might take some time to look at some OS X issues!
Wow, what a great response! Thanks so much!!!! What about the 10th and 11th of October - or do we need a doodle?
That's great for me
On Sun, Sep 11, 2016 at 6:53 AM Björn Grüning notifications@github.com wrote:
Wow, what a great response! Thanks so much!!!! What about the 10th and 11th of October - or do we need a doodle?
— You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub https://github.com/bioconda/bioconda-recipes/issues/2277#issuecomment-246171757, or mute the thread https://github.com/notifications/unsubscribe-auth/AB4sSqGahSWKXnK7RQIVN1BZUO9D3X2Kks5qo8-KgaJpZM4J0iGT .
Best regards, Léo Biscassi
I'm on vacation from 2 to 15. October. If nothing else works, you can of course still do it without me though.
I am really looking forward to this!
What about the 2-3 November? Is this better?
Works for me!
Great for me too! I'm excited!
Is there an agenda? Do we all just choose things we want to contribute?
I see that there are ideas listed. I'll quite happily work on moving the perl to a perl- prefix.
We can use the new project board functionality that github recently integrated!
@bioconda/all let's fix the data for our first online bioconda hackathon: 2-3 November! Looking forward to it!!!!
Managed to choose the exact dates of our national bioinformatics conference - but that's ok :) http://www.abacbs.org/conference/
arg, sorry :( Maybe you can organize a break-out session :)
Another idea for the contribution fest would be to start transitioning generic packages (ex. scala
) from bioconda to conda-forge, now that we're depending on the latter. It would mean we have fewer to maintain, and would also make generic packages more widely available to others.
@tomkinsc please add it to the top post.
Any high priority issues that we should add to the backlog for this sprint?
Two more ideas:
@kyleabeauchamp added. @dkoppstein I think everyone has a different priority list but we will introduce all our ideas and we are happy for every single contribution ... docu, code, recipes, license cleanups ....
For processes that can be automated, I would advocate adding functions to bioconda-utils
so we can easily repeat parts of this effort in the future.
source_url_https <package_name>
— changes urls http://
-> https://
for hostnames known to support TLS (github, etc.)list_sources_without_hash <package_name> [--update_recipe]
— lists packages that include url:
but no md5:
/sha1:
/sha257:
/etc, perhaps with an optional argument to automatically populate hash values: download each source for a package, calculate hashes, and add to the recipe) validate_recipe <package_name>
— a validation function, including https://github.com/bioconda/bioconda-utils/issues/19 and checks of our own: that the license field is populated, that https is used for known TLS hostnames, etc.attempt_version_update <package_name> [--leave_on_build_failture]
— A function to update a recipe and try to build it, where possible. For packages sourced from GitHub, this is a matter of comparing the current version with the most recent release/tag, with an optional function to convert the GitHub tag to the version used by conda (i.e. strip the preceding v
from v1.x
). Not sure how feasible this would be for sourceforge packages. This is in response to #2282. If the build fails after the automated update attempt, the recipe could be rolled back, or left as-is for manual fixes.For each of these, a package name could be provided, or if omitted all bioconda packages would be used.
I plan to go over all PR in the next days and label them. For example see this one: https://github.com/bioconda/bioconda-recipes/pull/2562
We need help from someone who owns a Mac and cares about OSX packages. If we can label PR appropriate we can use this hopefully during our hackathon.
I have a mac and I definitely care about OS X packages - I will participate as much as I can.
I have collected a few issue and tagged them as hackathon
: https://github.com/bioconda/bioconda-recipes/labels/hackathon
Feel free to add more if relevant.
@gregvonkuster thanks!!!
I'm also interested in helping with the OSX packages if I have time! On Sun, 9 Oct 2016 at 14:52, Björn Grüning notifications@github.com wrote:
I have collected a few issue and tagged them as hackathon: https://github.com/bioconda/bioconda-recipes/labels/hackathon
Feel free to add more if relevant.
@gregvonkuster https://github.com/gregvonkuster thanks!!!
— You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub https://github.com/bioconda/bioconda-recipes/issues/2277#issuecomment-252484797, or mute the thread https://github.com/notifications/unsubscribe-auth/AASyGy9RrMCBdNq8hMTk4Z21A221ljARks5qyOOUgaJpZM4J0iGT .
I'm in!
Will try to join you to get a gist on how to give a hand in the future to this project.
I updated the description a little bit and I'm starting to get exited only for days left. Please prepare a bioconda-recipes fork that is working with travis to distribute the work load a little bit. Let me know if you have any questions.
I might have some blocks of time to contribute but I'm probably in a different timezone to most. What time (and timezone) are you planning to start the Hangout / Gitter?
With all the changes that will come in the next weeks and a few open issues concerning the overall quality of our packages I thought about organizing an online contribution fest. Maybe over one or two days, where we all gather together (online) and work on some specific tasks.Our first Contribution Fest will be on the 2-3 November! We will have an IRC channel (maybe gitter?) and a google hangout in place.
We will start with a short presentation of all ideas and try to create small groups to tackle problems small groups. I guess it's a good idea if you fork bioconda-recipes and get your own travis setup up and running so we avoid the travis bottleneck.
Some ideas on what we can work on:
git_url
tourl
Moreover, we have some issue that could be worked on: https://github.com/bioconda/bioconda-recipes/labels/hackathon
PreHack preparation: