Can we include the Act templates in the new YAPC-NA repo on github
rob.kinyon at gmail.com
Sun Mar 24 10:48:44 PDT 2013
The biggest value is community participation and reducing barriers to that participation. I helped run 2010 and I never had access to the ACT svn. If it had been on github, I could have helped in further ways. Github already has the wiki, the issue tracker, and is where all the current work on process improvement is happening.
I'm not saying ACT has to change its process. I'm saying that github allows greater participation, and that's a "Good Thing". Robert's point about integrating with ACT is well-taken.
Sent from my iPhone
On Mar 24, 2013, at 4:01, Todd Rinaldo <toddr at cpanel.net> wrote:
> Robert, I'm not convinced there's value in this. ACT uses svn still for having event custom files. As best I can tell, referencing the previous year doesn't buy us much. And even if I do want to do this, it's all on the same ACT server the 2013 one is on.
> Short version: This creates more work to keep it in sync with svn, which is where the authoritative copy of all previous years are stored. What is the value?
> On Mar 23, 2013, at 9:35 AM, Robert Blackwell <robert at robertblackwell.com> wrote:
>> I am so excited to see the new YAPC-NA repo on Github,
>> I would like to propose adding the Act templates to the repo.
>> To make this work best we will need to work out a workflow that works
>> with the current SVN set up that is used now.
>> yapc mailing list
>> yapc at pm.org
> yapc mailing list
> yapc at pm.org
More information about the yapc