Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tools-pmc] PMC approval for composer usage in PDT
+1

From: <tools-pmc-bounces@xxxxxxxxxxx> on behalf of Dawid Pakuła <zulus@xxxxxxxxx>
Reply-To: Tools PMC mailing list <tools-pmc@xxxxxxxxxxx>
Date: Wednesday, August 24, 2016 at 11:10 AM
To: Tools PMC mailing list <tools-pmc@xxxxxxxxxxx>
Subject: Re: [tools-pmc] PMC approval for composer usage in PDT

Thank You for fast response! 

Dear PMC, please approve composer as works-with dependency.
Composer [1] is released under MIT license [2]. As mentioned before, it’s required to introduce additional (not required) functions to php/composer support. For example install/update project dependencies from eclipse. 

-- 
Dawid Pakuła

From: Aleksandar Kurtakov <akurtako@xxxxxxxxxx>
Reply: Tools PMC mailing list <tools-pmc@xxxxxxxxxxx>
Date: 24 August 2016 at 13:38:20
To: Tools PMC mailing list <tools-pmc@xxxxxxxxxxx>
Subject:  Re: [tools-pmc] PMC approval for composer usage in PDT



----- Original Message -----
> From: "Dawid Pakuła" <zulus@xxxxxxxxx>
> To: "Tools PMC mailing list" <tools-pmc@xxxxxxxxxxx>
> Sent: Wednesday, 24 August, 2016 2:08:06 PM
> Subject: [tools-pmc] PMC approval for composer usage in PDT
>
> Hi Tools PMC,
>
> PDT Team wants introduce support for composer [1] [2]. In short, it’s very
> popular dependency manager dedicated for PHP, similar to bower / maven.
>
> During CQ process for community plugin integration [3] IP Team suggest us to
> ask PMC for approve, and to create workswitch CQ if needed.
>
> Regarding to guidelines [4] I’m not sure if it’s works-with or prerequisite
> dependncy, so please help:
> 1. We don’t redistribute composer.phar file (btw to run composer.phar, PHP
> command is also required)
> 2. We provide settings page/wizard to select tool form file system, or to
> download it (globally or per project).
> 3. We need such tool to run some command like update / install
> 4. Without composer.phar install, PDT will be still functional (composer.json
> editor, php editor etc…), except methods that require it.

4. Makes it a clear "works-with" dependency for me. As long as PDT is usable without the dep but provides greater value when the dep is available this should be works with dependency.

>
> [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=493886
> [2] - https://getcomposer.org/
> [3] - https://dev.eclipse.org/ipzilla/show_bug.cgi?id=11669
> [4] -
> https://eclipse.org/org/documents/Eclipse_Policy_and_Procedure_for_3rd_Party_Dependencies_Final.pdf
>
> --
> Dawid Pakuła
>
> _______________________________________________
> tools-pmc mailing list
> tools-pmc@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/tools-pmc

--
Alexander Kurtakov
Red Hat Eclipse team
_______________________________________________
tools-pmc mailing list
tools-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tools-pmc

Back to the top