#1869: Move Parrot::Embed into it's own repo
---------------------------------+------------------------------------------
 Reporter:  whiteknight          |       Owner:  whiteknight
     Type:  deprecation          |      Status:  new        
 Priority:  normal               |   Milestone:  2.11       
Component:  Parrot::Interpreter  |     Version:  master     
 Severity:  medium               |    Keywords:             
     Lang:                       |       Patch:             
 Platform:  all                  |  
---------------------------------+------------------------------------------
 The Parrot::Embed module for Perl5 is included in the main Parrot
 repository. There are some advantages to this in terms of proximity and
 testing. However, I think it should be moved out into it's own repository.
 I suggest this for several reasons:

  - More visibility for it, if it were a top-level project of it's own
  - It would be less likely to be lost in the shuffle from being wedged
 into the repo of a larger project
  - There would be more symmetry with other Perl5 modules on CPAN, which
 are their own repos

 I suggest we move the Parrot::Embed code out into a repo at
 github.com/parrot/Parrot-Embed, and set it up with all the necessary
 infrastructure (it's own tests/harness, it's own section on smolder for
 reports, etc).

 I mentioned this idea yesterday at #parrotsketch and got unanimous support
 for it. We can keep snapshots of it in the ext/ folder of the Parrot repo,
 to avoid issues with deprecations.

-- 
Ticket URL: <https://trac.parrot.org/parrot/ticket/1869>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets

Reply via email to