Remy Blank wrote: <snip> > - What are the currently "hot" topics for core developers? I would > rather invest time on an issue or feature that is perceived as being > important (desired, interesting, cool, etc.) than any old issue. This > would also lower the risk that a contribution would be left out because > other things are more important at some point.
Some of the hot topics are (definitely not all inclusive): * Workfow * Internationalization (asmodai, scheduled for 0.12) * Multi-repos support (cboos) * Account management * Notification > - Once a desired work topic has been found, I would need some help for > defining the general direction for a solution. It would not be very > efficient to just run head down into some direction, only to get told > later that it wasn't adequate. As Eli said, this was part of his motivation in calling for lieutenants. Also, many devs hang out in #trac on irc.freenode.net. IRC is generally a good way to get help and find someone to "mentor" you. > - What would be the workflow for contributions by non-core developers? > Would I send patches against trunk or a branch, and have them reviewed? > Should the patches be reviewed by one core developer (a tutor) or should > the patches be reviewed on trac-dev? Or should I use an > externally-accessible DVCS (I'm currently using Mercurial)? This would depend a little on what topic you're working on. For general bug fixes, etc. Patches against trunk and attached to tickets are the best option. Also, if you are tackling a ticket that doesn't seem to be very high traffic, pinging a developer via IRC or via trac-dev is recommended. If it is a larger feature change, there should be a branch where the majority of work is taking place. For example, cboos already has a multirepos branch that he has been working on [1] > In short, I would need a topic, some initial guidance, and regular > feedback. Does that sound reasonable? Very reasonable. -John --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
