Closed jasmainak closed 4 years ago
Love the idea
On Tue, May 21, 2019, 5:39 PM Mainak Jas notifications@github.com wrote:
Hi everyone,
@pavanramkumar https://github.com/pavanramkumar and myself have in the past discussed about writing a JOSS paper for pyglmnet.
JOSS articles generally provide a very high level description of the software and its relevance:
Your submission should probably be somewhere between 250-1000 words.
It would allow us to properly point to pyglmnet in citations and get some scholarly recognition for our work.
For this to reach fruition, we need to (checklist will be updated):
- Fix the cdfast solver. Currently it is broken (cf #278 https://github.com/glm-tools/pyglmnet/pull/278, #289 https://github.com/glm-tools/pyglmnet/issues/289).
- Make a new release and update the documentation.
- Create a /paper directory in our repository where we prepare the submission. [see author guidelines https://joss.readthedocs.io/en/latest/submitting.html]
- Get a list of authors. I suggest being liberal -- that is anyone who contributed even one commit is invited to join the list as long as they are okay with it. Of course, it also implies you will use Pyglmnet in your work https://en.wikipedia.org/wiki/Eating_your_own_dog_food
cc @the872 https://github.com/the872 @themantalope https://github.com/themantalope @daniel-acuna https://github.com/daniel-acuna @marquesVF https://github.com/marquesVF @tommyod https://github.com/tommyod @ravigarg27 https://github.com/ravigarg27 @hugoguh https://github.com/hugoguh @BeibinLi https://github.com/BeibinLi @peterfoley605 https://github.com/peterfoley605 @geektoni https://github.com/geektoni @cxrodgers https://github.com/cxrodgers @evadyer https://github.com/evadyer
and of course @koerding https://github.com/koerding and @mshamalainen https://github.com/mshamalainen.
If you have any thoughts / objections, now is the time to voice them. Otherwise, we'll make this happen in the next couple of months.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/glm-tools/pyglmnet/issues/297?email_source=notifications&email_token=AA2XUNO3HG3NLAF5TZMYBBLPWRTXNA5CNFSM4HOO55CKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GVCGMWA, or mute the thread https://github.com/notifications/unsubscribe-auth/AA2XUNOUDYZV2BKKHM7JLSTPWRTXNANCNFSM4HOO55CA .
Great initiative, thanks for cc'ing me. :+1: I can spare a few hours here and there over the next months, so if you want some help reviewing the software/docs/paper feel free to CC me on a PR/Issue. It's nice to work towards something concrete.
Great idea! I will be glad to participate. Thanks for notifying me :+1:
Fantastic; let me know if you need help with reviewing/editing
@DreHar would you mind looking at this PR: #313 ? Thanks a lot!
Hi everyone,
@pavanramkumar and myself have in the past discussed about writing a JOSS paper for pyglmnet.
JOSS articles generally provide a very high level description of the software and its relevance:
It would allow us to properly point to pyglmnet in citations and get some scholarly recognition for our work.
For this to reach fruition, we need to (checklist will be updated):
cc @the872 @themantalope @daniel-acuna @marquesVF @tommyod @ravigarg27 @hugoguh @BeibinLi @peterfoley605 @geektoni @cxrodgers @evadyer
and of course @koerding and @mshamalainen.
If you have any thoughts / objections, now is the time to voice them. Otherwise, we'll make this happen in the next couple of months.