https://pantsbuild.org/ logo
#development
Title
# development
h

hundreds-breakfast-49010

01/18/2020, 1:48 AM
I guess nothing is stopping us from deliberately publicly-sharing any google docs design document link that we feel is ok for public consumption, but that's a bit of friction and I don't think anyone's been consistently doing this - I certainly haven't been
h

hundreds-father-404

01/18/2020, 1:49 AM
I’m not sure I follow. I liberally link to the Google doc in my PRs
e

enough-analyst-54434

01/18/2020, 1:49 AM
Public sharing is fine. I'd be in favor though of moving do markdown docs checked in to the repo. That would allow a normal PR to suffice as the design discussion plus have explicit sign-off. The biggest upside besides all that is you can actually reference real code well.
đź‘Ť 4
h

hundreds-breakfast-49010

01/18/2020, 1:50 AM
@hundreds-father-404 can random people who are coming across the pants project access them? and be guaranteed to access them on a long-term basis?
h

hundreds-father-404

01/18/2020, 1:50 AM
I always mark mine as “anyone with the link can comment”
h

hundreds-breakfast-49010

01/18/2020, 1:51 AM
I'm not sure what I do, I wasn't thinking about it until now
I think I generally give access to a doc to everyone on the pants-dev mailing list
a

average-vr-56795

01/20/2020, 12:19 PM
Yeah, I just “anyone with the link can comment” that kind of thing
w

witty-crayon-22786

01/21/2020, 9:19 PM
at Twitter, we have perennially had issues deciding early enough in a design process that something needs upstream involvement
and so it's very common for a doc to start closed (ie, using a google drive
@twitter.com
account) and for us to realize afterward that it should be open
when we do, we have settled for
pants-devel@
as the group to open for comments. we cannot completely open the doc for anonymous editors/viewers in that case.
the
pants-devel@
convention is "not bad" though. it allows for a good balance of "relevant folks are able to read/comment" with spam protection