Application not compilable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Groundhog Usenet Reader |
New
|
Undecided
|
Unassigned |
Bug Description
Some source fioes seem to be missing in the bazaar repo.
Please add them, I need to build the app to test my french translation,
Plus I'd like to contribute to the code.
Adrian Gruntkowski (adrian-gruntkowski) wrote : | #1 |
Toxico Nimbus (toxn) wrote : Re: [Bug 912958] Re: Application not compilable | #2 |
Le 23/01/2012 04:56, Adrian Gruntkowski a écrit :
> I am not sure if Juanjo drops in here anymore. Indeed the bzr repo is incomplete.
> I have managed to contact with him directly and retrieve the complete code.
> I've done some preliminary cleanup of the codebase, mainly to make it easily
> compilable/
> if you let me know if the project builds for you.
>
> http://
>
> I didn't have time to work on it recently, but I'm planning to get back to it.
> There are one or two really small fixes that I've made to scratch my itch
> (that was the main driving force for me to get my hands on that code).
>
Juanjo did contact me and wrote that he's currently migrating the
project to github. I'll review
your changes and maybe include it in my own fork, which is just intended
to explore a new UI.
I will backport any bugfix to the main project (that is if Juanjo still
supports it) and maybe to yours.
my fork is on
<http://
It's nice to see some interest in the project. I'd like to see it evolve
well.
juanjux (juanjux) wrote : | #3 |
Hi,
@Adrian, I could compile your version and it works perfectly, I tought I
told you so by gtalk.
Since I'm not actively maintaining the project anymore, Adrian told me that
he was interested on maintaining the project so if he is still interested
we could use his repository as main trunk. If @Toxico is interested in
maintaining the project too you could choose one repository as the main one
and just work together (and with me once I go back to read Usenet and
improve the program, which I do from time to time :)
On Mon, Jan 23, 2012 at 8:45 AM, Toxico Nimbus <email address hidden> wrote:
> Le 23/01/2012 04:56, Adrian Gruntkowski a écrit :
> > I am not sure if Juanjo drops in here anymore. Indeed the bzr repo is
> incomplete.
> > I have managed to contact with him directly and retrieve the complete
> code.
> > I've done some preliminary cleanup of the codebase, mainly to make it
> easily
> > compilable/
> nice
> > if you let me know if the project builds for you.
> >
> > http://
> >
> > I didn't have time to work on it recently, but I'm planning to get back
> to it.
> > There are one or two really small fixes that I've made to scratch my itch
> > (that was the main driving force for me to get my hands on that code).
> >
>
> Juanjo did contact me and wrote that he's currently migrating the
> project to github. I'll review
> your changes and maybe include it in my own fork, which is just intended
> to explore a new UI.
> I will backport any bugfix to the main project (that is if Juanjo still
> supports it) and maybe to yours.
>
> my fork is on
> <http://
>
> It's nice to see some interest in the project. I'd like to see it evolve
> well.
>
> --
> You received this bug notification because you are the registrant for
> Groundhog Usenet Reader.
> https:/
>
> Title:
> Application not compilable
>
> Status in Groundhog Usenet Reader:
> New
>
> Bug description:
> Some source fioes seem to be missing in the bazaar repo.
> Please add them, I need to build the app to test my french translation,
> Plus I'd like to contribute to the code.
>
> To manage notifications about this bug go to:
> https:/
>
juanjux (juanjux) wrote : | #4 |
There is the question of how we could do new releases, since the Android
Market key is non-transferable. I see several options:
1. I continue to publish the new versions. It doesn't take much time so I'm
ok with that.
2. The new maintainer get a new Android Market key and start publishing the
program. It will need to change name (something like Groundhog-ng or any
other new name). I would update the description of the old Groundhog entry
in the market to point users to the new project (and make an update so they
see it).
On Mon, Jan 23, 2012 at 7:20 PM, Juanjo Alvarez <email address hidden> wrote:
> Hi,
>
> @Adrian, I could compile your version and it works perfectly, I tought I
> told you so by gtalk.
>
> Since I'm not actively maintaining the project anymore, Adrian told me
> that he was interested on maintaining the project so if he is still
> interested we could use his repository as main trunk. If @Toxico is
> interested in maintaining the project too you could choose one repository
> as the main one and just work together (and with me once I go back to read
> Usenet and improve the program, which I do from time to time :)
>
>
> On Mon, Jan 23, 2012 at 8:45 AM, Toxico Nimbus <email address hidden> wrote:
>
>> Le 23/01/2012 04:56, Adrian Gruntkowski a écrit :
>> > I am not sure if Juanjo drops in here anymore. Indeed the bzr repo is
>> incomplete.
>> > I have managed to contact with him directly and retrieve the complete
>> code.
>> > I've done some preliminary cleanup of the codebase, mainly to make it
>> easily
>> > compilable/
>> be nice
>> > if you let me know if the project builds for you.
>> >
>> > http://
>> >
>> > I didn't have time to work on it recently, but I'm planning to get back
>> to it.
>> > There are one or two really small fixes that I've made to scratch my
>> itch
>> > (that was the main driving force for me to get my hands on that code).
>> >
>>
>> Juanjo did contact me and wrote that he's currently migrating the
>> project to github. I'll review
>> your changes and maybe include it in my own fork, which is just intended
>> to explore a new UI.
>> I will backport any bugfix to the main project (that is if Juanjo still
>> supports it) and maybe to yours.
>>
>> my fork is on
>> <http://
>>
>> It's nice to see some interest in the project. I'd like to see it evolve
>> well.
>>
>> --
>> You received this bug notification because you are the registrant for
>> Groundhog Usenet Reader.
>> https:/
>>
>> Title:
>> Application not compilable
>>
>> Status in Groundhog Usenet Reader:
>> New
>>
>> Bug description:
>> Some source fioes seem to be missing in the bazaar repo.
>> Please add them, I need to build the app to test my french translation,
>> Plus I'd like to contribute to the code.
>>
>> To manage notifications about this bug go to:
>> https:/
>>
>
>
Adrian Gruntkowski (adrian-gruntkowski) wrote : | #5 |
I'm open to either option. The problem I see with option 2. is that existing users may not notice the description change and won't be aware of new updates. @juanjux, are you sure that app is non-transferable in the market (not necessarily the key)? I will try to investigate it.
Adrian Gruntkowski (adrian-gruntkowski) wrote : | #6 |
Found this:
http://
However, it seems that in the process, the old account is removed. Eventually I can cover the switch costs, but I'm not sure if Juanjo would be happy with it (provided that groundhog is the only app in the market on his account). Maybe that can be resolved on per-app basis if that's a partly manual process anyway. I'll drop a mail to support and see how it comes out.
juanjux (juanjux) wrote : | #7 |
Mmm, the problem is that my Market account is my personal google account
(with my gmail, calendar, etc), so I would not want that to be cancelled.
Maybe the Android market account can be untied from the Google account?
Also, I use the google checkout account (which is also tied to everything).
I will open a request here:
http://
Here is the message I sent:
=======
Hi,
I develop an open source usenet reader on Android Market (Groundhog Usenet
Reader). The soft is getting a new maintainer, but we don't have a clear
idea of what steps should be followed to transfer ownership of the project
to the new maintainer without cancelling my Market/
which I use for other things.
Could you help us with that?
Thanks and regards,
Juanjo
=======
On Tue, Jan 24, 2012 at 1:15 PM, Adrian Gruntkowski <
<email address hidden>> wrote:
> Found this:
>
>
> http://
>
> However, it seems that in the process, the old account is removed.
> Eventually I can cover the switch costs, but I'm not sure if Juanjo
> would be happy with it (provided that groundhog is the only app in the
> market on his account). Maybe that can be resolved on per-app basis if
> that's a partly manual process anyway. I'll drop a mail to support and
> see how it comes out.
>
> --
> You received this bug notification because you are the registrant for
> Groundhog Usenet Reader.
> https:/
>
> Title:
> Application not compilable
>
> Status in Groundhog Usenet Reader:
> New
>
> Bug description:
> Some source fioes seem to be missing in the bazaar repo.
> Please add them, I need to build the app to test my french translation,
> Plus I'd like to contribute to the code.
>
> To manage notifications about this bug go to:
> https:/
>
juanjux (juanjux) wrote : | #8 |
Got an automated reply with more info. Looks like the "cancel the old
account to get a refund" part is entirely optional and not required for the
transfer, which is nice since I would like to keep my account (it doesn't
have any monthly or yearly costs).
So once you've registered a new account, tell me the associated email and
I'll reply to that email to initiate the transfer process replying to that
email.
=======
Thank you for contacting us. So we may assist you with your account, please
reply to this email with the information requested below.
Once an account is created, we cannot change the email address or country
for your account. However, we can transfer your apps to a new Google
Account (with a different email address), and refund the registration fee
after you’ve canceled the old account:
1. Edit your current account name. If you’d like to continue to use your
developer name with a new account, you will need to change your current
name in order to free it up for the new account. For example, name the old
account “DeveloperName-
account. Save your settings.
2. Create a second Google Account (with a different email address). After
you’ve created the second account and the corresponding Google Checkout
Merchant account (if you want to sell applications), please select the
appropriate country.
3. After you've registered the newly created Google Account with Android
Market, we can transfer your existing applications to your new account (if
applicable). To do this, please respond to this message including the
following information:
- What you are changing. E.g. email address, country, or ownership of your
developer account.
- The apps you would like to transfer to the new account (please provide
the package name).
- The sign-in email address of the new developer account. (We will verify
ownership at this address).
- Please let us know if you would like us to cancel and refund the old
account.
4. Please note that we cannot transfer applications until the new account
has been created, validated, and the registration fee has been purchased.
We are able to cancel your original account and refund the registration
fee. Once the refund is processed, you will no longer be able to sign in to
the Android Market Developer Console with that account.
=======
On Tue, Jan 24, 2012 at 1:30 PM, Juanjo Alvarez <email address hidden> wrote:
> Mmm, the problem is that my Market account is my personal google account
> (with my gmail, calendar, etc), so I would not want that to be cancelled.
> Maybe the Android market account can be untied from the Google account?
> Also, I use the google checkout account (which is also tied to everything).
>
> I will open a request here:
>
>
> http://
>
> Here is the message I sent:
> =======
> Hi,
>
> I develop an open source usenet reader on Android Market (Groundhog Usenet
> Reader). The soft is getting a new maintainer, but we don't have a clear
> idea of what steps should be followed to transfer ownership of the project
> to the new m...
Adrian Gruntkowski (adrian-gruntkowski) wrote : | #9 |
Ok, done with it. Wow, when I saw that appear on my account it felt like big burden falling on my shoulders :] Hope I will manage to handle it well enough. I will try to fix all the crash situations first (at least the reproducible ones) - that would be first maintenance release. From there we could see where to go feature-wise. Everybody interested in contributing please let me know via github, or eventually email ( adrian dot gruntkowski at [insert gmail dot com domain here] ).
juanjux (juanjux) wrote : | #10 |
You will do fine, I hope you don't have many problems maintining the
source, there are ugly parts (like the threading :] ) but it's pretty
straightforward because usenet is a pretty simple protocol.
On Tue, Jan 24, 2012 at 5:43 PM, Adrian Gruntkowski <
<email address hidden>> wrote:
> Ok, done with it. Wow, when I saw that appear on my account it felt like
> big burden falling on my shoulders :] Hope I will manage to handle it
> well enough. I will try to fix all the crash situations first (at least
> the reproducible ones) - that would be first maintenance release. From
> there we could see where to go feature-wise. Everybody interested in
> contributing please let me know via github, or eventually email ( adrian
> dot gruntkowski at [insert gmail dot com domain here] ).
>
> --
> You received this bug notification because you are the registrant for
> Groundhog Usenet Reader.
> https:/
>
> Title:
> Application not compilable
>
> Status in Groundhog Usenet Reader:
> New
>
> Bug description:
> Some source fioes seem to be missing in the bazaar repo.
> Please add them, I need to build the app to test my french translation,
> Plus I'd like to contribute to the code.
>
> To manage notifications about this bug go to:
> https:/
>
I am not sure if Juanjo drops in here anymore. Indeed the bzr repo is incomplete. deployable. Here's the code if you're interested. It would be nice
I have managed to contact with him directly and retrieve the complete code.
I've done some preliminary cleanup of the codebase, mainly to make it easily
compilable/
if you let me know if the project builds for you.
http:// github. com/zoldar/ groundhog- reader
I didn't have time to work on it recently, but I'm planning to get back to it.
There are one or two really small fixes that I've made to scratch my itch
(that was the main driving force for me to get my hands on that code).