> > > > 1) Would they like to merge R4ML code into the main SystemML project > ALOK: In R we have to follow a pattern dir structure. we might be able to > create more R pacakges. There will be a sub dir in systemML called R or > something > in that subdir there will be subdir R4ML (one R pacakge) in future more R > pacakge as subdir (more details later) > > > itself? (Currently we have no modules.) > > 2) What would they like to merge? > ALOK see 1) > > 3) If so, how do they propose to do so? > ALOK: will explain in future proposal email > > > 4) Who will do the majority of the work to add R4ML code to SystemML? Or > > who would like to volunteer to do this? > ALOK: I will do majority of work > > 5) Who will maintain the contributed code? Or who would like to volunteer > > to do this? > ALOK: Alok and Brendan will maintain. > > 6) Documentation is needed (fit in SystemML documentation framework). > ALOK: as Brendan pointed out R docs are different and we will take care of > it . it is self contained > > > 7) Testing is needed (fit into SystemML testing framework). > ALOK: testing will usually by the maven system command exec where it just > calls > cd <somesubdir> ; ./bin/install_all > > 8) How is this packaged? > ALOK:subdir > >
I think offering to add R4ML to SystemML and to maintain the codebase is great. I think that addresses a couple of the main issues (how to get the code into the project and how to maintain it). Deron
