We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 26903
    • 1,336 Posts
    Sorry if this is the docs somewhere but just to clarify, looking at the new JIRA we don’t have a components project any more, so :-

    1. I assume we file bugs against components in GitHub, i.e. Shauns area mainly by raising issues.
    2. The components svn repo is now effectively dead?
    3. Bugs raised against core/XPDO are still raised in JIRA, not as an issue in GitHub.

    The move to GitHub is great in many respects but I’m not sure how detaching this from the Atlasian toolset(Crucible/Fisheye) is meant to work yet.
      Use MODx, or the cat gets it!
      • 28215
      • 4,149 Posts
      Quote from: shamblett at Aug 17, 2010, 12:40 PM

      1. I assume we file bugs against components in GitHub, i.e. Shauns area mainly by raising issues.
      Correct; bug tracking is now decentralized, and we prefer people use GitHub. modxcms.com/extras also can integrate with your GitHub repo, if you have a GitHub account.

      2. The components svn repo is now effectively dead?
      Correct.

      3. Bugs raised against core/XPDO are still raised in JIRA, not as an issue in GitHub.
      Correct.

      The move to GitHub is great in many respects but I’m not sure how detaching this from the Atlasian toolset(Crucible/Fisheye) is meant to work yet.
      We’re still debating using Crucible/Fisheye at all; primarily for the future we expect to only use Confluence (wiki) and JIRA in the Atlassian stack.

      Source code management and tracking we’d like to decentralize to github.
        shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
        • 26903
        • 1,336 Posts
        Ok thanks
          Use MODx, or the cat gets it!
          • 28215
          • 4,149 Posts
          We *really* want people to start using GitHub more, as it allows for easier collaborative development - you can submit patches to MODx or Extras directly without having explicit SVN access. This is a huge boon to collaborative work in MODx.

          So, the more we get people using Git, the better for MODx. And we’ll continue to build more integration into GitHub with your Extras as GitHub continues to upgrade their public APIs.
            shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
            • 26903
            • 1,336 Posts
            Yes agreed, I’ve moved some of my extra’s already and will move the others as we go, the ability to fork/push and branch easily allowing different people to work together is seriously good. I’ve used Git before but not as collaboratively as this, this is it’s great strength IMHO. Even the somewhat limited issue tracking provided by GitHub seems to work Ok.
              Use MODx, or the cat gets it!