Skip to content

Renaming to Fluxie#280

Merged
lionel42 merged 5 commits intodevelfrom
fluxie
Mar 16, 2026
Merged

Renaming to Fluxie#280
lionel42 merged 5 commits intodevelfrom
fluxie

Conversation

@lionel42
Copy link
Copy Markdown
Collaborator

@lionel42 lionel42 commented Mar 9, 2026

This PR renames the project from fluxy to fluxie #249

Steps missing:

  • move this repository to openghg/fluxie
  • change external links to openghg/fluxie
  • add deprecation and redirection in openghg/fluxy
  • rename the environment to fluxie on the ICOS jupyter hub (will be done after
  • others ?

@lionel42
Copy link
Copy Markdown
Collaborator Author

Hey @SutarPrasad ,

During last meeting we discussed this renaming issue.
Since I don't have maintainer rights on openghg repo, do you think you can go through the points up there and help with the renaming ?

@lionel42 lionel42 requested a review from SutarPrasad March 13, 2026 12:33
@SutarPrasad
Copy link
Copy Markdown
Member

Hi @lionel42 , I can see the name on pypi as fluxie. Also I have renamed this repo to be fluxie. I think once this PR is merged it should be ready for release. We usually have automated release via github CI. On fluxie it seems to be manual at the moment.

Copy link
Copy Markdown
Member

@SutarPrasad SutarPrasad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything looks good, just the one suggestion related to versioning. The renaming of openghg repo is done and fluxie is available on pypi, so once this is merged fluxie is ready for release. Let me know.

name = "fluxy"
version = "v2.0"
name = "fluxie"
version = "0.0.1"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
version = "0.0.1"
version = "0.1.0"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As fluxie is fairly stable this resembles good starter version.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the release version, I would prefer automatic release using github tags. I will set this up in another PR

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes that would be good. once the PR is ready I'll update the PR with Pypi Trusted Publisher Management

@lionel42 lionel42 mentioned this pull request Mar 16, 2026
@lionel42
Copy link
Copy Markdown
Collaborator Author

@SutarPrasad I guess this is ready to merge if you want to approve the PR

@lionel42 lionel42 mentioned this pull request Mar 16, 2026
14 tasks
@lionel42 lionel42 merged commit a1bfae9 into devel Mar 16, 2026
1 check passed
moPeterAndrews pushed a commit that referenced this pull request Mar 18, 2026
* update toml for pypi

* code rename fluxie

* docs rename

* move to fluxie dir
mo-aliceramsden added a commit that referenced this pull request Apr 2, 2026
* Update pyproject.toml (#281)

- Add Peter to authors list

* Renaming to Fluxie (#280)

* update toml for pypi

* code rename fluxie

* docs rename

* move to fluxie dir

* Black formating (#284)

* format code with black

* adding black formatting check

* adding uv build

* fix dep name

* Update README.md (#287)

- update title following renaming

* test deployement

* comment line skipped

* change back for prod

---------

Co-authored-by: melodb <161489641+melodb@users.noreply.github.com>
Co-authored-by: Lionel Constantin <43442120+lionel42@users.noreply.github.com>
Co-authored-by: Lionel42 <lionel.constantin@empa.ch>
Co-authored-by: Prasad <75735315+SutarPrasad@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants