search

diggsweden / DCAT-AP-SE-Processor

GNU General Public License v3.0
9 stars 8 forks source link

Include usage example #8

Open jonassodergren opened 1 year ago

jonassodergren commented 1 year ago

Two students working for CSN during the summer has developed an demo using the processor:

Those repositories could be included as an example how to use the dcat-ap-processor. We need a way to group repositories to the same product (dcat-ap-processor) to prevent a scattered account (DIGGSweden).

janderssonse commented 1 year ago

Hi, we might have two discussions going here lets see.

  1. Gathering repos belonging to "theme" and external collaborators role: That is a good thing, we had a brief discussion over email about GitHubs possibilties here but it seems more fitting to continue here. Recap: There is no such nice feature (as in for example in gitlab where namespaces can be used) to present group of projects other than to use labels on "front". But at least one could group right people to right projects so that access rights and project listings would be correct when browsing project as a logged in user, etc. Would have done that already for the dcat-project, if it were not one caveat - a member with a role of "External collaborator" can not be handled liked that, they are per repo only and is a "long standing GitHub feature wishlist/painpoint" - see https://github.com/orgs/community/discussions/6404

So what to do? - most GitHub-organisations just add (in this case) the external collaborators to the org (not as external collaborators), puts them in correct team with correct rights, and that is fine. However, I'm need to sync that policy and some others before going ahead internally,, and so well, we have to wait until I get an ack, or a no.

I think that (team+label) solution will be a good enough one to get a more "gathered, and a thats the way others usually do (in GitHub). In general, Otherwise maintaining "External Collaborators" over time is bound to be a mess so I see this as a must for that kind of user (external maintainers).

  1. Code - Should the mentioned example code be in seperate repos or under an example folder in the the DCAT-AP-project? So, Should the repos above just be added into to current repo under a folder "examples/" with a brief documentation and minor cleanup. If so 1 could be arranged for "later" and the examples be added. That was your proposed solution earlier also and that would be a straight forward good solution.

Let me know your thoughts.