License? about andlytics HOT 17 CLOSED

Good question.

It should be better if Timelappse (the original owner of the code) decides what open-source license give to Andlytics.

I'll try to forward them the question, in case of no response we will try to decide here.

from andlytics.

Thank you for your effort Bruno.

Looking at the fact the widely used frameworks like roboguice and actionbarsherlock use the Apache License 2.0... I would vote for Apache License 2.0 just for compatibility issues license-wise.

• I would like to add the actionbarsherlock top this app in the future :)

from andlytics.

And we have to know if we could use the images in the "open source source code"

from andlytics.

Well I will fork Bruno's master and replace all the graphics with ICS icon work and custom ones I have to create so this shouldn't be an issue in case Bruno will at that point merge my "image changes" :)

from andlytics.

I like the green style. Wold be nice if we could keep it..

from andlytics.

I have to say I thought about blue to complement the ICS styling which completely abandoned the classic Android green. Especially when implementing ActionBarSherlock at some point with a light holo dark actionbar theming. Any comments on that? fda, Bruno, anyone else. I would love to have feedback from all the people contributing to the app at the moment.

from andlytics.

Will try to push a first blue revamped version on Saturday evening. Just fyi in case you guys want to then take look and decide what you think about

from andlytics.

+1 Apache License 2.0 and thanks for maintaining!!

from andlytics.

Ok, I'm assuming "andlytics" is Timelappse's account.

Let it be Apache License 2.0, it seems that's the best solution for us too.

About the graphics, maybe we should consider a brand new look, also because I think only the code can be licensed under Apache 2.0 (please correct me if I'm wrong).

from andlytics.

great! for the graphics I think at least new icons are necessary because not all of them arc cc licensed even though I made most of them myself

from andlytics.

@bruno true, but we will use the official Google Android icon set and will release all custom icons under the same license. So that is fine.

Play account isn't an issue. My idea was to register a new account and pay for it myself. Than I will add you guys as developers, so you all can publish new versions in the market! It isn't community, but you do not want that. It is way better to have "lead developers" who publish new releases and not anyone who is in the mood to do so. For me this is a matter of quality!

For source and release management I will open an organization on github. We then need to transfer your repo to the organisation. I then add you guys to this project and all of you can solve pull requests. This not just one person has to do all the merge work.

Sounds all fine to me, even though it looks like a big process. But it is necessary imho to split the work and being able to have proper releases with a defined feature set and milestones.

Any opinions on this approach?

I think this covers all of our requirements.

from andlytics.

I committed LICENSE and NOTICE files, but since there isn't a company or an official "organisation" ATM, I had to put my name on the LICENSE file.
This will be changed when we will have a better name to put there. Any suggestion on how to solve that?

About the organisation on GitHub, than'ts ok... it is just something I dind't know, or I would have done it from the beginning :) Thanks.

from andlytics.

+1 to the actionbarsherlock implementation, I am using it in all my projects.

from andlytics.

Plus it is on github too :) plus I am using it on my other projects too :)

First thing on my agenda is the new design though to give the users a visual sign regarding the development shift to a larger team working on this. After that I might work on ABS.

from andlytics.

There are some wired copyright comments:

AdmobAuthenticationUtilities.java:
Copyright (C) 2010 The Android Open Source Project

Rotate3dAnimation.java:
Copyright (C) 2007 The Android Open Source Project

I think they should removed?

from andlytics.

Under no circumstances! This would be a copyright violation. I guess @andlytics copied these from the sdk / AOSP Tmaster. This is what you do when you need stuff from newer Android releases and is perfectly normal and fine. But you have to keep the copyright comments.

from andlytics.

Oh damn, I read "Andlytics Open Source Project" ^^

from andlytics.