We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 22303 MODX Staff
    • 10,725 Posts
    Great news: Atlassian has approved an unlimited user license for the MODx/xPDO projects and I have now enabled public signup from the JIRA installation. Here’s what I want to see happen:

    1. All team members who have SVN accounts are already signed up and should have access to all the systems (no action needed here).
    2. Those without SVN accounts should help test the public signup and ensure you have access to JIRA, Confluence and Crucible via your new account.
    3. Once you have access by virtue of 1. or 2., pick a system and start trying to participate by using the system as seems natural when you first encounter it. Feedback on your experience and things that might need to be adjusted (like permissions to do certain things) would be appreciated.

    I will be posting additional information and tips on how we can take full advantage of these new tools. Let’s just make sure everyone on the team can get access appropriately first.

    http://svn.modxcms.com/jira/
    signup here and participate in issue tracking system

    http://svn.modxcms.com/docs/
    confirm access to author wiki documentation, commenting, etc. here

    http://svn.modxcms.com/crucible/
    confirm access to Fisheye profile and Crucible team code reviews; more on this in subsequent posts
      • 28042 ☆ A M B ☆
      • 24,524 Posts
      I’m OK for svn, jira, and confluence, but no go with fisheye/crucible.
        Studying MODX in the desert - http://sottwell.com
        Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
        Join the Slack Community - http://modx.org
        • 7231
        • 4,205 Posts
        Question: are we to not use the old bug tracking (flyspray) system anymore?

        Question2: I would like to contribute in the wiki but I don’t know what is a good place to start. I noticed that there are some articles already covering 0961 (which is where I could contribute at the moment since I have not even peaked at 097 yet). I have been working on some stuff that I was going to post in the current wiki on snippets (the anatomy of a snippet call) and an intro to Ditto. Should I not post in the old wiki and save this for the new wiki or will the new wiki be for more "official" stuff?

        Question3: Will there be some sort of "Publishing" guidelines for the wiki? Should things be approved before published to make sure it is up-to-par? Who is the "wiki big boss" or is this not the point?

        BTW - Good show. The new setup looks really good. I just checked out the three above and they are great. I will need to poke around to figure it out completely, but my initial reaction was WoW!
          [font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

          Something is happening here, but you don't know what it is.
          Do you, Mr. Jones? - [bob dylan]
          • 28215
          • 4,149 Posts
          Quote from: dev_cw at Feb 20, 2008, 02:29 PM

          Question: are we to not use the old bug tracking (flyspray) system anymore?
          Correct.


          Question2: I would like to contribute in the wiki but I don’t know what is a good place to start. I noticed that there are some articles already covering 0961 (which is where I could contribute at the moment since I have not even peaked at 097 yet). I have been working on some stuff that I was going to post in the current wiki on snippets (the anatomy of a snippet call) and an intro to Ditto. Should I not post in the old wiki and save this for the new wiki or will the new wiki be for more "official" stuff?
          I know ConseilsWeb (Oliver) has been working on filling out the 096 space of the wiki, and I’m sure he’d love help. We’d like to get the confluence wiki (docs/) to pretty much replace the current MODx wiki at wiki.modxcms.com, so we can have centralized data. So if you want to port over articles, that’s definitely needed.

          I’ve also drafted up a rough outline in the 097 space of things that need documenting, should anyone want to try a hand at it. Documenting something is a great way to learn it. smiley
            shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
            • 22303 MODX Staff
            • 10,725 Posts
            Quote from: dev_cw at Feb 20, 2008, 02:29 PM

            Question: are we to not use the old bug tracking (flyspray) system anymore?
            It will be retired when we publicly announce JIRA.

            Quote from: dev_cw at Feb 20, 2008, 02:29 PM

            Question2: I would like to contribute in the wiki but I don’t know what is a good place to start. I noticed that there are some articles already covering 0961 (which is where I could contribute at the moment since I have not even peaked at 097 yet). I have been working on some stuff that I was going to post in the current wiki on snippets (the anatomy of a snippet call) and an intro to Ditto. Should I not post in the old wiki and save this for the new wiki or will the new wiki be for more "official" stuff?
            Converted stuff from the existing wiki would be a good place to start. Let’s try and coordinate that stuff, though I’m not sure the best way to do so at the moment. Suggestions anyone?

            Quote from: dev_cw at Feb 20, 2008, 02:29 PM

            Question3: Will there be some sort of "Publishing" guidelines for the wiki? Should things be approved before published to make sure it is up-to-par? Who is the "wiki big boss" or is this not the point?
            Likely there will be publishing guidelines, but again, I’m just as new with this software as everyone else. This is why I need folks to "try it out" and see what works best.

            Quote from: dev_cw at Feb 20, 2008, 02:29 PM

            BTW - Good show. The new setup looks really good. I just checked out the three above and they are great. I will need to poke around to figure it out completely, but my initial reaction was WoW!
            Indeed, the tight integration between these tools is simply wonderful; if we can get a good grip on how to use these tools properly (i.e. develop good processes with it), it should improve project contributions both in terms of quality and quantity.

            Just wait until I show you how anyone can signup and submit a patch into Crucible which the team can then review (pre-commit) in context of the current code in SVN and then decide whether to adopt as-is, refactor and adopt, or reject altogether.
              • 22303 MODX Staff
              • 10,725 Posts
              Quote from: sottwell at Feb 20, 2008, 02:29 PM

              I’m OK for svn, jira, and confluence, but no go with fisheye/crucible.
              What is your experience when trying to login to fisheye/crucible?
                • 28042 ☆ A M B ☆
                • 24,524 Posts
                Never mind, I must have mistyped one of the characters. Can’t see well enough to tell i from I from l from ! from 1 until I enlarge the font.
                  Studying MODX in the desert - http://sottwell.com
                  Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                  Join the Slack Community - http://modx.org
                  • 27708 MODX Staff
                  • 2,502 Posts
                  No Problem getting in...
                    Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup magician. Blog ✦ Twitter ✦ LinkedIn ✦ GitHub
                    • 7231
                    • 4,205 Posts
                    Converted stuff from the existing wiki would be a good place to start. Let’s try and coordinate that stuff, though I’m not sure the best way to do so at the moment. Suggestions anyone?
                    I would hate to convert something to find out that someone else has already done it! The only suggestion I could think of would be to put together a team or at least a coordinator and assign or organize tasks to keep it straight. There are a few wikis that could use an update too. Maybe since ConseilsWeb (Oliver) has started this process he could coordinate (I hate to volunteer someone behind their back). I could do it, but I just got on this bus and haven’t earned a window seat yet grin
                      [font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

                      Something is happening here, but you don't know what it is.
                      Do you, Mr. Jones? - [bob dylan]
                      • 33337
                      • 3,975 Posts
                      I must say its great update!

                      I confirm working SSO for me smiley
                        Zaigham R - MODX Professional | Skype | Email | Twitter

                        Digging the interwebs for #MODX gems and bringing it to you. modx.link