EzDevInfo.com

Commit without whitespace changes on github

Is there a way to display a commit on github.com without showing whitespace changes?

Is there a way to display that from console? i.e. clone and then look at commit (tree) locally ignoring all white space changes?

I use Trac extensively; I'm looking for something similar to Ignore White space changes (which can be found on the changeset view).

How to export Trac to Github Issues

We use Trac for an open-source project I'm working on. I'd like to export all of our open tickets to Github's Issues. I've found a couple small scripts that might do it, but I was wondering if anyone has done this and has suggestions.

Ideally, it would convert trac's description syntax to markdown and also export metadata like milestone information, but even a simple, working export is probably okay.

Is there an equivalent to Trac written in PHP? [closed]

Is there an equivalent to Trac written in PHP? I need something that integrates with SVN and is free. It should allow me to browse the SVN source, have some kind of bug tracking and show recent changes in the SVN. A wiki isn't essential.

Thanks in advance.

What are some recommended plugins for Trac?

In particular, I need a more full fledged version of Trac to support robust project management, and task tracking. I went through the plugins and literally found over 50 that looked promising.

My question is to the admins/users of Trac: which ones are indespensible for making Trac feature complete and which ones should be avoided (e.g. stability issues)?

"make_sock: could not bind to address [::]:443" when restarting apache (installing trac and mod_wsgi)

I'm trying to install trac and mod_wsgi over SSL. I tried to manually install it, but that didn't work out so well so I started to follow this: trac-on-ubuntu

I skipped the svn part because I'd like to use git instead. After the first edit of httpd.conf:

WSGIScriptAlias /trac /var/trac/apache/trac.wsgi

<Directory /var/trac/apache>
    WSGIApplicationGroup %{GLOBAL}
    Order deny,allow
    Allow from all
</Directory>

I restarted apache only to get this error:

* Restarting web server apache2                                                    

(98)Address already in use: make_sock: could not bind to address [::]:443

                                                                     [ OK ]

Doing these showed nothing.

 netstat -anp | grep 443 
 fuser 443/tcp

Doing this didn't yield anything except the grep command that I ran:

ps -aux | grep httpd

Why is it saying that something else is using the port when there's nothing showing up?

EDIT: You guys are going to laugh at this. I had an extra Listen 443 in ports.conf that shouldn't have been there. Removing that solved this.

Trac vs. Redmine [closed]

I'm working in research and my bioinformatics work group needs a project management software for keeping track of multiple projects (Linux environment). Originally, we planned for using TRAC but then I got aware of REDMINE. Moreover, I read in some earlier posts from 2008 and 2009 that many projects had switched to Redmine. Right now, I cannot find any up-to-date or reliable comparison between both systems and thus cannot wage which one is better (maybe both are equally good).

My question:

Does anyone of you have recent experience in one or even both of these systems and can point out some (big) advantages/disadavantages of either Redmine or Trac (or even both)?

Requirements would be:

• svn and/or dcvs (Git) support
• document management
• ticketing
• bug tracking
• wiki / internal blog (i.e., knowledge management)
• multiple project support
• installation should be as easy as possible
• there shouldn't be hundreds of plugins to be installed before getting a usable project management software up and running (base installation should have most features)

Thanks a lot for your time! Cheers

Trac: code review plugin [closed]

I'm looking for a code review plugin for our trac installation.

I found these two as the top result for "trac code review" query on google

• PeerCodeReview
• CodeReview

I'm leaning towards PeerCodeReview plugin.

Requesting the SO community for inputs about these plugins to help me select the one for our trac installation.

If you know about any other plugins please let me know about those as well. :)

What I'm looking for in the plugin

• A Way to annotate code with comments.
• Approve/Dis-approve ; kind of like a button to inform that code needs to change. maybe a bug is created.
• A way to assign code review "Task" to a person(s).

The first feature is required (I guess that's the whole point); others are optional. I can hack trac to get something similar to fit into that workflow. Hopefully! ;)

web based subversion viewer [closed]

Is there a tool that allows me to point to a subversion repository to browse the contents of the repository. I am thinking something similar to what trac provides with SCM. I describe some of the features here for those not familiar with trac's source integration:

• access it from a browser - it must be a webapp
• ability to view any version of a file. Preferably this feature can be invoked using a url. This means one can link to a specific version of a file.
• display on a single page all the modified files in a changeset (gravy: show the diffs of the modified files)
• ability to display (in a color coded way) the diff between two versions of a file with the ability to invoke it using a url.
• a time line of changes to the repository with modified files for each changeset.
• It would be great if it's open source but doesn't have to be.

What other features should a whizzbang web based repository viewer have?

Do you need a project management system if you work alone? [closed]

Do you need a project management system if you work alone? I mean a project management system that includes issue tracking, wiki, etc. Currently I keep my issues in a very good organizer software and I keep project documentation in Word files (and of course I have a version control system), so I am not really sure if I need a project management software, because I work alone.

One useful thing, I can think of, that project management system can additionally give me is linking issues with commits (UPDATE: I've found this feature useful enough: for example, right now I am creating documentation for the new release of my project and I consequently open every issue with "Pending for release" status, then I read the issue's description and then I can quickly view the diff of the commit for this issue - this helps me to see details and write better documentation).

Another one - sharing issues so your users or your employer can view or manage them.
What am I missing? Is project management software necessary when working as the only programmer?

UPDATE: I've thought up another useful thing: In comments we can give a link to an issue or a wiki article with detailed information about the code being commented.

What headaches should I expect from using Trac?

No tool is perfect, and I'm about to start several long-term projects using Trac, and wanted a heads up of the kinds of problems I may or may not experience with it. In other words, Trac meets my needs in the short term, and I've already made the decision to use it, but I want to know what to expect down the road.

I am not looking for:

• "Use product X instead of Trac because..." answers.
• "Trac is great because..." answers.
• A comparison to any other specific system.
• "Trac doesn't support Feature X" answers. I can read the feature list too, thank you very much.

I am looking for:

• "Feature X does not behave as expected..."
• "Trac behaves oddly when..."
• "Trac doesn't fully support..."
• "Trac itself has a known bug that will likely never be fixed..."
• And especially "Trac can't handle..."
• etc

So, what Trac-induced headaches do I have to look forward to?

For future reference, this question was asked while Trac v0.11 was the latest stable release.

How do you handle multiple (overlapping) projects in trac?

We are using trac and are really satisfied with it. However, out of the box, trac is best suited for single-project environments only. I'd be interested to hear about the various approaches people take to make it work with multiple projects nevertheless and their experiences with them. Are there any plugins to recommend? Any patches, tweaks or whatnots? Are you maybe even using an entirely different bug-tracking system that offers all of trac's functionality plus multi-project support?

We recently started managing a second project ourselves which generally works okay but also has some drawbacks, especially where the two projects overlap because of common library code we wrote that is used in both projects. How do you handle this?

(I'll attach our own current approach as an answer to this post.)

Managing Milestones and Web development Project

I am trying to implement Trac+SVN. But am encountering a project management issue. To give you a background, most of my projects are related to web development (they go thru phases like design, programming, testing etc.).

Now I am implementing Trac for my projects. Now the problem is what should I place as milestones and tickets. For tickets how granular should I get? e.g. should I say Make X part of Y feature or Make Y feature only. The more tickets I make, the more time I spend making these tickets.

Also, for milestones, I have seen projects like CakePHP etc. When they use Trac, they set their milestones as version numbers (corresponding to tags in the SVN). Is that the best way?

So say I have a client whose final deadline is X date. Then I set my milestone as 1.0 with deadline as X. But then how do I track the project say weekly? Cause I don't want to realise one day before the release date that that too much is left. I want to have somehow weekly checks.

Also I want to take into account enhancements/bugs also as tickets and club them together as milestones.

Ive imagined something like 1.x.x where first x corresponds to group of feature enhancements while second x corresponds to bug fixes. Is there a better way? How do I manage weekly status in such a system?

Is there a standard way to do this? How do I go about it? Am totally confused.

Thank you.

Improving our dev environment at work

In the near future i will get some 2 weeks for moving and improving our development environment at work.

We mainly develop one large PHP/MySQL project with 2-10 developers.

At the moment we have one dev server, running apache with mod_userdir, each dev has a /public_html folder in his (samba-accessible) home. For VCS and Project Management/Issuetracking we use Subversion and Trac. Testing/Deployment takes some manual steps, not much automation there.

My plans for the new setup include the following changes to the existing stuff:

• Continuous Integration
• Integrate CI to Trac, create/find a plugin which offers to start actions after success or failure of the build progress (i.e. deploy to staging/live)
• Create automated deployment-scripts (one-click)
• Integrate (Doxygen)-Documentation into the build-progress and somehow into Trac
• Add automatic versioning
• Add another layer of monitoring (local nagios monitoring our production-system-nagios)
• Add a nightly running MySQL Replication Slave, which can then by the developers be used to test stuff on up2date data
• Review the backup plans
• Document how and why I set everything up in this way

Do you have any tipps/hints what can be improved further? Anything we should do in a different way?

"Selling" trac/buildbot/etc to upper management

My team works mostly w/ Flex-based applications. That being said, there are nearly no conventions at all (even getting them to refactor is a miracle in itself) and the like.

Coming from a .NET + CruiseControl.NET background, I've been aching to getting everyone to use some decent tracking software (we're using a todo list coded in PHP now) and CI; I figured trac+BuildBot would be a nice option.

How would you convince upper management that this is the way to go, as well as some of the rules mentioned in this post? One of my main issues is that everyone codes without thinking (You'd be amazed at the type of "logic" this spawns...)

Thanks

How best to do Agile Development with Trac? [closed]

We use Trac as our bug tracking / development / wiki system and I was wondering if anyone has experience and uses some of the Trac Agile/Scrum plugins or functionalities? Anything you'd recommend?

Or would it be better to duplicate Trac tickets as dead-tree user story index cards and a hand-drawn burndown chart?

Note that I found a similar question here. Though it's specifically about Scrum. They recommend Agilo. Has anyone tried Agilo yet?