Report from the Budapest sprint on Drupal 8 Multilingual Initiative issues
We just held a one-day sprint in person in Budapest (sponsored by the NIIF Institute, heavy Drupal users themselves) and over IRC on #drupal-i18n this past weekend to make significant progress on some of the D8MI issues. Given almost all in-person attendees were new to Drupal 8, some new to working on Drupal core, I chose issues which were easier to pick up but great help for D8MI to roll along, as well as asked people to help review existing issues and work on (upgrade) tests. All-in-all, we had the following people in attendance in person: @balagan, @csg, @Desire, @eager, @hairqles, @kalman.hosszu, @pkiraly, @roderik, @tanarurkerem, @zly and myself. In attendance over IRC were @clemens.tolboom, @fubhy, @reyero and @tstoeckler. (Hope I did not leave anybody out).
We made very good progress on the following issues.
Added missing langcode schema elements on entities
To add the possibility to track language information on entities where this support is/was missing. User interface and settings to be added later by generalization of the extended node settings, see below.
Made good progress converting existing 'language' schema keys to 'langcode'
As part of the unification effort to improve DX (by using 'language' only where we have a full language object available).
- #1439686: Rename $node language property to langcode
- #1439680: Rename $user language property to langcode
- #1439692: Rename field language properties to langcode
Reviewed/verified issues with existing patch/tests
Reviewed patch, cleaned up tests, wrote upgrade tests
- #673020: Add the Content-Language HTTP header to the generated page
- #1272840: Add upgrade path for language domains and validation
Reviewed and improved
Finally made good progress on implementing two new features!
- #1445004: Implement custom/community string bit on translations which would let locale module differentiate between community sourced and locally customized translations, making easier to keep and share customizations (part of migrating l10n_update module into core)
- #258785: Provide more flexible settings for language on content types which extends content language features with all i18n options merged in but with a user experience re-thought from the ground-up; should eventually be used across entity types and applicable to taxonomy, users, etc.
Further reviews and help in these issues is of course very welcome. We still need to drive these home to land in Drupal 8! I sincerely hope we can complete and land the ones not yet done soon and continue the work on even more advanced issues at the Denver D8MI sprint.
Thanks again for everybody who attended and helped to make this a great event.
Drupal 8 InitiativesD8 Mobile Initiative IRC Meeting #4
Please join us for our fourth IRC meeting to discuss issues related to the Drupal 8 mobile initiative. The meeting will be held in #drupal-mobile on IRC at 19:00 UTC on Thursday, February 16. Using IRC is easy; Drupal.org provides a guide to using IRC.
Thursday, March 1:
San Francisco — 11am
New York — 2pm
London — 7pm
Taipei — 3am (Friday)
Convert to your timezone
As a reminder, the scope of the D8 Mobile Initiative includes:
- Mobile-friendly Drupal admin
- Responsive design issues
- Front-end performance
- Converting existing D8 themes to be responsive
The agenda will be driven by the questions and suggestions given by attendees.
Please post your proposed discussion topics in the comments.
Drupal 8 InitiativesD8 Mobile Initiative office hours
This Sunday, the Drupal 8 mobile initiative will be holding our first weekly office hours in IRC. The office hours will allow regular contributors to work together at the same time on the Initiative’s issues. And will allow new people to figure out how they can help too!
Should I attend?
If any of the following apply to you, then you should absolutely attend:
- You're looking to get involved, but don't know where to start.
- You have questions about the initiative goals or any outstanding issues.
- You want to meet/co-work with others working on Mobile issues.
- You have a patch that you need reviewed.
When and Where
The office hours will be held in #drupal-mobile on IRC from 8-10 PM EST on Sunday, February 19. Using IRC is easy; Drupal.org provides a guide to using IRC.
Sunday, February 19:
San Francisco — 5pm
New York — 8pm
London — 1am (Monday)
Taipei — 9am (Monday)
Convert to your timezone
Extra set of office hours
Obviously, the office hours work fine for me in Taiwan and those of us in North and South America. But Europe through Central Asia are left in the dark. We need to set up a second set of office hours for those regions. If you are in that region, please let me know what times would work best for you and we'll arrange another set of office hours. Thanks!
Drupal 8 InitiativesDrupal 8 Multilingual Initiative sprint at and after the end of Drupalcon Denver
There is already a traditional code sprint day at the end of Drupalcon Denver. While US Drupalcons are not usually flush with interest for multilingual topics, there is always a sizable set of people interested, and we are looking forward to Suzanne's and Florian's great session on the topic.
Therefore we added an additional two days of sprinting for those interested in the Drupal 8 Multilingual Initiative, so we can continue our work. I always found the one day sprints at Drupalcons are not good to do larger scale work and having a minimum of three days makes the work much more productive.
There is of course nobody stopping people from sprinting all through the conference, as a work home-alone geek I'm more than happy to meet people and have great discussions and conversations, so I'm not planning for a computer focused coder extravaganza on the Drupalcon days. I will definitely support people who do intend to work on multilingual patches throughout the conference especially if you can come to the general Drupalcon days but not extend your stay (which would be sad).
Planned dates for the Denver sprint are therefore: March 23 (Fri), 24 (Sat), 25 (Sun) 2012. We are still working on booking a venue for the additional days. The Friday sprint day will take place as part of the regular Drupalcon sprint organization.
Additionally or instead of signing up here please indicate your availability for the sprint at http://www.doodle.com/54gtf4xqxe7hd6qz#table - a table that includes all Drupalcon days as well to get an inea of people interested sprinting on Drupalcon days (too).
Drupal 8 InitiativesD8 Mobile Initiative IRC Meeting #3
Please join us for our third IRC meeting to discuss issues related to the Drupal 8 mobile initiative. The meeting will be held in #drupal-mobile on IRC at 19:00 UTC on Thursday, February 16. Using IRC is easy; Drupal.org provides a guide to using IRC.
Thursday, February 16:
San Francisco — 11am
New York — 2pm
London — 7pm
Taipei — 3am (Friday)
Convert to your timezone
As a reminder, the scope of the D8 Mobile Initiative includes:
- Mobile-friendly Drupal admin
- Responsive design issues
- Front-end performance
- Converting existing D8 themes to be responsive
The agenda will be driven by the questions and suggestions given by attendees.
Please post your proposed discussion topics in the comments.
Drupal 8 InitiativesDrupal 8 HTML5 Initiative Meeting #20
Please join us for our 20th bi-weekly meeting to discuss issues and progress related to the Drupal 8 HTML5 initiative. The meeting will be held in #drupal-html5 in IRC at 4 PM EST.
AgendaDuring the meeting, we will discuss the progress of the current sprint and schedule issues for the next sprint. Please post your proposed discussion topics in the comments if you have any.
SubscribeYou can subscribe to the Google Calendar for this and future meetings via the iCal or XML feeds.
IRC Meeting LogPosted after meeting.
Drupal 8 InitiativesOne day Drupal 8 Multilingual Initiative sprint on Feb 18th
We are holding a one day sprint for people interested in working on solutions for the Drupal 8 Multilingual Initiative. The physical sprint is in Budapest, on Saturday, Feb 18th from 9am to 6pm local time (CET). Because most of you would not be able to make it in person, we'll also hang out in #drupal-i18n so if you want to join, feel free to do so then and there. Because this is a one day sprint only and people attending the sprint will be mostly new to Drupal 8 development (experienced in Drupal development in general though), we expect to work on lower hanging fruit tasks.
If you show up and want to help with more complex issues, just ask in the #drupal-i18n channel and we'll surely find something good for you!
Drupal 8 InitiativesDrupal 8 Multilingual Initiative meeting on Feb 15, 2012
It is that time again! We'll review current top priority tasks and discuss new ones to work on. No other specific special topics planned at the moment.
The meeting is in the #drupal-i18n channel on IRC. See http://drupal.org/irc for more information. The time above is marked with UTC - check in your own timezone.
AttachmentSize D8MI-meeting-log-feb-15-2012.txt8.98 KB Drupal 8 InitiativesStrategy for the Mobile Initiative
This strategy document uses the Minimal Viable Product strategy, which you can read more about on Wikipedia.
General OverviewThe Drupal 8 Mobile initiative’s goal aims to make Drupal the leading mobile CMS platform. Certainly, there are some fantastic contributed modules that already make Drupal a great starting point for mobile solutions; modules like Mobile Tools, Domain Access, Responsive Images, as well as a whole slew of new ones that have been released in the past few months. But in order for a CMS to earn the moniker "mobile-friendly", setting it all up needs to be easy.
Right now, Web development experts are building mobile apps and websites while looking for integration with existing CMSs. And they are having to build a lot of the tools themselves because there are very few mature tools. The Web development industry as a whole is still trying to figure out the best way to build mobile sites and Drupal needs to engage and become a leader as that work continues.
There are currently at least five different ways to provide mobile solutions:
- Native apps (code compiled to run natively on iPhones, Androids, etc.)
- Web apps (HTML5 and JavaScript-based apps running on mobile browsers)
- Mobile/desktop domain switching (parallel websites: one for desktop and one for mobile, with device detection to switch between the two.)
- Responsive design (a single HTML source that uses CSS3 media queries and JavaScript to respond to different device capabilities)
- RESS: Responsive Design + Server-side Components (a hybrid approach that uses Responsive Design techniques combined with a light amount of device detection to alter the markup before being sent to the user.)
Drupal, whether in core or contrib, should support all of them.
Now that’s a pretty broad spectrum of things to cover and they can’t all be included in core. But, to reach that “mobile-friendly CMS” status, what are the top issues Drupal 8 core should provide?
- Web services for native app integration
- HTML5 elements necessary for HTML5 Web apps
- Ability to use Drupal’s administrative forms in mobile devices
- All of Drupal 8’s core themes should be responsive
- Front-end performance improvements
Fortunately, the first two points are already covered by the Web Services and Context Core Initiative and the HTML5 Initiative.
That just leaves the last three items for the Drupal 8 Mobile Initiative to focus on.
Objectives
Responsive Web design
Responsive design is the hottest technique in producing mobile friendly websites because, relative to traditional mobile building techniques, it lowers the development cost for including mobile device support. Websites that only support large screens will become an anachronism, so converting all of core’s current themes to have mobile-first responsive designs is essential for Drupal to remain relevant. (Incidentally, the Drupal 8 Design Initiative, which is focusing on building new themes for Drupal 8, will also ensure its themes are responsive.)
Mobile-friendly forms
If users can’t create content or administer a Drupal site while on a mobile device, we have a serious problem. Those are the first tasks attempted by users on new Drupal websites. Much as the “ugly themes in Drupal 6” made a bad first impression of Drupal to Web designers, not providing mobile administrative solutions will leave a sour taste in the mouths of mobile developers evaluating CMS solutions. To complete this task, we’ll have to look at the complete stack for administrative tasks, including form definitions, form submit handlers, the Toolbar, the Overlay, and the Seven theme.
The target is 100% mobile-friendly administration via responsive design, but we recognize that certain pages, e.g., the permissions page, may require a dedicated mobile presentation.
Front-end performance
Lastly, performance has always been a priority for websites, but with mobile it becomes critical. Some studies show up to 97% of a page’s render time takes place in the front-end. There are a laundry list of best practices for front-end performance that will help mobile and desktop users. And I’ve seen several members of the Drupal community speak about these issues multiple times this past year.
However, when dealing with responsive design, the single biggest performance concern is image handling. The first demo of responsive design had over-large images being sent to mobile devices. While no single best solution has yet been found, we intend to leverage Drupal 7’s image styles to solve this issue.
Program tasks
Program tasks are defined in the following way:
- Must have (essential to success)
- Should have (significant impact to success)
- Could have (should be done, but are not essential)
- Won’t have (future functionality)
-
Must have / Critical
Responsive Web design
- Seven converted: http://drupal.org/node/1088792
- Stark converted: http://drupal.org/node/1322794
- Bartik converted: http://drupal.org/node/1192044
Mobile-friendly administration
- For all content editing and workflow related pages (adding users, taxonomy terms, menu items, new content, moderating content, etc.)
- Review of the Toolbar
- Review of the Overlay
Front-end performance
- Responsive images: As the layout is resized, the browser will serve the proper image size (“real” size, not height/width attributes) See Responsive image discussion for current status.
- Optimized images
- Sprites used wherever appropriate
- Optimized css: Evaluate the CSS/JS aggregation process and adjust where improvements can be made. Offer more flexible JS loading options so Drupal can stay current as new tools arise.
One of the first issues that needs tackling is determining a dependencies list so the critical tasks can be done as quickly as possible. For example, all mobile-friendly admin tasks are dependent on Seven being responsive.
-
Should have / Major
- A “Mobile Handbook” for how to make websites mobile-friendly using contributed projects. http://drupal.org/node/1341310
Front end performance
- Documentation of the use cases that css aggregation serves.
- Documentation for how to optimize for other use cases.
Mobile-friendly administration
- Configuration pages converted (creating a new content type; adding fields to a user profile, etc.)
-
Could have / Normal & Minor
TBD
-
Won’t have
- Any impact on Drupal.org; See http://drupal.org/node/951114
D8 Mobile Initiative IRC Meeting #2
Please join us for our second IRC meeting to discuss issues related to the Drupal 8 mobile initiative. The meeting will be held in #drupal-mobile on IRC at 19:00 UTC on Thursday, February 2. Using IRC is easy; Drupal.org provides a guide to using IRC.
Thursday, February 2:
San Francisco — 11am
New York — 2pm
London — 7pm
Taipei — 3am (Friday)
Convert to your timezone
As a reminder, the scope of the D8 Mobile Initiative includes:
- Mobile-friendly Drupal admin
- Responsive design issues
- Front-end performance
- Converting existing D8 themes to be responsive
The agenda will be driven by the questions and suggestions given by attendees.
Please post your proposed discussion topics in the comments.
Drupal 8 InitiativesDrupal 8 HTML5 Initiative Meeting #19
Please join us for our 19th bi-weekly meeting to discuss issues and progress related to the Drupal 8 HTML5 initiative. The meeting will be held in #drupal-html5 in IRC at 4 PM EST.
AgendaDuring the meeting, we will discuss the progress of the current sprint and schedule issues for the next sprint. Please post your proposed discussion topics in the comments if you have any.
SubscribeYou can subscribe to the Google Calendar for this and future meetings via the iCal or XML feeds.
IRC Meeting LogAttached below.
AttachmentSize html5_meeting_irc_log_02-07-12.txt24.33 KB Drupal 8 InitiativesA new dynamic hub for the Drupal 8 Multilingual Initiative
Drupal.org is great to maintain a solid number of issues but all of us trying to wrangle a huge number of issues need way better tools to have overviews of what is going on and how is work structured. We need to be able to help new people join in quick, let them have an overview of current tasks and also on the place of tasks in a bigger picture. So we need to have the bigger picture documented with the possibility for people to dive in on demand and we need to keep it always up to date and relevant.
The Drupal.org issue queue is great to see a status of issues, but it is not good at all in maintaining relations and especially bad at providing support for hierarchy and in-context structural information. All we get is basically a list of issues like this one: http://drupal.org/project/issues/search/drupal?issue_tags=D8MI
Recap of predecessors
Different people got to different approaches to these problems. Here are some previous solutions that Jacine and I looked at and tried and the reasons I think they did not work the way I wanted them to work for me and people working with me.
1. Documentation pages. Jacine did a superb work in the HTML5 initiative collecting tasks into documentation pages with explanation on how can one contribute. One such page can be seen at http://drupal.org/node/1183606. This is great for getting some overview of the tasks at hand, but there is not a lot of metainformation on the issues and it needs manual editing to keep up to date. It cannot be dynamic in itself to show current tasks. Regardless, the documentation tree for the initiative (starting at http://drupal.org/community-initiatives/drupal-core/html5) works well for the people working on it as far as I've heard. I was just looking for a more dynamic solution.
2. Issue trees. I started to make up an issue tree for the Drupal 8 Multilingual Initiative back in August (in preparation of the London code sprint), so there would be an overview of the perts of the initiative. Turned out there are so many levels required that META-issues needed a META-META issue (http://drupal.org/node/1260534). Many people don't know what's a meta issue, let alone meta-meta. Also, again, the hierarchy (up-down) requires manual maintenance, and gradually got outdated as work focused on patches instead of maintaining the whole structure.
2a. Issue tree visualization. To make the issue tree more friendly for people I talked to some of my great Hungarian Drupaler pals who went on and created the Issue tree module to visualize the tree represented by the data from above. See http://drupal.org/project/issue_tree. Unfortunately this did not get much support for deployment on drupal.org and the topic pages efforts are in full force to propose something much bigger and better (http://groups.drupal.org/node/144584) so this has fallen through the cracks.
3. Mindmap. So given the issue tree did not have a chance for deployment and I wanted to provide an overview of the initiative, the initiative mindmap was born (and posted on the META-META issue at http://drupal.org/node/1260534). This was also plagued by the data disconnect. When tasks changed the map needed to be updated. Current tasks were only marked here, not on the issues themselves, so I need to manually keep a list of current issues updated elsewhere. This was/is a more up to date version of the structure compared to the issue tree, but is/was still lot of work to update and lacking features like pulling out current tasks or helping people find tasks that need testing or are easier to do.
Enter the Rocketship!
So in frustration of not having a good overview on all tasks even myself and not being able to sleep due to that frustration, the ambitiously labeled "codename rocketship" was born. Experience for yourself at http://hojtsy.hu/d8mi.
Basically rocketship comes from the idea that we need structure and higher level organization for huge sets of issues while at the same time be able to have an overview of both metadata on the issues and current state. It is a combination of all things I liked about the HTML5 book solution with a lot more automation based on metadata exclusively pulled from drupal.org. The initiative hub consist of a hierarchic book at its core, where each book page can have a taxonomy term name specified. If a term is specified, the issue nodes tagged with that term are pulled and sorted into 6 groups based on their status. For the first version I lumped "active" and "needs work" for example under a "To do" label, and did some more complex mangling to sort backport issues into a group as well (i.e. issues that were worked on for Drupal 8 before but are being worked on for Drupal 7 or 6 now).
Pulling issues based on taxonomy terms lets us create a page for example, that does the same sorted overview for current focus issues (D8MI and sprint tag at once, again an idea lifted from Jacine): http://hojtsy.hu/d8mi/current-top-priority-tasks
Then based on "lower level" tags we can dive into only the issues that deal with converting to "langcode" from "language" in schemas and APIs at http://hojtsy.hu/d8mi/migrate-schemas-and-apis-langcode for example.
We can also tag things for different areas, so they show up in different areas of the structure tree in their respective place.
Then when looking at let's say the base language issues (http://hojtsy.hu/d8mi/base-language-features), you can see I color coded the critical and major issues as well as the current focus issues. I also took liberty to mark the "Needs tests" tag with a distinctive color, so people looking to be able to help with that can spot those easily. I can imagine a couple other key tags can get colors, but we should got go absolutely overboard in that. An issue board with rainbow effects is not really useful.
Technology background
The feature works with a local cache of all issues tagged with D8MI with all the information scraped from Drupal.org (given no API available) and stored in local nodes. While that is not a great long term solution, I'm focused on improving Drupal 8's multilingual capabilities, so I tried to get to good results fast. The local cache of issues is updated every hour, so drupal.org should not be hammered at all. Similar issue status overviews are likely possible on drupal.org, I'd love to work on that given resources, however that is probably not going to happen with me personally for another 1.5 years or so given my focus on Drupal 8.
Drupal 8 InitiativesDrupal 8 Multilingual Initiative meeting on Feb 1, 2012
If you don't find you way through the maze of the Drupal 8 Multilingual Initiative issues, wondering where to contribute, this is your place! If you are actively contributing and need some timely feedback, make sure to be there too. We'll review current issues and shorter term plans to focus on, but we'll probably also touch on longer term todo items (still confined to Drupal 8). The meeting is in the #drupal-i18n channel on IRC. See http://drupal.org/irc for more information.
(Note time above is marked with UTC - check in your own timezone).
AttachmentSize D8MI-meeting-log-feb-1-2012.txt12.59 KB Drupal 8 InitiativesWSCCI Status Meeting - 2012-01-31
Normal update meeting in #drupal-wscci. No agenda set yet.
AttachmentSize #drupal-wscci.01-31.txt43.08 KB Drupal 8 InitiativesDrupal 8 HTML5 Initiative Meeting #18
Please join us for our 18th bi-weekly meeting to discuss issues and progress related to the Drupal 8 HTML5 initiative. The meeting will be held in #drupal-html5 in IRC at 4 PM EST.
AgendaDuring the meeting, we will discuss the progress of the current sprint and schedule issues for the next sprint. Please post your proposed discussion topics in the comments if you have any.
SubscribeYou can subscribe to the Google Calendar for this and future meetings via the iCal or XML feeds.
IRC Meeting LogSee attachment below.
AttachmentSize html5_meeting_irc_log 01-24-12.txt28.02 KB Drupal 8 InitiativesCMI IRC Meeting
It's for another "bi-weekly" IRC meeting! I've been trying to get these going more frequently but it has been really difficult as I've started planning my move and the like.
The meeting will take place in the #drupal-cmi channel on Freenode at 20.00 UTC.
Here are some agenda items for this meeting:
- Update process - There are various ideas about what should happen to notify modules when a config update happens (discussion at http://groups.drupal.org/deployment-build-systems-change-management) and beejeebus recently committed some code to a branch that is a start at implementation of this (http://drupalcode.org/sandbox/heyrocker/1145636.git/shortlog/refs/heads/...) so lets talk about it some more. I will be in Boston mid-February at the same time as beejeebus, and it is my hope that we can get some real progress going on this.
- Patch status - The patch could really use more attention and more serious reviews. Please take a look and comment!
- Internationalization - I had a meeting with the D8MI team last week to further discuss internationalization issues (see http://groups.drupal.org/node/201448 for the log.) Some issues came out of that which neeed further discussion.
Hope to see everyone there!
Drupal 8 InitiativesIn-person sprints planned for the Drupal 8 Multilingual Initiative in 2012
While we made some progress last year for better multilingual support in Drupal 8, the lion's share of the work is still ahead of us. Make no mistake, most planned multilingual features are still vaporware. There is a lot to do to improve what is in there and to add the missing functionality. Never did I see a shortage of tasks to do, much more so lack of people with dedicated time available to focus on the tasks. Therefore it looked only logical to put together a well planned series of in-person sprints with a well planned structure to gather like-minded people who want to make Drupal 8 a much better multilingual release, getting them out of their daily habits to entirely focus on Drupal 8.
Therefore I propose the following threefour in-person sprints for the foreseeable part of this year to gather and improve our codebase. I'd love if more people can come to these sprints, so I purposefully propose them for around the biggest Drupal events of the year. Also, I'm announcing these plans so that we can organize ahead of time for travel, accommodation and sprinting space for each attendee and last but not least sponsors.
Update: one day sprint in Budapest, Feb 18th
I'm also holding an in-person sprint for the Hungarian developer community in Budapest on Saturday Feb 18th. If you are interested, read the Hungarian post at http://drupal.hu/node/15357 (in short and in English, sprint times are 9am to 6pm). We'll be hanging out in #drupal-i18n so if you want to join, feel free to do so then and there. Because this is a one day sprint only and people attending the sprint will be mostly new to Drupal 8 development (experienced in Drupal development in general though), we expect to work on lower hanging fruit tasks.
Two additional days trailing Drupalcon Denver
There is already a traditional code sprint day at the end of Drupalcon Denver. While US Drupalcons are not usually flush with interest for multilingual topics, there is always a sizable set of people interested, and we are looking forward to Suzanne's and Florian's great session on the topic. So I propose we add an additional two days of sprinting for those interested in Drupal 8 Multilingual Initiative, so we can continue our work. I always found the one day sprints at Drupalcons are not good to do larger scale work and having a minimum of three days makes the work much more productive.
There is of course nobody stopping people from sprinting all through the conference, as a work home-alone geek I'm more than happy to meet people and have great discussions and conversations, so I'd not plan for a computer focused coder extravaganza. I will definitely support people who do intend to work on multilingual patches throughout the conference especially if you can come to the general Drupalcon days but not extend your stay (which would be sad).
Planned dates for the Denver sprint are therefore: March 23 (Fri), 24 (Sat), 25 (Sun) 2012.
Four additional days before Drupal Dev Days Barcelona
Drupal Dev Days is the biggest developer focused gathering in Europe each year. Last year there were close to 600 signups for the event in Brussels. It is going to be a big event in an area full of interest for multilingual topics, so it is evident that we should organize a sprint around it. While not widely publicized, this year Drupal Dev Days goes to Barcelona in June, and the organizers secured sprinting space in Citilab (their very nice event facility) for the week before the event. There is no complete information about the program of the Dev Days. It might include a sprint day in itself as well.
Planned dates for the Barcelone sprint are therefore: June 11 (Mon), 12 (Tue), 13 (Wed) and 14 (Thu) 2012.
Two additional days after Drupalcon Munich
Drupalcon comes to Munich this August. Although the exact structure of the conference is not yet publicized, I'm assuming it will follow the "traditional" structure applied recently to Drupalcons with a training day, 3 days of main session program and a day of sprints. So I'm proposing a sprint again for two days after the conference. My thinking on sprinting on Drupalcon days themselves is similar to that about Denver.
Planned dates for the Munich sprint are therefore: Aug 24 (Fri), 25 (Sat) and 26 (Sun) 2012.
General notes
I understand this is a bit too much to commit to for any single person, and I realize the sprints might not have a huge overlap in attending people due to sheer availability and the compromises involved. It would be great however to have a good set of knowledgeable people to work on current issues and make great progress on getting Drupal 8 a multilingual boost.
I'm planning to post these sprints as individual events in the Internationalization group for people to be able to sign up for and communicate with attendees. I wanted to post the overall proposal first to do a reality check with people and gather general suggestions for the larger scale plan. Feedback very welcome!
Drupal 8 InitiativesWSCCI Status Meeting - 2012-01-17
Agenda:
Demo of plugins
General discussions
Drupal 8 HTML5 Initiative Meeting #17
Please join us for our 17th bi-weekly meeting to discuss issues and progress related to the Drupal 8 HTML5 initiative. The meeting will be held in #drupal-html5 in IRC at 4 PM EST.
AgendaDuring the meeting, we will discuss the progress of the current sprint and schedule issues for the next sprint. Please post your proposed discussion topics in the comments if you have any.
SubscribeYou can subscribe to the Google Calendar for this and future meetings via the iCal or XML feeds.
IRC Meeting LogSee attachement below.
AttachmentSize html5 meeting log 01-10-12.txt31.99 KB Drupal 8 InitiativesDrupal 8 Multilingual Initiative meeting on Jan 18, 2012
If you don't find you way through the maze of the Drupal 8 Multilingual Initiative issues, wondering where to contribute this is your place! If you are actively contributing and need some timely feedback, make sure to be there too. We'll review current issues and shorter term plans to focus on, but we'll probably also touch on longer term todo items (still confined to Drupal 8). The meeting is in the #drupal-i18n channel on IRC. See http://drupal.org/irc for more information.
(Note time above is marked with UTC - check in your own timezone).
AttachmentSize D8MI-meeting-log-jan-18-2012.txt27.12 KB Drupal 8 Initiatives