I've also been contemplating a FM replacement, and by contemplating I mean coding it.
Here's a first prototype:
http://freshcode.club/
It's currently a lookalike of the late freecode. But a few feature divergences are planned.
Allow me to list a few to indicate where this is going:
- It's a non-commercial project, so no paid advertisements etc.
- No account registration requirement. It uses OpenID (but even that could be disabled).
- Prefer community editing over moderation (though adminstrative features are prepared).
- Automatic release updates are a pre-requisite IMO to get a vibrant FM substitute.
- Content licensing is strictly CC-BY-SA, so another FM shutdown won't impact the whole FLOSS ecosystem.
- Submissions get distributed, multiple frontends feasible.
Foremost I'm looking here for feedback on a possible data exchange protocol. I envisioned something like a JSON feed, as @stefan already had; just a broader data structure containg project info and separate release/version data. Was thinking about a JSONified ATOM structure perhaps.
freshmeat.club and freecode.club are currently aliases to freshcode.club, but obviously I'd like to share them out for setting up mirrors or preferrably alternative implementations (@stefan).
Greetings!
P.S.: @Lothar, thumbs up on the effort here to get the ball rolling.
