Re: [pgsql-www] Where to put shared designs/images
От | Josh Berkus |
---|---|
Тема | Re: [pgsql-www] Where to put shared designs/images |
Дата | |
Msg-id | 52F97893.2060706@agliodbs.com обсуждение исходный текст |
Ответ на | Where to put shared designs/images (Josh Berkus <josh@agliodbs.com>) |
Ответы |
Re: [pgsql-www] Where to put shared designs/images
Re: [pgsql-www] Where to put shared designs/images |
Список | pgsql-advocacy |
>> I think github (or maybe bitbucket, does mercurial have the same >> issues as git for dealing with images?) is probably the way to go. we >> need something where people can do social coding without a lot of >> permissions overhead. (As an example, our graphic designer did some >> work on the postgres logos for LISA this year, but couldn't get past >> the pgfoundry process to give that back publicly; if it had been on >> github, it would have been much simpler to do a pull request). > Definitely. A simple idea would be to create a git repo dedicated to > advocacy in the organization "postgres" of github > (https://github.com/postgres/). Push permissions can be handled easily > from there. My 2c. > Regards, So I'm happy with github as a choice. However, I don't know that there's any way to do "link to the latest version of raw file X", so we'd still want to publish stuff to FTP.postgresql.org, no? Probably not everything, though -- if we were selective, we'd avoid the space issue. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com
В списке pgsql-advocacy по дате отправления: