Hello David, David Eads wrote: > Hello, Trac development community! > > I'm writing because I'm (tentatively) interested in becoming involved > in the Trac development community. >
It's easy, really - just pick a few tickets you find interesting (or propose your own) and start sending patches ;-) > <snip cool background ;-) > > > * Working on a theme that uses the Blueprint css library and makes > Trac look a little slicker. I like the default theme *a lot* -- it is > a great, straightforward default, better than most open source > packages. But I'm curious how it can be made more usable by the smart > layperson. Using Blueprint has the added advantage, when mixed with > div processors, of allowing very flexible layouts. Because I don't > know Trac well enough yet, the current incarnation of the theme is > pretty unholy and hacked up, but there's a live demo at > http://blueprintdemo.invisibleinstitute.com/ if anyone wants to see. > Yep, that's interesting. We more or less have a revamp of the css in mind for some later release, see #5997 and #633. > * Experimenting with rewriting the notification system to be more > robust and have less of an explicit connection between email, tickets, > and notifications. We have 2 parts here: first about the robustness, it should be noted that the existing notification system badly needs some maintenance (Manu, *cough*, *cough*, where are you?). We have therefore lots of opened tickets there: http://trac.edgewall.org/query?status=!closed&component=notification Getting started on some of those will also help to get a better picture of the requirements for a rework of this subsystem. Such a rework will certainly benefit from both improvements to the currently not-so-existent user subsystem (see #2456 and possibly what has been done so far in the /sandbox/accountmanager branch) and from basing the notifications on the change listeners (#6543), which goes in the direction of your second point (less explicit connection). > I'm curious how I should bring this work to the > development community. I've been working against the 0.12-multirepos > branch, but it sounds like this work would make more sense in the > discussed 0.13 (enhancements) branch. Branching based off trunk or multirepos is a good idea. Though there's no official git or Mercurial mirrors of Trac, using such tools make it quite easy to maintain your own branch. If we're convinced by the patches, the next step is to get you a branch into the sandbox (where it will slowly die... hey, just joking ;-) ). > I also don't want to conflict > with other on-going projects (the journaling proposal had a lot of > paralles to what I've been doing), The journaling proposal is stale for now (three of the major motivations for this have been or will be addressed in different ways; I'll update the pages). > so I'd also love to know if there's > been much discussion of notification handling. I'd like more robust > email processing, and an architecture that makes it easier to > integrate with other services (like the dreaded Twitter). > There had been several discussions about this on this mailing list. For example: - http://groups.google.com/group/trac-dev/msg/6d117b310e2a21dd - http://groups.google.com/group/trac-dev/msg/32117737c9aa0498 - http://groups.google.com/group/trac-dev/msg/724c55ca7ad413db Not to mention lots of ideas in the notification related tickets ... Look also at related plugins on TracHacks. > * Writing a lot on effective use of Trac, deployment issues on > Debian, etc, to someday go on the soon-to-be-revamped > invisibleinstitute.com on a blog I've set up for myself. > Well, I'd *love* to see someone with good writing skills take more care of the Trac wiki itself. Be it contributing to the recently started CookBook or just sanitizing the existing docs, deprecating the various out-dated guides where they need to be, or starting the rewrite of some of the pages (e.g. the debian install guide). I think this could have a wider benefit to the Trac community, but that being said, it's not exclusive to your writing a blog ;-) > I've been writing a lot of Drupal code over the past few years, and > most of my Python knowledge was forged when I studied physics, so I > probably will wind up writing some offensive code. But I'd like to > contribute back to Trac, and help Trac kick ass. Laudable goal ;-) I'm looking forward to your contributions! -- Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
