On Wednesday, April 24, 2013, Dishara Wijewardana wrote: > On Tue, Apr 23, 2013 at 3:59 AM, Ian Boston <[email protected] <javascript:;>> > wrote: > > > Hi Dishara, > > The diagram looks good and summarises how resource providers are > integrated > > into the resources resolver. Obviously there is a little more detail in > > reality, but its a good overview. > > > Thanks Ian for the feedback. > With that diagram I have just submitted my one and only GSoC 2013 project > proposal to Google ;-).
Good. Don't forget to state that this is your only GSoC 2013 submission in the proposal, and to declare if you will be doing anything other than your studies during the time period. Of importance are other part time jobs, studies and exams. Part time jobs are not allowed by GSoC which requires your full attention. Studies and exams clashing with the GSoC timescales are an unfortunate feature of the GSoC programme being based on the US academic year. I have worked with students who were also doing finals, and managed to achieve excellent project outcomes, (and an outstanding final degree result) but any conflicts need to be declared up front, so that the mentor and the student can plan around them. If your studies are active during GSoC then you should also let your academic staff know that you are taking part. If you could declare that information in the proposal, including if there are no conflicts, then they will strengthen your proposal. Best regards Ian > > > > > Ian > > > > On Tuesday, April 23, 2013, Dishara Wijewardana wrote: > > > > > Hi Ian, > > > Here [1] I have attached the high level architecture diagram of the > > > cassandra back end implementation for Sling to the JIRA. Please let me > > know > > > if there is any concerns so that I can use this diagram to the > proposal. > > > > > > [1] - > > > > > > > > > https://issues.apache.org/jira/secure/attachment/12579842/Sling%20Cassandra%20backend%20Architecture.jpg > > > > > > On Sat, Apr 13, 2013 at 4:29 PM, Ian Boston <[email protected]> wrote: > > > > > > > Hi, > > > > The breakdown looks good, but I think you should aim to keep the > > > > implementation in Cassandra simple to start with and not > underestimate > > > how > > > > much time it may take to implement both read/write and access control > > on > > > > read/write. No need to change the plan or be too specific at this > > stage. > > > > > > > > Best Regards > > > > Ian > > > > > > > > > > > > On 12 April 2013 23:24, Dishara Wijewardana <[email protected] > > > > > > wrote: > > > > > > > > > Hi Ian, > > > > > I am in the process of writing the proposal. So as you mentioned > > > earlier > > > > it > > > > > is better to split this in to 4 sub tasks and 2 before midterm and > 2 > > > > after > > > > > mid term. > > > > > > > > > > So in summary I would like to add the subtasks that I feel. Please > > add > > > > > anything I am missing or anything required to have. > > > > > > > > > > Main tasks overview: > > > > > 1. Implementing a CassandraResourceProvider to READ from > Cassandra. > > > > > Implementation Details [1] > > > > > 2. Test with one node Cassandra cluster end to end with the > > > > implementation > > > > > of #1. > > > > > 3. Enhance CassandraResourceProvider to READ with access control > > (with > > > > > latest security related APIs). > > > > > 4. Enhance CassandraResourceProvider(or may be a new interface for > > > > writing > > > > > i.e CassandraPopulator) to WRITE and WRITE with access control. > > > > > > > > > > Here as I feel, #1 and #2 completion will more weight and > relatively > > > more > > > > > time consuming than #3 and #4 (I am not aware of the complexity of > > > > > incoperating the access control to READ/WRITE). > > > > > > > > > > Appreciate your valuable feedback on this, whether this task > > breakdown > > > is > > > > > appropriate or not suits to the GSoC time line or anything more to > > > > > add/remove and etc ? > > > > > > > > > > [1] : Implementation Details: > > > > > > > > > > - Write a CassanrdaResourceProviderUtil which is basically a > > cassendra > > > > > client which will facilitate all cassandra related operations > > required > > > by > > > > > other modules (CassandraResourceProvider and > > > CassandraResourceResolver). > > > > > > > > > > - Implementation of CassandraResourceProvider > > > > > > > > > > - Implementation of CassandraResourceResolver > > > > > > > > > > - Implementation of CassandraResource > > > > > > > > > > > > > > > On Sun, Apr 7, 2013 at 3:27 PM, Ian Boston <[email protected]> wrote: > > > > > > > > > > > On 7 April 2013 14:07, Dishara Wijewardana < > > [email protected]> > > > > > > wrote: > > > > > > > > > > > > > On Sun, Apr 7, 2013 at 3:00 AM, Ian Boston <[email protected]> > > wrote: > > -- > Thanks > /Dishara >
