I've been working on OSQA internally for a project and I'm keen not to diverge too far from SVN trunk. We've been really impressed with OSQA and have benefited from other's work here, so this is also a way of paying back a little.
What's the process for requesting for patches to be reviewed/landed in SVN?
I'd much prefer to send pull requests - Git's SVN bridge works great and I assume https://github.com/OSQA belongs to the project? I understand SVN is used internally, but it'd actually be really easy for one of the project engineers to keep a git clone of the SVN repo internally and push and pull to the GitHub repository from there, merging work back to SVN over the bridge.
Here's the basics: Effectively Using Git with Subversion
One word of warning though. If you're on Windows, all of these bridge implementations will cause you all end of problems if your line ending support isn't properly configured. Make sure you use LF everywhere except in the Git working directory - otherwise merge conflicts will make this impossible:
Help.GitHub - Line endings
IMO it'd be well worth the time having someone learn how to do this. I've seen a lot of chatter here about people wanting to contribute in this way.
Major New Functionality
Since I first posted these patches, I've added an entirely new theme, endless pagination and PJAX support to OSQA. It's very stable and massively improves the frontend experience when using OSQA. Background here:
Changes are available on my OSQA-SVN/OSQA fork on GitHub - https://github.com/BinaryRage/OSQA
Each commit is linked from the JIRA issue. Add .patch to the end of the URL to generate a patch. The entire set will apply cleanly to SVN 1230. Enjoy!
- OSQA-779: Fix accept rate calulation. Now reflects the expected behaviour of end-users used to Stack Exchange sites
- OSQA-809: Includes summaries on the 'Question' and 'Unanswered' tabs. The index page is now a summary page, and the Questions tab is not selected
- OSQA-810: Improved default theme for OSQA
- OSQA-811: Replace WMD with PageDown. PageDown is the reverse engineered and improved version of WMD used at Stack Exchange. Also fixes the text area grippie that should appear at the bottom of the editor, but was lost in the style transition from CNPROG. AJAX upload isn't wired up however, so if someone on the core team could give an opinion on effort on that and if that's something you can manage internally great, otherwise I'll see if I can look at it in the next few weeks (it's not a core requirement for our project, but I did need to fix the editor)
- OSQA-814: Google Libraries API - allow to be turned off in favor of local resources, fix mixed content warnings when using SSL
- OSQA-815: Configurable resource minification. Turns off minification is the setting is disabled or DEBUG is enabled. Includes both Google API and local files, media tag looks for <filename>.min<ext> in the media directory
- OSQA-816: Improved Markdown autolink extension. Better handles punctuation and includes question titles if raw links link to a question
- OSQA-817: Load Google API resources directly. Combine jQuery/UI when loaded locally. Configurable CSS sprite support with automated generation
- OSQA-818: Slightly improved English locale. Capitalisation for the tab labels, improve badge and question sort descriptions
- OSQA-820: Configurable anonymous voting
- OSQA-663: Add setting to display real name instead of screen name
- OSQA-425: LDAP authentication module updated slightly to work on latest code
- OSQA-821: Related question results now show whether questions have answers
- OSQA-826: Highlight important questions
Other things I'm considering are in GitHub issues. I'll add them to JIRA if I get around to them:
New default theme
New autolinker that doesn't include punctuation and adds question titles
Web config panel for added fronted optimisations
PageDown editor with fixed grippie
Answer display in related questions search
Highlighting of interesting tags
27 Feb '12, 06:50