Closed Bug 816415 Opened 12 years ago Closed 7 years ago

Filter L10N events in product release calendar

Categories

(Mozilla Localizations :: Infrastructure, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: arky, Assigned: akeybl)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Filter L10N related events in the product release calender. https://mail.mozilla.com/home/akeybl@mozilla.com/Release%20Management.html This would help L10N contributors stay on top of upcoming merges and release cycles.
this is not an l10n infrastructure problem. next best step is to prove that zimbra does actually do queries like https://mail.mozilla.com/home/axel@mozilla.com/Dummy%20Public.html?query=tag:l10n in a local install. that calendar doesn't exist no more, but the query=tag:something is the thing that is hardly documented and that I can't get to work.
Blocks: 746930
Im sorry Im a bit confused can you please explain what you are requesting here a little bit more? Maybe if you have time to stop by we can talk about this in person.
(In reply to Peter ONeill [:zero] from comment #2) > Im sorry Im a bit confused can you please explain what you are requesting > here a little bit more? Maybe if you have time to stop by we can talk about > this in person. Essentially, we have this release management calendar that contains all appointments for meetings and release milestones for the rapid release cycle. We need to find a way to filter those appointments to only display the events in the calendar that are relevant to l10n (i.e., string freezes, merge day, etc.) and provide this filtered result in an exportable format (.ics, or even an RSS feed, if possible) for localizers to follow.
It seems like it would be much easier to just create a 2nd calendar for just the l10n related events. than to try and filter out specific events.
(In reply to Peter ONeill [:zero] from comment #4) > It seems like it would be much easier to just create a 2nd calendar for just > the l10n related events. than to try and filter out specific events. Agreed, however, I think the reason arky wants this to be a l10n filtered version of the release calender is to ensure that it updates dynamically when there are changes made to the release management calendar itself. I'm not sure we'd be able to accomplish that if we created our own calendar. Thoughts Arky?
Sorry, but maintaining the same data in two places is garanteed to fail. It's nice that we have an example at hand, all the date shuffling we're doing this cycle to not run in to new years eve is perfect. I have read comments on the internet about zimbra being able to filter events by tags, see comment 1. I haven't been able to get those filters working on our zimbra install, and I haven't bothered installing the open source version locally to have a test environment. That makes it hard to say "X should work in zimbra, but doesn't in our install".
(In reply to Axel Hecht [:Pike] from comment #6) > Sorry, but maintaining the same data in two places is garanteed to fail. > It's nice that we have an example at hand, all the date shuffling we're > doing this cycle to not run in to new years eve is perfect. I agree completely. > > I have read comments on the internet about zimbra being able to filter > events by tags, see comment 1. > > I haven't been able to get those filters working on our zimbra install, and > I haven't bothered installing the open source version locally to have a test > environment. > > That makes it hard to say "X should work in zimbra, but doesn't in our > install". It's on my list of q1 goals to look into this. Knowing that tags exist will be a good place to start. Thanks Axel.
Yes, I've seen that and wondered, tbh. The issue is potentially deeply zimbra admin foo or issue tracking and source code reading, feel free to punt that.
Thanks Jeff, Axel. Peter let me know if you need any further information.
Yes, I need to know who is the "owner" of the these calendars. And a list of events that need to be filtered off.
Alex owns the calendar. "l10n freeze for release" as well as the migration dates and the actual release dates would be a good start.
Sorry for the delayed response. But I've been gone for the holidays. What is Alex's last name? I do not see him CC'ed on this bug. I will need his permission before I make any edits to the calendar.
Peter, Alex Keybl is CCed, akeybl@m.c
We're planning on splitting out the calendars into meetings/milestones in Q1 2013. Do you all feel it's necessary to further split out l10n milestones from general milestones (merge days, builds, etc.)?
Assignee: nobody → akeybl
(In reply to Alex Keybl [:akeybl] (currently out, please email release-mgmt@mozilla.com for quicker response) from comment #14) > We're planning on splitting out the calendars into meetings/milestones in Q1 > 2013. Do you all feel it's necessary to further split out l10n milestones > from general milestones (merge days, builds, etc.)? Yes. Many localizers ignore the calendar events because they don't understand which apply to them. A separate l10n calender or event filter will make it easier for l10n teams and newcomers to plan their work and know exactly what event/milestones apply to them.
My hope was that we could get to a single calendar but allow consumers of that calendar to see only a subset. The idea of having a single timeline maintained in separate places scares me. Even if they're not duplicated data. But yeah, I'm hoping for a really focused view of the release calendar for localizers.
I received the suggestion that maybe someone in WebDev could help build out something that could accomplish this. I've CC'ed morgamic in case he knows anyone that could help.
Looping in Dave, too. Do you know if we can get filtered calendars based on tags on the events in zimba?
Flagging Dave for needinfo.
Flags: needinfo?(justdave)
I cannot for the life of me find anything that actually works as a search term in that query field. I likewise found it in the docs, only saying that the field exists, and not describing what the valid contents of it are. Seems the ideal solution here is probably to create a second calendar for just the l10n stuff (as suggested in comment 4). You do *not* duplicate anything between the calendars. The l10n stuff would only go on the l10n calendar. You then have both calendars loaded when you want to view it all together (check both boxes in Zimbra web client or in iCal when you have the ics files subscribed to). Getting some web-based calendar app that can import both .ics files to display them together would probably be the best bet for a web view. I hear Google Calendar may be capable of doing this (something simple like PHPCalendar may do the trick, too).
Flags: needinfo?(justdave)
(In reply to Dave Miller [:justdave] from comment #20) > I cannot for the life of me find anything that actually works as a search > term in that query field. I likewise found it in the docs, only saying that > the field exists, and not describing what the valid contents of it are. > > Seems the ideal solution here is probably to create a second calendar for > just the l10n stuff (as suggested in comment 4). You do *not* duplicate > anything between the calendars. The l10n stuff would only go on the l10n > calendar. You then have both calendars loaded when you want to view it all > together (check both boxes in Zimbra web client or in iCal when you have the > ics files subscribed to). > > Getting some web-based calendar app that can import both .ics files to > display them together would probably be the best bet for a web view. I hear > Google Calendar may be capable of doing this (something simple like > PHPCalendar may do the trick, too). Thank you for looking into this Dave. I suppose then that next steps need to be: 1) Determine who on our team will own this l10n calendar. 2) Coordinate with Release Management to create this l10n calendar and remove l10n events from the Release Management calendar. Granted, this is not an ideal solution, but our localizers really need a simpler way to view events in the release process the relate to them only. Perhaps Axel, Arky and I can get together and hammer out these details? What do y'all say?
We've got the action to figure out a final solution (multiple calendars, queriable tags outside of Zimbra, etc.) owned by RelMan this quarter. If you all want to move faster than that, you can temporarily maintain your own calendar as suggested in Comment 21. In the end, I think it makes sense for Release Management to own release events.
I'm not a friend of maintaining two calendars. For one, I think that people subscribing to the current calendar should continue to receive l10n-relevant aspects of the calendar. On top of that, maintaining one is a struggle already. I wonder if we can create a decently-reliable algorithm to filter the original ics through some http://icalendar.readthedocs.org/en/latest/ code on the elmo side. That's still an order of magnitude worse than being able to filter on the zimbra side, but still a whole metric ton better than two calendars, IMHO.
The script takes an ICS file and a keyword to extract all events based on that keyword.
Hi Sajjad, thanks a lot. Can you serialize the output back into an ics file? It'd be cool if you could take a sequence of names, and I guess it's enough to just do something like 'lookfor.lower() in summary.lower()' as check.
Sure Axel. I'll make the changes. Oh yes, lookfor.lower() in summary.lower() is much more sensible. I don't know what I was thinking. :)
Fixed this: https://github.com/geohacker/ical You can specify a series of keywords and it will dump all the events satisfying all the keywords to filtered.ics I'll add conditional filtering when I have more time.
I've sent you a pull request with some tweaks, and we'd need a license on that code, too.
Awesome! Merged the changes. MPL2 sounds good!
@Pike any update on this. Did this go into elmo?
Any updates?
Flags: needinfo?(l10n)
(In reply to Alex Keybl [:akeybl] from comment #22) > We've got the action to figure out a final solution (multiple calendars, > queriable tags outside of Zimbra, etc.) owned by RelMan this quarter. If you > all want to move faster than that, you can temporarily maintain your own > calendar as suggested in Comment 21. > > In the end, I think it makes sense for Release Management to own release > events. Alex, is there progress to report from your side?
Flags: needinfo?(l10n) → needinfo?(akeybl)
moving the ni? to release-mgmt so I can get back to this when we return from closure. No updates yet but will look into this further in the new year.
Flags: needinfo?(akeybl) → needinfo?(release-mgmt)
So we did move over to a public calendar: https://mail.mozilla.com/home/publiccalendar@mozilla.com/Releases%20Scheduling.html when Alex left, no longer using his personal share. What else is there to do here?
Flags: needinfo?(release-mgmt)
(In reply to Lukas Blakk [:lsblakk] from comment #34) > So we did move over to a public calendar: > https://mail.mozilla.com/home/publiccalendar@mozilla.com/ > Releases%20Scheduling.html when Alex left, no longer using his personal > share. What else is there to do here? Hey Lukas, One key l10n event appears to be missing from the calendar: localization freeze at Beta-Release migration. Does the new calendar have the keywords that Pike landed in comment 28, or will have to be done again?
Now that we'll be moving calendaring systems, it's likely that this will become easier to accomplish. I'll take a look at how this will be accomplished in the next week or so.
We expose relevant information about deadlines in tools these days.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: