Andrew Swerlick | 20 Aug 04:11

[Chandler-dev] Feature Suggestion, Project Notes

Hey all,

I've been using Chandler for about a week, and really loving it. It's definitely helped me get organized.

I have a feature suggestion though, a fairly major one, so it may not be something you're interested in implementing but I thought I'd pass it along. Basically I think it would be useful to have a special type of note called a "Project Note." Project Notes would only show up in their own Project section, available by clicking on an icon on the top menu bar. They would be no different from regular notes, except they wouldn't have a triage status.

Then what users could do is associated specific normal notes with a project note. Then when they clicked on that note, the project note would also show up in the sidebar. I've attached a screenshot mockup.

Here's the user justification for this, using an example from my own life. I had a tree fall on my house recently, so I've got lots of tasks related to working with the insurance agency. Even though each of these tasks is different there's alot of persistent information across all of them. My claim number, my agents phone number, my contractors phone number, the contractors estimate, the insurance estimate, etc. It would be nice if I could tell Chandler that all the notes I create to deal with this are "Tree Damage" Notes. Then I could have all that information stored in the "Tree Damage" Project note, and I could view it from the details section of every note I create.

The basic idea is to help store information that is persistent across a number of notes, instead of copying again and again. What do you think?

~Andrew S.

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
Mimi Yin | 20 Aug 02:08

[Chandler-dev] [Proposal] Fixes for Chandler 1.0.1

Release date: If we are rolling monthly releases, is a release date of Tuesday September 9th realistic?

MUSTFIX - Bug 12306
I. Increase the timeout period to 5 minutes (from 40 seconds)?
II. Improve error messages and add links to the newly updated Troubleshooting page for the email dialogs mocked-up below.


NICE-TO-HAVE USABILITY FIXES
Bug 12318 Rename "Tools" menu --> "Debug" and do something with "Plugins" menu
-- Rename Tools menu --> Debug
-- Hide the Plug-ins menu under new Experimental section at the bottom of the Debug menu. OR Remove it completely.

- Jeffrey's fix for the URL problem reported here: http://lists.osafoundation.org/pipermail/chandler-users/2008-August/002535.html (Don't have a bug number for this, but Jeffrey has already created a patch for it. Jeffrey, is this something that needs to be tested? Is it risky to include this change?)

These are the issues I've nominated. Are there others that should be put up for consideration? Here is the list of un-targeted bugs: http://tinyurl.com/38okzm

One issue I'm concerned about is: Chandler hangs at 10%: Opening Data and then Quits
But I think it's still to early to tell how widespread the problem is.

Mimi

=====

1. Error: Time out error.
*****
Attempt to sync '%(hostName)s' timed out after 5 minutes. Server not responding.

Troubleshoot [Cancel] [Edit Account Settings...]
*****

2. Configure Chandler Folders.
*****
Configure Chandler Folders
-----

The following folders have been created in your account:

<p>Chandler Mail - Add messages here to download them into Chandler as mail.
<br>Chandler Starred - Add messages here to star them.
<br>Chandler Events - Add messages here to put them on the calendar.

<p>Note: Messages will appear in Dashboard, In and Out accordingly.
<br>Note: Folders make take a while to appear in your email application.

Folders not showing up? [Close Window]
*****

3. Remove Chandler Folders
*****
Remove Chandler Folders
-----

The following folders have been removed from your account:

<p>Chandler Mail 
<br>Chandler Starred
<br>Chandler Events

Folders not showing up? [Close Window]
*****
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
Mimi Yin | 19 Aug 22:03

[Chandler-dev] [Proposal] Criteria for fixing 1.0 Desktop issues

Last week we met to discuss Post 1.0 priorities. Stay tuned on our blog for more detailed posts on planning. In the meantime, here's a brief summary of where we're headed. Going forward, we are shifting developer focus to:

1. iPhone apps and building out UI for configuring and receiving notifications from Chandler Hub.

2. Desktop re-architecture project to address performance issues as well as to improve overall stability, testability and ease of maintenance.

3. Building developer community.

We will continue to support the existing 1.0 Desktop on an as-needed basis, but our primary goal for the Desktop is to shift project momentum to the re-architected Desktop as soon as possible.

We anticipate rolling monthly releases to fix critical bugs (e.g. Chandler won't start, I can't get my data into Chandler, I can't sync to Chandler Hub, etc) as well as addressing frequently reported usability issues (e.g. What's the Tools menu for? Looks scary.)

Proposed criteria for nominating issues as "Must Fix" for 1.0 Desktop:

1. Issue has a proven history of being a problem. This means many users reporting the problem over a prolonged period of time. (Let's say half a dozen reports over a period of at least 1 month? The significance of the # of reports will change as the size of our user population changes.)

2. Issue is a blocker for users to get started with Chandler (e.g. App won't download / start. Can't get my data into the app. Can't share.)

3. Issue has a clearly spec'd out, low-risk fix, where low-risk means fix requires minimal testing and very unlikely to introduce new bugs. As a default, let's say issue is fixable with 1/2 day's work. (With the caveat that this will vary depending on severity of the problem.)

To clarify, these are criteria for nominating issues we "Must Fix". Meaning issues that meet these criteria justify rolling a new release. Once we have a "Must Fix" issue, I imagine that other smaller fixes will tag along, assuming they are trivial to fix and don't require a lot of testing.

Caveat: This is our first try at nailing down criteria for nominating "Must Fix" bugs. We will be revisiting the viability of this proposal on a regular basis and adjust accordingly.

****

Given these 3 criteria, we have nominated and approved our first 1.0 Desktop issue: Users have trouble setting up Chandler IMAP folders. I will sending out a summary of the proposal for the fix.

Mimi
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
Grant Baillie | 19 Aug 21:33

[Chandler-dev] Building Chandler on windows with a more recent Visual Studio

This came up during today's checkin: Jeffrey mentioned that we should  
see if Chandler can be built using a free (or definitely more recent)  
version of Microsoft Visual Studio. Currently, we run MS Visual  
Studio .Net 2003 on the build machines.

As Jeffrey mentioned, Heikki looked into this a while back, and it  
turns out he documented what he did extensively (Thanks, Heikki!):

+ wiki summary: http://chandlerproject.org/Journal/VisualC2005ExpressEdition
+ bug with more detail: https://bugzilla.osafoundation.org/show_bug.cgi?id=5671
   (see also the 2 "Depends on" bugs, 1 of which is fixed)
+ short dev list thread: http://markmail.org/message/ughue52fb5ktnfbf

The upshot seems to be:

+ there were some DLL issues to solve (though it's possible those have  
been mitigated by the PyLucene switch to openjdk)
+ some optimization ("performance guided optimization") is not  
available in the free version.

Anyway, this makes me thing going down this path is a bit of a can of  
worms for now ...

--Grant
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev

Mimi Yin | 19 Aug 20:42

[Chandler-dev] Check-in 8/19/2008

sheila
- board-related work
- meetings and phone calls
- change our bylaws wrt board - need to follow up with lawyer
- pls respond to thread re: 1.0 build on strategy list
- IMAP issue, when do we fix it by?

* mimi - need to clarify how quickly we should respond to 1.0 issues

mimi
- more board-related meetings today
- started discussion re: user advisory group on strategy (writing up notes)
-- spurred more thoughts on projects for user advisory group in the next 3 months
-- set up web forum
-- set up troubleshooting page
-- set up "feature gallery" some way for users to vote for features and bugs (basically user surveys)
- as well as more thoughts on post 1.0 build / release cycle
- received invitation to speak at Non-profit Software Dev event, any objections to going?

* Mimi - ideas for stuff Randy should work on? email gateway, etc?
- Randy write up blog post re: data in/out stuff that server supports
* Jared - add your ideas in?

- today: did a lot of catching up on users list

- need to fix osaf website

grant
- responding to users list issues
- making good progress on re-arch roadmap stuff now

jared
- hub backup broke
- interim fix in place that let's hub continue with backup
- ignore the root issue for now

- last night, hub lost a disk
-- need to investigate and repair
- wiki lock-out issue

- trying to talk to ISC - swapping machines, etc
-- not getting a response, might need to find another contact

* sheila - what's our contigency plan?
* jared - we can stay in co-lo for now

* jared - re: 1.0 desktop build
- would like to prioritize shutting down tinderbox for builds
- need to figure out a way to produce builds first
- grant volunteered to host build machine

* next action - Jared develop a plan for shut-off with Grant and others

jeffrey
- board-related mtg yesterday
- very ugly iPhone UI things happening
- blocked on using interface builder - chat with Grant a bit

_______________________________________________
strategy mailing list
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
Jared Rhine | 16 Aug 01:10

[Chandler-dev] Problems sharing Sharing Activity collection

I've just opened:

   https://bugzilla.osafoundation.org/show_bug.cgi?id=12312

Problems occur when Chandler Desktop users publish the Sharing  
Activity collection.  Besides being kinda a weird thing to publish,  
there's a behavior where backslashes in items in that collection get  
doubled each time the collection syncs.  This has caused some items on  
Chandler Hub to have bodies of 8Mb.

The real production issue is that the 8Mb bodies have broken the  
ability to create standard MySQL backups of Chandler Hub.  I  
originally assumed someone just published a big item and was going to  
bump a parameter to allow larger backups but then I found the  
backslash-doubling problem.  Pasting Grant's description of how the  
backslash problem originates:

-----

When you sync, a NoteRecord gets added to that collection, containing
basically the log file text for the sync.
That log file text contains quotes (the theory is you could
paste it into a python interpreter)
But, because we then go and sync that collection, we add a
NoteRecord (for the original sync).
That NoteRecord will quote one extra level (so as to
reproduce the singly quoted text we sent to the server)
That new NoteRecord will then get synced to the server next
time around
And so we will create a new NoteRecord in Sharing Activity,
which will have one extra level of syncing

-----

So basically the root cause is Chandler escaping backslashes in log  
files coupled with Sharing Activity log entries being posted to  
Sharing Activity itself.

I'm experimenting now with ways to protect the Hub from (or fix, at  
least) these situations.  We could talk about fixing Chandler Desktop,  
but since we can't force 1.0 clients to upgrade (except by blocking  
all 1.0 clients), I'd like to develop a manual (and automatable)  
procedure as a first step.

A few options for a fix are listed in the bug above.  There's a couple  
of Desktop-oriented fixes, there's a cronjob fix maybe (forgot to list  
that one), or possibly we could block Cosmo from accepting any  
collections named "Sharing Activity".

My first priority is to restore the ability to perform Hub backups.   
If deleting collections on the server-side works without Chandler just  
republishing, it seems reasonable to just delete the collection for  
the problematic user(s) without warning (and probably a followup  
email); I really don't think anyone is relying on this.  It seems  
people probably just published "everything" when they went through a  
publish step.

-- Jared

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev

Mimi Yin | 15 Aug 20:16

[Chandler-dev] Checkin 8/15/2008

sheila
- mtg yesterday about post 1.0 issues
- need to follow up with emails
- board related mtgs
- bunch of users list and inquiries to respond to

mimi
- sent some thoughts on 1.0 desktop fixing criteria and 
- longer-term building community processes around product decisions, etc

- board related meetings
- users list
- project ideas for randy - started thread on cosmo re: emailing items to hub

* mimi - what is next action on IMAP issue?
* sheila - i thought we agreed that the IMAP issue fits the criteria, it's more an issue of the builds

* mimi - resend proposal about what's getting fixed (dev)
* sheila - start thread re: builds
- mimi, send criteria email to dev list?

grant
- met with pje yesterday re: the rearch, am pulling my thoughts together
- tested out some build ideas jaredrhine & i had discussed
- setting up windows xp build machine

jeffrey
- read lots of iPhone docs
- which, combined with public source to WordPress app, should make app pretty easy
- although I fumble with objective-c syntax a lot
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
Paul Dorman | 14 Aug 21:56

[Chandler-dev] Building Chander 1.0 on Ubuntu Hardy AMD64

Hi all,

having a go at building chandler for my up-to-date Ubuntu laptop (as opposed to Feisty or Gutsy). Doing this of course because though the project has gotten to a 1.0 release, there doesn't appear to have been much regard for the diversity of user OS's out there. I'm not shy and will have a go at building, but just imagine how many more users you'd have if you just put some effort into making binaries for current Linux distros!

Anyhoo, I checked out 1.0 from subversion and have been running the build successfully so far. I'm using the "make world" command to build. For some reason the build script wants to download http://builds.osafoundation.org/external/linux/x86_64/openjdk-7-ea-j2re-b21-3.tar.gz, which naturally doesn't exist.

What's the workaround for this? I already have openjdk-6-jdk on my system, and as openjdk-7 is not final I'm curious as to the dependency for a stable Chandler release.

Thanks in advance. When I get Chander 1.0 working on my system I'll be sure to report back on my experience (I could even provide a .deb for you if it would be useful).

Paul (really looking forward to GTD with Chandler!)

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
Mimi Yin | 13 Aug 21:29

[Chandler-dev] Checkin 8/13/2008

sheila
- mostly meetings
- starting to think about decisions, priorities post 1.0 and listing out issues to discuss
- met with Hao and Peter at 543 Howard on Thursdays
- keeping up with 1.0, user questions, blog posts, stats, etc

jared
- couple of hub account deletions
- looking at wiki ban right now
- chandlproject.org restart this morning
- no explanation available or pending - mystery
- sign up for public monitoring on the todo, not implement our own but monitor the homepage for one of the free services
- additional email out to isc yesterday
- phone tomorrow/friday
- need to read grant's post-tbox messages - seems highish priority

- move internal wiki
- found some more stuff, going to move again

* sheila - jared, we should talk more about phone/conference service, etc

grant
- reinstalling XP machine to figure out current requirements for building for windows
- looked a little at OpenSuse/Ubuntu build services
- reading up on trellis and rearch as before
- couple of users/dev list emails

* sheila - goal for a draft of arch plan?
* grant - for technical goals/plan i'll need to meet w pje first

jeffrey
- fixed a bunch of problems with qe widget, but apparently not all - finished that up this working
- working on iPhone app

mimi
- aside from recent activity summarized on strat list
- another blog post re: user story
- going to pull together a blog rollup of user hacks
- thinking through productizing re-arch / chandler lite options
-- trying to come up with a list of end-user features we can shuffle around into various configurations for mini-releases

- am worried about IMAP issues - appears to be popular feature and blocker for people when they can't get it working
-- am unable to get IMAP working with my personal IMAP account (not osaf), so thinking maybe Alex's "Outlook" problem isn't really Outlook problem

pje
- meeting with Grant tomorrow afternoon 1PM PDT
- now that the BytecodeAssembler stuff is done, adding listcomp/genexp support to PEAK-Rules
- I debated over it would be better to base the SQL conversion off of pre-built AST vs. doing some of it in the builder
- And I think it will be better to do it over a pre-built structure, because then it should be easier to integrate nested expressions e.g.  [(x.foo, sum(y.bar for y in x.baz)) for x in Z]
- That should be a SELECT ...  GROUP BY in SQL, rather than two separate queries.
- I'm going to just implement the AST building in PEAK-Rules so that it builds the appropriate nested ListComp(For(...)) structure
- And then pattern matching rules can be used to "lift" the inner queries out.
- Also, it might be a bit easier to test things that way, and it'll certainly be a reasonable incremental step to get things moving.

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
Sheila Mooney | 13 Aug 01:47

[Chandler-dev] Checkin 8/12/2008


Sheila
- More budget stuff
- Follow-up on action items from board meeting
- Responding to 1.0 emails, some follow-up tasks
- Working with developers on plan for post 1.0
- Setup meeting for discussing post 1.0 user support and bug fixing plan
- A number of calls and meetings this week

Grant
- Met with Sheila
- Working on proposal and roadmap for architecture plan

PJE
- Looking at working some more on setup tools
- Spending some time on getting a released updated version on the  
developer front
- A couple of people who are building existing chandler and running  
into this problem
- Just released another version of Byte code assemblers to fix a bug
- Working on Python to SQL conversion algorithm
- Schedule going forward - a couple of days a week - at least through  
Sept

Jeffrey
- Ordering of sort of list view on hub - change never got rolled out  
to hub
- Not a high priority but probably should get this fix in
- Work another day on quick entry stuff
- Move on to iPhone app stuff after that

Mimi
- Blog post - asking people to field questions about Chandler
- Started compiling a list of questions re: post 1.0 plan in OSAF  
Collection
- Posted to blog re: syncing all your data to iCal / Lightning (no e!)
- Have post re: Avner SMSing stuff to Chandler via IMAP folders ready  
to go for tomorrow
- Responding to user questions and other inquiries
- Need to catch up on users list
- Oh also, landing page and wiki were really slow this morning, css  
was broken - servers crapping out?
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev

Sebastian Hilbert | 12 Aug 21:31

[Chandler-dev] medical scheduling application

Hi all,

Congratulations on the release of Chandler Desktop 1.0. I wouldl like you 
input (even a short note) on a potential use case for chandler. Please also 
tell me if my views don't fit your vision.

I am looking for a solution to schedule patients in a doctor's office. So this 
needs something like appointment types with preconfigured durations, 
appointment times for individual doctors and the likes.

Is chandler potentially fit for this at all or is it easier to attempt to 
build something like this from scratch ?

--

-- 
Sebastian Hilbert 
Leipzig / Germany
[www.gnumed.de]  -> PGP welcome, HTML ->/dev/null
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev


Gmane