Thank you Roman for an encouragement! No, by no means, it is not required. Issues jsut must be logged in ASF tracker and tagging with "gsoc2015" and they allow to use a ComDev one. See http://s.apache.org/gsoc2015ideas for the full list.
Although Zeppelin has already jira of its own we still in a migration mode with the plan of bulk-transfer issues from GH to Jira after the source code is moved. This will allow us to preserve issue numbers I.e issues/1 will become ZEPPEPIN-1. That is why a ComDev jira was used for now. We will transfer those back to project jira after it is operational. On Sat, Feb 14, 2015 at 9:15 AM, Roman Shaposhnik <[email protected]> wrote: > Great work guys! Quick question though (just for my own edification): > is GSoC requires these to be COMDEV JIRAs? Just curious. > > Thanks, > Roman. > > On Fri, Feb 13, 2015 at 9:56 AM, Alex B. <[email protected]> wrote: > > Those are the GSoC 2015 proposals logged in ASF Jira, related to Zeppelin > > project: > > > > - Leverage Zeppelin to interactive with Kylin > > https://issues.apache.org/jira/browse/KYLIN-591 > > > > - create a Deeplearning notebook tutorial with Zeppelin > > https://issues.apache.org/jira/browse/COMDEV-118 > > > > - frontend: boost test coverage of Angular.js part > > https://issues.apache.org/jira/browse/COMDEV-117 > > > > - frontend: implement new D3 visualisation library > > https://issues.apache.org/jira/browse/COMDEV-119 > > > > > > Please feel free to add\update them. > > > > On Wed, Feb 11, 2015 at 10:22 AM, Alex B. <[email protected]> wrote: > > > >> Dear All, > >> > >> it is this Fri that is deadline when we can apply for with Zeppelin to > >> participate in Google Summer of Code under ASF org. > >> > >> Here is a very rough list of ideas, just for start: > >> - create a Deeplearning notebook tutorial with Zeppelin > >> - backend: implement X interpreter to Zeppelin (R, Python, etc) > >> - frontend: boost test coverage of Angular.js part > >> - frontend: implement new D3 visualisation library > >> - ... > >> > >> I would suggest that we start putting those to ComDev wiki ASAP for > >> visibility purpose, so others can see us interested. > >> > >> Please post more ideas here! > >> > >> -- > >> Kind regards, > >> Alex > >> >
