[guardian-dev] Forking APG

Hans-Christoph Steiner hans at guardianproject.info
Mon Mar 12 13:09:02 EDT 2012


Sounds like you want to do more than just apply some patches to APG.  Perhaps it makes sense to name the app something different since you'll be changing the APIs.

.hc

On Mar 12, 2012, at 12:42 PM, Dominik Schürmann wrote:

> Thanks for your response.
> 
> I think you are partially right. I was too fast with releasing it to the
> Market. I deactivated it their.
> Instead you can download it here:
> https://github.com/dschuermann/apg/downloads
> 
> I sent thialfiar a email 3 days ago informing him about my fork.
> 
> I forked instead of branching because of several reasons:
> - there exists branches and repositories with code that was never merged
> back
> - I am breaking compatibility to redesign some APIs
> - and of course use github/gitorious instead of google code :D
> 
> Regards
> Dominik
> 
> 
> On 12.03.2012 17:12, Nathan of Guardian wrote:
>> On 03/12/2012 11:50 AM, Dominik Schürmann wrote:
>>> A small progress update on my fork: 
>>> I released the first version to Google Play:
>>> https://play.google.com/store/apps/details?id=org.apg
>> 
>>> My mantra is: Release early and often.
>> 
>> Sounds good. Perhaps you should post test builds to:
>> https://github.com/dschuermann/apg/downloads before you push something
>> to the market?
>> 
>> That is generally our approach, where you at least have a few RC's
>> before giving it to the world. Now users on the market will see APG and
>> APG+ (Beta), and might be confused which to get. It also means that I
>> have to reimport all my keys into your app, correct?
>> 
>>> This first version is mainly the beginning of a new user interface for APG.
>>> I also realized that signing keys, uploading keys, and qr code scanning
>>> was already available in one of the repositories I merge into the fork.
>>> Especially these features seems to be a little buggy. I will concentrate
>>> on those after the user interface.
>> 
>>> As always: I encourage other devs to participate:
>>> https://github.com/dschuermann/apg
>> 
>> Have you reached out to thi at thialfihar.org at all? Why not just submit
>> patches and merge into a branch of
>> http://code.google.com/p/android-privacy-guard/ instead of forking his
>> project? You have every right to of course, and you are obviously giving
>> proper credit, but I would just think a bit more about the full
>> lifecycle of APG perhaps, especially since you are pushing releases to
>> the Play Store.
>> 
>> I know he isn't the most responsive individual, but up until September
>> 2011, he was still making updates to his repo.
>> 
>> Please understand I support your efforts greatly, I just know that when
>> someone comes out of the blue and says "I am going to fork Gibberbot and
>> make it go XYZ feature" that I tend to not feel very happy about that,
>> wishing instead they would submit a patch or pull request, and be part
>> of our big happy dev family.
>> 
>> Best,
>> Nathan
>> 
>> _______________________________________________
>> Guardian-dev mailing list
>> 
>> Post: Guardian-dev at lists.mayfirst.org
>> List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev
>> 
>> To Unsubscribe
>>        Send email to:  Guardian-dev-unsubscribe at lists.mayfirst.org
>>        Or visit: https://lists.mayfirst.org/mailman/options/guardian-dev/dominik%40dominikschuermann.de
>> 
>> You are subscribed as: dominik at dominikschuermann.de
> 
> 
> _______________________________________________
> Guardian-dev mailing list
> 
> Post: Guardian-dev at lists.mayfirst.org
> List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev
> 
> To Unsubscribe
>        Send email to:  Guardian-dev-unsubscribe at lists.mayfirst.org
>        Or visit: https://lists.mayfirst.org/mailman/options/guardian-dev/hans%40guardianproject.info
> 
> You are subscribed as: hans at guardianproject.info



More information about the Guardian-dev mailing list