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

Change project name to ide #142

Closed
sjimenez77 opened this issue Jul 15, 2019 · 5 comments · Fixed by #294
Closed

Change project name to ide #142

sjimenez77 opened this issue Jul 15, 2019 · 5 comments · Fixed by #294
Labels
documentation related to documentation (AsciiDoc) question Further information is requested
Milestone

Comments

@sjimenez77
Copy link
Member

Category: enhancement

Severity: Low

Description of issue / expected enhacement /Comments
Since we have the trademark devonfw I think that we should rename all the repositories, projects and tools to match this name and avoid potential confusions. Does it make sense?

@sjimenez77 sjimenez77 added question Further information is requested documentation related to documentation (AsciiDoc) labels Jul 15, 2019
@hohwille
Copy link
Member

IMHO trademark is only relevant for URLs, domains, and maven groupIDs as well as for official publications, etc.
In case we want to enforce strict rules on consistency and avoid devon vs. devonfw confusions, we can of course go for it. However some constraints and thoughts from my end:

  • IMHO devon is the "better" name as we are not building a real framework and devonfw is hard to pronounce. Therefore my preference would be to use devonfw only but strictly for all official things like domains, groupIds, etc. but for everything else go for the lax but nicer devon term.
  • We provide a CLI tool. The power of such tool lies in its shortness. If we can not use devon then I am voting strongly against renaming it to devonfw but rather pick something else like ide (however we already have an ide commandlet, etc. so this would have some bigger impact).
  • We have already published versions of devon-ide: https://repo1.maven.org/maven2/com/devonfw/tools/ide/ - hence, changing the name would "pollute" the maven central repo and may cause confusion.
  • Based on the versions already published to maven central there is a build in updating mechanism (devon ide update). This would stop working and will require extra effort and may introduce new bugs harder to test and find.

After all I think we should first clarify the first issue with the team/community.
I see quite some effort in changing the name and would personally vote against it. However, if we agree to the naming strategy for a consistent devonfw, I am surely willing to proceed and do all the required changes :)

@hohwille
Copy link
Member

FYI: I changed the versioning back to beta as I had fixed several bugs and meanwhile pushed out a release. It is about time for a non-beta release but we should have this namespace issue clarified before.

@hohwille
Copy link
Member

So AFAIK the latest discussion state is:

  • we are talking about renaming the repository - devon- prefix should either be omitted or be devonfw-. Fine with that (will break some links but moderate effort to fix).
  • we might also consider renaming the entire project. @maybeec was thinking about renaming this from ide to cli. This would still have the hugh impact and refatoring effort. After all, I would say that it always remains a development tool providing me with all I need on my local machine to deveop devonfw and other projects. I also was thinking about renaming our central CLI command from devon to just dev. This would be less "biased". However dev is very universal and generic and could easily clash with other things now and in the future. So after all these discussions I would rather leave everything as is, since I can not see a clear and compelling change that is worth all the effort. Instead I would rather walk through the entire CLI (commandlets and their arguments) and see if we have room here to improve UX.

So to conclude. I would simply rename this repo to just ide and fix the absolute links going here from documentation or other repos. Then I would close this issue.
Do you agree or not?

@hohwille hohwille added this to the release:3.0.0 milestone Aug 30, 2019
@hohwille hohwille mentioned this issue Aug 30, 2019
3 tasks
@sjimenez77
Copy link
Member Author

The cli was a good idea we have had during this week, but anyway I think that renaming to just ide is fine for me.

Indeed, we have thought that we should remove devonfw prefix from all the repositories names as we already have it in the organization name.

So, I agree 😊.

hohwille added a commit to devonfw/ide-settings that referenced this issue Sep 3, 2019
@hohwille hohwille changed the title Change project name to devonfw-ide Change project name to ide Sep 3, 2019
@hohwille
Copy link
Member

hohwille commented Sep 3, 2019

Done. See PR #245

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation related to documentation (AsciiDoc) question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants