You're right, we definitely need this. On Saturday, January 2, 2016 at 4:54:18 PM UTC-5, Steve Piercy wrote: > > OK, so we need to set that expectation in a contributing.md > document for the repo. We cannot assume that contributors know > our process when it's not documented for a given repo. > > GitHub uses contributing.md: > > https://help.github.com/articles/setting-guidelines-for-repository-contributors/ > > > Example from another Pylons Project: > https://github.com/Pylons/pyramid/blob/master/contributing.md > > I've logged an issue for trypyramid.com: > https://github.com/Pylons/tpc/issues/35 > > --steve > > > On 1/2/16 at 1:33 PM, bla...@laflamme.org <javascript:> (Blaise Laflamme) > pronounced: > > >Contributor should be able to compile and see their own changes > >before they submit PRs, and we should do the same when > >reviewing. The dev branch I was proposing earlier was to help > >us merging PR and make sure we don't publish unfinished work on master. > > > > ------------------------ > Steve Piercy, Soquel, CA > >
-- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-devel+unsubscr...@googlegroups.com. To post to this group, send email to pylons-devel@googlegroups.com. Visit this group at https://groups.google.com/group/pylons-devel. For more options, visit https://groups.google.com/d/optout.
