Opened 3 years ago

Last modified 3 years ago

user story #104 (new)

Steps to aiding community

Test Complete Size: undefined Test Complete Date:
Documentation Complete Size: undefined Documentation Complete Date:
Acceptance Complete Size: undefined Acceptance Complete Date:
Reported by: dfraser Owned by: ja11sop
Milestone: Undecided Component: agile-trac.org
Version: Keywords: suggestion
Cc: Blocked By:
Patch SVN Revision: Patch Trac Version: not_applicable
Blocking:
In Iterations: None

Description

OK, this should really be type "suggestion" - please consider as constructive attempt to help...

My observations:

  • This is a fantastic project
  • Looking at the timeline, one ja11sop is currently doing all the work
  • The rate of ticket increase is greater than the rate of ticket decrease
  • Some tickets (#91, #94, #101) have patches that could be applied, but ja11sop seems overloaded
  • Hey, this is agile! It needs a team!
  • Getting more developers to help, forming a community would be great

Of course you don't want to give people commit rights if they're going to mess things up... and you have a clear vision for where the project should be going, so the key is harnessing any available energy to meet those ends well

My social suggestions:

  • A recommended IRC channel for discussion (even if it's #trac)
  • A mailing list (which is where I would have posted this if there'd been one)

My technical suggestions:

  • This is about agile development ... unit tests would really help, right?
  • Give people who already contribute to other trac-related projects and submit patches commit rights
  • It would also be nice to be able to contribute to the wiki

Basically I'm keen that the project moves forward fast enough so that new people coming along find their issues addressed and stay with the project...

Any comments?

Change History

Have a look at the list of modified files related to this ticket.

Changed 3 years ago by ja11sop

Wow, thanks a lot for taking the time to provide such a thoughtful list of ideas. This is clearly the start of a deeper discussion which I'll follow up with offline (expect an email - if you don't get one comment back here). A quick response to some of your comments though.

  • yes growing the project with a larger team is definitely goal
  • yes, recently most commits have been through a single developer, though quite a few have been the result of a wider discussion. In fact the whole project grew out of the work of team of 5 people.
  • growing a community has been something that is getting overdue. The initial plan was to stabilise the current plugin as much as possible but that has taken a little longer than hoped.
  • a mailing list is high on the list of things that need done
  • an open wiki is a good idea, though lower priority than some method of discussion (like a mailing list)
  • we're certainly keen to grow the number of active developers and improve the simplicity and quality of the plugin

So in short I agree with pretty much most of what you said. I envisage this thread might grow more which will be a good thing.

Changed 3 years ago by dfraser

OK so some good discussion in email, and nice to hear the above. I'm going to start hanging out in  #agile-trac on freenode - it's unregistered but the main trac channel is very full, and if anyone else wants to join it may grow into a place to discuss things...

Changed 3 years ago by ja11sop

Yes - hopefully use of the IRC channel will grow. Certainly an effort will be made to grow a presence there.

Note: See TracTickets for help on using tickets.