Drupal.org Git Team

Welcome

The Git migration is complete, but the work is ongoing. Join us!

Drupal.org Git Team

podarok's picture

Drupal long-term advanced training program - stage 1

Start: 
2013-09-06 (All day) - 2013-09-07 (All day) Europe/Kiev
Organizers: 

9 sessions - one (2-3 days) per month

Course program

<

ol>

  • Introuduction session (group still opened) (2 days)
  • Drupal.org (group still opened) (2-3 days)
  • Drupal Code of Conduct, Code Style, Core gates + module creation (this and others groups closed) (2-3 days)
  • Core (Release) + module creation (2-3 days)
  • Theming(release) + module creation (2-3 days)
  • Drupal Core (HEAD) + VCS (git..) + code review + core patches + increase learning curve (2-3 days)
  • Contrib + Server + Security (2-3 days)
  • Read more
    eliza411's picture

    Phase 1 of the Drupal.org Testing Initiative Concludes

    Background

    Back in April, a handful of us from the Git team set out to create functional tests to tell us if Drupal.org is working as expected when new features are developed and before new code is deployed.

    We had the great good fortune to start this project when CapGemini offered the Drupal community three Drupal developers full time for six months. It was my privilege to work closely with these talented and motivated individuals to implement a comprehensive set of tests. We could not have come nearly so far as we have without them.

    Accomplishments

    Read more
    eliza411's picture

    BDD Testing Community Demo

    Start: 
    2012-09-10 07:00 - 08:00 America/Los_Angeles
    Organizers: 

    The BDD testing team has been working to make the transition from Drupal 6 to Drupal 7 (and all future improvements) as smooth as possbible. Join us on Monday, September 10 at 7am PDT / 10am EDT for a demonstration of just a few of over 100 feature tests, learn how you can get involved, and pick up great ideas for quality assurance for your own client projects!

    The demo will last no more than 30 minutes with an additional half-hour for questions and answers.

    A brief background on BDD:

    • What it is
    • How it can be used, and how it is being used on Drupal.org
    Read more
    kamranzafar's picture

    Software Engineer | Cognitive Axis

    Employment type: 
    Full time
    Telecommute: 
    Not allowed

    Hi,
    We here at Cognitive Axis are in need of a resource who possess skills and can be an addition to our team. Kindly forward your Resume/CV at your earliest to careers@cognitiveaxis.com.

    Requirement:
    Good knowledge of Web Development Standards and Technologies
    Knowledge and experience in PHP and PHP frameworks like Drupal, WordPress and Joomla is a plus.
    Good grip of CSS, Javsscript, JQuery , XML etc.

    Responsibilities:
    Requirement Analysis.
    Understanding of Current Web Application.
    Follow and maintain design and coding standards.

    Read more
    eliza411's picture

    Web Acceptance Testing with Behat and Mink

    Start: 
    2012-07-27 08:00 - 08:45 America/Los_Angeles
    Organizers: 

    Automated testing is great for code, but what about testing your Drupal site when you've configured all that code and you need to see that users are able to do what you want them to do? Behat and Mink provide a flexible and robust acceptance testing framework to check application behavior and help deploy new features and security updates with confidence.

    Read more
    eliza411's picture

    Git Scrum Call

    Start: 
    2012-05-18 13:00 - 13:30 America/Los_Angeles
    Organizers: 

    Note the time change!

    Currently happening on Skype. Ping me via my contact form or in #drupal-vcs with your Skype info to get dialed in.

    1. A very brief go-round (10 minutes total) where you tell:
      • What you have done since we last talked.
      • What you are working on before our next call.
      • If you are you blocked (and if so, by what).
      • If you have a topic for longer discussion after the go-round.
    2. Discussion (20 minutes)
    fotuzlab's picture

    Code standard check at the time of git commit

    Was wondering if we could include pre-commit git hooks in module/theme repositories to check drupal coding standards. (Like the ones provided by http://drupal.org/project/git_hooks).
    This would help in standardizing the code on d.o

    The only problem I find is ... new contributors may find it irritating and hence put them off.

    Thoughts???

    eliza411's picture

    Git Scrum Call

    Start: 
    2012-05-11 10:00 - 10:30 America/Los_Angeles
    Organizers: 

    Currently happening on Skype. Ping me via my contact form or in #drupal-vcs with your Skype info to get dialed in.

    1. A very brief go-round (10 minutes total) where you tell:
      • What you have done since we last talked.
      • What you are working on before our next call.
      • If you are you blocked (and if so, by what).
      • If you have a topic for longer discussion after the go-round.
    2. Discussion (20 minutes)
    eliza411's picture

    Git Scrum Call

    Start: 
    2012-05-04 10:00 - 10:30 America/Los_Angeles
    Organizers: 
    cgireeshs's picture

    How do i commint my new project

    I have started a new project,I need to commit my codes .How do i commit my code Please help

    webchick's picture

    Upgrade Drupal.org to Drupal 7 Sprint!

    Start: 
    2012-04-23 (All day) - 2012-04-27 (All day) America/Los_Angeles

    The week of April 23 - April 27, the Drupal Association is sponsoring a sprint, hosted by the Oregon State University Open Source Lab, to upgrade Drupal.org from Drupal 6 to Drupal 7!

    The sprint will be mainly focused on the following areas, and the following attendees will be there:

    Read more
    webchick's picture

    Drupal.org Office Hours

    Start: 
    2012-04-09 11:00 - 12:00 America/Los_Angeles
    Organizers: 

    Come to Drupal.org office hours to share what you're working on and help us come up with the weekly drupal.org hit list!

    Stop by #drupal-infrastructure from 11am to 12pm Pacific Time (18:00 - 19:00 UTC).

    BoF Discussion notes from Denver 2012 DrupalCon

    The Current Needs, as outlined by @sdboyer

    • Git components are currently managed by several disparate tools, Puppet, ...
    • Version control git modules are functionally complete, but need to make it through testing.
    • Setting of default branches is now tested and working.
    • Sdboyer needs to distribute more of his current server management responsibilities to other people, but there are access and permissions blockers. Marco, Howard, Pat, @drumm, @bejeebus, and @webchick are available to help. @drumm will email OSL to ask for the needed access changes.
    Read more
    dstuart's picture

    Can't cut dev release

    Hi,

    For some reason I am not able to cut new dev release since migration. I have checked into the HEAD and the 6.x-1.x release and it still doesn't seem to build any ideas?

    http://drupal.org/project/apachesolr_views

    I'm sure its just a training issue, but your help would be appreciated

    Regards,

    Dave

    sdboyer's picture

    Building a Drupal.org deployment pipeline

    Leading Drupal's migration from CVS to Git made something eminently clear to me (and eliza411, the migration's PM): there's a lot that's broken about how we manage, maintain, and improve drupal.org (and its subsites). Since then, I've been gradually chatting up more and more people with the idea that we could build a structured, participatory model for updating and adding new features to drupal.org. And that if we do it right, it could become a best-practice model for (Drupal) site management (open, participatory) workflows.

    Read more
    eliza411's picture

    Git team lightning talks

    Start: 
    2011-05-10 12:00 - 12:20 America/Los_Angeles

    Join us from noon - 12:20pm PDT to learn about the two Git-related Google Summer of Code projects: Drupal.org Auth compatible Git and Http daemons and Version Control Activity logging, Activity Streams and Development Statistics.

    WebEx: https://shomeya.webex.com/shomeya/j.php?ED=150662272&UID=1180180112&RT=MiM0
    Access code: 805 789 868
    Phone Number: +1-408-600-3600

    eliza411's picture

    Git team lightning talks

    Start: 
    2011-04-26 15:00 - 15:20 America/New_York
    Organizers: 

    Join the Git team for our regularly scheduled, semi-weekly demonstration of progress on new features for Git and Drupal.org. This is a great opportunity to see what's happening and find a way to become part of the team. We'll be looking at interface mock-ups for new functionality: adding service hooks and setting a default branch.

    Location: https://shomeya.webex.com/shomeya/j.php?ED=150662272&UID=1180180112&RT=MiM0
    Dial-in: 1-408-600-3600 (You should be able to join via your computer's headset.)
    Access code: 805 789 868

    rfay's picture

    Testbots now use git to apply patches, so binary patches and copies/moves work in patches

    The testbots now use git to apply patches, so binary patches and copies/moves work in patches. See the issue.

    To create a binary patch: git format-patch --binary --full-index --stdout

    To create a moves-and-copies patch (one that magically moves and copies): git format-patch -C -M --stdout

    dww's picture

    Change convention for referencing issues in commit messages?

    This started life over as a comment I posted at #1059966-20: Change recommended format for commit messages (no more '#1234 by abc') but I'm moving it here at eliza411's suggestion to hopefully gather more feedback on the proposal...

    Sorry I didn't suggest this sooner, but I just came up with it today while I was happily doing Git commits on a plane. ;)

    Instead of:

    Issue #1234 by xxx

    How about this?

    [#1234] by xxx

    Read more
    rfay's picture

    Phasing out -p0 patches - May 31?

    When we did the Git migration, we set up the testbots to continue to allow both -p0 (old style Drupal patches) and -p1 (the normal Git style patches), but started encouraging the community to switch. This allowed existing patches on issues to continue to test OK, and avoided irritating everybody enormously.

    However, now we have a problem. How do we teach people to successfully apply patches if there can be more than one kind? I think we have to phase out -p0 patches sooner rather than later. This would mean:

    Read more
    Subscribe with RSS Syndicate content

    Drupal.org Git Team

    Group organizers

    Group notifications

    This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

    Hot content this week