[Picante-devel] New developer and manuscript plans

[Matthew R. Helmus]

I think that is a great idea and it sounds fair. I am happy to 
contribute manuscript text and images on all the code I have written.

Now for some rambling open ended questions that maybe we can think about:

Do we want to start with an outline being passed around? Do you have a 
target journal in mind? Is it the same journal that Steve wrote his 
phylocom article? Would NESCent perhaps pay for open access since Peter 
and I were funded through them/Google this summer... perhaps Hilmar 
would know? Would we include examples of all the functions or just 
highlight some functions?

No answers needed now, but we should keep the Qs in mind as we go about 
this.

Matt

PS Nice work on your PNAS paper Helene!



Steven Kembel wrote:
> Hi all,
>
> Helene Morlon, a postdoc at the University of Oregon, is joining the  
> picante developers and will be adding some functions to calculate  
> measures of phylogenetic beta diversity. Welcome Helene!
>
> I have received several requests from picante users who want a way to  
> cite the package. I would like to begin preparing a manuscript  
> describing the picante package for publication as an application note  
> in a bioinformatics journal. We should look into publication funding  
> options since I think it would be good to publish in an open-access  
> journal. My suggestion is that everyone who has contributed code to  
> the package should be included as an author on the manuscript, but  
> that the developers will be first authors in order of the magnitude of  
> their contributions to the package and/or manuscript, and that we will  
> note this in the manuscript. Does this sound fair? I'll get in touch  
> with developers individually in the near future to discuss further.
>
> Best,
> Steve
> _______________________________________________
> Picante-devel mailing list
> Picante-devel at lists.r-forge.r-project.org
> https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/picante-devel
>
>