Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename the project #25

Closed
ghost opened this issue May 16, 2014 · 19 comments
Closed

Rename the project #25

ghost opened this issue May 16, 2014 · 19 comments
Assignees
Milestone

Comments

@ghost
Copy link

ghost commented May 16, 2014

It seems that PowerPoint is a registered trademark of Microsoft.

I suggest to rename into PHPPresentation.

@ivanlanin
Copy link
Contributor

I agree.

@Progi1984
Copy link
Member

Like PHPExcel... :S

@ghost
Copy link
Author

ghost commented May 21, 2014

Yep. :) So, are you agree with renaming into PHPPresentation?

@Progi1984
Copy link
Member

Not totally. I would be interested by @MarkBaker thought about this.

@Progi1984 Progi1984 added this to the 0.2.0 milestone May 21, 2014
@ghost
Copy link
Author

ghost commented May 21, 2014

OK. Please, let us know when you get any feedback from him.

P.S.
I would recommend @MarkBaker renaming from PHPExcel into PHPSpreadsheet. :)

@MarkBaker
Copy link
Member

While I have no worries about Microsoft objecting to the use of their trademarks (they have been aware of the PHPOffice suite of libraries for some years now), I can see pros and cons for renaming.... PHPExcel has support now for a wide range of spreadsheet formats, not merely Excel, so their would be some logic in changing to a more generic name; but PHPExcel is also a recognised name, and changing it would lose that recognition that has taken many years to build. On the other hand, it would allow a complete break from the codeplex site.

@ivanlanin
Copy link
Contributor

Thanks for letting us know your opinion, @MarkBaker. I agree that PHPExcel has become a recognised "brandname". Decision to change it will be much harder to take. So, for me, I think I better leave the harder decision to you :) At least I know that you're aware of the issue.

Before PHPPowerPoint suffers the same dilemma with PHPExcel ;) do you think it's better to change the name now?

@Progi1984
Copy link
Member

I agree with @MarkBaker... I am going to add three points :

  • If PHPExcel must change its name, that must to be at the moment of a new version (2.0 / 3.0 / etc...)
  • If PHPExcel change, we could change all PHPOffice others', like PHPPowerPoint, PHPWord, etc..
  • PHPOffice has not to change its name

@ghost
Copy link
Author

ghost commented Jun 4, 2014

One more point. In case of renaming I suggest renaming in accordance with our coding rules. I mean using PhpOffice as bundle name (like DbUnit does) instead of PHPOffice. Moreover, such naming will match our namespaces.

@Progi1984
Copy link
Member

Good idea @RomanSyroeshko :)

@Progi1984 Progi1984 removed this from the 0.2.0 milestone Jul 21, 2014
@Progi1984
Copy link
Member

So @MarkBaker, what have you decided for PHPExcel 2.0 ?

@MarkBaker
Copy link
Member

PHPExcel would easily become PHPSpreadsheet (it handles a lot more file formats now than merely MS Excel), PHPPowerPoint is also easy to rename as PHPPresentation; PHPProject doesn't really need renaming.... PHPWord and PHPVisio are harder to come up with a more generic name.

@Progi1984
Copy link
Member

So when PHPExcel 2.0 will be released with the name PHPSpreadsheet, each project will change its name with their next release,

@MarkBaker
Copy link
Member

It seems a reasonable approach to take, and we make sure that the old project README points to the new name/repo as well

@Progi1984
Copy link
Member

I agree totally :)

@Progi1984
Copy link
Member

... WIP ...

@Progi1984
Copy link
Member

... DONE...

A link to FAQ for explaining the change : http://phppowerpoint.readthedocs.org/en/develop/faq.html#why-phppowerpoint-become-phppresentation

ToDo Release :

@Progi1984
Copy link
Member

New project RTD created

@Progi1984
Copy link
Member

New project Scrutinizer CI created

Progi1984 added a commit to Progi1984/PHPPresentation that referenced this issue Jan 26, 2016
Progi1984 added a commit to Progi1984/PHPPresentation that referenced this issue Jan 26, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants