App cannot launch and only available in AU app store?

[dzulhelmi]

I bought this app, the website is not helpful, left abandoned. Now the app cannot be launched from my mac. No support at all?

[csmu-cenr]

What operating system are you using?

[studgeek]

I'm not the original reporter, but I am on 10.6.8.

If I follow the link from http://www.macupdate.com/app/mac/31472/pomodoro/ I get to the message "the item you've requested is not currently available in the US store". I'll add even though I am 10.6 I can still see other 10.7 apps in the ap store.

If I follow the developers link I see the problem I reported in #274.

[pitkali]

Yeah, I believe the application is stil available in Australian store only. Generally it looks abandoned.

Fortunately enough, it's open source. I've already fixed the bug with voice selection that hurt me, and some other cleaning on todo list. I was not able to find other application so well suited to my goals.

[csmu-cenr]

It's not available in the Australian Store.

[pitkali]

Curious. The point still stands though—it looks abandoned. I'm fine with it, actually, as long as features go, because it has all I need. I'm only somewhat worried that one day Apple will shut down all the deprecated API calls it is using :)

[studgeek]

Since he is not accepting pull requests either should we switch to a different owner who can add co-owners to bring in those requests, update the local doc, generally keep it at least breathing?

On a related note, does anyone have copies of the original documentation? I can get the top-level from the wayback machine, but the detailed help are not in there.

[studgeek]

Actually, he is actually active (as of May) in ugol/cocos2d-iphone, so he just isn't paying attention to this project anymore. Perhaps we can convince him to add a couple more project admins to keep it going while he focuses on his new project.

[csmu-cenr]

Good idea.

[pitkali]

Agreed.

[studgeek]

I just got an email from Ugol. He does plan to continue the project, but is in a busy time right now and also is dealing with some TM issues around the Pomodoro name. I did encourage him to add someone to help with developer pull requests and so forth. I told him he can do that and still own the official releases of course....

[pitkali]

Superb!

[studgeek]

Well superb if something happens...

[francof]

so, no news?

[AlekSi]

@ugol

[spaceland-zz]

Anyone want to publish a build of this for us n00bs?

[partlyhuman]

Also put some related comments on #274

[studgeek]

@partlyhuman, I don't really have any more info from @ugol than I posted above. We just exchanged a couple emails on 7/10/12. He said he had a cease&desist from Francesco Cirillo, but was too busy with a job change to do take action on it. Haven't connected with him since then.

He did suggest he might be willing to bring on a co-maintainer...

[partlyhuman]

Yeah, co-maintainer or not, I would just want to know what specific steps should be done, and someone can do them. I have heard that the tomato timer icon is trademarked or somesuch - simple enough solution: create a new icon. But what's this about the Pomodoro name, is that trademarked too? Is that so? Should we simply change the name of the app? Or would we have to remove every mention of the word "Pomodoro"? Or add some language to the about box? Could you glean any of this from the email exchange?

[partlyhuman]

Ugh, I guess we just need to conform to all this http://www.pomodorotechnique.com/trademark-guidelines/ If anyone is brave enough to parse the legalese and find out specific concrete steps we would need to take and file them as issues I can help do them.

[ugol]

Yep, basically it's only:

• remove the icon
• change the app name
• remove every reference to "Pomodoro", we can only say "The Pomodoro
  Technique", with the TradeMark icon.
• refresh every linked library
• be sandbox friendly (scripting is not, at the moment)

I have a new clock icon but I don't like it very much, if there is any
volunteer able, it will be highly appreciated. Something fruit related
should be ok:
cucumber, banana, etc...

Ah, and Cirillo said it must not be something RED, or that would be enough
to violate the TM. I think a lawyer will laugh at that, but hey, I don't
want to spend 1k$ per hour just to scratch an itch

On Tue, Feb 12, 2013 at 11:15 PM, Roger Braunstein <notifications@github.com

wrote:

Ugh, I guess we just need to conform to all this
http://www.pomodorotechnique.com/trademark-guidelines/ If anyone is brave
enough to parse the legalese and find out specific concrete steps we would
need to take and file them as issues I can help do them.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/272#issuecomment-13462431.

uL

Pragmatist
http://blog.ugolandini.com
http://www.flickr.com/photos/ugol/

[studgeek]

The first 3 are for Pomodoro trademark issues and the last 2 are for App
Store, right? I would hate to give up the scripting in all forms.

d

On 2/12/13 3:37 PM, ugo landini wrote:

Yep, basically it's only:

• remove the icon
• change the app name
• remove every reference to "Pomodoro", we can only say "The Pomodoro
  Technique", with the TradeMark icon.
• refresh every linked library
• be sandbox friendly (scripting is not, at the moment)

I have a new clock icon but I don't like it very much, if there is any
volunteer able, it will be highly appreciated. Something fruit related
should be ok:
cucumber, banana, etc...

Ah, and Cirillo said it must not be something RED, or that would be
enough
to violate the TM. I think a lawyer will laugh at that, but hey, I don't
want to spend 1k$ per hour just to scratch an itch

On Tue, Feb 12, 2013 at 11:15 PM, Roger Braunstein
<notifications@github.com

wrote:

Ugh, I guess we just need to conform to all this
http://www.pomodorotechnique.com/trademark-guidelines/ If anyone is
brave
enough to parse the legalese and find out specific concrete steps we
would
need to take and file them as issues I can help do them.

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/272#issuecomment-13462431.

uL

Pragmatist
http://blog.ugolandini.com
http://www.flickr.com/photos/ugol/

—
Reply to this email directly or view it on GitHub
#272 (comment).

[kfdm]

The Growl project is working on some scripting additions for their next release.
http://code.google.com/p/growl/issues/detail?id=535&

Enter NSUserAppleScriptTask, new to 10.8, it provides an asynchronous, sandbox friendly way of running AppleScript's, and handling the responses from them. This has made it possible, and very easy to leverage the power of AppleScript to provide users with a rules system where they can make any arbitrary rule they want, and we don't have to figure out how to display it, how to handle its backend, etc.

...

Some background info on NSUserAppleScriptTask (and its parent/cousins). The scripts the user wishes a sandboxed app to use must go in the blessed folder, ~/Library/Application Scripts/<code signing id>/ The sandboxed app may not write to this folder, but it may read from it. These scripts are executed by a system helper process, outside of a sandbox, and the return value comes back to growl asynchronously. The scripts can block if the user needs them to without affecting other notifications, as each rule evaluation is handled separately.

Though I don't know if that applies as directly to this project or not. I'm not sure if that would exclude too many people that are not comfortable with moving files around their machine or not.

[ugol]

Yes, using NSUserAppleScriptTask could be a a way to circumvent the issue,
but probably that means you can't anymore edit your script directly inside
pomodoro...

On Wed, Feb 13, 2013 at 4:13 AM, Paul Traylor notifications@github.comwrote:

The Growl project is working on some scripting additions for their next
release.
http://code.google.com/p/growl/issues/detail?id=535&

Enter NSUserAppleScriptTask, new to 10.8, it provides an asynchronous,
sandbox friendly way of running AppleScript's, and handling the responses
from them. This has made it possible, and very easy to leverage the power
of AppleScript to provide users with a rules system where they can make any
arbitrary rule they want, and we don't have to figure out how to display
it, how to handle its backend, etc.

...

Some background info on NSUserAppleScriptTask (and its parent/cousins).
The scripts the user wishes a sandboxed app to use must go in the blessed
folder, ~/Library/Application Scripts// The sandboxed app may not write
to this folder, but it may read from it. These scripts are executed by a
system helper process, outside of a sandbox, and the return value comes
back to growl asynchronously. The scripts can block if the user needs them
to without affecting other notifications, as each rule evaluation is
handled separately.

Though I don't know if that applies as directly to this project or not.
I'm not sure if that would exclude too many people that are not comfortable
with moving files around their machine or not.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/272#issuecomment-13472574.

uL

Pragmatist
http://blog.ugolandini.com
http://www.flickr.com/photos/ugol/

[partlyhuman]

Thank you for the info @ugol ! I think @studgeek is on the right track: getting the app to not piss off Cirillo's lawyers and getting the app ready for App Store distro are two separate goals.

If I can suggest a plan of attack:

1. convert the items enumerated in your comment into issues
2. categorize these issues into App Store Readiness issues and Trademark issues
3. you may assign the Trademark issues to me (unless another contributor really wants them!)
4. @ugol come up with a new name for the app, or open it up to discussion, it is of course your app to name! 👌

[pitkali]

Actually, refreshing dependencies is not just App Store readiness, but sane regular maintenance practice ;)

[bbirand]

Hi all, Is there any progress on this front? Is there a fork that distributes binaries under a different name? Is there still interest in this?

[pitkali]

Personally, I had no time to look into it.