-
Notifications
You must be signed in to change notification settings - Fork 16
PB-1911 Add publiccode.yml #patch #1392
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
base: develop
Are you sure you want to change the base?
Conversation
This was generated with a beta version of a tool developped by Puzzle ITC on behalf of the the Federal Chancelory: https://puzzle.github.io/publiccode-editor/ I added all I could imagine to be possibly of use, just to have a first example showcasing the possibilities. Debatable: - `softwareVersion`/`releaseDate`: Do we really want to add that? We would have to adapt the CI to update that automatically. - `usedBy`: Probably better to keep that empty as usage goes probably far beyond that. - `description`: I just added the English version (`en`) but we could easily also add other languages. Not sure if worth the effort though as the target audience is probably tech-savvy. - `longDescription`: I did not invest much here, this is generated by an LLM. - `features`: Just from the top of my head. Probably too much in depth already. Someone from support could probably phrase this better. - `videos`: It's our most recent video about embedding with an iframe, so not really a good overview video. Unfortunately, the only overview video we have is over 7 years old and is not representative anymore.
web-mapviewer
|
||||||||||||||||||||||||||||
| Project |
web-mapviewer
|
| Branch Review |
feat-PB-1911-add-publiccode-yml
|
| Run status |
|
| Run duration | 07m 26s |
| Commit |
|
| Committer | Alexander Steiner |
| View all properties for this run ↗︎ | |
| Test results | |
|---|---|
|
|
0
|
|
|
0
|
|
|
20
|
|
|
0
|
|
|
260
|
| View all changes introduced in this branch ↗︎ | |
For starters, we don't want to modify our CI to update the version. We don't have an up-to-date overview video of the software, so we remove the link.
changed usedby
GeoPhilo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have adjusted the usage (usedby). Otherwise, it's OK for me.
In general, I'm just wondering whether it's really worth it now (we're going to freeze the code for the viewer soon anyway / change the tech docs / etc.) and whether it wouldn't be better to start the publiccode.yaml with the new SWISSGEO viewer right away.
The field `usedBy` is defined as > A list of the names of prominent public administrations (that will serve as “testimonials”) that are currently known to the software maintainer to be using this software. So "Various federal offices" is not specific enough to add any value.
Thanks! I have removed the You are right that the moment is not ideal. The OSS catalog by the chancellery is going to be publicly announced at the beginning of December, so it's going to be in Swisstopo's interest to be listed there even if some things might change soon. Also, we can reuse this file as a template for SWISSGEO. So I propose to merge this anyway. |
|
For the record: We cannot merge this to The CI was adapted such that it is compatible with branch The change in the CI is going to be reverted by @pakb on the next deploy around the beginning of November. That is when we can relaunch the build of our branch here and merge to |
This was generated with a beta version of a tool developped by Puzzle ITC on behalf of the the Federal Chancelory: https://puzzle.github.io/publiccode-editor/
I added all I could imagine to be possibly of use, just to have a first example showcasing the possibilities.
Debatable:
softwareVersion/releaseDate: Do we really want to add that? We would have to adapt the CI to update that automatically.usedBy: Probably better to keep that empty usage goes far beyond that.description: I just added the English version (en) but we could easily also add other languages (DE, FR, IT). Not sure if worth the effort though as the target audience is probably tech-savvy.longDescription: I did not invest much here, this is generated by an LLM.features: From the top of my head and probably too much already. Someone from support could certainly phrase this better.screenshots: Probably we could have a more representative screenshot, I just chose an iconic location that looks nice.videos: It's our most recent video about embedding with an iframe, so not really a good overview video. Unfortunately, the only overview video we have is over 7 years old and is not representative anymore.Test link