That sounds good. How about we revive 'mapnik-svn' (maybe rename to 'mapnik-code' or something) and send both commits and ticket comments to it?
Dane On Oct 12, 2009, at 4:14 AM, Artem Pavlenko wrote: > +1 good idea. We can create a separate list or revive : > https://lists.berlios.de/pipermail/mapnik-svn/ > Artem > > > 2009/10/11 David Leaver <[email protected]>: >> Sounds good to me. >> >> So long as they are tagged so we can differentiate mailing list >> messages >> vs Trac messages. >> Either that or another mailing list, mapnik-trac ? >> >> Cheers, >> Dave. >> >> Dane Springmeyer wrote: >>> Mapnik-dev, >>> >>> While this list is fairly quiet, we have quite a bit of development >>> activity and discussion on the Trac site via tickets. In many ways I >>> think this is ideal as discussions are logged nicely against issues >>> and not all people subscribe to the mapnik-devel list. >>> >>> But, it raises the question: Should we cc ticket activity to mapnik- >>> devel so that people subscribed can also follow ticket activity? >>> >>> Post your vote, + or -. >>> >>> Thanks, >>> >>> Dane >>> _______________________________________________ >>> Mapnik-devel mailing list >>> [email protected] >>> https://lists.berlios.de/mailman/listinfo/mapnik-devel >>> >> _______________________________________________ >> Mapnik-devel mailing list >> [email protected] >> https://lists.berlios.de/mailman/listinfo/mapnik-devel >> _______________________________________________ Mapnik-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/mapnik-devel
