New Github group

[Graham Knop]

There is already PSGI port of Act (in the psgi branch) that could be
updated and merged relatively easily.  It provides some shims for
mod_perl compatibility where needed.  It would be a sensible place to
start for either refactoring or to hack on the existing code.

On Sun, Aug 24, 2014 at 2:49 PM, Todd Rinaldo <toddr at cpanel.net> wrote:
>
> On Aug 24, 2014, at 9:21 PM, Philippe Bruhat (BooK) <philippe.bruhat at free.fr> wrote:
>
>> On Sun, Aug 24, 2014 at 03:45:15PM +0300, Todd Rinaldo wrote:
>>>
>>> To follow on to the BOF at YAPC::EU
>>>
>>
>> Is a summary of the BOF going to be published somewhere?
>> Or at least sent here?
>>
>
> I did not take notes so I am hoping those who did will. I can give you top of my head and hopefully someone can correct me.
>
> There was a split in the group between those who wanted to hack on the existing code and get new features and those who want to slowly re-factor the modperl apache 1.0 code into a modern framework. Sawyer proposed providing a plack solution that would fake modperl to the old code which would allow us to then have a dancer/DBIC framework setup for the new stuff along side the old stuff. We could then slowly migrate old functioning code off the old system to the new, keeping a working ACT through the whole process.
>
> The two short term goals agreed on, which I codified in the issues list in github were:
> 1. Setup a DBIC schema set matching the existing ACT database
> 2. Setup a plack/modperl infrastructure such that with a database and a git checkout, I can run an ACT development instance locally on my box, potentially without the need for apache.
>
> If people have enhancement ideas for down the road, it might be good to get those into the list. I'm cautious that the list will get to big, but hopefully we can manage it with careful use of milestones and tags.
>
> Todd
> _______________________________________________
> Act-dev mailing list
> Act-dev at mongueurs.net
> http://listes.mongueurs.net/mailman/listinfo/act-dev