search

giabaio / BCEA

Bayesian Cost Effectiveness Analysis. Given the results of a Bayesian model (possibly based on MCMC) in the form of simulations from the posterior distributions of suitable variables of costs and clinical benefits for two or more interventions, produces a health economic evaluation. Compares one of the interventions (the "reference") to the others ("comparators"). Produces many summary and plots to analyse the results
https://gianluca.statistica.it/software/bcea/
GNU General Public License v3.0
40 stars 16 forks source link

User contribution guide #11

Open seabbs opened 4 years ago

seabbs commented 4 years ago

Depending on your thinking regarding user contributions it would be really great to have some sort of guidance for how you would like features to be suggested.

I have implemented this as a folder previously (and in the README but other solutions could be equally as good.

Linked to #6

giabaio commented 4 years ago

So far, most of the contributions have either come from my wider "team" (=people and students with whom I work), so it's all been relatively informal. I'm happy to think of a more formal way, if needs be --- or you can simply push requests, especially if we're starting with relatively smaller and less fundamental changes/additions... Of course, happy to go more specific if we're doing something more series - eg by creating projects and assigning tasks etc...

I'm closing this now, but again, discussion can continue.

seabbs commented 4 years ago

My thoughts on this are that one of the great strengths of R is that it is open source and can capture community best practices in an organic way. Lowering the barriers to entry for this - by providing guidelines etc. can make this much easier. It is also community recognized best practice so it may make users trust the package more. The tidyverse are great example of packages that make this easy (https://github.com/tidyverse/dplyr/tree/master/.github).

For example, I imagine that you receive a lot of personal communication about the package but it would be really great to move this into the open (by encouraging the use of GitHub etc.). Having said that I do see some of this in the issues here so that is good. In a similar vein having the future work centralized somewhere (i.e GitHub issues) with clear guidelines for how to contribute would make it much easier to know how to give back.

I typically list all future work on GitHub for packages and have had users do the work before I could get to it (which for dull things like docs is very nice!). So there is also a time-saving element :).

Would you be happy for a pull request based on the example I linked above?

giabaio commented 4 years ago

Yes.

n8thangreen commented 1 year ago

closed