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

Move the package repository to GitHub #286

Open
numere-bot opened this issue Dec 30, 2024 · 0 comments
Open

Move the package repository to GitHub #286

numere-bot opened this issue Dec 30, 2024 · 0 comments
Assignees
Labels
change Change something in an existing feature
Milestone

Comments

@numere-bot
Copy link
Collaborator

DESCRIPTION

Describe, what you observe or want to be changed:
The package repository on SourceForge is functional, but there is no easy way of comitting to this repository as a non-member of the project. Converting the whole setup to something, which resembles winget, is probably better and more future-proof.

Describe, what you expect to happen:
Use the GitHub REST Api like so:

curl -L -H "Accept: application/vnd.github.raw+json" -H "X-GitHub-Api-Version: 2022-11-28" https://api.github.com/repos/numere-org/NumeRe/contents/build_wxwidgets.nscr

to get the contents of a repository and the structure (the raw-less API will return JSON to obtain the meta data including content-type, ref: https://docs.github.com/en/rest/repos/contents?apiVersion=2022-11-28).

Re-think as well, how the package structure will be organized: Using a structure like in winget with folders corresponding to version numbers will simplify the possibility to use a different package version than the currently latest one. As a possible setup:

root
  /OFFICIAL
    /pkg_tools
       /v1.0.2
         /pkg_tools.nscr
  /THIRD-PARTY
    /...

DEVS' SECTION

ANALYSIS

(Describe, what's the issue and which changes have to be made)

IMPLEMENTATION STEPS

(see also our Wiki for implementation guidelines)

  • Implement the necessary changes in a new branch created here on GitHub
  • Test your implementation

DOCUMENTATION STEPS

(see also our Wiki for further information)

  • Update the changes log
  • Add comments to your implementation
  • Add Doxygen documentation comments- Create or update the documentation articles (*.NHLP and *.NDB files, if needed)
  • Update the language strings (*.NLNG files, if needed)

PULL REQUEST

  • Create a pull request for your changes
  • Fill out the template
  • Assign @numere-org/maintainers as reviewers
@numere-bot numere-bot added the change Change something in an existing feature label Dec 30, 2024
@numeredev numeredev added this to the v1.1.8-beta milestone Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
change Change something in an existing feature
Projects
Status: New
Development

No branches or pull requests

2 participants