Collaboration tool for new team for localize.drupal.org

In my opinion, the issue queue is OK. In order to keep everyone engaged, I think weekly updates might be useful, too. I imagine 2 ways:
* weekly meeting (difficult because of time-zones)
* weekly activity digest curated by a different team member each week (rotation)

I think we can take project issue queue as initial collaboration tool. It's possible to subscribe to notifications, use d.o. advanced search etc.

Let's see first what timezones we use. If it's mostly America and Europe, then it's not that hard to find common time. If we have America, Europe and Far East, that can be a problem

Mail I have written to the manual "mailing list" that was used by the volunteers for l.d.o so far. Feedback on that should go into this issue.

Hi everyone!

I totally agree with Gabor that things will not go forward if we continue to write mails like this. I utilized some train rides since drupalcon to brainstorm a bit what needs to be done and what project infrastructure I would like to see so it is easily possible to bring new people on the team and keep everyone informed who has already said that he or she will help.

Here is an evernote document with my outcome so far:
https://www.evernote.com/shard/s31/sh/548760af-e499-41cb-8f75-25f059419b...

At the moment a have huge amount of work that needs to be done till friday. (yes its multilinguale, and yes it makes me cry every day because of stuff that is not working :-)

From next week on - I have two weeks vacation from my dayjob an plan to spend some hours on the "make localize.drupal.org awesome" project.

If nobody feels offended by my plans I will just go forward.

Here are steps I intend to do or have already done. Please sent me some feedback if it is not allowed (in the d.o world) to do things like that because I use google or something and people don't like it because they feel google is evil and is messing around with there data and thats why they wouldn't go to a hangout for example and will only participate if meetings take place on IRC.

So if nobody has serious concerns I will:

• Create a parent wiki page on drupal.org similar to http://drupal.org/make-drupalorg-awesome
• Put documentation about the infrastructure, the website setup, the project workflow on pages underneath it
• To collect all this information I will try to collect as much information that is already there and line out some things and collect questions on the way
• I will try to setup an online meeting with people from d.o infrastructure and Gabor and go through my questions and collaborate on some diagrams to line out how things work together
• I will create tickets for all things that arise during this documentation process at http://drupal.org/project/issues/localizedrupalorg
• I would like to figure out where the people are located that have volunteered to work on this stuff
• I have set up a google spreadsheet where you can write down your location
• https://docs.google.com/spreadsheet/ccc?key=0ArZoLumgGpTgdDNsQ0EtRjh3eXZ...
• This will generate a map with all team member locations visualized here:
• https://docs.google.com/spreadsheet/ccc?key=0ArZoLumgGpTgdDNsQ0EtRjh3eXZ...
• If I got all the locations and timezones I would like to figure out a timeslot were it makes sense to have a (maybe regular) online meeting. Google Hangout / IRC, etc.
• Accompanying of collecting information about the infrastructure / site configuration I would like to ask the d.o infrastructure team to get an anonymized dev environment where I can look at things.
• I would prever not doing development on some development server. But there might be reasons why this should be done like this as is outlined here:
• http://drupal.org/node/1018084
• If it is possible I would like to setup a vagrant project for easy local development that anyone on the team can than easily check out.
• I have also set up a twitter account where we can communicate some stuff and maybe get some attention
• https://twitter.com/drupal_localize
• A Google+ page / Account
• Where we could store/share data or documents over gDrive that should only be available to the team. Also we can use it for doing meetings via Google hangout.
• I have put the access data for these accounts in an encrypted KeePass file we can share over gDrive / Dropbox so other people on the team are able to do access these accounts. http://keepass.info/ Just in case I get hit by a bus or something and we can use the google tools without depending on someones personal account.

I have no idea how far I will come with the time I have but I think setting up the basic documents and breaking down other things into sensible work packages / tickets should be no problem. Than people can grab tasks from the issue queue if they have a minute or so.

kind regards
marcus

P.S: I will also post this at http://drupal.org/node/1773876

For the first few items about infrastructure, please keep it generic. All our sites, even Drupal.org itself, now use the same tools and processes. There is some documentation out there, that certainly can be improved.

Provided my data too, I hope to set up a meeting soon!

@Gábor Hojtsy

Ahh had a pretty crappy wifi as I was away. Only scribbling things down in some offline docs. I requested a dev environment today. #1797694: I want a LOCALIZE.drupal.org development site for ... I would like to move things on over the weekend or next week.

Just a reminder, #1751288: Set up dev sites for D7 localize is the blocking issue for Localize D7 dev sites. Once that is done, we'll be able to easily spin up dev sites to work on.