I had a report for AI slop today. 1m LOC in 3 months. How do you even modify and distribute that? I do not think we had a rule against it.

IMHO if we allow, the community gets drowned out by AI vomit and it is harder to see handcrafted loved projects that are easy to modify and distribute.

My mind is to ban it to preserve open source.

Are folk in agreememt with this line? Would love to hear your thoughts.

  • Captain Beyond@linkage.ds8.zone
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    12 hours ago

    To be frank, you appear to be set on pre-punishing a solo developer for sharing a family-and-friends project based on a rather cursory examination. Doesn’t that run somewhat contrary to the spirit of FOSS?

    “The spirit of FOSS” entails the users having the four freedoms (to use, modify, share verbatim copies, and share modified copies) of the source code. You’ve suggested that this project is primarily binary-only with only intermittent source code dumps, meaning that until these binaries have corresponding source code they are neither FOSS in letter nor in spirit, and thus inappropriate for this community as well as for !aials@lemmy.ml, which is for AI-assisted FOSS. Given that you’ve suggested you will only provide source code for “major revisions” this suggests that “minor versions” never will be FOSS. Effectively you’re promoting a proprietary product here that may or may not have intermittent source code snapshots.

    Furthermore, the fact that you seem to consider it a great effort to “sanitize” the source code for public release suggests that what is being shared with the public is not in fact the corresponding source code to the binaries you upload.

    As you pointed out the MIT license does allow you to make proprietary derivatives, so nothing you’ve done is “wrong” or illegal. That doesn’t make it not proprietary.

    Edit: I’m a different person than the admin who removed your post. I’m not suggesting your project is slop or that the effort you’ve put into it is inconsequential. I’m just saying that binaries without source code are not FOSS even if you publish occasional snapshots of selected releases. I’d probably be more favorable to this approach if there were FOSS builds from the source code snapshots, or maybe if only the FOSS releases were on github and the proprietary ones somewhere else - but that’s probably asking a bit too much.

    • Spite_By_Design_LLC@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      10 hours ago

      The current 32.71 snapshot includes both source code and APKs compiled there from. I take your point that I should make that correspondence clearer, along with which future interim releases might have no public source.

      At present, under the definitions you’ve provided, the current release meets all four FOSS criteria.

      As for “sanitising”, I mean removing private configuration, credentials and development files, not stripping out functional source code. That’s literally all I meant.

      As I’ve said, development happens in my private Forgejo repository, so preparing a public snapshot involves a little housekeeping. I prefer to keep the public release clean, and .gitignore only does part of that job.

      I appreciate you being civil. The other points I raised are worth serious community consideration (especially what constitutes “slop”, AI disclosure, and the unintended consequences of penalising transparency rather than judging projects on their merits), but I have said my piece.