I am wondering what would be a fully proper way (if any) of:
creating a public clone of ODK collect
renaming it to XXX ODK collect
making some changes and additions to the code
changing its package name
publishing it on the market under the XXX ODK collect
of course leaving all original references to ODK collect while at the
same time publishing all changed code publicly again (hopefully
contributing some of it back to ODK as well).
according to the apache license, you are allowed to do whatever you
want. what we would prefer is the following...
make a server side clone on google code or bitbucket or whever. make
any changes to the source (including to the package name). as per the
license leave the copyright intact. also, we'd love it if you leave as
many pointers to the odk website and brand as you feel is reasonable.
we've been telling people to add "odk" in the name and "powered by
open data kit (odk)" or something similar in the market description so
people can search for odk and find all the related apps. i think
calling it x odk collect is probably confusing to users, but x odk
seems fine. if you have an accompanying site, it'd also be nice to add
links (and logos) back to the odk website.
if you are earning money off odk, we do accept donations to support
continued development at http://opendatakit.org/participate/donate.
without donations, we simply cannot continue to write code and answer
emails.
again, the bottom line is that you are free to do whatever, but we
trust that our users will do the right thing. anyway, thanks for
asking and good luck with your app!
yaw
···
On Sat, Sep 3, 2011 at 15:54, rok wrote:
> Hi,
>
> I am wondering what would be a fully proper way (if any) of:
> 1. creating a public clone of ODK collect
> 2. renaming it to XXX ODK collect
> 3. making some changes and additions to the code
> 4. changing its package name
> 5. publishing it on the market under the XXX ODK collect
>
> of course leaving all original references to ODK collect while at the
> same time publishing all changed code publicly again (hopefully
> contributing some of it back to ODK as well).
>
> Cheers
> Rok
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
>
Indeed we plan to leave references to ODK collect inside the app since
we have no reason for hiding them. Hopefully we can contribute back
something as well and as we start making money, make a donation as
well. We've changed the package name and published it on the Android
Market as well.
···
On Sep 3, 6:10 pm, Yaw Anokwa wrote:
> hi rok,
>
> according to the apache license, you are allowed to do whatever you
> want. what we would prefer is the following...
>
> make a server side clone on google code or bitbucket or whever. make
> any changes to the source (including to the package name). as per the
> license leave the copyright intact. also, we'd love it if you leave as
> many pointers to the odk website and brand as you feel is reasonable.
>
> we've been telling people to add "odk" in the name and "powered by
> open data kit (odk)" or something similar in the market description so
> people can search for odk and find all the related apps. i think
> calling it x odk collect is probably confusing to users, but x odk
> seems fine. if you have an accompanying site, it'd also be nice to add
> links (and logos) back to the odk website.
>
> if you are earning money off odk, we do accept donations to support
> continued development athttp://opendatakit.org/participate/donate.
> without donations, we simply cannot continue to write code and answer
> emails.
>
> again, the bottom line is that you are free to do whatever, but we
> trust that our users will do the right thing. anyway, thanks for
> asking and good luck with your app!
>
> yaw
>
>
>
>
>
>
>
> On Sat, Sep 3, 2011 at 15:54, rok wrote:
> > Hi,
>
> > I am wondering what would be a fully proper way (if any) of:
> > 1. creating a public clone of ODK collect
> > 2. renaming it to XXX ODK collect
> > 3. making some changes and additions to the code
> > 4. changing its package name
> > 5. publishing it on the market under the XXX ODK collect
>
> > of course leaving all original references to ODK collect while at the
> > same time publishing all changed code publicly again (hopefully
> > contributing some of it back to ODK as well).
>
> > Cheers
> > Rok
>
> > --
> > Post: opendatakit@googlegroups.com
> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> > Options:http://groups.google.com/group/opendatakit?hl=en