Request for project archiviation
maoo opened this issue · comments
This project have been merged with Open Source Readiness, see osr.finos.org , therefore it can be archived.
If anyone would be interested to restore activity, at any time, please comment on this issue.
If there is no reaction in the following 14 days, the FINOS team will proceed with the archiviation.
so, this project is being archived? if that's correct, why?
@copiesofcopies FYI
so, this project is being archived? if that's correct, why?
Hi @jlovejoy - the main reason for archiviation is that the contents of this repository are now published under https://osr.finos.org and maintained by the FINOS OSR Special Interest Group.
To avoid duplicates, we're proposing here (nothing have been done yet) to archive this repository.
CC @robmoffat
when I go to https://osr.finos.org/docs/welcome - all the links to the Open Source License Compliance Handbook go to this repo, assuming those links are to be updated, where will they go?
This should now point to here: https://osr.finos.org/docs/operations/oslc
I will update the welcome page if that works for you?
so, that link looks like a publication in HTML of the intro to the handbook. But without a Github repo with all the source, no one can ever contribute or build upon this. More so, one goal was to enable machine-readability - if the repo is archived, wouldn't that make it difficult to do that?
I realize it has not been active (which is unfortunate) but this still has a lot of potential. I also recall that various tool developers were interested in this. If anyone is using it, then it seems like archiving the repo could also cause problems for that.
I reached out to the LF sometime ago about trying to get project more visibility, but since it came from FINOS, it wasn't clear who decides. If FINOS is not interested in maintaining this, then let me see if I can move it elsewhere so it doesn't completely die.
so, that link looks like a publication in HTML of the intro to the handbook. But without a Github repo with all the source, no one can ever contribute or build upon this.
There is a Github repo, the OSR one - https://github.com/finos/open-source-readiness ; the contents published on https://osr.finos.org are read from https://github.com/finos/open-source-readiness/blob/main/docs . Note that every page has an "edit this page" link at the bottom, which makes it super easy to submit a Pull Request with changes. I think that merging OSLC with OSR will give this content more exposure and help finding more maintainers.
More so, one goal was to enable machine-readability - if the repo is archived, wouldn't that make it difficult to do that?
No, consumers will still be able to read files even if the repo is (publicly) archived.
On this matter, are you aware of anyone that is currently using the machine-readable version of this?
We could move also the machine-readable files into https://github.com/finos/open-source-readiness and continuously build the output in markdown format, to embed it into the osr.finos.org website
I realize it has not been active (which is unfortunate) but this still has a lot of potential. I also recall that various tool developers were interested in this. If anyone is using it, then it seems like archiving the repo could also cause problems for that.
Archiving the repository will not affect consumers at all, but it will notify them that the repository is not maintained, which is an unfortunate truth, and the main reason behind project archiviation.
I reached out to the LF sometime ago about trying to get project more visibility, but since it came from FINOS, it wasn't clear who decides. If FINOS is not interested in maintaining this, then let me see if I can move it elsewhere so it doesn't completely die.
I think that the OSR SIG finds this content very valuable, which is why it got embedded into https://osr.finos.org ; the question IMO is whether to also migrate the YAML source files too. It shouldn't be too hard to run the export from markdown as part of the website publication process. @robmoffat - what do you think?