IMO, each of them could be a two-three month project. The project itself could be conceptually simple and has a relatively small scope, but we probably should lift the exit bar. Here are my thoughts for the exit criteria: 1. the feature reliably works for all edge cases; 2. the implementation does not hack things, which can result in general-purpose refactoring of other modules; 3. there are regression unit tests and integration tests along with the code; 4. the code is carefully reviewed by 1-2 committers.
Getting sth. done as a proof-of-concept and then disappearing doesn't seem a very effective approach..:-) Best, Yingyi On Tue, Jan 31, 2017 at 9:07 PM, Steven Jacobs <[email protected]> wrote: > Do you think these could be a single project (dataset improvements)? I'm > wondering about whether one alone would be a full two-three month project. > Steven > > On Tue, Jan 31, 2017 at 9:00 PM Yingyi Bu <[email protected]> wrote: > > > I have two proposals for data loaders: > > > > 1. add AWS S3 as an external data source; > > 2. support POSTing a user file on the client side through HTTP into an > > internal dataset. > > > > Thanks! > > > > Best, > > Yingyi > > > > > > On Thu, Jan 19, 2017 at 2:06 PM, Steven Jacobs <[email protected]> wrote: > > > > > Hi All, > > > The Google Summer of Code official start email was sent out today. This > > can > > > be a useful opportunity for us as an Apache software. We will probably > > want > > > to look at potential Asterix projects to suggest for student proposals. > > > Steven > > > > > >
