On 2014-08-16 06:50-0400 Hezekiah M. Carty wrote: > I agree with Hazen here - adding hooks on day one seems overkill for > the project. [...] > Given that the project and developers are overall new to git I think > it would be premature to start stacking automated restrictions on top > of our use of the tool.
Hi Hez: I would likely be amenable to just immediately going ahead with git if we were developing our own workflow ideas from scratch, and I hadn't read all those cautionary tails (after Hazen brought up the subject, by the way) concerning tangled and largely useless git logs because of bad workflow. However, because there was group concern about that issue, we have pretty much arrived at a consensus that we should base our workflow on what has worked since 2010 for the CMake software project (which has a large web-based development community with many of them git newbies when they start and thus prone to making workflow mistakes). If you haven't done so already, please take a look at that workflow <http://public.kitware.com/Wiki/Git/Workflow/Topic> to make sure you are willing to go along with that workflow for PLplot. In my opinion, a killer feature of that workflow implementation is it has workflow rules that are enforced with an update hook (much more appealing to me than time-consuming human intervention by some inner core of our developers) to automatically make sure nobody screws up the desired "clean shape of history" of the integration branches. So leaving out that killer feature just does not make sense to me. That said, I appreciate you and Hazen are anxious to get started with git for PLplot after such a long wait, and I also feel similarly even though I am pretty much still a git newbie. So I suggest we should jointly review my decision (to not allow push to the official repo until we get the required modification of the update hook figured out) sometime late next week (say roughly in 6 days from now). That gives enough time to find out if Brad King is willing to share his implementation, and also to pursue a lot further the backup plan of modifying .git/hooks/update(.sample) appropriately ourselves. As I already stated to Hazen I am actively pursuing that backup plan as my current top priority. He and you are certainly invited to participate in this mini-project if you have time at the moment, but in any case stay tuned to this thread where I will be documenting my progress. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------------ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
