> Trust me. Take it from somebody who has been working full-time for > years on an 10 year old open source project (so the processes are > mature). Workflow in a tracking system can work, but you have to > commit to it. No half-way efforts. (For patch review and tracking) > Either use e-mail 100% of the time or tracking 100% of the time. Not > both.
The first mail (from john) was about this choice : my vote as user and occasional submitter goes for tracking 100% of the time. > > > feel the need to discuss your patch, we suggest you start a > > new thread for that on the madwifi-devel mailing list and refer to > > the ticket that has the patch attached. Don't forget to explain > > what your patch is intended to do. > > " > > > *And* to give devs/maintainers an easy way to keep track and review > > patches. > > Of course. I would suggest having them have to use a tracking system > *and* e-mail for this process is overly cumbersome too. Rather than > simply starting to make comments on a patch posted, now they have to > go back to the patch owner and say "ok, now I need you to post that > same patch to the ML so that I can open it back up, try to remember > what I wanted to critique and start writing my response". I agree this case is really cumbersome. > > > I don't know any tracking system (except review-board) offering > > what the devs want: inline review of patches. > > Bugzilla does it just fine. Patch owner attaches a patch to a ticket, > then the reviewer then "opens the attachment in a comment" (that's a > bugzilla feature) and goes about commenting, inline, on what he likes > or doesn't like, the result being a new comment in the bug. Oups, I never paid attention to it... :/ > > > So there is no right tool to > > satisfy them. > > I disagree. You are right. > Perhaps. I know BZ lets you do it. I don't know about Trac. But it > seems that Trac already fails the "review inline" requirement anyway, > so why bothering arguing about what else it doesn't do. > > > I don't think it's worth the migration and configuration cost. > > To get inline review, where the only alternative is this mish-mash of > a tracking system and e-mail that means more work for both posters and > reviewers? I guess that's a call for the owners of the project. > Whether they feel the migration effort is worth attracting and keeping > contributors or not. Certainly not my call. Perhaps they read the list and they will agree with John for improving Trac configuration (or decide a bigger move), or state things stay the same : bugs in tracker, patches in mailing-list. Regards, fred _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
