Hi Everyone, We would like to change Forge from the LGPL license to the EPL license; this will remove the restriction on Plugin licensing which currently requires Plugins to be written with a compatible open-source license. We don't want to restrict how people can develop and distribute plugins, and the EPL license is much more permissive in this regard; while maintaining the same open-source requirements for the core Forge framework itself, plugins may be developed under any license a person would wish to use. Before we this change, if you have any objections, please *reply now*; if you are in agreement, please respond to this email stating,*"I approve of the change to EPL."* *Additionally*, the reason we need to ask for this permission is because some of our contributors have not yet signed the JBoss CLA for Forge. Once we change to EPL, the CLA will not be necessary :) Thanks all, -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better." _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

Hi Everyone, We would like to change Forge from the LGPL license to the EPL license; this will remove the restriction on Plugin licensing which currently requires Plugins to be written with a compatible open-source license. We don't want to restrict how people can develop and distribute plugins, and the EPL license is much more permissive in this regard; while maintaining the same open-source requirements for the core Forge framework itself, plugins may be developed under any license a person would wish to use. Before we this change, if you have any objections, please *reply now*; if you are in agreement, please respond to this email stating,* "I approve of the change to EPL."* *Additionally*, the reason we need to ask for this permission is because some of our contributors have not yet signed the JBoss CLA for Forge. Once we change to EPL, the CLA will not be necessary :) Thanks all, -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better."

I approve of the change to EPL On 21 Jun 2012, at 18:47, Lincoln Baxter, III wrote: > Hi Everyone, > > We would like to change Forge from the LGPL license to the EPL license; this will remove the restriction on Plugin licensing which currently requires Plugins to be written with a compatible open-source license. We don't want to restrict how people can develop and distribute plugins, and the EPL license is much more permissive in this regard; while maintaining the same open-source requirements for the core Forge framework itself, plugins may be developed under any license a person would wish to use. > > Before we this change, if you have any objections, please reply now; if you are in agreement, please respond to this email stating, "I approve of the change to EPL." > > Additionally, the reason we need to ask for this permission is because some of our contributors have not yet signed the JBoss CLA for Forge. Once we change to EPL, the CLA will not be necessary :) > > Thanks all, > -- > Lincoln Baxter, III > http://ocpsoft.org > "Simpler is better." > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

*I approve of the change to EPL.* On Thu, Jun 21, 2012 at 10:51 PM, Jason Porter <lightguard.jp(a)gmail.com <mailto:lightguard.jp@gmail.com>> wrote: +1 Sent from my iPhone On Jun 21, 2012, at 11:12, Max Rydahl Andersen <max.andersen(a)redhat.com <mailto:max.andersen@redhat.com>> wrote: > I approve of the change to EPL > > On 21 Jun 2012, at 18:47, Lincoln Baxter, III wrote: > >> Hi Everyone, >> >> We would like to change Forge from the LGPL license to the EPL license; this will remove the restriction on Plugin licensing which currently requires Plugins to be written with a compatible open-source license. We don't want to restrict how people can develop and distribute plugins, and the EPL license is much more permissive in this regard; while maintaining the same open-source requirements for the core Forge framework itself, plugins may be developed under any license a person would wish to use. >> >> Before we this change, if you have any objections, please reply now; if you are in agreement, please respond to this email stating, "I approve of the change to EPL." >> >> Additionally, the reason we need to ask for this permission is because some of our contributors have not yet signed the JBoss CLA for Forge. Once we change to EPL, the CLA will not be necessary :) >> >> Thanks all, >> -- >> Lincoln Baxter, III >> http://ocpsoft.org >> "Simpler is better." >> _______________________________________________ >> forge-dev mailing list >> forge-dev(a)lists.jboss.org <mailto:forge-dev@lists.jboss.org> >> https://lists.jboss.org/mailman/listinfo/forge-dev > > > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org <mailto:forge-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/forge-dev _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org <mailto:forge-dev@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/forge-dev _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

I think someone did not read the email ;) On 21 Jun 2012, at 21:51, Jason Porter wrote: > +1 > > Sent from my iPhone > > On Jun 21, 2012, at 11:12, Max Rydahl Andersen <max.andersen(a)redhat.com&gt; wrote: > >> I approve of the change to EPL >> >> On 21 Jun 2012, at 18:47, Lincoln Baxter, III wrote: >> >>> Hi Everyone, >>> >>> We would like to change Forge from the LGPL license to the EPL license; this will remove the restriction on Plugin licensing which currently requires Plugins to be written with a compatible open-source license. We don't want to restrict how people can develop and distribute plugins, and the EPL license is much more permissive in this regard; while maintaining the same open-source requirements for the core Forge framework itself, plugins may be developed under any license a person would wish to use. >>> >>> Before we this change, if you have any objections, please reply now; if you are in agreement, please respond to this email stating, "I approve of the change to EPL." >>> >>> Additionally, the reason we need to ask for this permission is because some of our contributors have not yet signed the JBoss CLA for Forge. Once we change to EPL, the CLA will not be necessary :) >>> >>> Thanks all, >>> -- >>> Lincoln Baxter, III >>> http://ocpsoft.org >>> "Simpler is better." >>> _______________________________________________ >>> forge-dev mailing list >>> forge-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/forge-dev >> >> >> _______________________________________________ >> forge-dev mailing list >> forge-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev > > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

That's right. You work for "the company," and they speak for you. On Fri, Jun 22, 2012 at 11:16 AM, Jason Porter <lightguard.jp(a)gmail.com&gt; wrote: Nope. Also just being difficult :) not that my vote counts really. Sent from my iPhone On Jun 22, 2012, at 4:22, Max Rydahl Andersen <max.andersen(a)redhat.com&gt; wrote: > I think someone did not read the email ;) > > On 21 Jun 2012, at 21:51, Jason Porter wrote: > >> +1 >> >> Sent from my iPhone >> >> On Jun 21, 2012, at 11:12, Max Rydahl Andersen <max.andersen(a)redhat.com&gt; wrote: >> >>> I approve of the change to EPL >>> >>> On 21 Jun 2012, at 18:47, Lincoln Baxter, III wrote: >>> >>>> Hi Everyone, >>>> >>>> We would like to change Forge from the LGPL license to the EPL license; this will remove the restriction on Plugin licensing which currently requires Plugins to be written with a compatible open-source license. We don't want to restrict how people can develop and distribute plugins, and the EPL license is much more permissive in this regard; while maintaining the same open-source requirements for the core Forge framework itself, plugins may be developed under any license a person would wish to use. >>>> >>>> Before we this change, if you have any objections, please reply now; if you are in agreement, please respond to this email stating, "I approve of the change to EPL." >>>> >>>> Additionally, the reason we need to ask for this permission is because some of our contributors have not yet signed the JBoss CLA for Forge. Once we change to EPL, the CLA will not be necessary :) >>>> >>>> Thanks all, >>>> -- >>>> Lincoln Baxter, III >>>> http://ocpsoft.org >>>> "Simpler is better." >>>> _______________________________________________ >>>> forge-dev mailing list >>>> forge-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/forge-dev >>> >>> >>> _______________________________________________ >>> forge-dev mailing list >>> forge-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/forge-dev >> >> _______________________________________________ >> forge-dev mailing list >> forge-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev > > > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better." _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

Hi Everyone, We would like to change Forge from the LGPL license to the EPL license; this will remove the restriction on Plugin licensing which currently requires Plugins to be written with a compatible open-source license. We don't want to restrict how people can develop and distribute plugins, and the EPL license is much more permissive in this regard; while maintaining the same open-source requirements for the core Forge framework itself, plugins may be developed under any license a person would wish to use. Before we this change, if you have any objections, please reply now; if you are in agreement, please respond to this email stating, "I approve of the change to EPL." Additionally, the reason we need to ask for this permission is because some of our contributors have not yet signed the JBoss CLA for Forge. Once we change to EPL, the CLA will not be necessary :) Thanks all, -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better." _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev