taskSavannah Administration - Tasks: task #16685, Submission of relysam

 
 

task #16685: Submission of relysam

Submitter:  - <_401308>
Submitted:  Sat 18 Oct 2025 08:54:29 PM UTC
   
 
Should Start On:  Sat 18 Oct 2025 12:00:00 AM UTC Should be Finished on:  Tue 28 Oct 2025 12:00:00 AM UTC
Category:  Group Approval Priority:  * 5 - Normal
Status:  Cancelled Privacy:  Public
Assigned to:  ineiev Open/Closed:  Closed
* Mandatory Fields

Post a Comment

Add a New Comment Rich Markup
   

Discussion

Jump to the original submission

Thu 04 Dec 2025 04:16:50 PM UTC, comment #33: 

Thank you; cancelling per sv-help-public@, <CAOW-JYqAjsLfoPisdzQEYMbDEXU89RW_VQy1b3BR-28uKO1g3A@mail.gmail.com>.

Ineiev <ineiev>
Site Administrator
Thu 04 Dec 2025 04:05:57 PM UTC, comment #32: 

attached reply to support request.

(file #57916)

- <_401308>
Thu 04 Dec 2025 02:00:45 PM UTC, comment #31: 

hi ineiev

i have submitted the request for change of email id as a support request.

i have also submitted support request for a review of relysam for rejection/approval as per your process, as i am not able to understand your comments any further.

in case i do get any further guidance on relysam, which is specific and comprehensive for action, lets proceed. otherwise please consider this request as closed from my end.

thank you for your guidance till now, it helped a lot.

comment #29:

>
> comment #28:
> > comment #27:
> > >
> > > 1. are there any more corrections or changes which i need to make and submit. i haven't received any feedback to work on. let me know if there is any critical or mandatory changes for any further issues.
> >
> > I haven't received the latest changes from you as well, so I think yes, there are, but I really can't point them out.
>
> > i have already provided my feedback as per my comments https://savannah. ... p?16685#comment26. and i have received any feedback on what do you suggest to close them. maybe you have missed this. let me know how do you recommend?
>
>
>
> > > 2. is there some available tool or script with which i can work further to make relysam compliant to group's approval?
> >
> > I'm not aware of such scripts.
> >
> ok, noted. thanks

> > > 3. how many days would it further take to get the group's approval for hosting relysam, if it meets all requirements?
> >
> > The point is not to build a compliant tarball; the point is to make sure that the maintainer is able and willing to follow Savannah hosting requirements.  So far, you are obviously not.
> >
>
> to be frank i do not understand what do you mean by "obviously not". if i understand that relysam isnt what you understand or relate to, i can understand. however if you mean to say, the relysam application is not as per non-gnu applications standard, i cannot comment. however i did submit it for being hosted. if there should be some other point of view of "obviously not", its ambiguous to me.
>
> > > 4. there is a votes feature down below on this page. what is the significance of it?
> >
> > Basically, none.
> >
>
> great. thank you

> > > 5. i had applied to change of my email on savannah site through account configuration, and confirmed on the email link, but there is no change. can you guide me on this.
> >
> > Yes, I can; please submit a support request.
> >
> noted, i will. let me reconsider if it is actually required, as i may not like to do this till relysam gets approved or rejected, for which i will have to wait for your next steps.
>
> thanks
>
> > comment #26:
> > >
> > > noted, the readme file has been prepared by following the below guidance on same page --
> > >
> > > "On the other hand, when merging some public domain code into an
> > ...
> > > The notice saying that the whole file is under the GPL (or other license) is legally sufficient. "
> > >
> > > verbatim.
> > >
> > > so what should be the correct way to proceed? please suggest.
> >
> > You don't merge parts of these files, you effectively copy them.
> >
> > > > Also, files like ai/data/failure_modes_data.csv are text, they should include copyright and license notices.
> > >
> > > well these are just initial synthetic data files, which should be removed from the relysam distribution .tar.gz. noted for future.
> >
> > Thank you!  Please make a tarball that will contain all and only files the distribution will contain.  Unrelated files make the evaluation harder.
> >
> > > should there be any more points, do share. thank you.
> >
> > Yes, there is,
> >
> > > > More important, I can tell if the legal notices are correct when I'm familiar with the files in question; for most files, I can't really check their origin and legal status.
> >

- <_401308>
Tue 02 Dec 2025 04:51:36 PM UTC, comment #30: 

Hi Richard (@rms@gnu.org)

Request your guidance on how to proceed forward.

At this point, i am not sure if this communication is helping me in anyway. as a requestor and sole developer of relysam, if your guidance could provide some specific and conclusive action points, i can work forward to close. if possible if someone could be included in this thread, i shall be obliged.

thank you
 


- <_401308>
Tue 02 Dec 2025 04:33:35 PM UTC, comment #29: 


comment #28:

> comment #27:
> >
> > 1. are there any more corrections or changes which i need to make and submit. i haven't received any feedback to work on. let me know if there is any critical or mandatory changes for any further issues.
>
> I haven't received the latest changes from you as well, so I think yes, there are, but I really can't point them out.


> i have already provided my feedback as per my comments https://savannah. ... p?16685#comment26. and i have received any feedback on what do you suggest to close them. maybe you have missed this. let me know how do you recommend?




> > 2. is there some available tool or script with which i can work further to make relysam compliant to group's approval?
>
> I'm not aware of such scripts.
>

ok, noted. thanks
 

> > 3. how many days would it further take to get the group's approval for hosting relysam, if it meets all requirements?
>
> The point is not to build a compliant tarball; the point is to make sure that the maintainer is able and willing to follow Savannah hosting requirements.  So far, you are obviously not.
>


to be frank i do not understand what do you mean by "obviously not". if i understand that relysam isnt what you understand or relate to, i can understand. however if you mean to say, the relysam application is not as per non-gnu applications standard, i cannot comment. however i did submit it for being hosted. if there should be some other point of view of "obviously not", its ambiguous to me.

> > 4. there is a votes feature down below on this page. what is the significance of it?
>
> Basically, none.
>


great. thank you
 

> > 5. i had applied to change of my email on savannah site through account configuration, and confirmed on the email link, but there is no change. can you guide me on this.
>
> Yes, I can; please submit a support request.
>

noted, i will. let me reconsider if it is actually required, as i may not like to do this till relysam gets approved or rejected, for which i will have to wait for your next steps.

thanks

> comment #26:
> >
> > noted, the readme file has been prepared by following the below guidance on same page --
> >
> > "On the other hand, when merging some public domain code into an
> ...
> > The notice saying that the whole file is under the GPL (or other license) is legally sufficient. "
> >
> > verbatim.
> >
> > so what should be the correct way to proceed? please suggest.
>
> You don't merge parts of these files, you effectively copy them.
>
> > > Also, files like ai/data/failure_modes_data.csv are text, they should include copyright and license notices.
> >
> > well these are just initial synthetic data files, which should be removed from the relysam distribution .tar.gz. noted for future.
>
> Thank you!  Please make a tarball that will contain all and only files the distribution will contain.  Unrelated files make the evaluation harder.
>
> > should there be any more points, do share. thank you.
>
> Yes, there is,
>
> > > More important, I can tell if the legal notices are correct when I'm familiar with the files in question; for most files, I can't really check their origin and legal status.
>

- <_401308>
Tue 02 Dec 2025 04:09:30 PM UTC, comment #28: 

comment #27:

>
> 1. are there any more corrections or changes which i need to make and submit. i haven't received any feedback to work on. let me know if there is any critical or mandatory changes for any further issues.


I haven't received the latest changes from you as well, so I think yes, there are, but I really can't point them out.

> 2. is there some available tool or script with which i can work further to make relysam compliant to group's approval?


I'm not aware of such scripts.

> 3. how many days would it further take to get the group's approval for hosting relysam, if it meets all requirements?


The point is not to build a compliant tarball; the point is to make sure that the maintainer is able and willing to follow Savannah hosting requirements.  So far, you are obviously not.

> 4. there is a votes feature down below on this page. what is the significance of it?


Basically, none.

> 5. i had applied to change of my email on savannah site through account configuration, and confirmed on the email link, but there is no change. can you guide me on this.


Yes, I can; please submit a support request.

comment #26:

>
> noted, the readme file has been prepared by following the below guidance on same page --
>
> "On the other hand, when merging some public domain code into an

...

> The notice saying that the whole file is under the GPL (or other license) is legally sufficient. "
>
> verbatim.
>
> so what should be the correct way to proceed? please suggest.


You don't merge parts of these files, you effectively copy them.

> > Also, files like ai/data/failure_modes_data.csv are text, they should include copyright and license notices.
>
> well these are just initial synthetic data files, which should be removed from the relysam distribution .tar.gz. noted for future.


Thank you!  Please make a tarball that will contain all and only files the distribution will contain.  Unrelated files make the evaluation harder.

> should there be any more points, do share. thank you.


Yes, there is,

> > More important, I can tell if the legal notices are correct when I'm familiar with the files in question; for most files, I can't really check their origin and legal status.


Ineiev <ineiev>
Site Administrator
Mon 01 Dec 2025 07:34:26 PM UTC, comment #27: 

hi ineiev

i have few questions:

1. are there any more corrections or changes which i need to make and submit. i haven't received any feedback to work on. let me know if there is any critical or mandatory changes for any further issues.

2. is there some available tool or script with which i can work further to make relysam compliant to group's approval?

3. how many days would it further take to get the group's approval for hosting relysam, if it meets all requirements?

4. there is a votes feature down below on this page. what is the significance of it?

5. i had applied to change of my email on savannah site through account configuration, and confirmed on the email link, but there is no change. can you guide me on this.

looking forwrad to your guidance .

thank you

- <_401308>
Tue 25 Nov 2025 07:46:21 PM UTC, comment #26: 


comment #25:

> Thank you, and sorry for the delay!
>
> www.gnu.org/prep/ ... hted-Package.html says,


> If the code is supposed to be in the public domain ...
> when copying the new files into your project, add a brief note
> at the beginning of the files recording the authors, the public
> domain status, and anything else relevant.


noted, the readme file has been prepared by following the below guidance on same page --

"On the other hand, when merging some public domain code into an existing file covered by the GPL (or LGPL or other free software license), there is no reason to indicate the pieces which are public domain. The notice saying that the whole file is under the GPL (or other license) is legally sufficient. "

verbatim.

so what should be the correct way to proceed? please suggest.


>
> web/static/images/README.md only says which files are in the public domain.
>
> More important, I can tell if the legal notices are correct when I'm familiar with the files in question; for most files, I can't really check their origin and legal status.
>
> Also, files like ai/data/failure_modes_data.csv are text, they should include copyright and license notices.


well these are just initial synthetic data files, which should be removed from the relysam distribution .tar.gz. noted for future.

should there be any more points, do share. thank you.

>

- <_401308>
Tue 25 Nov 2025 05:54:45 PM UTC, comment #25: 

Thank you, and sorry for the delay!

www.gnu.org/prep/ ... hted-Package.html says,

If the code is supposed to be in the public domain ...
when copying the new files into your project, add a brief note
at the beginning of the files recording the authors, the public
domain status, and anything else relevant.


web/static/images/README.md only says which files are in the public domain.

More important, I can tell if the legal notices are correct when I'm familiar with the files in question; for most files, I can't really check their origin and legal status.

Also, files like ai/data/failure_modes_data.csv are text, they should include copyright and license notices.

Ineiev <ineiev>
Site Administrator
Mon 24 Nov 2025 02:13:14 PM UTC, comment #24: 

hi ineiev

just a quick check. haven't heard any further feedback and guidance on relysam. request if you could share next steps.

thank you

- <_401308>
Sun 16 Nov 2025 09:22:10 AM UTC, comment #23: 


comment #21:

> You are dangerous.  You don't hesitate to add invalid legal notices.  For instance, both notices for web/static/images/gfdlv1.3-136x68.png are definitely wrong.  I'm surprised I have to point out this after the great work you've done.


corrected the README in web/static/images directory.

>
> comment #20:
> >
> > > thanks for pointing out inconsistencies. have fixed and attached summary .txt file below.
>
> You changed the reference to direct to LICENSE_GFDL.  I've just read it again.  It has an addendum, 'How to use this license for your documents', and it says, 'include a copy of the License in your document'.


the patch file attached with all the corrections as per guidance.

>
> > >sure, once relysam gets hosted, will introduce the patches. uploaded the corrected file at https://savannah. ... 114_003424.tar.gz.
>
> I don't mean hosting, I'm suggesting that instead of using excessive Savannah disk space, you could attach patches when commenting here, like you attach the .txt files.


I have successfully created a patch file between the two distribution versions:-
From: relysam_v0.1.0_20251114_003424.tar.gz
To: relysam_v0.1.0_20251116_143834.tar.gz.
patch file attached below.

please review and share next steps.

(file #57808)

- <_401308>
Sat 15 Nov 2025 07:11:08 PM UTC, comment #22: 


comment #21:

> You are dangerous.  You don't hesitate to add invalid legal notices.  For instance, both notices for web/static/images/gfdlv1.3-136x68.png are definitely wrong.  I'm surprised I have to point out this after the great work you've done.


understood, is the attached readme in @web/static/images directory fine? check and confirm.

>
> comment #20:
> >
> > > thanks for pointing out inconsistencies. have fixed and attached summary .txt file below.
>
> You changed the reference to direct to LICENSE_GFDL.  I've just read it again.  It has an addendum, 'How to use this license for your documents', and it says, 'include a copy of the License in your document'.


i have read this addendum section again. so, does this mean along with a GFDL copyright and license header in every document, the complete license text should also be there? or does it mean that License Location- Information about where the full license can be found is enough? what is your recommendation?

>
> sure, once relysam gets hosted, will introduce the patches. uploaded the corrected file at https://savannah. ... 114_003424.tar.gz.
>
> I don't mean hosting, I'm suggesting that instead of using excessive Savannah disk space, you could attach patches when commenting here, like you attach the .txt files.


>yes understood. i will attach patch files henceforth.


thank you

- <_401308>
Sat 15 Nov 2025 04:50:00 PM UTC, comment #21: 

You are dangerous.  You don't hesitate to add invalid legal notices.  For instance, both notices for web/static/images/gfdlv1.3-136x68.png are definitely wrong.  I'm surprised I have to point out this after the great work you've done.

comment #20:

>
> > thanks for pointing out inconsistencies. have fixed and attached summary .txt file below.


You changed the reference to direct to LICENSE_GFDL.  I've just read it again.  It has an addendum, 'How to use this license for your documents', and it says, 'include a copy of the License in your document'.

> >sure, once relysam gets hosted, will introduce the patches. uploaded the corrected file at https://savannah. ... 114_003424.tar.gz.


I don't mean hosting, I'm suggesting that instead of using excessive Savannah disk space, you could attach patches when commenting here, like you attach the .txt files.

Ineiev <ineiev>
Site Administrator
Thu 13 Nov 2025 07:13:46 PM UTC, comment #20: 


comment #19:

> If files contain copyright and license notices, README is not needed.  And in particular, ai/data/README.md says that the files are under GPLv3+ while, for example, ai/data/ai_models_training_guide.md says it's under GFDL v1.3+.  Similarly, DATA_LICENSE.md says about binary files without listing them.
>
> Also, files like README.md says that a copy of its license is included in the section entitled "GNU Free Documentation License" but no such section is present in the file.
>
> Could you fix such inconsistencies?


> thanks for pointing out inconsistencies. have fixed and attached summary .txt file below.
>
> By the way, I wonder if it makes sense to attach a patch against the latest tarball instead of uploading a complete tarball again.


>sure, once relysam gets hosted, will introduce the patches. uploaded the corrected file at https://savannah. ... 114_003424.tar.gz.


thank you

- <_401308>
Thu 13 Nov 2025 04:24:57 PM UTC, comment #19: 

comment #18:

> >> noted . completed. json files also have copyright and license headers in data directory. in ai directory have placed a README with list of files applicable.


If files contain copyright and license notices, README is not needed.  And in particular, ai/data/README.md says that the files are under GPLv3+ while, for example, ai/data/ai_models_training_guide.md says it's under GFDL v1.3+.  Similarly, DATA_LICENSE.md says about binary files without listing them.

Also, files like README.md says that a copy of its license is included in the section entitled "GNU Free Documentation License" but no such section is present in the file.

Could you fix such inconsistencies?

By the way, I wonder if it makes sense to attach a patch against the latest tarball instead of uploading a complete tarball again.

Ineiev <ineiev>
Site Administrator
Mon 10 Nov 2025 08:32:30 PM UTC, comment #18: 


comment #17:

> Files like db/seed_data.sql still have no valid copyright and license notices.


noted. completed the changes. db/seed_data.sql has copyright and license header.

> Directories like 'ai' and 'data' contain text files, they should include copyright and license notices.  Even when using a README, it's desirable to explicitly list the covered files rather than say 'all files in this directory' because such arrangements are prone to errors when new files are added to the directory.


>> noted . completed. json files also have copyright and license headers in data directory. in ai directory have placed a README with list of files applicable.


the updated .tar.gz file uploaded at https://savannah. ... 111_014617.tar.gz.

please review and share next steps. thank you.

- <_401308>
Mon 10 Nov 2025 06:34:45 AM UTC, comment #17: 

Files like db/seed_data.sql still have no valid copyright and license notices.

Directories like 'ai' and 'data' contain text files, they should include copyright and license notices.  Even when using a README, it's desirable to explicitly list the covered files rather than say 'all files in this directory' because such arrangements are prone to errors when new files are added to the directory.

Ineiev <ineiev>
Site Administrator
Thu 06 Nov 2025 04:54:17 PM UTC, comment #16: 


comment #15:

> Thank you!  Unfortunately, I can't see the new tarball.  Where did you upload it?


as its more that the upload file size, i have uploaded. please check https://savannah. ... 105_215259.tar.gz

please review and share next steps.

thank you

- <_401308>
Thu 06 Nov 2025 04:50:03 PM UTC, comment #15: 

Thank you!  Unfortunately, I can't see the new tarball.  Where did you upload it?

Ineiev <ineiev>
Site Administrator
Wed 05 Nov 2025 04:47:48 PM UTC, comment #14: 


comment #13:

> Thanks!
>
> Please make sure that all copyrightable files in your tarball have valid copyright and license notices.


hello again,

i have uploaded the .tar.gz file and the relysam compliance report which includes valid copyright and license headers check and scored 100%. please review and share next steps.

thank you

- <_401308>
Tue 04 Nov 2025 03:28:04 PM UTC, comment #13: 

Thanks!

Please make sure that all copyrightable files in your tarball have valid copyright and license notices.

Ineiev <ineiev>
Site Administrator
Sat 01 Nov 2025 08:01:36 PM UTC, comment #12: 

thank you.

comments



comment #11:

> Thank you!  Please note that Savannah hosting requirement is compatibility with GPLv3 and any later version, not just GPLv3.


yes noted.

>
> comment #10:
> >
> > may i also request you to keep sharing some links to next steps with links which can help me prepare to host the package on savannah once it is approved.
>
> Generally, user documentation is available at savannah.nongnu.o ... enance/FrontPage/; I can only guess what your package will need so I can't be more specific.


great, i have already started reading. thank you.

>
> > i use linux and havent used savannah as hosting site or sync with my PC.
>
> I'm confused.  Do you currently host your package on the hosting site linux?


no, i meant to say, my system uses Debian, and i am developing this application on GNU/Linux. presently i havent hosted relysam anywhere else. if approved, i will host it on savannah.nongnu.org

>
> But let us proceed with approving your package.
>
> comment #4:
> > 1. the relysam application - it has been ensured that it always uses GNU/Linux and not Linux when refering to OS.
>
> Could you comment on pyproject.toml line 85?


i have already updated pyproject.toml. have attcahed the file below. please review and share.

thank you

- <_401308>
Sat 01 Nov 2025 05:19:19 PM UTC, comment #11: 

Thank you!  Please note that Savannah hosting requirement is compatibility with GPLv3 and any later version, not just GPLv3.

comment #10:

>
> may i also request you to keep sharing some links to next steps with links which can help me prepare to host the package on savannah once it is approved.


Generally, user documentation is available at savannah.nongnu.o ... enance/FrontPage/; I can only guess what your package will need so I can't be more specific.

> i use linux and havent used savannah as hosting site or sync with my PC.


I'm confused.  Do you currently host your package on the hosting site linux?

But let us proceed with approving your package.

comment #4:

> 1. the relysam application - it has been ensured that it always uses GNU/Linux and not Linux when refering to OS.


Could you comment on pyproject.toml line 85?

Ineiev <ineiev>
Site Administrator
Tue 28 Oct 2025 06:04:34 AM UTC, comment #10: 

hello ineiev

thank you for being so patient and sharing guidance.

having done a bit more study, yes you are correct, MIT license isnt to be used. i have updated the dependencies list and attached. please review and share.

may i also request you to keep sharing some links to next steps with links which can help me prepare to host the package on savannah once it is approved. i use linux and havent used savannah as hosting site or sync with my PC.

concurrently as relysam is still under development, i am working on improvements and troubleshooting, to make it useful.

thank you.

- <_401308>
Tue 28 Oct 2025 04:39:34 AM UTC, comment #9: 

comment #8:

> 2. the dependencies license information with licenses names from official GNU website is attached.


Thank you!  Could you check once more?  The GNU Project doesn't use the name 'MIT License' unless I'm mistaken, does it?

Ineiev <ineiev>
Site Administrator
Mon 27 Oct 2025 05:12:29 PM UTC, comment #8: 

noted.

1. point of re-submission not to be done. the file size was above the attachment limit which popped up. hence could not attach.

2. the dependencies license information with licenses names from official GNU website is attached. hope this is fine. i am pasting it here.

please let me know next steps. thank you


 


- <_401308>
Mon 27 Oct 2025 04:31:13 PM UTC, comment #7: 

comment #4:

> 5. as the .tar.gz file is >30MB, i could not attach while reply from UI to your email, hence submitting again.


Then it may be easier to post diffs, for example, against relysam_v0.1.0_20251019_020024.tar.gz.  At any rate, please don't re-submit.

By the way, this file is only 4.5MB long,

comment #6:

> https://savannah. ... 027_010119.tar.gz


From task #16690, I'm still not sure what license names like "Apache-2.0/BSD-3-Clause License" mean.  Could you use names from https://www.gnu.o ... license-list.html?

Ineiev <ineiev>
Site Administrator
Sun 26 Oct 2025 07:58:43 PM UTC, comment #6: 
- <_401308>
Sun 26 Oct 2025 07:56:39 PM UTC, comment #5: 

thank you.

1. the relysam application - it has been ensured that it always uses GNU/Linux and not Linux when refering to OS.

2. Included both Licenses in root of application. required licenses headers on each sourcecode ind\cluding documentation.

a. GNU GENERAL PUBLIC LICENSE, Version 3, 29 June 2007. Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
 

b.GNU Free Documentation License, Version 1.3, 3 November 2008, Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. <https://fsf.org/>.

3. it has been ensured that list your dependencies with links to their licensing conditions.

4. I have selected NonGNU correctly.

5. i could not attach the tar.gz file while reply from UI to your email, hence submitted again.

Thank you

- <_401308>
Sun 26 Oct 2025 07:51:14 PM UTC, comment #4: 

thank you.

1. the relysam application - it has been ensured that it always uses GNU/Linux and not Linux when refering to OS.

2. Included both Licenses in root of application. required licenses headers on each sourcecode ind\cluding documentation.

a. GNU GENERAL PUBLIC LICENSE, Version 3, 29 June 2007. Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
 

b.GNU Free Documentation License, Version 1.3, 3 November 2008, Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. <https://fsf.org/>.

3. it has been ensured that list your dependencies with links to their licensing conditions.

4. I have selected NonGNU correctly.

5. as the .tar.gz file is >30MB, i could not attach while reply from UI to your email, hence submitting again.

Thank you

- <_401308>
Sun 26 Oct 2025 02:07:43 PM UTC, comment #3: 

I can download the new file but I can't see your comments.  Could you post them again?

Ineiev <ineiev>
Site Administrator
Thu 23 Oct 2025 07:02:40 PM UTC, comment #2: 

resubmitted with updated/corrected details and files. upoaded at . https://savannah. ... 023_234120.tar.gz. thank you.

- <_401308>
Mon 20 Oct 2025 04:43:22 PM UTC, comment #1: 

Thank you!

First, could you make sure your package always uses 'GNU/Linux' rather than 'Linux' when referring to the operating system?

Then, please make sure that all copyrightable files in your tarball have valid copyright and license notices.  Please note that the documentation should be FDL-compatible,

https://www.gnu.o ... s-for-Other-Files
https://www.gnu.o ... for-Documentation

Please list your dependencies with links to their licensing conditions.  In particular, "the MIT license" doesn't identify a license unambiguously: people use it to refer to a number of various licenses.  Likewise, I don't understand what 'Apache-2.0/BSD License' means.

At last, you selected 'Official GNU software' as the type of group.  If you really want to offer your package to the GNU Project, please follow the directions on https://www.gnu.o ... p/evaluation.html.  If it was a mistake, I'll change the type to 'non-GNU software and documentation'.

Ineiev <ineiev>
Site Administrator
Sat 18 Oct 2025 08:54:29 PM UTC, original submission:  

A new group has been registered at Savannah.
This group will remain inactive until a site admin approves
or discards the registration.


Registration Administration


Approving or discarding the registration must be done using the specific
Group administration page, accessible only to site
administrators logged in as superusers.

Registration Details


  • Name: relysam
  • System Name:  relysam
  • Type: Official GNU software
  • License: GNU General Public License v3 or later (## Dependencies and Licenses


### Core Web Framework & API Infrastructure
- fastapi==0.116.1 - MIT License
- starlette==0.47.3 - BSD-3-Clause License
- uvicorn==0.35.0 - BSD-3-Clause License
- gunicorn==23.0.0 - MIT License
- pydantic==2.9.2 - MIT License
- pydantic-core==2.23.4 - MIT License
- pydantic-settings==2.10.1 - MIT License
- python-multipart==0.0.20 - Apache-2.0 License
- h11==0.16.0 - MIT License
- httptools==0.6.4 - MIT License
- uvloop==0.21.0 - MIT/Apache-2.0 License
- watchfiles==1.1.0 - MIT License
- websockets==15.0.1 - BSD-3-Clause License

### HTTP Client & Networking
- httpx==0.28.1 - BSD-3-Clause License
- httpcore==1.0.9 - BSD-3-Clause License
- aiohttp==3.12.15 - Apache-2.0 License
- aiohappyeyeballs==2.6.1 - PSF License
- aiosignal==1.4.0 - Apache-2.0 License
- requests==2.32.5 - Apache-2.0 License
- urllib3==2.5.0 - MIT License
- certifi==2025.8.3 - MPL-2.0 License
- idna==3.10 - BSD-3-Clause License
- charset-normalizer==3.4.3 - MIT License

### Database & ORM
- SQLAlchemy==2.0.43 - MIT License
- alembic==1.16.5 - MIT License
- greenlet==3.2.4 - MIT License
- psycopg2-binary==2.9.10 - LGPL-3.0 License
- Flask-SQLAlchemy==3.1.1 - BSD-3-Clause License

### Authentication & Security
- Authlib==1.6.3 - BSD-3-Clause License
- cryptography==45.0.7 - Apache-2.0/BSD License
- passlib==1.7.4 - BSD-3-Clause License
- python-jose==3.5.0 - MIT License
- bcrypt==4.3.0 - Apache-2.0 License
- pyasn1==0.6.1 - BSD-2-Clause License
- pyasn1-modules==0.4.2 - BSD-2-Clause License
- rsa==4.9.1 - Apache-2.0 License
- cffi==1.17.1 - MIT License
- pycparser==2.22 - BSD-3-Clause License
- ecdsa==0.19.0 - MIT License

### Data Science & Analytics Foundation
- numpy==2.2.6 - BSD-3-Clause License
- pandas==2.3.2 - BSD-3-Clause License
- scipy==1.16.1 - BSD-3-Clause License
- matplotlib==3.10.6 - PSF License
- seaborn==0.13.2 - BSD-3-Clause License
- plotly==6.3.0 - MIT License
- scikit-learn==1.7.1 - BSD-3-Clause License
- pyarrow==21.0.0 - Apache-2.0 License
- contourpy==1.3.3 - BSD-3-Clause License
- cycler==0.12.1 - BSD-3-Clause License
- fonttools==4.59.2 - MIT License
- kiwisolver==1.4.9 - BSD-3-Clause License

### Reliability Engineering Core
- lifelines==0.30.0 - MIT License
- reliability==0.9.0 - LGPL-3.0 License
- autograd==1.8.0 - MIT License
- autograd-gamma==0.5.0 - MIT License
- statsmodels==0.14.5 - BSD-3-Clause License
- patsy==1.0.1 - BSD-2-Clause License
- formulaic==1.2.0 - MIT License

### Machine Learning & AI Frameworks
- torch==2.8.0+cpu - BSD-3-Clause License
- torchaudio==2.8.0+cpu - BSD-2-Clause License
- torchvision==0.23.0+cpu - BSD-3-Clause License
- torchmetrics==1.8.2 - Apache-2.0 License
- keras==3.11.3 - Apache-2.0 License
- tf-keras==2.15.0 - Apache-2.0 License
- transformers==4.56.0 - Apache-2.0 License
- huggingface-hub==0.34.4 - Apache-2.0 License
- sentence-transformers==5.1.0 - Apache-2.0 License
- tokenizers==0.22.0 - Apache-2.0 License
- safetensors==0.6.2 - Apache-2.0 License
- joblib==1.5.2 - BSD-3-Clause License
- xgboost==3.0.4 - Apache-2.0 License
- lightgbm==4.6.0 - MIT License
- threadpoolctl==3.6.0 - BSD-3-Clause License

### Deep Learning Support (TensorFlow Ecosystem)
- astunparse==1.6.3 - BSD-3-Clause License
- gast==0.6.0 - BSD-3-Clause License
- google-pasta==0.2.0 - Apache-2.0 License
- grpcio==1.74.0 - Apache-2.0 License
- libclang==18.1.1 - Apache-2.0 License
- ml-dtypes==0.5.3 - Apache-2.0 License
- opt-einsum==3.4.0 - MIT License
- protobuf==6.32.0 - BSD-3-Clause License
- termcolor==3.1.0 - MIT License
- wrapt==1.17.3 - BSD-2-Clause License

### PyTorch Lightning & MLOps
- lightning==2.5.4 - Apache-2.0 License
- lightning-utilities==0.15.2 - Apache-2.0 License
- pytorch-lightning==2.5.4 - Apache-2.0 License
- mlflow==3.3.2 - Apache-2.0 License
- mlflow-skinny==3.3.2 - Apache-2.0 License
- mlflow-tracing==3.3.2 - Apache-2.0 License
- databricks-sdk==0.65.0 - Apache-2.0 License
- optree==0.17.0 - Apache-2.0 License

### Natural Language Processing
- spacy==3.8.7 - MIT License
- spacy-legacy==3.0.12 - MIT License
- spacy-loggers==1.0.5 - MIT License
- nltk==3.9.1 - Apache-2.0 License
- thinc==8.3.6 - MIT License
- blis==1.3.0 - MIT License
- catalogue==2.0.10 - MIT License
- cloudpathlib==0.22.0 - MIT License
- confection==0.1.5 - MIT License
- cymem==2.0.11 - MIT License
- langcodes==3.5.0 - MIT License
- language-data==1.3.0 - MIT License
- marisa-trie==1.3.1 - MIT License
- murmurhash==1.0.13 - MIT License
- preshed==3.0.10 - MIT License
- srsly==2.5.1 - MIT License
- typer==0.17.3 - MIT License
- wasabi==1.1.3 - MIT License
- weasel==0.4.1 - MIT License

### File Processing & Document Handling
- Jinja2==3.1.6 - BSD-3-Clause License
- MarkupSafe==3.0.2 - BSD-3-Clause License
- et-xmlfile==2.0.0 - MIT License
- lxml==6.0.1 - BSD-3-Clause License

### Configuration & Serialization
- PyYAML==6.0.2 - MIT License
- toml==0.10.2 - MIT License
- tomlkit==0.13.3 - MIT License
- python-dotenv==1.1.1 - BSD-3-Clause License
- attrs==25.3.0 - MIT License
- msgpack==1.1.1 - Apache-2.0 License
- jsonschema==4.25.1 - MIT License
- jsonschema-specifications==2025.4.1 - MIT License
- referencing==0.36.2 - MIT License
- rpds-py==0.27.1 - MIT License
- ruamel.yaml==0.18.15 - MIT License
- ruamel.yaml.clib==0.2.12 - MIT License

### System Utilities & Monitoring
- psutil==7.0.0 - BSD-3-Clause License
- watchdog==6.0.0 - Apache-2.0 License
- APScheduler==3.11.0 - MIT License
- schedule==1.2.2 - MIT License
- opentelemetry-api==1.36.0 - Apache-2.0 License
- opentelemetry-sdk==1.36.0 - Apache-2.0 License
- opentelemetry-semantic-conventions==0.57b0 - Apache-2.0 License
- prometheus-client==0.22.1 - Apache-2.0 License

### Command Line & User Interface
- click==8.2.1 - BSD-3-Clause License
- rich==14.1.0 - MIT License
- tqdm==4.67.1 - MPL-2.0/MIT License
- colorama==0.4.6 - BSD-3-Clause License
- colorlog==6.9.0 - MIT License
- shellingham==1.5.4 - ISC License
- markdown-it-py==4.0.0 - MIT License
- mdurl==0.1.2 - MIT License
- Pygments==2.19.2 - BSD-2-Clause License

### Async & Concurrency Support
- anyio==4.10.0 - MIT License
- trio==0.30.0 - MIT/Apache-2.0 License
- trio-websocket==0.12.2 - MIT License
- websocket-client==1.8.0 - Apache-2.0 License
- wsproto==1.2.0 - MIT License
- sniffio==1.3.1 - MIT/Apache-2.0 License
- outcome==1.3.0.post0 - MIT/Apache-2.0 License
- sortedcontainers==2.4.0 - Apache-2.0 License

### Caching & Performance
- cachetools==5.5.2 - MIT License
- CacheControl==0.14.3 - Apache-2.0 License
- diskcache==5.6.3 - Apache-2.0 License

### Flask Ecosystem
- Flask==3.1.2 - BSD-3-Clause License
- Werkzeug==3.1.3 - BSD-3-Clause License
- itsdangerous==2.2.0 - BSD-3-Clause License
- blinker==1.9.0 - MIT License

### GraphQL Support
- graphene==3.4.3 - MIT License
- graphql-core==3.2.6 - MIT License
- graphql-relay==3.2.0 - MIT License

### Web Scraping & Automation
- beautifulsoup4==4.13.5 - MIT License
- selenium==4.35.0 - Apache-2.0 License
- webdriver-manager==4.0.2 - Apache-2.0 License
- soupsieve==2.8 - MIT License
- PySocks==1.7.1 - BSD-3-Clause License

### Computer Vision
- pillow==11.3.0 - HPND (PIL License)
- opencv-python-headless==4.12.0.88 - Apache-2.0 License

### Scientific Computing
- sympy==1.14.0 - BSD-3-Clause License
- networkx==3.5 - BSD-3-Clause License
- h5py==3.14.0 - BSD-3-Clause License
- mpmath==1.3.0 - BSD-3-Clause License
- cloudpickle==3.1.1 - BSD-3-Clause License
- mplcursors==0.7 - MIT License

### Logging & Structured Logging
- loguru==0.7.3 - MIT License
- structlog==25.4.0 - MIT/Apache-2.0 License

### Deployment & Build Tools
- GitPython==3.1.45 - BSD-3-Clause License
- gitdb==4.0.12 - BSD-3-Clause License
- smmap==5.0.2 - BSD-3-Clause License
- fsspec==2025.9.0 - BSD-3-Clause License
- docker==7.1.0 - Apache-2.0 License
- setuptools==80.9.0 - MIT License
- wheel==0.45.1 - MIT License
- hatchling==1.27.0 - MIT License
- build==1.3.0 - MIT License
- pyproject-hooks==1.2.0 - MIT License

### Package Management & Metadata
- packaging==25.0 - Apache-2.0/BSD-2-Clause License
- platformdirs==4.4.0 - MIT License
- filelock==3.19.1 - Unlicense
- importlib-metadata==8.7.0 - Apache-2.0 License
- typing-extensions==4.14.1 - PSF License
- zipp==3.23.0 - MIT License
- distlib==0.4.0 - PSF License
- trove-classifiers==2025.8.26.11 - Apache-2.0 License

### Regex & Text Processing
- regex==2025.9.1 - Apache-2.0 License
- pyparsing==3.2.3 - MIT License
- six==1.17.0 - MIT License
- defusedxml==0.7.1 - PSF License

### Time & Date Handling
- python-dateutil==2.9.0.post0 - Apache-2.0/BSD License
- pytz==2025.2 - MIT License
- tzdata==2025.2 - Apache-2.0 License
- tzlocal==5.3.1 - MIT License

### Data Formats & Serialization
- marshmallow==4.0.1 - MIT License
- flatbuffers==25.2.10 - Apache-2.0 License
- frozenlist==1.7.0 - Apache-2.0 License
- multidict==6.6.4 - Apache-2.0 License
- propcache==0.3.2 - Apache-2.0 License
- yarl==1.20.1 - Apache-2.0 License

### Additional Utilities
- tenacity==9.1.2 - Apache-2.0 License
- smart-open==7.3.0.post1 - MIT License
- absl-py==2.3.1 - Apache-2.0 License
- annotated-types==0.7.0 - MIT License
- boolean.py==5.0 - BSD-2-Clause License
- cyclonedx-python-lib==9.1.0 - Apache-2.0 License
- dparse==0.6.4 - MIT License
- hf-xet==1.1.9 - Apache-2.0 License
- interface-meta==1.3.0 - MIT License
- license-expression==30.4.0 - Apache-2.0 License
- packageurl-python==0.17.5 - MIT License
- pbr==7.0.1 - Apache-2.0 License
- py-mini-racer==0.6.0 - ISC License
- py-serializable==2.1.0 - Apache-2.0 License
- ripgrep==14.1.0 - MIT License
- sproto==0.1.4 - BSD-3-Clause License
- sqlparse==0.5.3 - BSD-3-Clause License
- stevedore==5.5.0 - Apache-2.0 License
- typing-inspection==0.4.1 - MIT License
- virtualenv==20.34.0 - MIT License
- narwhals==2.3.0 - MIT License
- nodeenv==1.9.1 - BSD-3-Clause License
- cfgv==3.4.0 - MIT License
- identify==2.6.13 - MIT License

### Development Tools
- black==25.1.0 - MIT License
- google-auth==2.40.3 - Apache-2.0 License
- iniconfig==2.1.0 - MIT License
- isort==6.0.1 - MIT License
- Mako==1.3.10 - MIT License
- Markdown==3.8.2 - BSD-3-Clause License
- mypy==1.17.1 - MIT License
- mypy-extensions==1.1.0 - MIT License
- namex==0.1.0 - Apache-2.0 License
- pathspec==0.12.1 - MPL-2.0 License
- pip==25.2 - MIT License
- pip-api==0.0.34 - Apache-2.0 License
- pip-audit==2.9.0 - Apache-2.0 License
- pip-licenses==5.0.0 - MIT License
- pip-requirements-parser==32.0.1 - MIT License
- pluggy==1.6.0 - MIT License
- prettytable==3.16.0 - BSD-3-Clause License
- pytest==8.4.2 - MIT License
- pytest-asyncio==1.1.0 - Apache-2.0 License
- pytest-cov==7.0.0 - MIT License
- pytest-mock==3.15.0 - MIT License
- pytest-timeout==2.4.0 - MIT License
- pytest-xdist==3.8.0 - MIT License
- ruff==0.12.12 - MIT License
- safety==3.6.1 - MIT License
- safety-schemas==0.0.14 - MIT License
- tomli==2.2.1 - MIT License
- wcwidth==0.2.13 - MIT License
- flake8==7.3.0 - MIT License
- pycodestyle==2.14.0 - MIT License
- pyflakes==3.4.0 - MIT License
- mccabe==0.7.0 - MIT License
- bandit==1.8.6 - Apache-2.0 License
- pre-commit==4.3.0 - MIT License
- execnet==2.1.1 - MIT License
- coverage==7.10.6 - Apache-2.0 License
- factory-boy==3.3.3 - MIT License
- Faker==37.6.0 - MIT License
- sentencepiece==0.2.1 - Apache-2.0 License

## Optional Dependencies

### TensorFlow (Optional)
- tensorflow-cpu==2.20.0 - Apache-2.0 License
- tensorboard==2.20.0 - Apache-2.0 License
- tensorboard-data-server==0.7.2 - Apache-2.0 License
)




Description:

relysam is a Core Reliability Engineering platform with AI/ML enhancements. Integrates Reliability engineering and analysis core tools with machine learning models for comprehensive analysis.

Built on FastAPI with a unified MLOps pipeline, it combines 10 specialized AI models for reliability engineering.Requires Python 3.12+ with minimum 4GB RAM (8GB recommended for AI features).Uses SQLite database with 133+ specialized tables and views for data storage and management. Key technologies include PyTorch, TensorFlow, scikit-learn, pandas, and numpy for ML/AI functionality.Features dual-layer architecture with active operations and archival storage layers.Primarily offline operation with locally-run AI models and local database storage.Unified MLOps pipeline manages predictive maintenance, anomaly detection, and performance optimization.Main application (app/main.py) provides API endpoints for health checks and model status.Startup script (relysam.sh) performs system validation before launch.Master database contains tables for users, AI model metrics, and reliability assessments.Provides DfR maturity assessment with AI-powered recommendations. Features 10 AI/ML models with 95+ % accuracy metrics.

It is intended to be distributed under GNU GPL v3 license for free software compliance.Includes automated GPL compliance checking and comprehensive monitoring capabilities. Includes pre-commit hooks and automated compliance scripts for GPL requirements.

Built for GNU/Linux systems with maximum offline operation capability. ai models updates, real time features of tools, licenses downloads etc will need online presence. Supports varied industries, but can be customized for user specific industries: aerospace, automotive, electronics, medical devices, energy, manufacturing, telecommunications.Designed for both industrial and research environments.


Other Software Required:

## Dependencies and Licenses

### Core Web Framework & API Infrastructure
- fastapi==0.116.1 - MIT License
- starlette==0.47.3 - BSD-3-Clause License
- uvicorn==0.35.0 - BSD-3-Clause License
- gunicorn==23.0.0 - MIT License
- pydantic==2.9.2 - MIT License
- pydantic-core==2.23.4 - MIT License
- pydantic-settings==2.10.1 - MIT License
- python-multipart==0.0.20 - Apache-2.0 License
- h11==0.16.0 - MIT License
- httptools==0.6.4 - MIT License
- uvloop==0.21.0 - MIT/Apache-2.0 License
- watchfiles==1.1.0 - MIT License
- websockets==15.0.1 - BSD-3-Clause License

### HTTP Client & Networking
- httpx==0.28.1 - BSD-3-Clause License
- httpcore==1.0.9 - BSD-3-Clause License
- aiohttp==3.12.15 - Apache-2.0 License
- aiohappyeyeballs==2.6.1 - PSF License
- aiosignal==1.4.0 - Apache-2.0 License
- requests==2.32.5 - Apache-2.0 License
- urllib3==2.5.0 - MIT License
- certifi==2025.8.3 - MPL-2.0 License
- idna==3.10 - BSD-3-Clause License
- charset-normalizer==3.4.3 - MIT License

### Database & ORM
- SQLAlchemy==2.0.43 - MIT License
- alembic==1.16.5 - MIT License
- greenlet==3.2.4 - MIT License
- psycopg2-binary==2.9.10 - LGPL-3.0 License
- Flask-SQLAlchemy==3.1.1 - BSD-3-Clause License

### Authentication & Security
- Authlib==1.6.3 - BSD-3-Clause License
- cryptography==45.0.7 - Apache-2.0/BSD License
- passlib==1.7.4 - BSD-3-Clause License
- python-jose==3.5.0 - MIT License
- bcrypt==4.3.0 - Apache-2.0 License
- pyasn1==0.6.1 - BSD-2-Clause License
- pyasn1-modules==0.4.2 - BSD-2-Clause License
- rsa==4.9.1 - Apache-2.0 License
- cffi==1.17.1 - MIT License
- pycparser==2.22 - BSD-3-Clause License
- ecdsa==0.19.0 - MIT License

### Data Science & Analytics Foundation
- numpy==2.2.6 - BSD-3-Clause License
- pandas==2.3.2 - BSD-3-Clause License
- scipy==1.16.1 - BSD-3-Clause License
- matplotlib==3.10.6 - PSF License
- seaborn==0.13.2 - BSD-3-Clause License
- plotly==6.3.0 - MIT License
- scikit-learn==1.7.1 - BSD-3-Clause License
- pyarrow==21.0.0 - Apache-2.0 License
- contourpy==1.3.3 - BSD-3-Clause License
- cycler==0.12.1 - BSD-3-Clause License
- fonttools==4.59.2 - MIT License
- kiwisolver==1.4.9 - BSD-3-Clause License

### Reliability Engineering Core
- lifelines==0.30.0 - MIT License
- reliability==0.9.0 - LGPL-3.0 License
- autograd==1.8.0 - MIT License
- autograd-gamma==0.5.0 - MIT License
- statsmodels==0.14.5 - BSD-3-Clause License
- patsy==1.0.1 - BSD-2-Clause License
- formulaic==1.2.0 - MIT License

### Machine Learning & AI Frameworks
- torch==2.8.0+cpu - BSD-3-Clause License
- torchaudio==2.8.0+cpu - BSD-2-Clause License
- torchvision==0.23.0+cpu - BSD-3-Clause License
- torchmetrics==1.8.2 - Apache-2.0 License
- keras==3.11.3 - Apache-2.0 License
- tf-keras==2.15.0 - Apache-2.0 License
- transformers==4.56.0 - Apache-2.0 License
- huggingface-hub==0.34.4 - Apache-2.0 License
- sentence-transformers==5.1.0 - Apache-2.0 License
- tokenizers==0.22.0 - Apache-2.0 License
- safetensors==0.6.2 - Apache-2.0 License
- joblib==1.5.2 - BSD-3-Clause License
- xgboost==3.0.4 - Apache-2.0 License
- lightgbm==4.6.0 - MIT License
- threadpoolctl==3.6.0 - BSD-3-Clause License

### Deep Learning Support (TensorFlow Ecosystem)
- astunparse==1.6.3 - BSD-3-Clause License
- gast==0.6.0 - BSD-3-Clause License
- google-pasta==0.2.0 - Apache-2.0 License
- grpcio==1.74.0 - Apache-2.0 License
- libclang==18.1.1 - Apache-2.0 License
- ml-dtypes==0.5.3 - Apache-2.0 License
- opt-einsum==3.4.0 - MIT License
- protobuf==6.32.0 - BSD-3-Clause License
- termcolor==3.1.0 - MIT License
- wrapt==1.17.3 - BSD-2-Clause License

### PyTorch Lightning & MLOps
- lightning==2.5.4 - Apache-2.0 License
- lightning-utilities==0.15.2 - Apache-2.0 License
- pytorch-lightning==2.5.4 - Apache-2.0 License
- mlflow==3.3.2 - Apache-2.0 License
- mlflow-skinny==3.3.2 - Apache-2.0 License
- mlflow-tracing==3.3.2 - Apache-2.0 License
- databricks-sdk==0.65.0 - Apache-2.0 License
- optree==0.17.0 - Apache-2.0 License

### Natural Language Processing
- spacy==3.8.7 - MIT License
- spacy-legacy==3.0.12 - MIT License
- spacy-loggers==1.0.5 - MIT License
- nltk==3.9.1 - Apache-2.0 License
- thinc==8.3.6 - MIT License
- blis==1.3.0 - MIT License
- catalogue==2.0.10 - MIT License
- cloudpathlib==0.22.0 - MIT License
- confection==0.1.5 - MIT License
- cymem==2.0.11 - MIT License
- langcodes==3.5.0 - MIT License
- language-data==1.3.0 - MIT License
- marisa-trie==1.3.1 - MIT License
- murmurhash==1.0.13 - MIT License
- preshed==3.0.10 - MIT License
- srsly==2.5.1 - MIT License
- typer==0.17.3 - MIT License
- wasabi==1.1.3 - MIT License
- weasel==0.4.1 - MIT License

### File Processing & Document Handling
- Jinja2==3.1.6 - BSD-3-Clause License
- MarkupSafe==3.0.2 - BSD-3-Clause License
- et-xmlfile==2.0.0 - MIT License
- lxml==6.0.1 - BSD-3-Clause License

### Configuration & Serialization
- PyYAML==6.0.2 - MIT License
- toml==0.10.2 - MIT License
- tomlkit==0.13.3 - MIT License
- python-dotenv==1.1.1 - BSD-3-Clause License
- attrs==25.3.0 - MIT License
- msgpack==1.1.1 - Apache-2.0 License
- jsonschema==4.25.1 - MIT License
- jsonschema-specifications==2025.4.1 - MIT License
- referencing==0.36.2 - MIT License
- rpds-py==0.27.1 - MIT License
- ruamel.yaml==0.18.15 - MIT License
- ruamel.yaml.clib==0.2.12 - MIT License

### System Utilities & Monitoring
- psutil==7.0.0 - BSD-3-Clause License
- watchdog==6.0.0 - Apache-2.0 License
- APScheduler==3.11.0 - MIT License
- schedule==1.2.2 - MIT License
- opentelemetry-api==1.36.0 - Apache-2.0 License
- opentelemetry-sdk==1.36.0 - Apache-2.0 License
- opentelemetry-semantic-conventions==0.57b0 - Apache-2.0 License
- prometheus-client==0.22.1 - Apache-2.0 License

### Command Line & User Interface
- click==8.2.1 - BSD-3-Clause License
- rich==14.1.0 - MIT License
- tqdm==4.67.1 - MPL-2.0/MIT License
- colorama==0.4.6 - BSD-3-Clause License
- colorlog==6.9.0 - MIT License
- shellingham==1.5.4 - ISC License
- markdown-it-py==4.0.0 - MIT License
- mdurl==0.1.2 - MIT License
- Pygments==2.19.2 - BSD-2-Clause License

### Async & Concurrency Support
- anyio==4.10.0 - MIT License
- trio==0.30.0 - MIT/Apache-2.0 License
- trio-websocket==0.12.2 - MIT License
- websocket-client==1.8.0 - Apache-2.0 License
- wsproto==1.2.0 - MIT License
- sniffio==1.3.1 - MIT/Apache-2.0 License
- outcome==1.3.0.post0 - MIT/Apache-2.0 License
- sortedcontainers==2.4.0 - Apache-2.0 License

### Caching & Performance
- cachetools==5.5.2 - MIT License
- CacheControl==0.14.3 - Apache-2.0 License
- diskcache==5.6.3 - Apache-2.0 License

### Flask Ecosystem
- Flask==3.1.2 - BSD-3-Clause License
- Werkzeug==3.1.3 - BSD-3-Clause License
- itsdangerous==2.2.0 - BSD-3-Clause License
- blinker==1.9.0 - MIT License

### GraphQL Support
- graphene==3.4.3 - MIT License
- graphql-core==3.2.6 - MIT License
- graphql-relay==3.2.0 - MIT License

### Web Scraping & Automation
- beautifulsoup4==4.13.5 - MIT License
- selenium==4.35.0 - Apache-2.0 License
- webdriver-manager==4.0.2 - Apache-2.0 License
- soupsieve==2.8 - MIT License
- PySocks==1.7.1 - BSD-3-Clause License

### Computer Vision
- pillow==11.3.0 - HPND (PIL License)
- opencv-python-headless==4.12.0.88 - Apache-2.0 License

### Scientific Computing
- sympy==1.14.0 - BSD-3-Clause License
- networkx==3.5 - BSD-3-Clause License
- h5py==3.14.0 - BSD-3-Clause License
- mpmath==1.3.0 - BSD-3-Clause License
- cloudpickle==3.1.1 - BSD-3-Clause License
- mplcursors==0.7 - MIT License

### Logging & Structured Logging
- loguru==0.7.3 - MIT License
- structlog==25.4.0 - MIT/Apache-2.0 License

### Deployment & Build Tools
- GitPython==3.1.45 - BSD-3-Clause License
- gitdb==4.0.12 - BSD-3-Clause License
- smmap==5.0.2 - BSD-3-Clause License
- fsspec==2025.9.0 - BSD-3-Clause License
- docker==7.1.0 - Apache-2.0 License
- setuptools==80.9.0 - MIT License
- wheel==0.45.1 - MIT License
- hatchling==1.27.0 - MIT License
- build==1.3.0 - MIT License
- pyproject-hooks==1.2.0 - MIT License

### Package Management & Metadata
- packaging==25.0 - Apache-2.0/BSD-2-Clause License
- platformdirs==4.4.0 - MIT License
- filelock==3.19.1 - Unlicense
- importlib-metadata==8.7.0 - Apache-2.0 License
- typing-extensions==4.14.1 - PSF License
- zipp==3.23.0 - MIT License
- distlib==0.4.0 - PSF License
- trove-classifiers==2025.8.26.11 - Apache-2.0 License

### Regex & Text Processing
- regex==2025.9.1 - Apache-2.0 License
- pyparsing==3.2.3 - MIT License
- six==1.17.0 - MIT License
- defusedxml==0.7.1 - PSF License

### Time & Date Handling
- python-dateutil==2.9.0.post0 - Apache-2.0/BSD License
- pytz==2025.2 - MIT License
- tzdata==2025.2 - Apache-2.0 License
- tzlocal==5.3.1 - MIT License

### Data Formats & Serialization
- marshmallow==4.0.1 - MIT License
- flatbuffers==25.2.10 - Apache-2.0 License
- frozenlist==1.7.0 - Apache-2.0 License
- multidict==6.6.4 - Apache-2.0 License
- propcache==0.3.2 - Apache-2.0 License
- yarl==1.20.1 - Apache-2.0 License

### Additional Utilities
- tenacity==9.1.2 - Apache-2.0 License
- smart-open==7.3.0.post1 - MIT License
- absl-py==2.3.1 - Apache-2.0 License
- annotated-types==0.7.0 - MIT License
- boolean.py==5.0 - BSD-2-Clause License
- cyclonedx-python-lib==9.1.0 - Apache-2.0 License
- dparse==0.6.4 - MIT License
- hf-xet==1.1.9 - Apache-2.0 License
- interface-meta==1.3.0 - MIT License
- license-expression==30.4.0 - Apache-2.0 License
- packageurl-python==0.17.5 - MIT License
- pbr==7.0.1 - Apache-2.0 License
- py-mini-racer==0.6.0 - ISC License
- py-serializable==2.1.0 - Apache-2.0 License
- ripgrep==14.1.0 - MIT License
- sproto==0.1.4 - BSD-3-Clause License
- sqlparse==0.5.3 - BSD-3-Clause License
- stevedore==5.5.0 - Apache-2.0 License
- typing-inspection==0.4.1 - MIT License
- virtualenv==20.34.0 - MIT License
- narwhals==2.3.0 - MIT License
- nodeenv==1.9.1 - BSD-3-Clause License
- cfgv==3.4.0 - MIT License
- identify==2.6.13 - MIT License

### Development Tools
- black==25.1.0 - MIT License
- google-auth==2.40.3 - Apache-2.0 License
- iniconfig==2.1.0 - MIT License
- isort==6.0.1 - MIT License
- Mako==1.3.10 - MIT License
- Markdown==3.8.2 - BSD-3-Clause License
- mypy==1.17.1 - MIT License
- mypy-extensions==1.1.0 - MIT License
- namex==0.1.0 - Apache-2.0 License
- pathspec==0.12.1 - MPL-2.0 License
- pip==25.2 - MIT License
- pip-api==0.0.34 - Apache-2.0 License
- pip-audit==2.9.0 - Apache-2.0 License
- pip-licenses==5.0.0 - MIT License
- pip-requirements-parser==32.0.1 - MIT License
- pluggy==1.6.0 - MIT License
- prettytable==3.16.0 - BSD-3-Clause License
- pytest==8.4.2 - MIT License
- pytest-asyncio==1.1.0 - Apache-2.0 License
- pytest-cov==7.0.0 - MIT License
- pytest-mock==3.15.0 - MIT License
- pytest-timeout==2.4.0 - MIT License
- pytest-xdist==3.8.0 - MIT License
- ruff==0.12.12 - MIT License
- safety==3.6.1 - MIT License
- safety-schemas==0.0.14 - MIT License
- tomli==2.2.1 - MIT License
- wcwidth==0.2.13 - MIT License
- flake8==7.3.0 - MIT License
- pycodestyle==2.14.0 - MIT License
- pyflakes==3.4.0 - MIT License
- mccabe==0.7.0 - MIT License
- bandit==1.8.6 - Apache-2.0 License
- pre-commit==4.3.0 - MIT License
- execnet==2.1.1 - MIT License
- coverage==7.10.6 - Apache-2.0 License
- factory-boy==3.3.3 - MIT License
- Faker==37.6.0 - MIT License
- sentencepiece==0.2.1 - Apache-2.0 License

## Optional Dependencies

### TensorFlow (Optional)
- tensorflow-cpu==2.20.0 - Apache-2.0 License
- tensorboard==2.20.0 - Apache-2.0 License
- tensorboard-data-server==0.7.2 - Apache-2.0 License



Other Comments:

1. Complete source code: Contains the full relysam application source
2. Database schema: Includes schema.sql and seed_data.sql as plain text SQL files
3. Model training scripts: Contains train_models.py to regenerate .joblib files from source
4. Installation scripts: Includes install.sh and start.sh
5. Documentation: Complete manuals, installation guides, and compliance documentation
6. FSF/GPL compliance: No binary files, only source code and plain text resources

--

License Compatibility Statement

All dependencies listed above have been verified to be compatible with the GNU General Public License v3 (GPL-3.0) or later. This includes:
- Permissive licenses (MIT, BSD, Apache-2.0, etc.) which are GPL-compatible
- LGPL-3.0 licensed components which can be linked to GPL-3.0 code
- Other GPL-compatible licenses

The relysam project maintains 100% GPL v3 compliance with all dependencies.

## Total Package Count

- Total dependencies: 274 packages
- GPL-compatible: 274/274 (100%)
- No proprietary or non-free software dependencies

--

1. Project description: "relysam is a Core Reliability Engineering platform with AI/ML enhancements"
   2. Development status: Active development (version 0.1.0)
   3. Intended audience: Reliability engineers, maintenance professionals, AI/ML researchers
   4. Programming language: Python
   5. Prepared for GNU General Public License v3.0 or later
   6. Compliance verification: Confirm that the distribution includes only source code and excludes any proprietary formats or binary files



Tarball URL:

URL: https://savannah. ... 019_020024.tar.gz


- <_401308>

 

Attached Files

Attached Files
file #57808:  relysam_patch_20251114_to_20251116.patch added by _401308 (477KiB - text/x-patch - atch file between the two distribution versions)
file #57806:  README.md added by _401308 (2.1KiB - text/markdown - README file of @web/static/images folder. )
file #57778:  relysam_distribution_compliance_output.txt added by _401308 (78KiB - text/plain - attcahed relysam compliance report for relysam .tar.gz file. )
file #57762:  pyproject.toml added by _401308 (43KiB - application/toml - pyproject.toml for relysam)
file #57750:  DEPENDENCIES_LICENSES_SUMMARY.md added by _401308 (31KiB - text/markdown - DEPENDENCIES_LICENSES_SUMMARY.md document)
file #57747:  relysam_dependencies_licenses_updated_with_official_GNU_licenses_names.md added by _401308 (27KiB - text/markdown - relysam_dependencies_licenses_updated_with_official_GNU_licenses_names.md)

(Note: upload size limit is set to 4.0MiB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

 

Dependencies

This item does not depend on any other items.

No items depend on this one.

 

Mail Notification Carbon-Copy List

Carbon-Copy List
  • -email is unavailable- added by ineiev (Posted a comment)
  •  

    Votes

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

    History

    Follow 14 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2025-12-04 ineiev Attached File#57916 Removed
    2025-12-04 ineiev Open/ClosedOpen Closed
    2025-12-04 ineiev StatusIn Progress Cancelled
    2025-12-04 _401308 Carbon-CopyRemoved sanjivkapur -
    2025-12-04 _401308 Attached File- Added Screenshot@at@2025-12-04@21-31-27.png, #57916
    2025-11-16 _401308 Attached File- Added relysam_patch_20251114_to_20251116.patch, #57808
    2025-11-15 _401308 Attached File- Added README.md, #57806
    2025-11-13 _401308 Attached File- Added summary_fixes_inconsistent_licenses.txt, #57799
    2025-11-05 _401308 Attached File- Added relysam_distribution_compliance_output.txt, #57778
    2025-11-01 _401308 Attached File- Added pyproject.toml, #57762
    2025-10-28 _401308 Attached File- Added DEPENDENCIES_LICENSES_SUMMARY.md, #57750
    2025-10-27 _401308 Attached File- Added relysam_dependencies_licenses_updated_with_official_GNU_licenses_names.md, #57747
    2025-10-20 ineiev StatusNone In Progress
        Assigned toNone ineiev

    Back to the top

    Powered by Savane 3.16-a7ba.
    Corresponding source code