Follow-up Comment #29, task #16685 (group administration):
[comment #28 comment #28:] > [comment #27 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.nongnu.org/task/index.php?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 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. > _______________________________________________________ Reply to this item at: <https://savannah.nongnu.org/task/?16685> _______________________________________________ Message sent via Savannah https://savannah.nongnu.org/
signature.asc
Description: PGP signature
