https://secure.phabricator.com/book/phabricator/article/prototypes/

k :)

Calendar's still a prototype and we have a few unfinished pieces like this, but we can keep this around as a reminder until we finish it up.

@Quazil, Maniphest Tasks support Custom Fields, which support dates. They just don't show on a calendar, but you can set a due date today.

In some fashion, Maniphest tasks have to have due-dates for the tool to be acceptable for use in most industries.
Without this feature Phabriactor's user-base is restricted to only people working on pure software while also using an agile method (subset of a subset).

Ah, thanks. That makes sense.

Hey, sorry for the dump and run report.

Yeah, there's no separation of Join/View policies currently.

Calendar from what I can see doesn't have a joinable policy, so not sure what that editable by invitees policy would really prevent.

Sorry, I know, that there is a rule that tells not to post bugs about prototype applications. Just wanted to make sure, that issue would be noted.

Calendar is a prototype application and is not ready for production use, sorry for the trouble. You can follow progress in Calendar or T7924.

As a heads up, Calendar is a prototype application, and is generally expected to be buggy, incomplete, and not "production ready".

Calendar is a prototype application:

We should probably just get hovercards activating in more places; I think there's a task for that (or at least some discussion) somewhere. For example, they don't activate for "Author" / "Subscribers" here in Maniphest, but I think there's no technical reason they couldn't.

I don't have plans to tooltip these. The information should be available on Profile and on Hovercards, I suppose it could be re-enforced there.

It might be worth mentioning that Wiggio.com has this exact feature. For them, the person doing the scheduling specifies the days and times that the meeting could start on, and then everyone checks the boxes for the timeslots that they are available. Like you mentioned, not the most innovative UI, but it is very effective.

This seems very likely. I'll take a look.

(I haven't tried to reproduce this.)

Okay thanks

I destroyed F641702 and F641705.

@epriestley that custom policy was intentionally set as the screenshots contain the names of people who may not want them on the internet (plus other event details and whatnot)

Yeah, I think we're likely to remove this. It generally needs a lot of effort to modernize even if we're going to keep it.

I don't believe people are actually using this feature of Conpherence and I'd like to see it removed and replaced with something more customizable, like feed or dashboards.

no, i'm just testing phabricator right now and noticed it...

Do you actively use this feature of Conpherence?

Yes, recurring events should be individually commentable. Meeting minutes can be a separate discussion.

I'm also in no way arguing against making these all individually commentable, I just try to look at core problems presented and make sure we solve the actual proble you are having and not just implanting random features. If there is some way to make Phriction work better for documenting recurring meetings, I'm generally more in favor of that.

Calendar is a prototype application, meaning it's unfinished, buggy, and still undergoing major changes. We generally prefer not to take bug reports or feature requests on prototypes.

OK, let's just forget about meeting minutes for Phabricator's calendar app. It may be a bad example from your point of view (even though I am not completely sold to using Phriction instead, due to the lack of a nice calendar view that makes it easier to browse events in a familiar way).

I agree with @chad and @lpriestley: meeting minutes on calendar events would be hard to find or search. Typically one doesn't remember the day the meeting took place, they remember the type of meeting and search all the minutes. Being able to tag wiki articles with a date or calendar would be useful though: or being able to couple an agenda + minutes + calendar entry.

Interesting point, @chad. I do still think that the current commenting behavior on recurring events is inconsistent. Ghost event exceptions are real live events, so they have their own comments, but other generated ghost events are not, and they all share comments with their parent. I think the way forward here is to convert ghost events to real events if you want to leave a comment on them.

My main concern here is we already have a tool for documenting things with Phriction. Changelog is a good example of what you are describing. We keep it updated every week.

Confirmed working, thanks! A future request might be to have that range configurable.

Month view is working, stupidity on my part -- didn't switch to the next month!

Oh, I think you're right. There's something sketchy happening in the "Upcoming Events" builtin query. I'll look into that.

After digging around this might be a limitation of the "upcoming events" query. We assumed that some views would present at least a minimal number of items, but that query now seems to be more restrictive. That's all this is. Is that timeframe configurable? We reported this because events went missing in some places, but that's just because they're far enough out in time.

@mbishopim3, I can't reproduce this on secure or my local install, but still trying. A few things to clarify:

1. You, the creator of an event, can't see the events you're creating in month view?
2. Are all users in the same timezone? What timezone are you in?
3. Are there more than 15 events on the day you're creating new events? (That's the maximum number for now. We're working on a "View More" link)
4. Does the day view also not show new events? How about via advanced search?
5. Are the new events recurring or does this apply to all events?